Openmoko Bug #2244: otimed is poorly designed/implemented in a way that affects its operation
Openmoko Public Trac
bugs at docs.openmoko.org
Sun Mar 1 13:39:17 CET 2009
#2244: otimed is poorly designed/implemented in a way that affects its operation
-------------------------+--------------------------------------------------
Reporter: BillK | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by mickey):
Thanks for your comments!
First off, ntp has not been rewritten. Second, ntp lacks critical features
that are necessary on systems such as a smartphone. E.g.
* getting time and timezone from GSM
* getting timezone based on the provider we are currently registered with
* getting time from GPS
Third, we did consider to extend ntp in the first place, but did not do
this yet since adding some logics in frameworkd to quickly improve the
user experience was a much lower hanging fruit. There is even task for
that in the FSO bugtracker [http://trac.freesmartphone.org/ticket/254],
albeit somehow slightly misnamed.
We will take your points into account for further work, especially
1.,3.,4.,5. seem reasonable to me. Oh by the way, you can disable otimed
or even individual time provider if you don't want it -- so I consider 2.
being fixed already.
If you have some time, we'd appreciate some ntp plugins that implement the
missing features. Also a dbus interface would be handy.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2244#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the devel
mailing list