Bluetooth changes are in the changelog though.
Did not solve the problem in my XA2 (H4113). My XA2 still require both “systemctl restart bluetooth” and “systemctl restart bluebinder” for bluetooth to work on my XA2 - please remove the solved flag.
1 Like
On my xa2+ it was always enough to restart bluetooth twice via Settings-Utilities.
I hope none of my friends and family will find out, the rediculous workaround we need to get our phone working.
3 Likes
this helps. thank you
Hi
After last update .18 bluetooth stopped working.
Any idea?
Thanks
I second this: situation is better(?) with the update but problem is not slved…
what I tend to see is trying to switch on the BT and the restarting BT subsystem from Settings/SFOS Utility solved issue more than not…
Yep, just realised this myself while trying to send a pic to my PC. I had to restart BT using Sailfish-Utilities. My device is an Xperia 10 II.
yet-another observation is restarting BT from utilities will be more successful if WiFi is OFF
1 Like
XA2 here, 4.5.0.18 - few restarts from utilities and it works, but thats not solved.
4 Likes
Xperia III, 4.5.0.18 - two distinct cases here:
- Cars: I must ALWAYS restart BT once after reboot from (SFOS utilities does it). Might relate to specific BT in bmw cars (same on older F11 and newer i3). After BT restart on phone, re/connection is fast, everything works -phone, media, etc.
Sometimes I noticed some lag to switch to voice on 1st call when BT media was streaming audio to car (music stopped but heard the 1st ‘hello’ of the callee from my pocket, then sound was routed in car’s audio).
Constant : no 1st restart, no connection. - most of my BT devices (headsets: plantronics and jabra; speakers: jbl, sony, b&o ) - work as expected , with or without BT restart.
Confirming XA2 Plus,
The bug disappeared with 4.5.0.18
and reappeared again on 4.5.0.19.
Console is the only way to make bluetooth work.
2 Likes
I cannot confirm that, it always existed on my XA2+ since 4.5.0.16
As mentioned above, there’s another way to activate Bluetooth:
- Open Settings
- Scroll down to and open Utilities (needs to be installed from Jolla store)
- Press button
Restarton sectionBluetooth
Sometimes, it’s required to go through this procedure twice
2 Likes
@jollajo Thank you for the notice.
Before commenting here I already did try reboot with and without wlan on, with and without mobile data on, utilities restart bluetooth, all this several times (XA2+ dual sim).
Inspired by you I did some more testing, after reboot bluetooth does not turn on, tapping bluetooth in the upper menu two times and then utilities restart bletooth worked, bluetooth turned on.
I had the same behaviour on my XA2 H3113, OS Version 4.5.0.19, restarting bluetooth via Settings-Utilities didn´t help. After a reboot I checked the bindings and unblocked hci0
# rfkill list
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
# rfkill unblock 0
# systemctl restart bluetooth.service
Now it works well, even after a reboot.
I still have this issue on 4.5.0.19.
This is what happens when I unsuccesfully! try to activate Bluetooth after a cold boot:
Apr 02 21:49:28 XperiaXA2-DualSIM bluebinder[3219]: Turning bluetooth on
Apr 02 21:49:28 XperiaXA2-DualSIM kernel: bt_ioctl: BT_CMD_PWR_CTRL pwr_cntrl:0
Apr 02 21:49:28 XperiaXA2-DualSIM kernel: bt_ioctl: BT chip state is already :0 no change d
Apr 02 21:49:28 XperiaXA2-DualSIM kernel: bt_ioctl: BT_CMD_PWR_CTRL pwr_cntrl:1
Apr 02 21:49:28 XperiaXA2-DualSIM connmand[3048]: Bluetooth device /org/bluez/hci0 not enabled
Apr 02 21:49:29 XperiaXA2-DualSIM bluebinder[3219]: Bluetooth binder initialized successfully
Then
> devel-su
> systemctl restart bluetooth && sleep 5 && systemctl restart bluebinder
fixes it.
> systemctl status bluetooth bluebinder
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2023-04-02 22:01:30 EEST; 2min 37s ago
Docs: man:bluetoothd(8)
Main PID: 6984 (bluetoothd)
Status: "Running"
Memory: 640.0K
CGroup: /system.slice/bluetooth.service
└─6984 /usr/libexec/bluetooth/bluetoothd -n
Apr 02 22:01:36 XperiaXA2-DualSIM bluetoothd[6984]: bluetoothd[6984]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc
Apr 02 22:01:36 XperiaXA2-DualSIM bluetoothd[6984]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink/sbc
Apr 02 22:01:36 XperiaXA2-DualSIM bluetoothd[6984]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc
Apr 02 22:01:36 XperiaXA2-DualSIM bluetoothd[6984]: bluetoothd[6984]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource/sbc
Apr 02 22:02:13 XperiaXA2-DualSIM bluetoothd[6984]: bluetoothd[6984]: profiles/audio/avctp.c:uinput_create() Can't open input device: No such file or directory (2)
Apr 02 22:02:13 XperiaXA2-DualSIM bluetoothd[6984]: bluetoothd[6984]: profiles/audio/avctp.c:init_uinput() AVRCP: failed to init uinput for JBL GO 2
Apr 02 22:02:13 XperiaXA2-DualSIM bluetoothd[6984]: profiles/audio/avctp.c:uinput_create() Can't open input device: No such file or directory (
2)
Apr 02 22:02:13 XperiaXA2-DualSIM bluetoothd[6984]: profiles/audio/avctp.c:init_uinput() AVRCP: failed to init uinput for JBL GO 2
Apr 02 22:02:13 XperiaXA2-DualSIM bluetoothd[6984]: bluetoothd[6984]: /org/bluez/hci0/dev_E8_D0_3C_E2_45_46/sep1/fd0: fd(28) ready
Apr 02 22:02:13 XperiaXA2-DualSIM bluetoothd[6984]: /org/bluez/hci0/dev_E8_D0_3C_E2_45_46/sep1/fd0: fd(28) ready
● bluebinder.service - Simple proxy for using android binder based bluetooth through vhci.
Loaded: loaded (/usr/lib/systemd/system/bluebinder.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2023-04-02 22:01:36 EEST; 2min 30s ago
Process: 7090 ExecStartPost=/usr/bin/droid/bluebinder_post.sh (code=exited, status=0/SUCCESS)
Process: 7054 ExecStartPre=/usr/bin/droid/bluebinder_wait.sh (code=exited, status=0/SUCCESS)
Main PID: 7065 (bluebinder)
Memory: 432.0K
CGroup: /system.slice/bluebinder.service
└─7065 /usr/sbin/bluebinder
Apr 02 22:01:35 XperiaXA2-DualSIM systemd[1]: Starting Simple proxy for using android binder based bluetooth through vhci....
Apr 02 22:01:35 XperiaXA2-DualSIM bluebinder_wait.sh[7054]: Bluetooth service running
Apr 02 22:01:35 XperiaXA2-DualSIM bluebinder[7065]: Own hci index: 2
Apr 02 22:01:35 XperiaXA2-DualSIM bluebinder[7065]: delaying writing host command to controller until bt is up
Apr 02 22:01:35 XperiaXA2-DualSIM bluebinder[7065]: Turning bluetooth on
Apr 02 22:01:36 XperiaXA2-DualSIM bluebinder[7065]: Got BLUEBINDER_LOCAL_FEATURES_MASK 0x0
Apr 02 22:01:36 XperiaXA2-DualSIM bluebinder[7065]: Bluetooth binder initialized successfully
Apr 02 22:01:36 XperiaXA2-DualSIM bluebinder[7065]: Successfully initialized vhci bluetooth
Apr 02 22:01:36 XperiaXA2-DualSIM systemd[1]: Started Simple proxy for using android binder based bluetooth through vhci..
> rfkill list
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
rfkill output is the same before & after the restart.
Added to internal tracker.
Kind request to readers/commenters: These kind of issues are highly specific to device type. This bug report is about Xperia XA2 Plus. Adding reports of working / not working devices on any other type of device only adds noise and makes finding the useful information more difficult. On the other hand, if you have logs or other useful information on XA2 Plus, please do share those.
3 Likes
OK. I have this issue (100% reproducible) on a “normal” XA2 DualSIM.
Should I make a new bug report post here?
I believe all XA2s share the same hardware platform, so probably this bug is common to all of them.
That is probably the case. My first assumption was that this bug was only on XA2 Plus, as the “normal” XA2 is much more common and the first bug report came from the plus version. But if @ohnonot indeed has 100% identical behaviour on normal XA2, I think it’s safe to assume it’s the same bug.
2 Likes
For me it’s pure XA2 (single SIM).
1 Like