Closed scubadunc closed 1 year ago
TomTom apparently stopped the service of providing the emphemeris files. As you can read in #33 TomTom apparently provided the emphemeris files provided by the GPS chip supplier. However, we find another source for providing these files. So far I didn't find such a source. So if have an alternative...
Ah! TomTom still provides the ephemeris service. Only the configuration service needed where to find this ephemeris service is no longer available. I hardcoded the ephemeris service URL in the code. We have to test if it works for all models, but I would suppose so.
Config service: https://mysports.tomtom.com/service/config/config.json Ephemeris service: https://gpsquickfix.services.tomtom.com/fitness/sifgps.f2p{DAYS}enc.ee
Hope they keep it alive for a while...
Amazing work...Will you provide an updated zip file for download with the updated code? v1.91 perhaps?
I'll make a release one of these days...
This is fantastic, I've just discovered this as about to set off for a run. Thanks so much for your work on this.
Of course we do not know how long TomTom will continue to provide these ephemeris files... :-( We still need a second source. So if anyone knows another source, let me know.
I would suggest to use some kind of setting accessible from UI or config text file for ephemeris URL. Anyway, THANKS for your volunteer work on abandoned device that you don't even own.
Might this be another source for the ehemeris files: https://choaristudio.com/
Thanks for your work on this project.
Wondering if this is of any relevance to the issue as another source of ephemeris file: https://github.com/felixge/node-ar-drone/issues/74#issuecomment-179910549
Would be nice a new release with eph file working, I don't think that tomtom is gonna close that backend service, maybe there are gps units using it 🤞
Thanks. The choaristudio file is not identical to the TomTom file. I can try it though... The parrot.com file nmainil refers to doesn't seem to work any more...
Also see #33
Thank you very much. Apparently I did not test well enough... I'll try again. If so, we've got a backup :-)
BTW Release 1.10 binaries on my blog
Thank you very much. Apparently I did not test well enough... I'll try again. If so, we've got a backup :-)
BTW Release 1.10 binaries on my blog
The files from TomTom and ChoariStudio WERE different until the end of October, more or less. Since the beginning of November though, they are identical.
I started using the files from the ChoariStudio recently and they are probably working ok (even the 14 days file!). However, I will have to test it some more, because I am using my watch in similar locations all the time and also the watch seems to cache the AGPS data somehow(?). One thing is, on my watch I originally found TWO identical files 0x00010100.bin and 0x00010102.bin with the same data from the .ee file. Second, even if I delete both files from the watch it keeps showing the ok sign (the check mark) in the AGPS status. Thus, I'll have to use the ChoariStudio files for longer and also use the watch farther from home to see if this really works.
By the way, I reconfigured my watch (without changing the program) by setting
Because the ChoariStudio has files for 1,3,5,7 and 14 days maybe the program could allow setting all those values in "quickFixDays" in the config? So far it only allows 3 and 7.
http://gpsquickfix.services.tomtom.com/fitness/sifgps.f2p7enc.ee http://choaristudio.com/agps/agps/f2p7enc.ee http://mail.hieroglyphe.net/agps/agps/f2p7enc.ee
All identical - checked with: https://www.duplichecker.com/page-comparison.php
@mike5x3 I just downloaded at 20:10 hours the files from TomTom (3, 7 days), choaristudio.com (1, 3, 7 and 14 days) and hieroglyph.net (1, 3, 7 and 14 days) and I find
Files are provided by the chip supplier at midnight. So you might expect that TomTom (or the other two) could be stale...
However... I tried the 3 day choarstudio file (and hence the hieroglyp file) in the TomTom watch and it resulted in a fix after 42 seconds. I tried the 7 days TomTom file on another watch: fix after 9 seconds Consistent with earlier measurement I did under #33
Of course not very statistical but it seems choarstudio and hierglyp are for another chipset or so... Maybe for Sirf IV iso Sirf V which is used in the TomTom.
Could you please verify your findings?
I made a script that downloads all the ephemeris files from all sites every hour, to check whether refresh time is the issue... I'll let you know...
http://gpsquickfix.services.tomtom.com/fitness/sifgps.f2p7enc.ee http://choaristudio.com/agps/agps/f2p7enc.ee http://mail.hieroglyphe.net/agps/agps/f2p7enc.ee All identical - checked with: https://www.duplichecker.com/page-comparison.php
@mike5x3 I just downloaded at 20:10 hours the files from TomTom (3, 7 days), choaristudio.com (1, 3, 7 and 14 days) and hieroglyph.net (1, 3, 7 and 14 days) and I find
- choaristudio files and hieroglyph files are identical, name and content
- TomTom files differ from the other two, though their file structure and size seems to be the same and the contents for the most part but not entirely
Files are provided by the chip supplier at midnight. So you might expect that TomTom (or the other two) could be stale...
However... I tried the 3 day choarstudio file (and hence the hieroglyp file) in the TomTom watch and it resulted in a fix after 42 seconds. I tried the 7 days TomTom file on another watch: fix after 9 seconds Consistent with earlier measurement I did under #33
Of course not very statistical but it seems choarstudio and hierglyp are for another chipset or so...
Could you please verify your findings?
I'll try again tomorrom morning: maybe TomTom and the others update the files at different times...
Yes, the TomTom file is stale:
curl -iks -X HEAD http://mail.hieroglyphe.net/agps/agps/f2p7enc.ee | grep Last-Modified Last-Modified: Mon, 06 Nov 2023 19:24:33 GMT
curl -iks -X HEAD http://choaristudio.com/agps/agps/f2p7enc.ee | grep Last-Modified Last-Modified: Mon, 06 Nov 2023 19:24:33 GMT
curl -iks -X HEAD http://gpsquickfix.services.tomtom.com/fitness/sifgps.f2p7enc.ee | grep Last-Modified Last-Modified: Mon, 06 Nov 2023 16:12:06 GMT
Yes, the TomTom file is stale:
Not really. The TomTom file is (and has always been) generated every four hours at 00:12, 04:12, ..., 20:12 GMT. This does not seem to have changed recently.
The choaristudio is updated more frequently, but also more irregularly (see choaristudio_updates.txt for timestamps of updated files). I discovered, that choaristudio and tomtom sometimes differ and sometimes not, but I do not see any regularity (see choaristudio_differences.txt). NOTE: All timestamps are GMT+1 (my TomTom update hours are 01:12, 05:12, ..., 21:12).
Clear! I find the timestamps of the update of choaristudio and hieroglype to be the same to the second. This might mean:
Since the timestamps differ from the tomtom timestamps I guess option 2...
Both choaristudio.com and hieroglyphe.net resolve to the same IP address: 198.100.148.158. Even though you can have multiple virtual WWW servers hosted at the same IP, I just assume they simply point to the same server and thus the files should be exactly the same.
Indeed same people behind the two domain name.
https://who.is/whois/hieroglyphe.net https://who.is/whois/choaristudio.com
French guy it looks like, I speak french, would be nice to know where he gets the file from :D
The choaristudio makes android games that use the GPS :)
The choaristudio makes android games that use the GPS :)
That's strange, because Android uses lto.dat files for A-GPS, not .ee files.
I send a mail to choaristudio asking for information about the origin of the ephemeris files but they don't appear to respond
thank you so much for providing this workaround. you cant possibly imagine how much it means to me
This can be closed.
As of yesterday afternoon, the GPS quick fix no longer connects. Is there any workaround?