murrayc <murrayc(a)murrayc.com> changed:
What |Removed |Added
--- Comment #2 from murrayc <murrayc(a)murrayc.com> 2011-06-08 11:09:59 UTC ---
Here's a summary of the current plan:
SyncEvolution can adapt to the capabilities of the device that it is syncing
with. However, that currently requires the user to manually select a template.
Ideally, SyncEvolution would be able to automatically detect popular devices,
avoiding this step.
Currently, SyncEvolution only knows the the device name assigned to a Bluetooth
device. But this string is simply a default human-readable value that can be
modified by users and might not describe the manufacturer or model at all.
There are several ways to obtain more information:
* Use bluez to obtain the Bluetooth Device ID Profile via the Bluetooth Service
We have confirmed that bluez already has support for this, via its
sdp_record_t query results, though the protcol only provides unsigned 16-bit
values, so SyncEvolution will require a mapping of these to actual vendor and
Not all mobile phones support the Bluetooth Device ID Profile, but apparently
enough do support it for it to be worth using. See BluetoothDeviceIDProfile.
* Use bluez to request the Bluetooth address and then parse if to discover the
Bluez already has functions to do this, such as ba20ui() and oui2comp() via
its own internal mapping. This will not provide a unique device ID, though it
should uniquely identify the device manufacturer. However, this might be the
manufacturer of the bluetooth adaptor rather than, for instance, the mobile
phone. This might at least be used to narrow the list of choices.
* Use SyncML's initialization stage to read the DevInf section.
However, this is currently ruled out. See #c1
We can make the device identification available to syncevo-dbus-server and to
use that to automatically select the appropriate template in the GTK+ GUI, or
to at least reduce the available choices there.
MeeGo Release: unspecified
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.