05-03-2013 06:49 AM
We are using GPS for continous tracking of a user's sport activity. We've seen that we often receive GPS locations with a timestamp which is older than the last GPS position. How can this happen. Is this a known issue for a certain OS/firmware version? See below log file output for an example:
location_id,system_timestamp,gps_timestamp 1, 1365411706.215, 1365411798.411 2, 1365411707.120, 1365411778.916 3, 1365411708.108, 1365411780.918 4, 1365411709.091, 1365411779.268 5, 1365411710.094, 1365411790.599 6, 1365411711.131, 1365411817.781 7, 1365411712.114, 1365411815.035 8, 1365411713.185, 1365411873.108 9, 1365411714.170, 1365411870.984 10 ,1365411715.178, 1365411867.561
05-03-2013 09:08 AM
following information is needed to understand the issue better:
Exact model of the device you are using: there are differences between Dev Alpha A and B (and C), so we need to know: settings menu --> About--> General-->Model number
Also, can you please confirm the version of the OS you are running it on? The latest recommended versions are:
OS: 10.1.0.1485 (check on the phone in Settings / About / OS)
Also can you explain the trace you pasted. I can't see through that listing the error you are describing
05-05-2013 10:13 AM - edited 05-06-2013 07:44 AM
one phone model is STL100-2 with OS 10.0.10.90. How can we update to 10.1.0.1485?
The other one is BlackBerry 10 Dev Alpha, model number "Dev Alpha", OS 10.0.10.263.
Explanation of trace:
The 2nd value in each line is the phone's system timestamp (which increases about 1s for each line). The 3rd value is the GPS timestamp. It is not incremented constantly but is also decremented (even by some seconds, e.g. 20 seconds between line 1 and line 2) over time which is a bug obviously.
05-07-2013 06:19 AM
you will need to wait for the Z10 update until your carrier approved the recent build.
Dev Alpha B can be updated here: https://developer.blackberry.com/blackberry10deval
would be very interested to see if the issue will be there after the update.
I escalated the issue internally through the Android runtime team. Will get back to you soon.