Page 1 of 1

PBAP, Desire S and VW Premium...

Posted: Tue Mar 05, 2013 4:11 pm
by Vampyre
Hi,

I don't know if it is a known issue, but yesterday encountered the problem that I could not sync my mobile's phone book to the VW Premium car kit any more (it used to work fine beforehand, though). I got different errors ranging from "Phone book cannot be loaded" to just hanging with the message "Syncing 0 entries" as well as being stuck in the settings menu where you can choose which contacts are to be synchronized. I suspected the newly installed SMS plugin, so I removed it but it did not help either and also re-installing the drivers did not cure this issue. Finally I noticed that when selecting "Synchronize SIM and mobile phone contacts" it works, but when only selecting "Mobile phone contacts" it shows this erranous behaviour.
Maybe you want to have a look at this issue - it is not that urgent as the work around does its job though producing a couple of duplicate entries in the car kit.
CU,
Vampyre

Re: PBAP, Desire S and VW Premium...

Posted: Wed Mar 06, 2013 8:22 am
by admin
First of all: phonebook problems are never caused by rSAP. So there is no need to change anything in rSAP settings or installation. It's always a problem of Phonebook Access Profile (PBAP) or Handsfree or the fact that the car does not support one of the two.

Re: PBAP, Desire S and VW Premium...

Posted: Wed Mar 06, 2013 2:59 pm
by Vampyre
"First of all" implies there is something else?;-)
Anyway, thanks for enlightening me. VW Premium car kit supports only PBAP and RSAP but not HF. What is strange is that it beforehand worked and as you are more deeply in the BT things I thought maybe you know what is causing this - there must be a difference when trying to sync mobile phone's contacts AND SIM contacts compared to syncing only the first ones...

Re: PBAP, Desire S and VW Premium...

Posted: Fri Mar 08, 2013 8:52 am
by admin
VW Premium also supports IrMC and probably some proprietary Nokia profile. That's why phonebook transfer is so complicated: you first have to find out what profile is used. E.g. the Audi SAP adapter uses Handsfree (!) and IrMC for phonebook transfer, while using rSAP for phone function.

SIM contacts are often (not always!) transferred via rSAP, that's why they work :lol:

The problems with PBAP are most of the times caused by the contact data itself. When you change something in your data the next transfer may fail. Perhaps you changed something in your Bluetooth configuration at the same time, which lets you think it was this change that caused the failed phonebook transfer.

The root cause for all these problems are a sloppy specification of the vcard format and programmers that make decisions how to handle unexpected data. Android has bugs and the car kits have bugs. When they overlap you end up without a complete and correct phonebook. The last bug I found in the Android phonebook implementation was that code execution reached a line with an error log like "should never get here" :o

Re: PBAP, Desire S and VW Premium...

Posted: Sat Mar 09, 2013 3:36 pm
by Vampyre
admin wrote:VW Premium also supports IrMC and probably some proprietary Nokia profile. That's why phonebook transfer is so complicated: you first have to find out what profile is used. E.g. the Audi SAP adapter uses Handsfree (!) and IrMC for phonebook transfer, while using rSAP for phone function.
That's what I guessed - no standards in automotive control units... :roll:
admin wrote: SIM contacts are often (not always!) transferred via rSAP, that's why they work :lol:
Okay, interesting...in my case not only the SIM contacts work but the phone book contacts as well but only if selecting SIM+Phone as synchronization sources for the phone book transfer in the car kit.
admin wrote: The problems with PBAP are most of the times caused by the contact data itself. When you change something in your data the next transfer may fail. Perhaps you changed something in your Bluetooth configuration at the same time, which lets you think it was this change that caused the failed phonebook transfer.
Yes, I did add contacts before syncing again, but as stated above, they can be transferred but only together with the contacts on the SIM.
admin wrote: The root cause for all these problems are a sloppy specification of the vcard format and programmers that make decisions how to handle unexpected data. Android has bugs and the car kits have bugs. When they overlap you end up without a complete and correct phonebook. The last bug I found in the Android phonebook implementation was that code execution reached a line with an error log like "should never get here" :o
This actually is pretty much standard in industry coding :roll: - as working in this field myself I've seen (not programmed, though ;-)) a lot of this kind of code.
So as a conclusion there is either a difference in asking for contacts from the car kit when selecting the different sources in its settings or Android just does not understand to send out the phone's contacts only but delivers them when asked for SIM contacts...