We have moved to a new Sailfish OS Forum. Please start new discussions there.
6

[3.2.0.12] XA2 bug: switching off bluetooth after connecting keyboard

asked 2019-10-30 00:01:52 +0300

AkiBerlin gravatar image

updated 2019-10-30 13:16:46 +0300

After switching Bluetooth off, the Bluetooth symbol is still shown and top menue also suggestes Bluetooth would be still on.

I observe this behavior only after updating to 3.2.0.12

The bug appears to affect only the XA2 after connecting a keyboard - which now works

EDIT: Reboot resolved the issue so far

EDIT2: Here is more detail

  • I can reliably reproduce the bug with my Bluetooth keyboard (Rapoo E6300)

  • The problem only occurs when trying to switch off Bluetooth on the XA2 before switching off the keyboard. In case I switch off the keyboard first, there is no problem - apparently the sequence matters

  • It appears that Bluetooth is indeed deactivated after switiching off but the indicators tell the opposite

  • There is no such issue with the Xperia X under 3.2.0.12 - only the XA2 is affected

  • I only encounter the problem with the keyboord. With car audio or with Bluetoth between XA2 and Xperia X, no such problem exists. However, when switching to another Bluetooth device after the issue occurred, the problem persists

Could somehow be related to [XA2] Bluetooth gets stuck after disabling; see @Sakke's hint below

add a comment

2 Answers

Sort by » oldest newest most voted
2

answered 2019-10-30 09:59:33 +0300

Sakke gravatar image

Most likely this is duplicate of https://together.jolla.com/question/214788/xa2-bluetooth-gets-stuck-after-disabling/ ? @AkiBerlin, if it's, then I'll update on to my post that it's still present in Sailfish 3.2.0.12 too. I haven't yet faced it up.

link

Comments

It could be the same issue, indeed. Curiously, for me, the problem only affectes the XA2 in combination with a bluetooth keyboard under 3.2.0.12 when operating keyboard and phone in a particular sequence

AkiBerlin ( 2019-10-30 13:13:17 +0300 )

@AkiBerlin, I was able to reproduce this issue using sequence you described. I think they're definitely the same issue. I updated this to my question too.

Sakke ( 2019-10-30 19:14:14 +0300 )
add a comment
1

answered 2019-10-30 08:42:59 +0300

Yes, known issue. (some weeks ago)

BT hickups can be resolved by
devel-su systemctl restart bluetooth bluebinder

Wrong status display (also "waiting, working") might need devel-su systemctl restart lipstick

link
add a comment
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2019-10-30 00:01:52 +0300

Seen: 386 times

Last updated: Oct 30 '19