I'll mostly use Skoda part numbers and names here as I have a Skoda superb outside for testing and severall Skoda bluetooth modules. Just google a little to find the corresponding Volkswagen or Audi part numbers.
I first encountered the (r)SAP Bluetooth profile when I was still developing for Windows Mobile. Yeah, anyone remembers?
Problems were many and large....
Symbian on the other hand always worked flawless (duh).
And now on to Android. My most recent Android device is the Galaxy I9300, or Galaxy S3/S III as we all like to call it.
Very often, messages refer to "Bluetooth not working with RNS 510", "Can't connect to RNS" etc. This is understandable as we all know our beloved navigation system is known as the RNS 510 (Columbus) or RNS 310 (Amundsen).
However, strictly speaking we are connecting with our phones or tablets to a small device that is mostly located underneath the front passengers seat. There are quite a few versions of this unit, the difference inside is probably only the firmware. But from a user's perspective the difference is much larger:
- 5N0 035 730 A
- 5N0 035 730 B (r)sap, pbap, red dot matrix display, RNS support
- 5N0 035 730 C (r)sap, pbap, white dot matrix display, RNS support
- 5N0 035 730 D (r)sap, pbap, a2dp, white dot matrix display, RNS support
(picture clipping due to forum stylesheets)
See also here for a very complete of the different units: http://wiki.ross-tech.com/wiki/index.ph ... trofitting.
All the various appearances of these devices are actually variations of the same hardware made by a company called NOVERO. And until recent they only supported (r)SAP. That makes sense, Novero used to be a subsidiary from Nokia. And Nokia was part of the "Car Working Group" at the Bluetooth Consortium and the main driving force behind (r)SAP.
I put the (r) inside parentheses since the bluetooth consortium officaly only knows about the Sim Access Profile https://www.bluetooth.org/Technical/Spe ... dopted.htm. But in common speak we often use the term rsap instead. Incidentally, anything you ever wanted to know about (r)SAP can be download from the above URL. The full specification to both v1.0 and v1.1 are available, free of charge, on that page.
(r)SAP is great! And also a big PITA
It is great, from a technical point of view. Remote hardware, radiation levels minimised inside the car. The unit only communicating APDU's with the phone's SIM using the bluetooth profile.
It's a pain for users. Depending on the implementation, phone's will be usable, partially-usable, completely unusable while the (r)SAP connection is active. SMS may go to your phone's memory, the car's memory or both. Etc. etc.
If your phone does not support (r)SAP, you have little options.
- Either replace your current bluetooth unit with a newer version that supports the A2DP bluetooth profile (which is almost universally present on mobile devices, yes: even on the iThingies).
- Start a campaign to get (r)SAP support at your phone manufacturer.
- And of course if you have an Android phone: use the app from this site.
That brings me finally to the part that started this (and why this message is in the Phone Book Access Protocol):
The Phone Book Access Protocol is used to transfer those contacts from your phone into the car's unit. Our site admin has written a lot about (problems with) implementations of the PBAP. And has asked for feedback for PBAP problems with the Volkswagen-Audi-Group (VAG) devices.
Here are some observations then, the list is not yet complete:
- Don't use "Home", "Work" specific labels for e-mail adresses
- Don't have XML in memo fields
- Don't have newline or carriage return in any fields (0x0a / 0x0d)
- The asterisk '*' is (inconsistently) causing problems in memo fields
Name, Multiple -labelled- phone numbers, birthday and address -without any newlines or carriage returns-
seems to be the way to go to sync OK.
Sorry for a) my non-native English and b) the lengthy post, but I'm sure peoply using search will find this info due the large number of keywords with a chance to match . I'm still analysing the exact field contents giving trouble. Should I gain new insights I will update the post.