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:
The service to kill on my phone is called bluetooth-rfkill-event.service
sorry, i dont read all thread, but with same problem restarting bluebinder helps me
devel-su
systemctl restart bluebinder
I do not exactly know at which version it changed.
But on 3.2 a
devel-su systemctl restart bluetooth bluebinder
works.
On 4.0 I guess then a
devel-su restart bluetooth bluetooth-rfkill-event
should do the trick as well?
on 4.0 i already has this bag, and restarting bluebinder works well
Yes.
Checked on different devices.
bluebinder is only present on devices with Android runtime installed
So something above is true 
–
maybe then?
devel-su restart bluetooth bluetooth-rfkill-event bluebinder
Could someone at Jolla add this bluetooth reset to the Jolla Utilities? That would be super useful.
And an Android on/off switch for the events view? Thank you ;-p
I think the best way is to make sure it works the right way without ever having the need to restart the service in the first place.
Yes I have this problem addition to loosing wlan and mobile network regularly. Irritating problem when you rely being reachable but the phone has dropped silently out of all connections.
Are there users with an Xperia 10 experiencing the same issue or is it restricted to X, XA2 ?
I may have a similar problem with Xperia 10. I have just discovered this thread and actually thought my issue was linked to the “Situations” application.
During the night, the situations application turns the ‘flight mode on’ on my phone, and in the morning, maybe in 20-25% of cases, when the application puts the flight mode off, bluetooth is not back and is impossible to turn on. I am using the application for ages and this is quite recent (some months…) even though I cannot remember when and which SFOS or Situations update triggered it.
When I have the problem, I usually deactivate the ‘situations’ application and reboot. Then I reactivate “situations” and all is fine for some days. The issue never happens during the day even though I am usually connected to a pebble watch all day long.
I can try to restart bluetooth services next time it happens to see if it solves my issue.
Hi.
I’ve been experiencing this problem lately on an Xperia X with Sailfish 4.0.1.
In my case, I can turn BT on, but only once. When I turn it off I get the following relevant lines in my logs:
mar 19 19:29:48 SailfishX bluetooth_rfkill_event[737]: main(bluetooth_rfkill_event.c:1259): BT power driver blocked
mar 19 19:29:50 SailfishX bluetooth_rfkill_event[737]: free_hci(bluetooth_rfkill_event.c:906): killing hciattach failed
mar 19 19:29:50 SailfishX bluetooth_rfkill_event[737]: main(bluetooth_rfkill_event.c:1261): BT disabled
The icon shows BT as disabled but the hciattach proccess is still alive…preventing every new attempt to turn BT on again from working.
I hope this is fixed in the next upstream release.
Best regards.
The solutions using the command line above work to restart the bluetooth and make it work again. There is also this thread that has a solution using the sailfish utilities app Add Bluetooth reset/restart to the Sailfish Utilities app
…does not work for me and my XperiaX in this case.
Another observation: After turning on BT and searching for devices it shows my Sennheiser MB Pro 2 in the list of known devices. But the visibility of the Xperia is OFF. A known device should connect anyway but it doesn’t. I cannot switch the visibility on – not even for 15 minutes. Every now and then when I switch on BT the visibility is ON. Then the headset connects immediately and works without a problem – until it disconnects once, then it cannot reconnect.
The BT on my phone, Xperia X, is always set on Visibility Off and the headset always connects automatically. But the phone is on 4.0 and not 3.4 as the OP title. It might make a difference.
Same here … a little frustrating
Yeah, and it’s even more frustrating when:
So we now need to reboot (or find the good command lines) each time we need to use Bluetooth or record a call, a great way to enter the 4th generation 
I noticed that to on my only a few days old flash of SFX 4.0.1 on Xperia 10. I tried restart first and it worked.
I just had to do the restart network in SF Utilities twice to get my BT working again.
Then you are the lucky one ;-).
BT doesn’t worke here anymore right now.