Promo

Google once again changed the internals of the Android Bluetooth stack, and guess what: it breaks my phonebook app. It is no longer able to properly stop the built-in phonebook service.

Today I found out that the latest Android source contains a change which once again enables my app. I don't have an idea when that change will be published in an official release or if there may be new Android 8 firmwares in the future which don't contain that fix. Simply check if your car connects to my app, if not you'll probably have to wait for the next firmware update.

And these problems all happen only because Google refuses to add a proper Bluetooth SDP API to the Android SDK. So they work their way from hack to hack. Sad...

Google modified the handling of the Bluetooth "Service Discovery" database (again) and now some cars can no longer be paired with phones using LineageOS 14. Strange enough everything is fine with the original Android 7, e.g. with a Nexus 5X. See here for a list of affected cars.

I'll try to add another hack to the Bluetooth driver to fix this problem, but it may take some time.

One user notified me that he managed to pair his Mercedes SAP V2 adapter with his phone by initiating the pairing from the phone. He touched the "MB-Bluetooth" device in Android Bluetooth settings, while the adapter was (unsuccessfully) searching for the phone. Maybe it works for others as well.

 

It looks like the rSAP app is used in more configurations than I can imagine. I tried to run the new version on as many phones with a lot of Android versions and different SOCs, but it is still not working for some users. So I decided to publish two more updates to the app (trial and full version):

  • V2.5.6 ist the same as the last version before 3.0. It is available for phones with Android less than 5.0 (Lollipop). You should get an "update" from Version 3.0 to 2.5.6 if you have a lower Android Version.
  • V3.0.2 is the redesigned version which will now only be available for phones with at least Android 5.0 (Lollipop). This was the first Android version where SELinux security was preventing RIL socket access, which led to ugly hacks in the 2.5 app version. After all, the 3.0 update was primarily necessary because of changed security settings in Android Nougat. In case you still have problems with the 3.0 version on Android versions later than 5.0 let me know.

I'm sorry for all the troubles which the update caused. I hope this will not happen again...

Today I released version 3.0 of the rSAP app. It is a complete redesign of the app, it is now prepared for the coming Android Nougat. I already ran it successfully on a Nexus 5X with the Nougat pre-release. Big changes were made in the user interface. I removed all outdated options and tried to better show error conditions. I also removed the SIM check, I will add this again when I find the time.

In case you find problems please report them in the forum.

Sadly some other issues showed up which I could not yet fix:

  • the app no longer works on Samsung phones with Android 6.
  • the app does not work on the OnePlus 3

I'm working on both problems but cannot say so far when (or if) I have a solution.

Today I published a new version of the installer app (2.5.9). It supports additional newer or 64 bit phones. On these phones a special "factory test mode" must be set to create the necessary file in the baseband's file system. Additionally the phone must be rebooted after setting the test mode.

Some phones don't remember the test mode after the reboot, so you still cannot make the change to the baseband settings. The Oneplus Two is affected by this problem. I'll keep trying to find a solution for these phones.

I could enable rSAP on a ZTE Nubia Z9 mini. It needs the reconnect plugin to properly work. I don't know if this happens on all 64 bit phones or only on the Nubia. So please give feedback.

Go to top