[3.4.0 onwards] Bluetooth turning on doesn't work

tom.i · 20 October 2020 12:10

REPRODUCIBILITY (% or how often): 60%
BUILD ID = OS VERSION (Settings > About product): 3.4.0.24
HARDWARE (Jolla1, Tablet, XA2,…): Xperia XA2
UI LANGUAGE: Czech
REGRESSION: (compared to previous public release: Yes, No, ?): -

DESCRIPTION:

Turning Bluetooth on doesn’t work in UI.

PRECONDITIONS:

STEPS TO REPRODUCE:

Settings → Bluetooth
tap to turn it on.

EXPECTED RESULT:

Turning Bluetooth on.

ACTUAL RESULT:

Bluetooth icon still blinking.

ADDITIONAL INFORMATION:

Restarting phone didn’t help everytime so I’ve tried to restart bluetooth.service via systemctl restart bluetooth.service and it helped and BT started to work.
I’m going to watch journalctl after it’ll be back, or can I see some log why BT isn’t working sometimes?

rulli · 24 October 2020 17:46

Same happened to me once with Xperia XA2 with latest 3.4.0.24. I wasn’t able to turn bluetooth on neither from Settings->Bluetooth nor from top menu Bluetooh button. Luckily reboot helped. Next time It happens, I’ll check Journal as well.

Quentin-ctrL · 16 November 2020 09:26

Same issue on XA2

[root@XperiaXA2 nemo]# systemctl restart bluetooth.service
[root@XperiaXA2 nemo]# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-11-16 10:24:10 CET; 2s ago
     Docs: man:bluetoothd(8)
 Main PID: 13761 (bluetoothd)
   Status: "Running"
   Memory: 560.0K
      CPU: 45ms
   CGroup: /system.slice/bluetooth.service
           └─13761 /usr/libexec/bluetooth/bluetoothd -n

Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: Failed to open RFKILL control device
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: Bluetooth management interface 1.10 initialized
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: bluetoothd[13761]: kernel lacks bnep-protocol support
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: bluetoothd[13761]: System does not support network plugin
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: bluetoothd[13761]: Failed to open RFKILL control device
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: bluetoothd[13761]: Bluetooth management interface 1.10 initialized
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: bluetoothd[13761]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSink
Nov 16 10:24:10 XperiaXA2 bluetoothd[13761]: bluetoothd[13761]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSink

rulli · 11 February 2021 07:34

Still same hapenning with Xperia XA2 and Koli 4.0.1.45. Only restarting bluetooth systemd service helps.

If trying bluetooth activation from top menu, nothing comes to journal.

If trying from Settings->Bluetooth some logs show in journal, icon blinks but bluetooth still doesn’t work:

Feb 11 09:18:11 Sailfish dbus-daemon[4474]: dbus-daemon[4474]: [session uid=100000 pid=4474] Activating service name='com.jolla.Bluetooth' requested by ':1.1775' (uid=100000 pid=28294 comm="booster [silica-qt5]                             ")
Feb 11 09:18:12 Sailfish dbus-daemon[4474]: dbus-daemon[4474]: [session uid=100000 pid=4474] Successfully activated service 'com.jolla.Bluetooth'
Feb 11 09:18:12 Sailfish lipstick-bluetooth-ui[15681]: [D] unknown:0 - Using Wayland-EGL
...
Feb 11 09:21:45 Sailfish lipstick-bluetooth-ui[15681]: [D] onTriggered:78 - lipstick-bluetooth-ui: exiting...

And finally when running systemctl restart bluetooth.service, everything works again. I can provide journal if needed.

s_mario · 11 February 2021 20:56

I discovered today the same problem on Jolla C and Xperia X (both with Koli 4.0.1.48). On XperiaX i was able to activate BT once after reboot and never again when deactivated it. On Jolla C i get no BT icon in the statusbar.

Output from Jolla C
> [root@Sailfish nemo]# systemctl status bluetooth.service
> ● bluetooth.service - Bluetooth service
> Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
> Active: active (running) since Thu 2021-02-11 20:59:42 CET; 4min 9s ago
> Docs: man:bluetoothd(8)
> Main PID: 7742 (bluetoothd)
> Status: “Running”
> Memory: 368.0K
> CGroup: /system.slice/bluetooth.service
> └─7742 /usr/libexec/bluetooth/bluetoothd -n
>
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: bluetoothd[7742]: Bluetooth management interface 1.3 initialized
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: Bluetooth management interface 1.3 initialized
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: bluetoothd[7742]: Failed to read advertising features: Unknown Command (0x
> 01)
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: Failed to read advertising features: Unknown Comma
> nd (0x01)
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: hci0 Load Connection Parameters failed: Unknown Co
> mmand (0x01)
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: bluetoothd[7742]: hci0 Load Connection Parameters failed: Unknown Command
> (0x01)
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: bluetoothd[7742]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2
> DPSource
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2DPSource
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: bluetoothd[7742]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2
> DPSink
> Feb 11 20:59:42 Sailfish bluetoothd[7742]: Endpoint registered: sender=:1.44 path=/MediaEndpoint/A2DPSink

Output from XperiaX
> [root@Sailfish nemo]# systemctl status bluetooth.service
> ● bluetooth.service - Bluetooth service
> Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
> Active: active (running) since Thu 2021-02-11 21:54:42 CET; 1s ago
> Docs: man:bluetoothd(8)
> Main PID: 14945 (bluetoothd)
> Status: “Running”
> Memory: 400.0K
> CGroup: /system.slice/bluetooth.service
> └─14945 /usr/libexec/bluetooth/bluetoothd -n
>
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: Unknown key PairableTimeout for group General in
> /etc/bluetooth/main.conf
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: bluetoothd[14945]: Unknown key Channels for group GATT in /etc/bluetooth/
> main.conf
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: Unknown key Channels for group GATT in /etc/bluet
> ooth/main.conf
> Feb 11 21:54:42 Sailfish systemd[1]: Started Bluetooth service.
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: bluetoothd[14945]: Starting SDP server
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: Starting SDP server
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: bluetoothd[14945]: Failed to open RFKILL control device
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: Failed to open RFKILL control device
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: bluetoothd[14945]: Bluetooth management interface 1.3 initialized
> Feb 11 21:54:42 Sailfish bluetoothd[14945]: Bluetooth management interface 1.3 initialized

gafry · 19 February 2021 10:39

I’ve got the same issue with mine Xperia X when upgraded to this version (no problems before in 3.4.x).

Restarting the services doesn’t help and restarting the device also doesn’t help.

I see the same error in the bluetooth.service log: Failed to open RFKILL control device … , but not sure how to troubleshoot further.

Did you have any luck fixing it?

tom.i · 19 February 2021 11:02

Just restarting systemd service helped…

gafry · 19 February 2021 11:55

I’ve tried systemctl restart systemd , but does not seem to be the correct command.

Could you share the actual command?

tom.i · 19 February 2021 12:07

In my original post, just to read more deeply

lhodas · 19 February 2021 12:39

In my case, the Xperia X dual SIM, it looks like this

when BT is off

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: active (running) since Thu 2021-02-18 15:44:56 CET; 21h ago
     Docs: man:bluetoothd(8)
 Main PID: 777 (bluetoothd)
   Status: "Running"
   Memory: 1.3M
   CGroup: /system.slice/bluetooth.service
           └─777 /usr/libexec/bluetooth/bluetoothd -n

feb 19 13:19:15 Sailfish bluetoothd[777]: bluetoothd[777]: Loading LTKs timed out for hci0
feb 19 13:19:15 Sailfish bluetoothd[777]: Loading LTKs timed out for hci0
feb 19 13:24:00 Sailfish bluetoothd[777]: bluetoothd[777]: Failed to set mode: Not Powered (0x0f)
feb 19 13:24:00 Sailfish bluetoothd[777]: bluetoothd[777]: Failed to read advertising features: Unknown Command (0x01)
feb 19 13:24:00 Sailfish bluetoothd[777]: bluetoothd[777]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
feb 19 13:24:00 Sailfish bluetoothd[777]: bluetoothd[777]: Failed to get connections: Not Powered (0x0f)
feb 19 13:24:00 Sailfish bluetoothd[777]: Failed to set mode: Not Powered (0x0f)
feb 19 13:24:00 Sailfish bluetoothd[777]: Failed to read advertising features: Unknown Command (0x01)
feb 19 13:24:00 Sailfish bluetoothd[777]: hci0 Load Connection Parameters failed: Unknown Command (0x01)
feb 19 13:24:00 Sailfish bluetoothd[777]: Failed to get connections: Not Powered (0x0f)

when BT is on

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: active (running) since Thu 2021-02-18 15:44:56 CET; 21h ago
     Docs: man:bluetoothd(8)
 Main PID: 777 (bluetoothd)
   Status: "Running"
   Memory: 1.3M
   CGroup: /system.slice/bluetooth.service
           └─777 /usr/libexec/bluetooth/bluetoothd -n

feb 19 13:19:08 Sailfish bluetoothd[777]: bluetoothd[777]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource
feb 19 13:19:08 Sailfish bluetoothd[777]: bluetoothd[777]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink
feb 19 13:19:08 Sailfish bluetoothd[777]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource
feb 19 13:19:08 Sailfish bluetoothd[777]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink
feb 19 13:19:12 Sailfish bluetoothd[777]: bluetoothd[777]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource
feb 19 13:19:12 Sailfish bluetoothd[777]: bluetoothd[777]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink
feb 19 13:19:12 Sailfish bluetoothd[777]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource
feb 19 13:19:12 Sailfish bluetoothd[777]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink
feb 19 13:19:15 Sailfish bluetoothd[777]: bluetoothd[777]: Loading LTKs timed out for hci0
feb 19 13:19:15 Sailfish bluetoothd[777]: Loading LTKs timed out for hci0

Sending contacts from the People app to another device (Gemini PDA) via BT works.
Sending a file from the File Browser to the same device does not work.

gafry · 19 February 2021 12:45

I’ve tried that also, but thought that you meant something more stronger/harder, because I reboot doesn’t help either.

It looks like I’m enjoying another issue with the same effects…

jiit · 19 February 2021 14:03

Thank you all for the detailed info about this problem. We have a bug report now.

incognito · 20 February 2021 10:06

Came here to see if somebody else is experiencing this after Koli update, was not disappointed

Restarting the BT service on my Xperia X doesn’t work (same RFKILL messages) but restarting the device makes BT work once; after a disconnect or toggling BT on/off it gets stuck and won’t budge until restart.

sgleo87 · 20 February 2021 18:25

I’m having the exact same problem after upgrading to SFOS 4 (Koli). Bluetooth works fine once, then gets stuck after trying to enable it a second time. Only rebooting resolves the issue. Using an Xperia X and everything worked as ist should before the upgrade.

Helly2 · 22 February 2021 08:52

I also have the exactly same problem in two XPERIA X (single and double SIM). Bluetooth works once. After disconnecting the headphones they cannot be reconnected. Only rebooting helps – but also not always. The headphones work perfectly with other devices.

calimarno · 22 February 2021 09:14

I have noticed the same problem with my Xpreria X. Bluetooth used to work like a charm, but now only once and reboot needed to (maybe) have it work again. Got headphones with a cable as a “workaround”.

sigurg · 22 February 2021 14:38

Restarting the bluetooth service (bluez) is only half the solution and for me does not fix the issue when it occurs (on XA2). I also need to restart bluebinder.service for bluetooth to work again.

sgleo87 · 24 February 2021 16:22

So I found out is has to do something with bluetooth.service as well as bluetooth-rfkill-event.service. After bluetooth fails to work when trying to enable it the second time, I did the following:

Killed the bluetooth-rfkill.service
Restarted bluetooth.service
Restarted bluetooth-rfkill.service
Turned on bluetooth via Settings as usual. And the it works again (for one time :)).

Maximilian1st · 2 March 2021 11:02

The service to kill on my phone is called bluetooth-rfkill-event.service

sashikknox · 2 March 2021 22:17

sorry, i dont read all thread, but with same problem restarting bluebinder helps me

devel-su
systemctl restart bluebinder