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

Audi MMI 2G contact sync over BT does not work

asked 2015-03-14 22:11:10 +0200

ziili gravatar image

updated 2015-05-06 17:27:40 +0200

chemist gravatar image


Jolla with SW can be connected to Audi MMI multimedia as hands free set via BT, all phone calls and audio is working as expected. But, the contact information is not shown at the car system. This was tested also with previous SW version and with second Jolla phones, with same results. As reference Samsung Galaxy Trend works as expected and all the phone contact info is accessible via the car UI. I believe this should work on Jolla too as there is profile for this:

PBAP 1.0 (Phone Book Access Profile)

Detailed information of the Audi A4 MMI:

SW: B8-HU 55.7.0 0835 HW: B8-HU 6329D2.0

edit retag flag offensive close delete


I thinking about retrofit Bluetooth on my Audi A4 with Basic MMI. I wish to here about this from other owners of cars from the VWAG-Enterprise. Retrofiting Bluetooth is really expensive, 300 to 500 Euro.

hoschi ( 2015-03-14 22:31:29 +0200 )edit


if you're willing to enable developer mode and debug the issue, please contact Jolla care for instructions on how to do that. We can have a look at the traffic between the phone and the carkit to investigate the problem.

Please file issue reports for Jolla Care in https://jolla.zendesk.com/hc/en-us/requests/new.

hmallat ( 2015-04-20 14:10:21 +0200 )edit

I have developer mode enabled, so can you define what logs you would need and is there any specific way to create them?

ziili ( 2015-04-20 21:52:23 +0200 )edit

We'll need Bluetooth traffic collected with hcidump (note that this will include any contact data transferred between the devices), bluetoothd debug logs and obexd debug logs. If you contact care, they will give you a script that sets up collecting the needed information and wraps it in a tar package you can send to them.

hmallat ( 2015-04-21 08:37:40 +0200 )edit

@hmallat, thank you for your input! I have also dev mode enabled, so I will also make a try at it.

nick75 ( 2015-04-21 09:31:35 +0200 )edit

3 Answers

Sort by » oldest newest most voted

answered 2015-04-23 13:52:48 +0200

nick75 gravatar image

updated 2015-05-15 14:38:21 +0200

So, I received the scripts, made the logs, sent them to Jolla and received this back from them:


thanks a lot for the log file. Our R&D has now investigated it and commented as follows:

The BT carkit of Audi does not seem to use the Phone Book Access Profile (PBAP) of Buetooth at all for synchronizing the contatcs. Jolla supports PBAP. Instead, Audi appears to use the SyncML protocol. Also SyncML is supported by Jolla. However, the Audi carkit does not seem to use the standard SyncML but a Nokia-specific tailored version which is not available as a public standard. This conclusion is based on the service UUIDs appearing in your log (we have the details, if needed) and a comparison with the standard. This also explains why Nokia N8 works without problems with your Audi.

Since we don't have access to the information how the Nokia implementation differs from the standard we cannot unfortunaltey safely modify the SyncML impementation of SailfishOS.

The only slight chances to make Jolla work in your Audi are these: - there is a software upgrade available for the Audi carkit such that it brings the support of PBAP or standard SyncML - the car kit has a setting to turn the Nokia compatibility mode off and enable the standard public protocols.

Sincerely, Jolla Customer Care

I have already the final version of the firmware for the carkit, and I have not seen any settings relating to compatibility mode. Regarding the reference to Nokia N8, that is my previous phone which worked nicely with the Audi carkit.

Edit 2015-05-06, more feedback from Jolla Care:

Seems that the carkit is looking for the following service UUIDs:

00005001-0000-1000-8000-0002ee000001 00005002-0000-1000-8000-0002ee000001

Did a Google search on the the UUID, and found out that (probably) is a IrMC sync. It further seems Citroën carkits also use IrMC instead of PBAP to do phone book syncing over Bluetooth. And apparently Jolla could/should support IrMC.

Edit 2015-05-15, Jolla Care instructed me how to enable (untested buggy) IrMC on my Jolla. So I made some further logging and their feedback was:

"The same behavior as in the previous log. For this carkit we'd either need to somehow implement "Nokia compatible" syncml server or start supporting phonebook transfer with AT commands". Based on this it seems that we won't be able to help you in near future, at least. Like discussed earlier, we will consider the AT commands. It will take some months if the decision were to implement it. Please bear with us.

So, for me, this is a dead end.

edit flag offensive delete publish link more


According to this service, there are a lot of different phones that supports phone book syncing over bluetooth with Audi carkit, in my case modell year 2008. http://microsites.audi.com/ngw_assets/mobile_db/index.html?ds=json_en

nick75 ( 2015-04-23 15:24:09 +0200 )edit

And, the Audi system I have is working perfectly with Samsung Galaxy Trend (cheapo Android model). Also wondering what was the comment about the update on the Audi, as the MMI SW version should be the newest available for that model. Will also try to look for the Nokia compatibility mode setting.

Personally I cannot commit that the Audi is the fault here... But need to take the logs also, might be different case what Nick75 has.

ziili ( 2015-04-23 17:17:40 +0200 )edit

Found this https://wiki.maemo.org/Bluetooth_PBAP

syncevolution - SyncML obex profile conflicting with nokia SyncML - should be disabled

I wonder if this is related to my problem?

edit: Feedback from Jolla Care:

The N900 page reference "conflicting with Nokia SyncML" refers to the fact that Nokia implemented a closed source synchronization application in N900.

nick75 ( 2015-05-05 15:05:20 +0200 )edit

answered 2015-03-14 23:46:49 +0200

nick75 gravatar image

updated 2015-04-23 14:11:28 +0200

I also have Audi MMI 2G in my A6, without successful phone book syncing. The reason is that the VAG cars (VW, Audi,etc) use RSAP instead of PBAP, read more in this thread https://together.jolla.com/question/26623/request-rsap-bluetooth-protocol/

Edit 2015-04-23: After investigations by Jolla care, the Audi carkit appearantly uses a modified version of SyncML instead of PBAP/RSAP. See my other answer for more details.

edit flag offensive delete publish link more



Hello nick75,

I doubt that this is related with rSAP support instead of PBAP. Usually the MMI is configured to prefer the rSAP profile, but if this isn't available the regular PBAP/HFP connection is established. I am working at a supplier of Audi on the next Gen MMI and I can't see issues with PBAP in the latest SW (neither from Jolla nor from MMI). But I can't give guarantees over all MMI-versions - probably you can ask for a SW update at your Car-Dealer. Note: in case of problems I recommend to reset MMI to factory defaults, erase the BT-Profile inside the Jolla and re-initiate the BT-connection. Other than that: It can take loooong time if you have lots of contacts on your phone until the contacts are displayed.

Kerwes ( 2015-03-15 12:36:16 +0200 )edit

Hi Kerwes!

Where to get more info on this item with the older MMI units? Are they using something else than PBAP 1.0?

Updating Audi MMI SW is not free on those and as there is no guarantee that the issue would fix with that, I would not go to that route as there is rumors that update might even disable some of the features of the working MMI.

As far as I understand, PBAP should be enough to get the communication to work, so could it still be debugged at Jolla end also? It has been tried to by removing the pairing and getting the connection done again, waiting for long time to get the sync to be done, but no success.

ziili ( 2015-03-15 20:23:34 +0200 )edit

@Kerwes, thanks for your feedback. The firmware in @ziili 's Audi is already the latest (and probably the last). I have the version prior to that, and have the cd's containing the upgrade, but haven't had the time yet to update my car.

nick75 ( 2015-03-15 21:37:09 +0200 )edit

Here is some intresting reading regarding RSAP vs PBAP in Audis: http://www.a5oc.com/forums/a5-s5-topics/13984-audi-list-compatible-phones.html I have not tried myself, but will make a try after I update my firmware.

Edit: Searched as crazy, could not find how to initiate the pairing from the car.

nick75 ( 2015-03-15 22:01:01 +0200 )edit

answered 2015-05-06 14:53:13 +0200

condo4 gravatar image

For me, Audi A3 2013, this bug was present in older Sailfish release, but it's fixed since 4 or 5 month (I don't remember exactly the release)

edit flag offensive delete publish link more


The problem discussed in this topic relates to the Audi MMI 2G, that was sold between circa 2004-2010 (depending on car model). So your Audi has a newer generation of MMI, with other Bluetooth functionalities and profiles.

nick75 ( 2015-05-06 15:12:05 +0200 )edit
Login/Signup to Answer

Question tools



Asked: 2015-03-14 22:11:10 +0200

Seen: 2,786 times

Last updated: May 15 '15