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

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.

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?

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.

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

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

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.

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.

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

guys, someone could please answer? Thanks