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.