AppSupport Bluetooth feedback thread

Hi,

The Bluetooth bridge for AppSupport is finally in a fairly stable shape, so it is now available in the Jolla Store for cbeta users only. How much further it goes, and how quickly, depends on your feedback.

IMPORTANT: Don’t install this on an Xperia 10V. See the note below for details.

What it is

The AppSupport Bluetooth Bridge shares the phone’s Bluetooth controller between Sailfish OS and AppSupport. It acts as a router, so each Bluetooth device can be handled by either Sailfish OS or AppSupport without handing the whole controller over.

For most devices this is controlled through pairing. BLE devices are more complicated, and that is one of the areas where broader testing will be useful.

For now, you should reboot after installing. The Bluetooth settings page now has an extra option to route incoming pairing requests to AppSupport. Devices found during scanning also have a long-press context menu option to pair them with AppSupport. You can see devices paired with AppSupport on the same page, and you should also unpair them from there when needed. Turning Bluetooth on and off in Sailfish also turns it on and off in AppSupport. You should not try to turn it on or off from Android apps.

Android apps that are designed to pair with devices internally should be able to do so.

If you have previously handed Bluetooth completely over to AppSupport as described elsewhere on the forum, revert those changes first. Otherwise things are likely to break.

When it breaks

We have tested this internally with a range of phones and Bluetooth devices, but there is a lot of Bluetooth out there. We need more testing before releasing this more widely.

When reporting problems, please include:

  • Phone model
  • Bluetooth device make and model
  • Android app involved, if any
  • Whether the device was paired with Sailfish OS, AppSupport, or both
  • What else is paired
  • Exact steps to reproduce the problem
  • Whether it works after restarting Bluetooth or rebooting
  • Relevant logs with debug logging enabled
  • Logs may contain Bluetooth device names and addresses, so possibly best not to share them publically. Have a look through before you share.

Debug logging goes to the journal. The main daemon logs as appsupport-bridge-bt, and the AppSupport companion service logs as appsupport-bridge-bt-aidl. Debug logging is disabled by default. You can enable it from the AppSupport settings page. The toggle is runtime-controlled, so you can enable it only for a short period if you are able to reproduce the problem reliably. Though it doesn’t do a lot of harm so it would be great if you could keep it turned on during this testing phase.

You can export the relevant journal logs with:

journalctl -lab 0 -u appsupport-bridge-bt -u appsupport-bridge-bt-aidl -u bluetooth > appsupport-bt.log

Crash logs for Android-side services can usually be found under:

/home/.appsupport/instance/defaultuser/data/tombstones/

or the equivalent path for your username.

Special warnings

The Jolla C2 has been known to be a little crashy in the Bluetooth. It should be fine in ordinary use, but restarting the services a lot probably will make it reboot at some point.

When we tested this on an Xperia 10 V, it broke the radio badly enough that even the modem stopped working until the device was reflashed to Android.

For that reason it has not been marked as available for the Xperia 10 V in the Jolla Store. You may still be able to install it manually, but you should not do that unless it is your phone and you enjoy breaking your phones.

Known issues

  • Some people have reported that AppSupport later decides Bluetooth is off, and toggling Bluetooth off and on again in Sailfish fixes it. We do not have logs showing what happens here yet.

  • If you pair a watch or some notification forwarding device with an Android app, then you will only receive notifications on it that originated in other Android apps. This has always been deliberate in Sailfish: we forward Android notifications to Sailfish but for privacy reasons not the other way around.

54 Likes

Wow! 13 Years i waited for this moment…. i miss the right words to say thank you @abranson ! Thank you @Jolla !

25 Likes

@krnlyng deserves most of the credit for this!

25 Likes

I seem to have killed Bluetooth on my C2. It will not activate again. Restart done on the phone, but didn’t help.

I managed to set up my watch with a connection, but connection was lost more or less in the same moment.

  • Jolla C2
  • Android app: Nothing X
  • CMF Watch Pro 2
  • Nothing else was paired when trying to setup a connection to the watch

I notice that the log does not contain info from when I tried to set it up yesterday.

2 Likes

Bluetooth started working again. I have paired the watch again.

  • Jolla C2
  • Android app: Nothing X
  • CMF Watch Pro 2

I seem to have a lasting connection between the phone and watch:

  • I can switch watch faces.
  • I can add contacts for fast dial from the watch.
  • I can build sets of widgets that are available on the watch.
  • Battery status is shown
  • Health data registered on the watch is shown in the Nothing X app on the phone: Calories, steps, standing still etc.
  • The watch receives push notifications (got two from Aurora Store)

7 Likes

Maybe it would make sense to have the button enabling the bridge always visible on the Bluetooth Settings page.

If BT is hosed in some way, the main Bluetooth button will not toggle on, and there is then no UI way to disable the bridge.

It’s a bit tricky to start/stop it at runtime. Some devices have a bad time with that. Best way is uninstall and reboot.

Success on Xperia 10 III and Withings app. Thanks for this new feature!

11 Likes

:frowning: :frowning: :frowning: :frowning:

Casio G Shock connection also works. Top. I’m testing my hearing aid tomorrow. Thanks to Jolla Boys!!

6 Likes

For some Reason on my 10 IV it is was available in the Store and there was no issue with a reboot after installation.

4 Likes

Someone was brave enough to test an IV and it didn’t self-destruct, so it’s been marked as available. I’ve edited the post. Good luck!

7 Likes

Any chance to get that update?

1 Like

If you mean the 5.1 update with AppSupport Bluetooth, you have to turn on Early Access updates to get that. It was released yesterday.

4 Likes

Nice! Have to test this on my XA2, since I have a Whitings also and was wondering if it would work. But again “results may vary”. :wink:

Just tested my Bold smart lock and it works perfectly!

I did notice what appears to be a minor bug: I didn’t have Bluetooth enabled when installing AppSupport Bluetooth and subsequently rebooting. AppSupport is set to boot automatically and it did. I then opened the application for the Bold lock and it told me to enable Bluetooth, so I enabled it, but the application still claimed Bluetooth wasn’t enabled. Only after restarting AppSupport with Bluetooth already enabled, did it work.

1 Like

Finally got my OP-banking app registered on my C2 + MicroG. So I dont need to go to bank to do it. It needed a coupple tries (my mistakes I guess. Allways read the instructions :slight_smile: ). I got paired my C2 and Nokia X20 wich had a working OP- app. My X20 app asked me to scann the tag on my C2 OP-app etc… First it was bit hard to make bt start on android side.

Mexican wave/Ola

5 Likes

The silentest assassin :raising_hands:

14 Likes

Jolla C2. Paired Ledger live app with Ledger nano X hw wallet via bluetooth. Worked like a charm. Thanks a million for a great job!

2 Likes