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

I had an nightly attack of the wish to "work" and went to the car:)

Had to update my car kit several times. (Don´t know why, i thought that i updated to that-time-latest-version when first trying to sync phonebook in December)
First problem: car kit updated only to second last firmware - after that no more connection to the update manager. So perhaps problems with the car kit are solved but i cannot test it - so it isnt sure if probs are made by mobile phone or by car kit.
But OPP seems to work (only with vcard 2.1, not with vcard3.0). not perfect, still some things to do (naming of phone numbers when the contact has several of them f.e.) - but it works... next days i will see if it is "usable" now with n900... bury added some nice features, they seem to like their customers - seems to be different to nokia^^ (update problem reported - waiting for answer)

But now to the big point: PBAP...
First i tried to read phone book several times... every time i got "successfull" - but the phone book in my car kit was still empty. Then i played again with opp.
when i after that tried again to import whole pb (via PBAP) - i got an error that contacts could not be pulled and they have to be pushed by phone?
After that i startet the dump and tried again.
In the dump there is nothing about x-bt/phonebook when opened in wireshark.
But as i tried the download only one or two times (didnt want to create a large dump) i am not sure if this is 100% precise. So i think that i will have to try again when having time.

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

Guys, there is one thing I noted during testing but forget to mention:
Even though PBAP is obviuosly working in general, my N900 still shows my car as device type "freehand" and a little headphone symbol (my old symbian phone showed a little car symbol) and in the device properties/details only HFP and OFP are listed as supported profiles for my car.

Guess its just a cosmetic detail, but if one of you Guys finds a way to fix this it would be nice..

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

Tested the PC-suite connection to the N900 using both stock and custom obex versions.

Procedure:
1 - pc-suite not started
2 - connect phone via USB
3 - press PC-suite button on N900
4 - start pc-suite.

See attached tarball containing three logs:

pc-suite-stock-success: succesful connection with pc-suite, N900 using stock maemo packages for libopenobex and obexd.

pc-suite-custom-fail1 and -fail2: pc-suite failed to connect, N900 using custom versions of libopenobex and obexd (the "PBAP-versions").

I don't understand everything in the logs, this is what I think I do understand:

Connecting cable and pressing PC-suite is visible in the logs. The faillogs contain quite some "unsupported method" events. These errors often come up when library versions don't match the applications using them. Multiple services report problems and/or fail. Solving this might lead to a cascade of package updates, with every update solving one problem and creating another.

I'm thinking about backporting PBAP to the obex versions used by Maemo. It might be more difficult technically, but with some luck, everything is contained within the obex package. That means less risk to other parts of the system, and it is easier to manage.

Eric.

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

Before you think of backporting it, you should test, whether pcsuite works with the original obexd and openobex 1.5.
Because if it does not work with openobex 1.5 you cannot use the async access to ebook.

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

Hi Everyone!

Please Note:

This thread is now summarized in Post #1 of a new thread regarding Bluetooth PBAP support.
From now on, please continue discussions regarding PBAP in the new thread...

Thank you!

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

Thank you. I didn't know about the lack of async ebook support in the stock openobex libs. I tested the configuration you suggested (upgraded lib, original obexd) and was quite happy to see pc-suite connecting to the phone.

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

My carkit does not supp\ort PBAP, but instead uses IrMC SYNC to get the contact list.

I created a basic IRMC YSN server plugin for obexd that only supports full phoenbook transfer. It works pretty well in my case.

If anyone is interested to test I'll can make it available

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

i'm interested to test it :) My Parrot work only with IRMC i think.

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

ok here it is. You probably need libopenobex-1.5 to make it run properly (see post 70 for a link).

This obexd is based on the latest trunk (0.29).

This is a version that uses the ebook phonebook backend. As far as I see it only grabs one phonenumber per contact. It also contains a lot of debugging info.


Many of my contacts have more numbers so I also use a different backend but that requires some additional steps. But first lets see if things get started this way.

Please run it with debugging on and running hcidump on the background so we can analyse problems afterwards.
To capture the obexd logging you also need the sysklogd package (apt-get install sysklogd).

put the obexd.ebook.gz file on your n900 and gunzip it.

Kill the currently running obexd (killall obexd)

As root start the new obex and hcidump as

obexd.ebook --debug --irmc --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability !/usr/bin/gen-obex-capability.sh


hcidump -w hci_irmc.log


In case of problems please post the hci-irmc.log and the relevant part out of /var/log/syslog

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

I wrote to the bluez and obexd mailing list about the pcsuite problem and got a promising reply:

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

@mirakels
I try to use your obexd.ebook. Not work for me :( I try with Parrot Evolution 3000.
What i did:
dpkg -i libopenobex1_1.5-2_armel.deb
dpkg -i openobex-apps_1.5-2_armel.deb
apt-get install bluez_hcidump
killall obexd

After them i run obexd.ebook with params and switch Parrot to recive vcard mode.
hci_dump -w hci_irmc.log

And try from Contacts send vcard with one phone.
N900 show list of available devices. I select Parrot and receive error message "Can not connect to device"...
I attach hci dump log file to this message.

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

well the hci log seems more or less empty.
you should start the hcidump before connecting to your parroy.

please also install syslog (se my previous message) as obexd can then log vrious info tot the /var/log/syslog file

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

@mirakels
Sorry, I'm mistake with the log file. I attach new file.
Unfortunately I can not now use syslogd - it is not compatible with my enviroment

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

Hi GLobster,
that is better, but unfortunately I do not see any IrMC sync request, or any sync request for that matter in this log.
Somehow you must get your carkit to start syncing the phonebook....

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

My carkit don't have sync mode. I must send by BT needed vcards to carkit in study mode. But Nokia can't to send it.

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

Therefore you can use the app Petrovich. Open your contacts and use "Export". Then use Petrovich to send it.

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

Is anyone got success with the newest VW Passat onboard computer?

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

I try it also as buy N900. It's not work. N900 not connected also.

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

:mirakels

Please see the attached logs from my BMW 320D 2005 - iDrive software updated in 2008.

Tell me what you think.. It's with the obexd you have provided (with irmc)

Thanks...

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

Hi john_doe252

from the syslog I see obexd is started, but it was never triggered to do something
so no sync did start...

your hci log does mention a sort of IRMCsync capability, but it did not start a sync.


PS: to get a readable hci output please use the following command to get some more details (assuming you got the log by 'hcidump -w hcilog.bin'):

hcidump -r hcilog.bin -t -V -X > hcilog.txt

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

Hi,

I build a obexd 0.29 version with a commit reverted, which might bring pc-suite support back (See previous post). Since I'm based on linux, I cannot test it.
Attached is the obexd and the patch. Maybe someone gives it a try.

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

Hi hschmitt!

Thanks for the new version.Tried to connect to PC Suite via

Bluetooth: PCSuite can`t find N900
USB-Cable: When connected in PC Suite mode, PC Suite says "Installing PC Connectivity Cable Drivers" and stays like this forever...
when connected in Mass Storage Mode PC Suite at least recognizes that N900 is in wrong mode and asks to change PC Suite mode.

Dammit, will keep testing a little more and let you know if it works...

Besides that, would you mind to place PBAP related post in the new thread ? This new thread lets the community follow the development in a more convenient and less confusing way. Because relevant information is not spread over 260+ posts but summarized within 1 Post and its not a confusing mixture of PBAB, IrMC Sync or whatever related development.
Thanks for your understanding and support again!

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

Okay i will post everything new in the other thread :).
One more question: What is in syslog? Can you attach it?

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

Thanks ;-)
How about uploading your new version also to the new thread so other followers find it and can start testing?

Which syslog do you need?
(apt-get install sysklogd doesn´t work at the moment due to unmet dependencies. If you need this I maybe need to revert to original obex first and install it from there...)

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

Exactly this /var/log/syslog. I updated the wiki page to mention the other pbap thread:
http://wiki.maemo.org/Fremantle_Unsu...ile_.28PBAP.29

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

:mirakels

Hello,

I've attached the log as you said,
please see it and tell me if you find anything else, because as you said, I've also saw that IRMCSync capability.

Thanks,

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

john_doe252

your irmc seems different from my carkit yours tells us:

010-07-28 13:30:37.722046 > ACL data: handle 11 flags 0x01 dlen 8
L2CAP(d): cid 0x0040 len 13 [psm 1]
SDP SS Req: tid 0x11 len 0x8
pat uuid-16 0x1107 (IRMCSyncCmd)
max 1
cont 00

mime says:

2010-07-28 16:59:49.477256 > ACL data: handle 11 flags 0x01 dlen 7
L2CAP(d): cid 0x0041 len 20 [psm 1]
SDP SSA Req: tid 0x100 len 0xf
pat uuid-16 0x1104 (IRMCSync)
max 256
aid(s) 0x0004 (ProtocolDescList)
cont 00

My updated obexd knows how to handle this 0x1104 service. But 0x1107 is not (yet) supported by obexd.

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

:mirakels

Thanks a lot for your time,

I would be grateful if you could enlighten me a little more related to the 0x1107 service... What is it related to?

Also please tell me why are u saying that is not "yet" supported? Do u have any info regarding this? If so please be kind and share that with me and the others....

Thanks a lot again.. :)

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

I tried to find some more info about thsi IRMCsyncCommand (1107) service, but couldn't find anything useful. 'yet' because I hope it will be implemented somehow (not necessarily me...)
Maybe the 1107 is just the client IrMC side. In that case your carkit could be be a IrMC server and expects your n900 to initiate the sync...

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

John_Doe, you might want to have a look at PBAP. Several BMW´s, also from 2008, were already tested successfully. See this thread for details.

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

GREAT I used the last versions of the deb and this version of obexd.
Then I edited the file with the configuration:
obexd.ebook --debug --irmc --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability !/usr/bin/gen-obex-capability.sh

and... I GET my phonebook on my car kit
I have a Ford S-Max (2008) with a sony kit.

The only problem is with pcsuite...

Thanks to all!!

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

I think you should use the latest version from mirakels:
http://talk.maemo.org/showpost.php?p...5&postcount=63

You can say thank you with the Thanks! button ;)

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

Thanks! now Pc-Suite is working fine... I'll retry later my connections with the car kit :)

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

ok all is perfect
of course no visualization of calling name but only number

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

So with this special application I could access the phonebook of the N900 via the phone book option of the Kenwood BT60?

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

Hi Crogge!

I googled for "Kenwood BT60 pbap" and it looks like your Kenwood kit supports pbap.

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

Sounds good, will there be a version in extra-devel soon? Because it seems to be quite difficult to install it.

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

I've tried the latest obex version with my Volvo V70 (Mod 08-) built-in bluetooth module...without success:mad:

I think the problem is that the obex daemon can`t find a specific file (/root/.osso-abook/db)

I've started the obex-daemon with the following command:

/usr/lib/obex/obexd --debug --irmc --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability !/usr/bin/gen-obex-capability.sh

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

i have try to get it work on my audi a4 2005 but it will not work i have make a hcidump file but i dont understand a **** of it

so please help me

i attached the file here (u can open it in Wireshark)

//Markus

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

none who knowws ???