Bluetooth not starting, nor configurable

Somehow I screwed the bluetooth setu, I’m afraid.

So far it used to work jus fine. So, I wanted to connect a bluetooth keyboard (Hama Travel 450), which I already had connected to the other Andoird mobile just fine.

It did show up in the list of detected devices, it connected once I tapped on it, but the keyboard wouldn’t work.

So I decided to leave it away, turned off the keyboard, and rebooted

After reboot, when I go to the Bluetooth setup page, the option “Bluetooth” just blinks, but apart from that the page remains empty. After another reboot, I again went to that page, it very briefly displayed devices before it again went blank (except “Bleutooth” and its tiny button in front of it blinking

So, is there a way to reset the Bluetooth setting? Or what else could I do to get it back?

thx!

p6

Have you tried “Utilities” / Restart Bluetooth and looking at the logfiles?

1 Like

yes, I did restart a) the phone itself and b) using the Restart in Utilities - no change

Not fully familiar with the log files, though. Which one(s) should I check?

Can you just please try a bit harder to read all the threads about issues you experience on your phone instead of starting a new thread with very little information. Try focus on finding workaround for BT stack race conditon/deep hardware issue which usually is shutdown and restart not reboot etc but some times the other way around.

2 Likes

I did search for bluetooth issues, but either the threads are old or for different phones etc.

I am not a linux expert I have to admit (not as much as all the others in this community). So I was hoping to at least get a link to other posts or some doc for me to find my way through.

thx!

I don’t put on my mind what phone you have from all your other threads. So I gave some quick general advice and what to potentially look for. Turn off AAS BT if you have it enabled do the two alternatives of shutdown restart and reboot and see which worked, right?

2 Likes

(Honestly!) thank you for this hint - that allowed me to resolve it.

AAS was turned on, so I turned it off and restarted. The config page came back nicely and I could remove that keyboard from the list of paired devices.

I then reenabled AAS and restarted and it also came back fine. My headset, which I had paired a while ago is still visible and also my hearing devices are back.

I then rebooted and still all is working.

Again thx - much appreciated!

However, I still don’t understand, why and how connecting a BT device can cause such a hazzle ..

P.S.: I have the new JP26

1 Like

well Android and Linux use different BT software stack and having them communicate between each other isnt easy, which is why the feature to get BT support for Android apps was only now recently introduced with 5.1 (and its still in progress)

3 Likes

Just some general advice: the Appsupport Bluetooth package “is still an early BETA”.

4 Likes

such a fundmenral device as a keyboard, would that still need AAS or wouldn’t it be on the same level as e.g. the network (logically)?

apologies, if that is too silly of a question …

Nothing needs AAS on SfOS. Not sure what you’re even asking. Yes, keyboards can be BT-connected to a SfOS device, without AAS.

1 Like