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

Hi everybody,
Audi A3 2010 with RNS-E with bluetooth preparation, phone N900.
It works great for me following the steps of post 70 (with Obex 0.28)!
I tried with Obex 0.29 but it didn't work at all anymore.
So I downgraded to version 0.28, I have all my contacts, they appear on the head when I receive or give a phone call, it's awesome!!!
The received and composed numbers are wrong, but I don't care!
I'll keep in touch to look if there are interesting updates, but I really don't see what I could be looking forward now!

Again, Thank you all, you really did an amazing job!

Ben

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

Thanks Jarmo for looking into this. It's seems, that my beloved BMW needs software update..

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

I don't think there is a need for such an option, as obexd should only send the parameters the carkit asks for. The reason you see picture references now is that the workaround I use ignores the carkit filter information and just sends all data.

Or, wait, does your carkit ask for pictures? Are they displayed? If so, I can look into that.

Currently I use a test environment using the pbap-client python script, so I can finally test without my carkit. Hope to have a proper implementation of the phonebook pull soon.

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

I finally found the time to run hcidump with the car-kit of my Toyota Prius MY 2010. Actually, I ran it twice.

First time using the obexd package ver 0.28 - I can't quite remember in which post I found that. Second time using the obexd binary compiled by tuxy - see post #179.

I turned on the car, paired the N900 with the car-kit, tried to transfer the phone-book to car-kit, dialed a number through the car-kit, tried phone-book transfert again.

No joy, no contacts transferred to my car-kit.

By reading the dump, I think that the N900 sent a few contacts, but they are not received by the car-kit.

The last vcard sent is broken right after "VCARDBEGIN:VCARD". Also there seems to be a CR-LF sequence between "VCARD" and "VERSION:2.1", so the first vcard looks like this:
BEGIN:VCARD
VERSION:2.1
TEL:
N:Surname;Name;;;
FN:Surname Name
END:VCARDBEGIN:VCARD
VERSION:2.1
It continues at the new line after "VERSION:2.1".

Any ideas?

Thanks for your help anyway!!!

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

Hi

Just to let the people know witch carkit i found working.
I still got the obex file from puxy i believe.

I first got a bury cc9055 carkit, and tried everything what was posted here with files. No luck at all.
Now i have a bury cc9056 carkit and i got name's. I haven't got the time to check all, but al the list are full.
The recieved/transmid list are working without name's
So that's 1 i found working with some tweaking.

Greetz

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

Checked your bt-dump with wireshark, and it doesn't show the CR/LF bytes between the vcards the binary from post 179 puts in the stream. You probably got your binaries mixed up.

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

See attached my latest version for /usr/lib/obex/obexd on the N900.

In this version:
1. vcards are properly separated by CR/LF
2. multiple (TEL) entries are included in the vcards
3. only entries the client (carkit) asks for are returned

Note that this version only differs from the earlier workaround version by solving problem 3.

One issue remains: my carkit (Peugeot Connect Nav) lists every contact twice. Anyone with the same problem?

I found my carkit asks for two different phonebooks: SIM1/telecom/pb and telecom/pb. The N900 (with the ebook backend) sends the same contacts for both requests, leading to duplicate contacts.

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

Tuxy!

I guess that you forgot to attach the new file?

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

Edit: solved the duplicate phonebook issue by returning an empty phonebook when SIM1/telecom/pb is queried. See attachments: obexd binary and the phonebook-ebook.c file containing all changes.

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

I'm getting old :)

Added attachment to original post, thanks.

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

Guys
I tried all apt get u wrote here to uninstall obex files but still can't use my device with PcSuit. What's wrong? I cant update system now cause it needs pcsuit connection :(
help pls

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

Tuxy, thanks a LOT for the new version and of course again for your efforts here!!!

Tested your file and after checking a couple of entrys it looks very good!

I only found few errors/deviations while browsing through some transfered entrys. I found that most of them were due to bad data quality in my phone book and I was able to fix them easily (e.g. bad formated email, contacts with no first/last name but only company name or false classification of phone numbers).
The only issue I was not able to solve yet is that for some contacts the phone number is still not transfered. What I noted here is that some(all?) of them have ä, ö or ü within the first or last name - is it possible that we have some kind of encoding issue here?

Of course I did not check all of my 300+ contacts (and had to quit testing as it was above 30 degrees celcius in my car :D ), but from my point of view the result is very good!

Broken PC Suite and Bluetooth connectivity, problems with downgrade to original obex as well as a false Maemo 5 update announcement in App Manager are known issues that occured with the obex files posted in this thread and were also mentioned in this thread before.

I hope that when PBAP works in general some of the genius here find solutions for those bugs and brings PBAP to extras so that every average user can simply download and install PBAP without loosing other features ;-)

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

The phone number is not transferred, so the contact itself is?
And if so, is the name with ä, ö or ü then displayed correctly?

Just tested with a fake contact with ö and ü in the name, and my carkit displays the contact correctly (names and number). The hcidump shows the N (name) parameter is sent in UTF8 (in a hex editor the ö character is represented by two bytes).

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

Both, Yes...

Ok, thanks for testing! Will have another look at these contacts later and see if I can identifiy another issue with them...

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

so no hope for now? :(

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

...I'm so glad to see some movement regarding this topic; also I hoped Nokia would take their "early adaptor customers" (spending quite a bunch of money) a bit more into consideration.
So - waiting this solution going to an "extra deb"; thanks so far!

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

Reinstalling the original packages that are manually updated in drew's post 70 is worth a try.

But keep in mind that this can cause problems for the phone. Backup your data, backup your config (apps > system > backup) and know how to reflash (http://wiki.maemo.org/Updating_the_tablet_firmware#N900).

To reinstall the original packages:
- open x-terminal on the N900 and get root privileges
sudo gainroot
or
ssh root@localhost if openssh-server is installed
- excecute these commands:
apt-get update
apt-get install --reinstall obexd libopenobex1 openobex-apps
- reboot the phone.

Edit: note that this procedure will remove the updated obexd binary, removing the PBAP capability from the N900.

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

Ok,had another sauna-(aka testing-)session in my car:cool:

First, what I noted: The contacts I identified take a while longer to show up, even a while after the "transferring data" message disappeared...Don`t know what that means, but something is going on here I guess!?

What I tried first, I created an exact copy of one of the contacts and made small changes to one of the contacts - with no success.
Next I added a fake number to the contact copy I created before - success the contact showed up with both (the real and the fake) number...

So, at the moment I still dont have an idea whats wrong with those contacts. Guess for further investigation I would have to look at a dump of the transfer, but as said before the installation of hcidump fails :-(

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

Cannot find that post just now, but I remember it was because of failing dependencies? Sometimes these dependencies are more of a packaging issue than a real one. Hcidump is a simple binary in bluez-hcidump, chances are it will work if installed manually.

Instructions for manual install:

1 - Download the deb-package.
The package containing hcidump is here:
http://repository.maemo.org/pool/fre...emo2_armel.deb
2 - Unpack it (alien on Linux, 7-zip on Windows)
3 - copy /usr/sbin/hcidump to the N900
4 - on N900: chmod a+x /usr/sbin/hcidump

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

== tracker backend ==

Now that I got my carkit working with the e-book backend, I started debugging the tracker backend, as it seems to support more use cases (missed calls, etc).

The tracker backend doesn't work because an expected dbus service: org.freedesktop.Tracker1 is missing on the N900. This service is implemented by the tracker-store daemon:
http://live.gnome.org/Tracker/Docume...gnalsOnChanges

Tracker-store is not available on maemo's tracker version 0.6. It is available in the debian-testing arm packages: tracker version 0.8. This service is new, and using it will require an upgrade.

That upgrade might wreak havoc on the phone. I don't know what services rely on tracker services, all kinds of apps might break. I'm not ready to risk that as I'll need my phone up and running the upcoming weeks. Any volunteers that have the N900 reflash capability on hot standby? :)

== extra deb ==

As HugoSon said, it would be nice to make e-book PBAP available for others via an extra-deb. But this package should not break pc-suite / bluetooth ftp functionality as reported in this thread.

Can anyone confirm breakage of pc-suite *and* restore of that feature after rolling back to the original maemo versions of libopenobex1, openobex-apps and obexd?

If so, I can check whether it is doable to implement PBAP starting from maemo source. If pc-suite breaks on the libopenobex upgrade it will be a pain. If it's obexd there is hope.

In any case, I'll need heavy help with testing, as pc-suite is a Windows only app, and I don't have a windows machine available.

Eric

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

Tuxy, with your instructions I got hcidump to run!

(BTW: I noticed that the BMW carkit has 2 contact lists:
1. Phonebook
2. My Contacts
Both seem to list contacts received via BT / PBAP + local contacts, but Nr. 1 seems to list only contacts with phone numbers)

The following are 2 vcards from the dump:

The first one is the one that is shown without number.
Thus it is only shown in My Contacts.
The second one is the one I created as duplicate entry, but added a "2" after the lastname and an additional phone number.
This one is shown just fine.

I highlighted the differences between both vCards in bold.
Anyone has an idea why the phone number for the first one is not shown correctly???

BEGIN:VCARD
VERSION:2.1
TEL;WORK;CELL:<number>
N;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:<lastname>;<firstname>;;;
FN;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:<firstname> <lastname>
END:VCARD

BEGIN:VCARD
VERSION:2.1
N;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:<lastname>2;<firstname>;;;
FN;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:<firstname> <lastname>2
TEL;WORK;CELL:<number>
TEL;VOICE:<number>
END:VCARD

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

This is just speculation Reflektorfalke, but that TEL;WORK;CELL combination seems strange. Usually my contacts have only voice as the third word (TEL;WORK;VOICE or TEL;CELL;VOICE). It is possible that your car kit ignores that number since it thinks that the number is not for voice communications.

Voice is the default. That makes TEL;CELL work.

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

Hmm, definitly a point I was looking at, too. But I dismissed that idea because...the duplicate contact I created for testing (second one in my last post) also has a TEL;WORK;CELL entry (besides the additional one) which is shown correctly while others with TEL;HOME;CELL or TEL;CELL are not shown !?

However, in order to get more insight on what is going on here I went through all my contacts:

- I found almost 30 of my 300+ contacts do have problems
- ALL of them have special characters within the name (either ä, ö, ü or ß)
- found only TWO contacts with those characters that are shown without errors (the one I created as duplicate for testing and another one)
- found NO entry without ä, ö, ü, ß having errors
- the almost 30 affected contacts show very different errors:
-- no number, one out of 2 numbers, two out of three numbers...
-- email adress is cut-off
-- company shows parts of contact name (last part of first name + first part of last name)
-- address is incomplete

Naturally the affected contacts differ regarding number as well as regarding kind of details they have.
Because of that and the various kinds of errors I cannot find a common cause for the problem except the special characters :-(
Even looking at the vcards in the dump didn´t help me find anything else...

Of course, a possible workaround would probably be to change the special characters into ae, oe, ue and ss.
Guess would be acceptable for me, but not sure if it would be for the average user if PBAP makes it to extras!?

From my point of view we need more testers with different carkits - who knows maybe its a BMW problem!? - and different languages - maybe the problem occurs also with other special characters?

So, I suggest to leave the problem for now and focus on the necessary steps to creating a package for extras-devel in order to attract more testers (solve the PC Suite connectivity issue and make it uninstalable).

What do you guys think?
(Especially you guys with the skills that brought us where we are and want to go :-) )

I think we already have a respectable achievement here, maybe we can get Nokia to give some support here as they did with fMMS - you think thats possible?

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

Hi all!

I tested the latest version and now EVERYTHING LOOKS GOOD for me. Phone book is transferred and all transferred data is correct. (Finnish special characters ÅÄÖ work ok)

Next I try this with my little sisters BMW X1.

I am a linux user so I can't help with the pc-suite problems, sorry.

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

Could be carkit related, but also vcard version related. Your carkit uses version 2.1, mine (and Jarmo2's?) uses vcard version 3.0. These vcard versions differ in character set handling: 2.1 specifies the charset parameter, 3.0 doesn't and therefore relies on charset autodetection by the client.

I agree. But there aren't any detailed test reports regarding pc-suite. I'm thinking about arranging a test laptop with windows so I can test this myself.

And making the package uninstallable certainly would prevent any problem with the package to affect a users phone :)

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

Ok, thanks for this info! Will have to see my car dealer anyway within the next weeks, gonna ask him if I can get a software update for my iDrive, maybe newer versions support v3.0 (mine is from 11/2008).

Hm, guess you are asking for a hcidump from a PC Suite connection attempt? Can someone provide this?
Unfortunately I can´t at the moment as PC Suite connection was broken for me on PC side before I started playing with obex.
And I don´t want to waste my time fixing it because I am planning to upgrade my PC to Win7 soon - maybe I should do it sooner ;-)
But wouldn´t be some input from Nokia/Maemo developers be helpful here?

Haha, nice typo, guess you know what i meant: DEINSTALLABLE :D

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

I can confirm: the libopenobex1 upgrade breaks PC-suite.

Just tested on a work PC:

- with upgraded obex stack on my N900, PC-suite didn't work with cable or bluetooth.
- after a downgrade to the official maemo versions for obexd and libopenobex1 pc-suite worked (tested with cable only)
- when I upgraded to libopenobex1_1.5-2 during a PC-suite session (with contacts window open) I could still edit my contacts. That's great.
- after disconnecting, pc-suite wasn't able to reconnect. It doesn't recognize the USB connection with the phone.

A note about downgrading:

when using apt-get --reinstall as I suggested a few posts back, maemo's apt-get complains it cannot download the packages. A solution is to download the packages manually, and install them with the dpkg command:

- download these packages:
http://repository.maemo.org/pool/fre...+0m5_armel.deb
http://repository.maemo.org/pool/fre...+0m5_armel.deb
and place them in a folder on the N900, say /home/user/mypackages
- open x-terminal on the N900 and get root privileges
- excecute these commands:
apt-get remove openobex-apps
cd /home/user/mypackages
dpkg -i *.deb
- reboot the phone.

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

For me, that would be premature. I'm still looking into the issues and the sourcecode involved. And I'm familiar with Linux, but Maemo is new to me.

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

Hi!

Now I tested my little sisters BMW X1 (2010). It also worked perfectly. Names, Company info, telephone numbers and e-mail addresses were all transferred correctly.

My 120d (2008) and sisters X1 (2010) both use vcard version 2.1.

X1 bluetooth version is VK13029-9224422. I cant find version info from my 120d :(

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

guys, someone could please answer? Thanks

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

Hi asfig!

Current pbap version does not support missed/last call functions. It can only transfer address book to the car.

I cant help with the ringing problem. It is a separate problem and does not have anything to do with pbap.

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

Damn, as I said I can live with my issue, use a workaround and wait till it is solved somehow...
But knowing that it works for you with the same setup (BMW carkit and latest obexd) is bugging me :cool:
Out of curiosity I want to at least know where this weird behaviour comes from :D

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

Still doesn´t work with my bury CC9060 (should support PBAP, OPP and some other BT protocols as said by manufacturer), so i have some questions:

a) I replaced obexd with the one in #209 (right one?), doing as described in #173. (replacing ONLY obexd)
In one or more posts about fixing PCSuite there was something written about reinstall more than only obexd - does this mean that installing means more than replace *only* obexd? if so - which file, mentioned in what post?

2) if not, any1 using CC9060 too and has something to report?

Will try to update my carkit tomorrow, maybe that brings some success, someone wrote about CC9055 not working and CC9056 working... and i think all the CC90xx use the same central box...
If not, i will try to make a dump - but i think that the kit supports pbap as said... my E90 synced with car kit via pbap i think...

ThanX

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

Did you start with the guide from Post #70?

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

No:D
As in the thread about OCn the N900 i am used to read a thread from the end :rolleyes:
just to much to read so many pages from the beginning and then finding out that the important posts are on the last 3 pages^^
I am just used to stop when there is explained something about installing - after that i do only a very fast view about the rest...

long post - short meaning:
No, i have not... so i will do that now:o

Thanks:)

Edit:
Now installed packages w/o developer.
overwritten obexd with the one from #209
lookin forward to next try of sync tomorrow

but i have seen that my car kit has a new firmware to install... new one "now" supports OPP - so perhaps the "italian" way with petrovich should work too... So no need for dealing with obex... too late^^ I think i will first try petrovich (again) if i succeed in updating my car kit - thats not so easy sometime at this special car kit...
And after that i will try PBAP:D

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

@SirTurbo: Of course you should use whatever approach you feel more comfortable with. But it would be nice if you could test PBAP and let us know about your results. Every input is helpful...

@Everyone: As obviuosly its already quite confusing to update obex for someone who didn´t follow the whole path. What do you think of creating a new thread?

This new thread could have a more appropriate title like e.g. "[Announce] PBAP/Carkit support coming to N900". Hopefully this will attract more interest and more testers...
A new thread would also give us the chance to have a "regularly updated summary post #1" and thus for everyone in the community a way to get a fast overview of current status/issues as well as an up-to-date installation guide...

What do you think guys, would this make sense/be helpful?

If yes, from my point of view it would be best if one of you guys who did all the work here (Tuxy, Jarmo, Drew...) would write the summary based on your knowledge.
Of course, in case you like the new thread idea, but prefer to focus on developing rather than / dont have the time to / want to write the summary I offer to give it a try myself...
Or any other volunteers out there :p ???

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

Reflektorfalke, about your non-working contacts. Have you imported them from a different phone/computer? Have you checked from the dump that there is no extra (non-printable) characters anywhere.

All my contacts were exported from a N95 and Google contacts (via Nuevasync) or they were created on N900.



About the new thread. There is also a wiki-page at wiki.maemo.org (very slow at the moment)

http://wiki.maemo.org/Fremantle_Unsu...tooth_profiles

and the bug 6368 at bugs.maemo.org.

https://bugs.maemo.org/show_bug.cgi?id=6368

Should we update something to those places also? To my mind we should have one place where the progress is documented and the other places should have just a link to the main page.

Bug 6368 has a long list of watchers. They could be potential testers?

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

Yapp, as my phonebook evolved over years by syncing over several phones and with Outlook as well as Notes I was thinking about this possibility too.
But I think I eliminated this by creating this one duplicate account for testing right on my N900 - this account was only transferred correctly after I added a second phone number.
I also copied several affected vcards from wireshark into wordpad and did not find any strange characters.
Further, I think it would be a impossible coincidence that only contacts with special characters are affected by that!?

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

Oh yes, very good point to have only a single place to maintain!
Besides easy maintainence I think another important point is user-friendliness...

From my point of view, the bug page is not the place where the average user looks. And I also think posts can not be updated there, resulting again in a confusing number of separate posts.
But most important, as I understand the bug page it is not the place for such a purpose!?
But of course winning those guys over there as testers would be great, but aren´t all of them also at tmo?

I really like the idea with the wiki, especially because it can be edited by everyone and not only by one person like a forum post (hope I am right here: tried once to edit a wiki but was not able to as it required a special account,right?).
What I am not sure about is the user acceptance of a wiki page as to me the community seems very forum focused...

Well, to me the best approach seems to be a new thread with a short first post explaining that all relevant information can be found on the wiki page...
Aehm well, at least if the wiki will be faster again, it doesn´t even open for me at the moment :eek:

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

I like all the suggestions from Jarmo2 and you. As I see it, a single post to the bug thread could not only attract testers, but also developers. A wiki page can be used to reflect the current status, and a new thread with a more positive title and a clarifying first post could eliminate some confusion seen in this thread.

Having said that, I'm perfectly comfortable with whatever you guys (where is Drew?) decide to do. I'll just keep on debugging and hopefully fix things :)