maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   Car kit can not access contact information... (https://talk.maemo.org/showthread.php?t=36272)

mirakels 2010-04-21 14:19

Re: Car kit can not access contact information...
 
I saw some IrMC code in the opensync package (up to version 0.36) See

http://opensync.org/download/releases/0.36

but I'm a bit confused about server versus clients... The opensync READMEs talk about opensync as being a client... but maybe it can work as a server too.

Ossman 2010-04-21 14:36

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

Originally Posted by mirakels (Post 621083)
I saw some IrMC code in the opensync package (up to version 0.36) See

http://opensync.org/download/releases/0.36

but I'm a bit confused about server versus clients... The opensync READMEs talk about opensync as being a client... but maybe it can work as a server too.

Yeah, as far as IrMC goes, it can only act as a client. It is useful as a reference on how a server is expected to behave though.

mirakels 2010-04-21 14:57

Re: Car kit can not access contact information...
 
On my previous phone, a nikia 7710, I once found a tool that allowed me to sync with my carkit. Presumably it must have benn using IrMC. The tool actually was created to sync to a Nokia 616 carkit.

The tool is called "Contacts Sync"

Unfortunately there seems to be no source code. But as we are on a nokiaworld now maybe it would be possible to get hold of the source.

hschmitt 2010-04-21 15:02

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

Originally Posted by Ossman (Post 617681)
This is how hcidump looks with my car kit:

...
No such request is ever seen from my kit for the PBAP profile though.

Same with mine. I am still waiting for an answer from parrot.
Another idea would be "phonebook over AT commands". This is implemented e.g. in Android:
http://sites.google.com/a/android.co...tooth-features
My Parrot asks for AT+CPBS=?.
According to
http://www.phys.unsw.edu.au/~mcba/ir...ommand_Set.pdf
and
http://www.anotherurl.com/library/at_test.htm
This asks for the available phonebooks.
This has to be implemented in bluez/audio/headset.c and should then call a function in telephony-XXX.c

Ossman 2010-04-21 15:07

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

Originally Posted by hschmitt (Post 621138)
Same with mine. I am still waiting for an answer from parrot.
Another idea would be "phonebook over AT commands". This is implemented e.g. in Android:
http://sites.google.com/a/android.co...tooth-features
My Parrot asks for AT+CPBS=?.
According to
http://www.phys.unsw.edu.au/~mcba/ir...ommand_Set.pdf
and
http://www.anotherurl.com/library/at_test.htm
This asks for the available phonebooks.
This has to be implemented in bluez/audio/headset.c and should then call a function in telephony-XXX.c

I was thinking of that as well. Unfortunately bluetoothd is a system process, whilst obexd is a user one. So it's a lot more difficult to get a decent architecture there.

There is another feature that might be interesting with that AT command abuse though, and that's SMS. My car kit is supposed to be able to indicate when I've gotten a message, and AFAIK the AT commands are the only way to access them.

Ossman 2010-04-21 17:38

Re: Car kit can not access contact information...
 
Some kind of progress. I jury rigged the PBAP stuff in obexd to appear as an IRMC sync service, and behold! The car kit actually connected to it. This might actually be a way forward...

(there is of course quite a bit of work to get this to behave as a proper IRMC sync service)

mirakels 2010-04-21 19:10

Re: Car kit can not access contact information...
 
my carkit also asks AT+CPBS=?.
so maybe the 'contacts sync; tool responds to that instead of IrMC.

Ossman 2010-04-21 20:01

Re: Car kit can not access contact information...
 
Ah fudge. I've gotten the car kit to actually request something from the n900, but unfortunately it does this:

Code:

REQ(0x2), GET(0x3), (null)(0x0)
OBEX_HDR_NAME: telecom/pb/luid/0.log
REQDONE(0x3), GET(0x3), (null)(0x0)

That thing is supposed to give some kind of changelog for the phonebook entries, and unfortunately support for it is mandatory in Bluetooth IRMC sync (but not in the original IR IRMC sync).

Might be some way to cheat here, but I don't know the format of that log file...

hschmitt 2010-04-22 08:57

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

Originally Posted by Ossman (Post 621506)
...
That thing is supposed to give some kind of changelog for the phonebook entries, and unfortunately support for it is mandatory in Bluetooth IRMC sync (but not in the original IR IRMC sync).

Might be some way to cheat here, but I don't know the format of that log file...

I found this doc link:
http://www.pday.com.cn/technology/ir.../IrMC_v1p1.pdf
Maybe it helps?

Ossman 2010-04-22 09:03

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

Originally Posted by hschmitt (Post 622167)
I found this doc link:
http://www.pday.com.cn/technology/ir.../IrMC_v1p1.pdf
Maybe it helps?

Indeed. I browsed through it last night and it might be possible to force a full resync everytime by pretending that the n900 has been reset at every connection. Should keep the implementation simple.

The biggest problem is finding time to implement this. I probably won't be able to look at it until next week.


All times are GMT. The time now is 12:12.

vBulletin® Version 3.8.8