http://bugzilla.meego.com/show_bug.cgi?id=736
Summary: Detect 'device model' for phones
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
OS/Version: IA
Status: ASSIGNED
Severity: enhancement
Priority: Undecided
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
This is from http://bugzilla.moblin.org/show_bug.cgi?id=10380
Description From Chen Congwu 2010-03-23 19:22:24 PST (-) [reply]
As discussed in thread [1], it would be better if the DBus API for GetConfig
can add a 'current device model' property to better present for user.
'current device model' is the model detected for the phone, we have to
implement some model guessing functionality for this. The information might
come from:
1) Device Name: The default bluetooth name of the phone likely has device model
information, eg: 'Nokia N900'
2) Bluetooth profile: There was a bluetooth profile for this, we can retrieve
this information if the phone implements such profile.
3) The DevInf sent from the phone: We may initiate a dummy session and get the
DevInf information.
No approach is guaranteed to work, so the 'current device model' is an optional
property.
[1]
http://lists.syncevolution.org/pipermail/syncevolution/2010-March/001176.html
------- Comment #1 From pohly 2010-03-24 00:23:44 PST (-) [reply] -------
(In reply to comment #0)
> 3) The DevInf sent from the phone: We may initiate a dummy session and get the
> DevInf information.
I don't think this is a viable option. Because we don't know the model, we
don't know which kind of SAN we need to send. Even if we manage to send the
right one, we are not ready for a real session. In OpenSync I've seen reports
of phones which crash and have to be rebooted when a sync session doesn't go as
expected, so we cannot start a sync session and then abort it.
------- Comment #2 From pohly 2010-03-24 02:34:46 PST (-) [reply] -------
We agreed to name the 'current device model' property "modelName" *and* defined
it such that it really is the exact model. It is clearly optional - if we
cannot determine the exact model, don't add it.
So for case 1) "device name", don't add "modelName", because we don't know how
exact it is.
--
Configure bugmail: http://bugzilla.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.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
