Openmoko Bug #1824: FSO: GPS time not available in TangoGPS

Openmoko Public Trac bugs at docs.openmoko.org
Thu Nov 13 21:30:32 CET 2008


#1824: FSO: GPS time not available in TangoGPS
------------------------+---------------------------------------------------
    Reporter:  hedora   |        Owner:  alphaone  
        Type:  defect   |       Status:  in_testing
    Priority:  normal   |    Milestone:  FSO       
   Component:  unknown  |      Version:            
    Severity:  normal   |   Resolution:            
    Keywords:           |     Haspatch:  0         
   Blockedby:           |    Estimated:            
 Patchreview:           |     Blocking:            
Reproducible:           |  
------------------------+---------------------------------------------------
Changes (by alphaone):

  * status:  assigned => in_testing
  * haspatch:  => 0


Comment:

 Time report works well as soon as the GPS has current UTC time. GPS time
 is acquired pretty fast, but UTC parameters take considerable more time to
 update. Once we got the UTC parameters and (most important) the amount of
 leap seconds that UTC and GPS time are off we should get the time much
 faster on subsequent attempts (it should be instantaneous since we write
 the time back to the GPS chip).

 You might need to let the FR sit with GPS enabled for quite a while to the
 the current UTC time, but then tangoGPS will show it.

 Note that the system time needs to be correct for this to work. If it
 isn't then the time reported by the GPS chip will also be off by the same
 amount.

 Please test with milestone4 and report back.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1824#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the buglog mailing list