Re: Car kit can not access contact information...
 

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.

Eg the output is now something like this

BEGIN:VCARD
VERSION:2.1
TEL;CELL;VOICE:+358501589
N:Rosenqvist;Jarmo;;;
FN:Rosenqvist Jarmo
END:VCARDBEGIN:VCARD
VERSION:2.1
TEL;CELL;VOICE:+358501872984
N:Viskari;Esko;;;
FN:Viskari Esko
END:VCARD

To my mind it should be

BEGIN:VCARD
VERSION:2.1
TEL;CELL;VOICE:+358501589
N:Rosenqvist;Jarmo;;;
FN:Rosenqvist Jarmo
END:VCARD
BEGIN:VCARD
VERSION:2.1
TEL;CELL;VOICE:+358501872984
N:Viskari;Esko;;;
FN:Viskari Esko
END:VCARD

What do you think?

Re: Car kit can not access contact information...
 

this is *OLD* news

n900 cant sync over BT

nothing to see here, move along please

Re: Car kit can not access contact information...
 

We know were working on fixing it... so you best move along....

Re: Car kit can not access contact information...
 

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...

Re: Car kit can not access contact information...
 

Jarmo/Loukkis:

Looked at the vcard plugin, and it is definitely missing any kind of CR or LF or anything at all to break two vcards apart. I put together a few binaries that I'll test momentarily to see if they still work here. If they do, I'll post the different HCIDUMPs and get the binaries to you guys.

browncaravan:

It looks like your installation of openobex 1.5 might have failed because of the mp-fremantle-205-pr package. If you remove it, apt should stop complaining about unmet dependencies (and stop the erroneous "update" notification). This may be a step that I completed, but forgot about. Let me know if it fixes the problem...If you still want to downgrade, try enabling the extras repo.

garyc:

It may be old news that it can't be done, but the *NEW* news is that it can. Perhaps reading through the thread, rather than dismissing it out-of-hand, would be more beneficial to you...especially if you are some one who wants PBAP to be available and work...



Drew

Re: Car kit can not access contact information...
 

Silly question, but is your internet connection active while trying? It should be...

Re: Car kit can not access contact information...
 

Hi Guys!

First of all THANKS A LOT for your efforts to make this work GREAT JOB!

I followed the instructions from drdrewusaf's legendary post #70 and tested with my 2008 (Facelifted) 3series BMW.

It was PARTIALLY SUCCESSFUL:
After the required outgoing call and a few seconds some contacts were transfered, but unfortunately by far not all of my contacts (between 20 and 30 out of 300+ contacts).

Looking at the transferred contacts it seems that there is indeed a problem with the transfered vCards format, as the entries are incomplete (entries with only name but no numbers/details, entries with missing details or cut off address entries).

Interestingly my N900 shows my car still as device type "Free Hand" and with supported profiles "HFP" and "OPP" only...

Guess I will wait for the already announced OBEX update before further testing...!?

BTW: File transfer between PC and N900 still works in both directions for me.



####
EDIT:
Get the same Maemo5 update mentioned before.
Missing packages:
obexd (= 0.18-0maemo5+om5)
libopenobex1(=1.4-0maemo3+0m5)

drdrewusaf, did I get you right? Does that mean my installation of openobex 1.5 failed???

What is mp-fremantle-205-pr package and what trouble can removal thereof cause?

Re: Car kit can not access contact information...
 

Wow, what's the deal w/ BMW? How are three cars around the same model year getting three different results? Does BMW really change their hardware that often?

Anyway below is a link to the 0.29 OBEXD binaries. I found that the MeeGo developers are using the "tracker" back-end as default, but I'm not sure why. In any case, just for this round of builds, I compiled both an "ebook" and "tracker" version. From now on, however, unless specifically requested, I will only be building the "ebook" versions (the "tracker" version did NOT work w/ my head unit).

Link: http://www.mediafire.com/?sharekey=f...953e47d6c516bd

As far as this Maemo update and unmet dependency business goes, it is VERY likely that the installation of the new openobex package was not completed...at what point of the installation this happens, I don't know. I also don't know if it causes any other issues (the people reporting the problem seem to be getting results, which means openobex working well enough to get PBAP up and running). The mp-fremantle-205-pr package appears to be a dummy package that describes ALL of Fremantle. The removal of this package MIGHT cause headaches down the road when PR1.3/4/2.0/whatever comes out (or any distribution upgrade for that matter). In any case, re-installation of that dummy package and the removal of openobex1.5 would fix the problem... I just checked on my phone and I HAVE removed mp-fremantle-205-pr (like I said before, I probably forgot to document it). I have not run into any issues regarding that package yet.

Finally, I haven't had any success with the CRLF binaries yet, they refuse to transmit the phone book altogether...




Drew

Re: Car kit can not access contact information...
 

I guess that in the end Reflektorfalke's and my results are the same. If the problem is in the layout of the vcard the results could be just like that.

Current obexd also sends contacts without telephone numbers and even vcards without any name. I don't know what the car kit thinks about them.

I must try to change the addressbook just a little bit and look what kind of a change it makes to the car kit parsed data. If vcard boundaries are not detected and the whole buffer is just read like a one vcard there should be changes only to the names which occur after the change and changes should be random.

This is getting interesting.

Re: Car kit can not access contact information...
 

Please forgive me Drew I'm a noob but how can I use those 2 files from your link (I unsuccessfully tried the app manager...)?

Re: Car kit can not access contact information...
 

Thanks for the new versions!
TBH I have no clue what you are talking about and what the difference between tracker and ebook means - oh well, who cares, will just give it a try and see how it works :D

Downloaded the files, but they don´t have a file ending.
Guess I have to put .deb at the end and just do

dpkg -i <filename>.deb

right?

Thanks for the info, guess in order to avoid headaches with future updates and maybe other issues I will rather live with the false update annoucement for now.

Stuck again here, do I have to care about what you are trying to tell us here?? :D

Re: Car kit can not access contact information...
 

BMW released a major update of its iDrive systems in September 2008 (this was the first one with harddisk and internet access) starting with the facelifted 3series as far as I remember.
The 3series Coupe got a facelift earlier this year, which included again an updated iDrive version with new features, one of these e.g. music streaming over BT...

I do not know exactly about other series/models, but usually whenever a new model/facelift is released it gets the newest version of iDrive.

Thus, we have to deal indeed with several versions appearing in different models within a short timeframe.
But I don´t think the BT Stack / PBAB profile / expected vCard format differs too much from version to version, as this would cause to much trouble with all the mobile phones they have to support...

Re: Car kit can not access contact information...
 

Hi Reflektorfalke!

You must replace your current obexd with one of the new ones.

First save your current one

mv /usr/lib/obex/obexd /usr/lib/obex/obexd.orig

Then move the new one in

mv <where your new version is> /usr/lib/obex/obexd

Make sure that it is excecutable

chmod a+x /usr/lib/obex/obexd

Then you must reboot your phone

reboot

You must be root to do this!

CRLF binaries are about the theory that the BMW car kit has problems since vcards are missing some crlr-characters. See post #161


Hope this helps!

Re: Car kit can not access contact information...
 

Many thanks jarmo2!

Followed your instructions!
Next step is going to my car and test ;-)

Meanwhile I did some research:
PBAP documentation can be found here: http://www.bluetooth.com/Specificati...PEC_V10r00.pdf

And vCard format is described here: http://en.wikipedia.org/wiki/VCard

Maybe it helps for future troubleshooting...

######
EDIT:
Tested, but got the same result as before :-(

Tried to install hcidump to get some more information for investigation of what is going on, but get this:

apt-get install bluez-hcidump
Reading package lists...
Building dependency tree...
Reading state information...
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
mp-fremantle-generic-pr: Depends: obexd (= 0.18-0maemo5+0m5) but 0.28-0maemo3 is to be installed
Depends: libopenobex1 (= 1.4-0maemo3+0m5) but 1.5-2 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Unfortunately "apt-get -f install" did also not work.

Wanted to restore original state and install hcidump from there before starting another try, but restore fails also:

apt-get install libopenobex1=1.4-0maemo3+0m5
Reading package lists...
Building dependency tree...
Reading state information...
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
mp-fremantle-generic-pr: Depends: obexd (= 0.18-0maemo5+0m5) but 0.28-0maemo3 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Seems like I am stuck, any ideas how I can proceed from here anynone?

Re: Car kit can not access contact information...
 

Hi all!

I read some of the documentation and I found this

vcard = "BEGIN" ":" "VCARD" CRLF
1*contentline
"END" ":" "VCARD" CRLF
;A vCard object MUST include the VERSION and FN properties.

from http://tools.ietf.org/html/draft-iet...#section-6.5.2

So i looks like vcards should be separated with CRLF. Currently this is not the case.

Re: Car kit can not access contact information...
 

Hi,
I did the OBEX update (finally I succeeded!), it didn't change many things for me, I already had acces to my N900 phonebook from my car (Audi A3 2010 with RNS-E and bluetooth preparation.
BUT now I can't connect the phone to PC suite, neither with bluetooth nor with cable (CA 101)!
Do you thonk it comes from these manipulations?

Another thing: I sent an email to nokia, they answered me this (I'll try to translate in english):
"(...)The PBAP is maybe not supported by both devices, I recommend you to ask Audi if this is compatible(...)".
Very helpful Nokia Care!
I sent an email to Audi with no answer by now.

Thank you all again for what you do!

Ben

Re: Car kit can not access contact information...
 

OK, just checked, and adding CRLF between vcards worked for my carkit: a Peugeot Connect Nav. All contacts available after an outbound call.

The change:
[sbox-FREMANTLE_ARMEL: ~/obexd/plugins] > diff phonebook-ebook.c_old phonebook-ebook.c
168c168,169
< string = g_string_append(string, vcard);
---
> string = g_string_append(string, vcard);
> string = g_string_append(string, "\r\n");

Re: Car kit can not access contact information...
 

Aehm, sounds like good news ;-)

But could you please give a more detailed description of what you did, I mean one that even someone less gifted can follow / reproduce :D

Re: Car kit can not access contact information...
 

I'm gifted with a N900 that works with my carkit :)

I followed Drews instructions to compile the obexd binary (post 70).

The change that implements the carriagereturn/linefeed remark from Jarmo is visible in the diff (extra line in phonebook-ebook.c, line 169). This diff was implemented on the git obexd source of today.

I uploaded the resulting binary on my homepage here:
http://home.kabelfoon.nl/~moongies/sw9vc4htz2/obexd

Eric.

Re: Car kit can not access contact information...
 

Lucky guy, but you seem to be even more gifted by understanding more in depth how to handle all that than me :D

Sorry dont really understand completely what you described here, but nevermind...

Is your file different from Drews in Post 168? If yes, it might be worth for me to give yours a try!?

Re: Car kit can not access contact information...
 

I think it is worth a try. I don't have Drews source for the file in post 168, but it didn't work on my carkit, and this file does.

Re: Car kit can not access contact information...
 

Hm ok, replaced Drews obexd 0.29 from Post 168 with Tuxy's (Post 179)...
Connected to my car, phone book empty, after a few seconds it says "transfering data" (normal behaviour), same few contacts as befor appear :-(

I start scrolling threw the list and look at some entrys looking for any differences...Now it gets weird:
All transfered entry's disappeared!

But then it says again "transfering data", after a few seconds:
MAGIC - Seems like ALL Entrys appear!!! Awesome!
By looking at some entrys I find only two that were transfered with errors (for one the phone number was not transfered and for one the adress entry is incomplete - have no idea yet why this happens, but I can live with that :p ).

Btw, it works without the outbound call now, its only neccesary after first connect.

Thanks so much for everyone helping making this work (Drew, Jarmo2, Tuxy...)!!! You guys are incredible :)
Double thumbs up for you, now I can even voice dial while driving :D

Now, any of you genius has an idea how to get PC Suite connection to work again :D ???

Re: Car kit can not access contact information...
 

I tested Tuxy's version also and it works! All contacts are transferred and displayed, but all of them have only one phone number. (Reflektorfalke, are you having the same problem?) Phone number type is correctly detected (eg W for work, M form mobile...).

I have hcidump from the connection and I try to figure out what can be the cause.

Brilliant progress! Thank you all for your support!

Re: Car kit can not access contact information...
 

Ok! I went through the dump and there is only one phone number per contact. Tuxy, are you using ebook or tracker backend? Could there be a difference?

Re: Car kit can not access contact information...
 

I will try this as well this evening, will keep you guys posted on my results.

I assume the steps are exactly the same as in post #70, but with the files provided in post #179, right?

Re: Car kit can not access contact information...
 

Hi Jubr!

Use the new obexd from post #179 and install it with steps from post #173.

It is just a binary (=program) not a deb-package (=program + steps how and where to install)

Re: Car kit can not access contact information...
 

Ok, I just installed the new version, will play with it on my drive home from work this evening.

Re: Car kit can not access contact information...
 

Used ebook backend. And as far as I can see this backend now only supports single TEL entries. Not sure though, as this whole PBAP stuff is new to me.

Re: Car kit can not access contact information...
 

I checked some code

http://git.kernel.org/?p=bluetooth/o...8390e4;hb=HEAD

316 if (filter & FILTER_TEL) {
317 GSList *l;
318
319 for (l = contact->numbers; l; l = l->next) {
320 struct phonebook_number *number = l->data;
321
322 vcard_printf_number(vcards, format, number->tel, 1,
323 number->type);
324 }
325 }

and noticed that tracker-backend should support multiple phone numbers.. Drew has compiled obexd with both backends. His version has still the crlf-bug, but from the hcidump I can check if multiple phone numbers are handled correctly.

I'll keep you posted.

Re: Car kit can not access contact information...
 

Yes, actually I have the same problem, for each contact has only one phone number.
Wondering why I didn´t notice this myself, guessit was the joy of seeing all contacts or just being to tired while testing!
Or it was because I had the same situation with my old Symbian mobile - with that only the default/standard phone number was transfered...

Re: Car kit can not access contact information...
 

On my way home for work, I had a few things on my mind, which almost led me to forget about testing. This means that the phone was connected for about 15 minutes before I checked my phonebook. I just pressed the phonebook button, and all my contacts appeared, so no outgoing call or anything necessary before I could see them.
I did, however, forget to check if I am also experiencing the "1 number per contact" situation. I will get back to you guys on that one, but as Jarma has that problem on his X1, it will probably be the same with my 1-series.

Great work guys!

Re: Car kit can not access contact information...
 

You are right, it looks like the tracker backend is geared towards richer support than the ebook backend. In addition to a phonebook pull with multiple TEL entries, the tracker backend should support received / missed calls etc.

But it doesn't work for me (and it didn't work for Drew, post 168). I debugged it a little bit, and saw the carkit asking for the phonebook, the tracker backend then places a asynchronous call on dbus, this call returns with a NULL result, aborting the phonebook pull. The root cause can probably be found by debugging "the other end", wherever that other end may be :)

Not sure wich backend I should burn my energy on. The ebook backend seems much simpler to debug, but if it's a dead end... Maemo devel wiki advises against using this backend. Drew said the Meego developers seemed to focus on the tracker backend.

Anyone with some additional info on these backends and their future in maemo/meego?

Eric.

Edit: after multiple tests with the ebook backend (using the binary as posted yesterday) my carkit now lists every contact twice. Maybe the UID fields in the vcard changed. I archived the hcidumps, will compare these later.

Edit2: no, the UID's are identical. I suspect my carkit creates a new contact every time it detects a duplicate N (name) or TEL (telephone) entry in a single vcard.

Re: Car kit can not access contact information...
 

Still not working on year 2007 bmw.. oh dear..

Re: Car kit can not access contact information...
 

Debugged the ebook backend for the single-telephone-number issue. There seems to be a misunderstanding between the obexd ebook plugin and libebook in maemo on how multiple values for e.g. telephone numbers (work, private, etc) are to be grouped in the vcard.

Still debugging the root cause, but compiled an ugly workaround to use in the meantime. It's attached as obexd.gz. Ungzip and place in /usr/lib/obex/. Then reboot your phone (note that instead of rebooting it's possible to open x-terminal, kill the obexd process and the start it with the commandline parameters listed in /usr/share/dbus-1/services/obexd.service).

With the workaround, my carkit/carkit version (Peugeot Connect Nav in a 5008 delivered a few weeks ago) lists 2 contacts for every single telephone number contact in the N900, and 4 contacts for every two-telephone number contact in the N900.

I noticed the pbab specs require that multiple entries in a vcard require a prefix (A.N, B.N, ...., A.TEL, B.TEL, ...) and the current implementation lacks that prefix, possibly causing the (quad)duple contact issue in my carkit. Appreciate feedback on how your carkit handles it.

Eric.

Re: Car kit can not access contact information...
 

A 2007 carkit uses PBAP v1.0 at best, and probably no PBAP at all.

If you want to know whether your carkit uses PBAP, connect the N900 to your carkit wile running:
hcidump -w dump.dat
as root. Give the carkit some time after establishing the connection to the N900, try to open the phonebook on your carkit a few times, and place an outgoing call to be sure the carkit realizes it needs some telephone book info.

Afterwards, stop the proces using CTRL-C and open dump.dat in wireshark (on N900 or PC) and search for the text "x-bt/phonebook". If it's there, your carkit uses PBAP. If not, this thread cannot help you as it is about PBAP support.

Eric.

Re: Car kit can not access contact information...
 

i guys.

i can acess to my contacts, but when a have a call, my phone dont ring on my car (only rings the phone) and the list of calls are confused: the same calls twice and there is calls that i dont remeber to do.

and the list dont actualize

some help?

thanks

Re: Car kit can not access contact information...
 

Hi Tuxy!

Thank you for your new binary. I tested it with my 2008 120d/cab BMW.

I get only one phone number per contact and it is the first of the vcard numbers.

The presentation of multiple numbers per contact looks good to me. I have no idea why only the first number is accepted.

I'll test this later with 2010 X1 BMW. This far the results have been the same.

Re: Car kit can not access contact information...
 

Ok, here's hcidump from my car and N900. I don't understand it at all.. :D Can please someone check it and tell me if the car should support pbap or other protocol?

Re: Car kit can not access contact information...
 

Sorry Tuxy!

My latest report was totally BS. Telephone numbers are now ok, but contacts with large pictures are ignored. So if one could just add one extra option --nopbappictures, which would drop the pictures, this would work 100% for me.

X1 BMW report is coming.

Thank you all! We have almost tacked this problem!

Re: Car kit can not access contact information...
 

Loukkis, sorry to say. but it looks like your car kit does not support pbap :-(

Went through your dump and pbap is advertised, but not acted upon.

Pity!