Thread: Car kit can not access contact information...
View Single Post
loukkis is offline loukkis
2010-07-13 , 05:32
Posts: 29 | Thanked: 30 times | Joined on Oct 2009 @ Jyväskylä, Finland
#164
Originally Posted by jarmo2 View Post
btw, I was looking my hcidumpfiles and I noticed that all attributes are separated by hex 0d 0a (like new line), but there is no separator between END:VCARD and BEGIN:VCARD. Is this a bug? This could lead to a situation where vcard boundaries are not detected and only buffer size would limit detection. This could result the situation I am seeing.

******

What do you think?
Jarmo, few days ago when I checked your HCI dumps I watched those too. I tried to find some sort of information about it but I didn't find anything else than Microsoft Navready's documentation, which might be valid for other PBAP implementations too. It says for example that:

A vCard is considered valid if all the following are true:

1.It contains at least one phone number with 2 or more digits.

2.Each line is exited only by using a carriage return and line feed (CRLF) character.

3.The character set used is either ASCII, UTF-8, or ISO 8859-1.

4.The vCard size does not exceed 400 KB.

5.If an encoding other than quoted-printable or 8-bit is not used.

****
So the current maemo implementation might work with some car kits, but some (like BMW) might be little picky about the format and CRLF character is needed to make it operational. It is easy to try thou...
 

The Following 2 Users Say Thank You to loukkis For This Useful Post: