[3.4.0 onwards] Bluetooth turning on doesn't work

rozgwi · 7 May 2021 11:45

I made the following observation on Koli (4.0.1.48, Xperia X):

Starting point:
Bluetooth turns on normally on a freshly booted phone.
Connecting to a Bluetooth device works, automatically as well.

Turn BT off
Turn BT on again - takes longer than usual (a few seconds)
Connecting is not working anymore
Turn BT off
Try turning it on: Won’t work. Top Menu button stays gray, radio button in setting keeps blinking.
Reboot the phone: Bluetooth is turned on automatically

The cycle repeats…

Does anyone have a hint on how to collect the right logs?

edit:
@jovirkku: I’m being blunt and ping you directly. Could you comment on this?
Can we do anything to help debugging?

Helly2 · 8 May 2021 10:26

I experience exactly the same pattern! Thank you for sharing. The only thing that miraculously changed is that it works now as if my XPERIA X had reprogrammed itself. In the beginning it would only connect occasionally. Since a few weeks it suddenly connects every day and I only have to restart it if I disconnect my headset.

jojo · 9 May 2021 15:03

I can testify that I have the exact same bug ! (on the same phone)
My current solution remains rebooting the phone every time… I tried this patch but it did not change anything…

jovirkku · 10 May 2021 08:32

Hmmm. You might want to start with our shotgun script that collects many kinds of logs from your phone.
Guidelines here: https://jolla.zendesk.com/hc/en-us/articles/360013910599

Naturally, it should be run after observing the problem again.

If you want to keep your logs in privacy, file a ticket at Jolla customer support at https://jolla.zendesk.com/hc/en-us/requests/new. Attach your log package there, please.

Sthocs · 10 May 2021 09:41

Oh wait that’s interesting @jovirkku. Does that means that no one at Jolla has experienced the issue and thus no specific fix is in the pipe?
Also, a reflash could potentially fix it then?

That’s the kind of info we’d love to have proactively, in order to try to provide you better logs and decide whether we should reflash our phones or not.

I still hope that 4.1 will fix it

s_mario · 17 May 2021 17:56

After the update to 4.1.0.23, the Bluetooth of my XperiaX also lives again after a restart and no longer after it has been deactivated.

Now the magic line for me to reactivate it is:
systemctl restart bluetooth-rfkill-event.service

Strangely enough, reactivation does not work here with the extended sailfish-utilities (from nephros) and only via the command line.
The problem seems to have been around for a while, as I’ve read here:
Sailfish OS for the Samsung Galaxy S2 (i9100)

rozgwi · 14 May 2021 11:51

Brilliant! Thanks a lot!

I’ll take the script to the ‘shooting range’ as soon as I find some time.
In the meantime: have a nice weekend @jovirkku

deloptes · 17 May 2021 00:01

it doesn’t work in 4.1.0.23

[root@XperiaX RPMS]# systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-05-17 01:54:02 CEST; 6min ago
     Docs: man:bluetoothd(8)
 Main PID: 6436 (bluetoothd)
   Status: "Running"
   Memory: 332.0K
   CGroup: /system.slice/bluetooth.service
           └─6436 /usr/libexec/bluetooth/bluetoothd -n

May 17 01:54:02 XperiaX systemd[1]: Starting Bluetooth service...
May 17 01:54:02 XperiaX bluetoothd[6436]: bluetoothd[6436]: Bluetooth daemon 5.54
May 17 01:54:02 XperiaX bluetoothd[6436]: Bluetooth daemon 5.54
May 17 01:54:02 XperiaX systemd[1]: Started Bluetooth service.
May 17 01:54:02 XperiaX bluetoothd[6436]: bluetoothd[6436]: Starting SDP server
May 17 01:54:02 XperiaX bluetoothd[6436]: Starting SDP server
May 17 01:54:02 XperiaX bluetoothd[6436]: bluetoothd[6436]: Failed to open RFKILL control device
May 17 01:54:02 XperiaX bluetoothd[6436]: bluetoothd[6436]: Bluetooth management interface 1.3 initialized

May 17 01:54:02 XperiaX bluetoothd[6436]: Failed to open RFKILL control device

May 17 01:54:02 XperiaX bluetoothd[6436]: Bluetooth management interface 1.3 initialized

deloptes · 21 May 2021 06:19

It seems to me in 4.1.0.23 hciattach cannot be deactivated.

When you execute killall -TERM hciattach or killall -KILL hciattach should be working

lhodas · 28 May 2021 08:16

The same in 4.1.0.24

I’m frustrated with that, until version 3.4 BT worked flawlessly, even pairing in a Mazda 3, now it’s completely useless! Jolla boys, what did you do with that?

jovirkku · 28 May 2021 12:06

I can easily reproduce the issue by following your steps (on 4.1.0.24). This happens on Xperia X only, to me, while Xperia XA2 and Xperia 10 II work almost flawlessly (*). I have filed an internal bug about this problem on Xperia X. This is not a promise on getting it fixed.

(*) Automatic reconnection at step 3 may fail but the manual one succeeds on XA2 and 10 II.

filip.k · 28 May 2021 19:29

@jovirkku Thanks! I very much appreciate your commitment in forum in general (not just this bug)! I’m sure I’m not alone ;).

DrDweeb · 29 May 2021 01:34

I’ll look forward to the fix

h.berd · 2 June 2021 20:01

Can anyone please write a patch which restarts bluetooth?

I’m a Xperia X user and had some hope till now, that kvarken will fix this nasty bug…

nephros · 2 June 2021 22:26

you rang?

https://coderus.openrepos.net/pm2/project/patch-restart-bt-with-network

github.com/sailfishos/sailfish-utilities

WIP: Add option to restart Bluetooth subsystem

sailfishos:master ← nephros:bt-restart

opened 11:55AM - 14 Mar 21 UTC

nephros

+54 -7

This adds a new option in the Utilities Menu to restart the Bluetooth related se…rvices, dealing with [this feature request](https://forum.sailfishos.org/t/add-bluetooth-reset-restart-to-the-sailfish-utilities-app/5407) Please review and comment: - Are the calls to systemctl in restart_bluetooth.sh correct? - There are two translation strings, one for the name "Bluetooth" and the description of the option itself.

h.berd · 3 June 2021 20:06

Thank you very much @nephros ! But my phone is updated to 4.1 (Kvarken) and your patch seems to be only workling till Koli or at least patchmanager tells me that.

Can you please update the patch for 4.1 compatibility?

nephros · 4 June 2021 09:12

Last I checked the patchmanager backend allows only to specify compatability up to Koli.

That doesn’t mean the patch does not work.

Please try it using PM in dev mode.

Alternatively, you can install an RPM from here, which will give you the bluetooth-restart function separately from network. Do uninstall the patch if you have it before installing this:

laustela · 6 June 2021 12:16

This happens on Xperia X only, to me, while Xperia XA2 and Xperia 10 II work almost flawlessly.
Automatic reconnection at step 3 may fail but the manual one succeeds on XA2 and 10 II.

I just had this happen on my new 10 II yesterday, ie. Bluetooth would not turn on. Just like on my X, I was watching YouTube in the browser, and attempting to skip ahead in the video left it loading. From my earlier experience I’ve learnt that this usually means that the Bluetooth (to my headphones) is messed up and I need to turn it off and on again. And I wasn’t able to turn it on again (until I rebooted).

Later in the evening it also happened once again on my Xperia X; running ‘systemctl restart bluetooth-rfkill-event.service’ did fix it there (first time testing it now) so I’ll surely keep that command at hand now…

klemolap · 11 June 2021 07:18

I am using Xperia 10 with SFOS 4.1.0.24 and yesterday this happened for the first time. The phone uptime was about 5 or 6 days and I could not start BT to connect to my car. I tried to start BT several times from the top menu with no success. Restarting network connections did not help. Rebooting the device fixed the problem. My phone usage is moderate: some calls, whatsapp msgs & some calls, emails, browser (duckduckgo), sportstracker.