Android 4.2 rsap does not work with Mercedes UHI any more

[Reini47]

After Upgrade to 4.2 (and now 4.21), the app does not work any more (with a Mercedes UHI-SN0544). Nexus is rooted again and the app seems to run. New Pairing also does not work: the UHI recognizes the Galaxy, but if I choose it, the Galaxy does not ask to enter the code (and if I choose the UHI in the Galaxy and enter the code, pairing simply does not work).

I thought, there will be a fix in Android or the app, but problem persists. The problem also seems to be unknwon in the forum. Any helb ?

[admin]

Did you probably forget to reinstall the system files?

[Reini47]

No, I did not forgot it and I just reinstalled them again and it does not worked again.

[admin]

Google exchanged the Bluetooth stack with 4.2, this may cause problems with Porsche and some Audis, but as far as I could see it should work with the Mercedes SAP modules. Which one do you have: V2 or V3?

[eagleCS]

Confirm! After upgrade at 4.2.1 rsap on my Mercedes don't work anymore.

I returned at 4.1.2 android: works.

This is my sap module:
http://www.motorbasar.de/mercedes-sap-b ... 07473.html

[admin]

D'oh! I did not yet find out how to specify Bluetooth service details with the new 4.2 Bluetooth stack, if it is possible at all! It seems the Mercedes SAP V2 does a more detailed search for the SAP profile which does not match the "standard" service description used in 4.2. So far I thought this only happens with Porsche and some Audis.

Can you please create a HCI log with 4.1,so I can verify that? Best would be to start the log before a fresh pairing.

[eagleCS]

Attach my log HCI (with 4.1.2) working connection.. if necessary make another log tomorrow with fresh pairing.. at this moment I can not do

PS Rename from .zip to .cap

Hi

[admin]

This log is sufficient. If you find the time you may create one with 4.2, but it is not urgent. Please send it by mail and delete the attachment above. Logs may contain private data...

I think the following is happening: The SAP V2 asks for profile "remote SIM Access" gets an answer, but does not accept it, because some additional attributes are missing. I'll have to understand how the new Bluetooth stack works and how to specify the additional parameters, then I can fix this.

[eagleCS]

This log is sufficient. If you find the time you may create one with 4.2, but it is not urgent. Please send it by mail and delete the attachment above. Logs may contain private data...

I think the following is happening: The SAP V2 asks for profile "remote SIM Access" gets an answer, but does not accept it, because some additional attributes are missing. I'll have to understand how the new Bluetooth stack works and how to specify the additional parameters, then I can fix this.

Ok thanks. At this moment I can not put the 4.2 because it is very complicated return to 4.1 and i need connection to my car..

[systemchef]

I have the same problem, Android 4.2.1 (on Galaxy Nexus 9250) with Mercedes SAP v2 module doesn't pair any more. Worked with 4.1. Is there a solution to use with Android 4.2?