Hi,
gpsOneXTRA has not been working since 2 weeks ago. Because of that , it takes so much time to cold start.
When devides download the gpsOneXTRA data, sometime we get ERROR, even when we get OK, wrong time was set such as '1980/01/06,00:00:00'.
We are getting same issues in xtra.bin and also xtra2.bin using chip sets MDM9206 and MDM6200.
Anybody getting same problems? How can we fix that ?
Thank you in advance.
We have also been getting this ERROR since November 3. We were originally using gpsonextra.net to download the xtra2.bin files, but all three servers (xtra1, xtra2, and xtra3) have expired data. We have now switched to the izatcloud.net, but even on these servers (xtrapath1, xtrapath2, xtrapath3) the xtra2.bin files have expired data. We finally found a file with a good date and time on xtrapath4.izatcloud.net. Why do so many servers have a bad date and time on their xtra2.bin files? How many servers do we need to query to guarantee we'll find one good file? Did the format of the files change?
Please help. We are exceeding our data allotment on our IoT cellular data plans
Edit on 12/18/19
- We eventually modified our embedded software to access the servers xtrapath4, xtrapath5, and xtrapath6.izatcloud.net. This seems to be working with validity lasting the full 7 days. Unfortunately, we had to reprogram almost 100,000 devices to fix this. Bad on data for IoT devices.
Thank you for the reply. I'm glad I'm not only one having this issue.
We are also using xtrapath4.izatcloud.net right now. But downloaded data only works for 4 hours or so. If you continue to use this data after 4 hours, you would not be able to catch GNSS. You have to download xtra2.bin file again from xtrapath4.izatcloud.net.
Any help would be greatly appreciated. We are also exceeding data allotment on our IoT cellular data plans.
This seems to be clearly tied in with the last GPS week rollover date on Nov 3. The "original" date for the rollover was in the spring, but some chips apparently have some offset on the date so it happened this month.
It seems that the http://xtrapath4.izatcloud.net/xtra2.bin address pushes new stuff out. We've updated a bunch of WWAN modems that have Qualcomm chips to patch the rollover issue, but as we use gpsOneXtra, what is the impact if the data is dated 1980? It would be nice to know what setup/config for gpsOneXtra is correct for patched devices.
Hi,
Any updates on this issue?
We are getting repeated downloads every 2 minutes of the xtra2.bin file. It is killing our IoT data plan.
One person mentioned a server that provides a file that lasts 4 hours.
Not sure if anybody found a complete solution for this issue.
Best,
Doron
Hi,
Has anybody been successful updatnig the GPS config file of an Android device to use the new URL?
We are changing the URLs and they are not being picked up.
Any other way?
Could it be that an LG phone hard codes these URLs?
Best,
Doron