RE: PM-8200

> I think I have it working..
> 
> Took the long number, divided it by 52428800.0  (if I rig the 
> program to request every second exactly, it hits that # the 
> most).  If I take the result and add 315964784 and then my 
> GMT offset (currently 18000 seconds), I get a number that 
> matches the UTC value my machine currently has.
> 
> The 315964784 number confuses me, since if I'm doing the math 
> right, it should be 315964814.
> 
> 315964800 to conver the GPS->Unix epoch differences, and 14 
> to cover the leap second offset.  Maybe Sprint is off 30 
> seconds?  If I can find a way to force the phone to lock onto 
> Verizon, I'll see if it changes.

If you have code I can try it on verizon.

What do you see if you compare your PC time with your cell phone time are
they in sync?

This site http://wiki.tcl.tk/552 contains some interesting code about the
conversion.
It suggests that there are a few more leap seconds and shows how to query
new leap seconds dynamically.


Simon 



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642