Quote:
Originally Posted by insol
I was just testing my GPS priming to make sure things were working well enough to be posted and I discovered something interesting. If I prime the GPS (my app will provide GPS status info on the screen, if told to remain open) then go into TomTom it works great (and has been working for me for a while now). I never turn off my radio tho.. and I pretty much always have cell coverage.
Well, I just tried to see if everything works without the cell radio on (no data connection possible) and while my app gets the GPS sats and positions, TomTom never does (or at least didn't in the 3 minutes I gave it to lock in sats). This happens even if my app is run first or even after TomTom is already running.
Despite this problem, assuming you have coverage/cell radio on, I don't have any trouble with TomTom and my app... However this radio off experience would suggest that my app is not necessary, if a data connection is available.
I will post the app tonight either way... and provide details on its use.
|
see my post on this thread from 3/24.
The issue is not priming as in kicking gps with agps , from my tests,
it is priming in the sense of tomtom being unable apparently to actually start a gps session of any kind on its own. (unline Garmin, navigon and a dozen programs which do start the treo pro gps in both standalone with radios off or in agps)
Let's separate the issues which people use the term priming for on threads here, in xda and ppc:
1) Programs initiating/starting GPS (not a problem on treo pro, but a problem with tt6&7 on many/all ppc)
2) GPS api/port handing within windows (not a problem on treo pro)
3) triggering agps (not a problem on treo pro)
4) maintaining current ephemeris in cache (not a problem on treo pro)
#3 and #4 is not an issue. Trep Pro seems to try agps and if not it will use stored ephemeris and almanac and f not present and current download them from the birds. ie its default behavior seems pretty optimal already.
#2 was an issue with 800w. this was solved with gps gate on 800w, which not only started gps but acted as kind of a port handler. This is not an issue with Treo Pro CDMA since if you test it you can see tomtom7 works without gsgate and what is more tomtom7 will work on either "built in gps receiver"
or on "other nmea gps receiver"
#1 is the only issue as far as I can tell for TT7. TomTom simply will not or has no way to start the Treo Pro GPS receiver. Once started it wokrs ok -- even if it reports no receiver (pointing to some kind of internal handling issues).
Here is my test to determine this using "efficasoft gps utilities" and tt7.
Test A:
-turn handset to airplane mode
- reset Treo
- Turn on tomtom
- place treo pro in optimal outdoor conditions
Result: no fix after several hours. Tom tom reports "no gps device", and reports no positon movment
Test B:
- Turn handset to airplane mode
- reset treo
- Start efficsoft gps utilities (or one of several other non net dependent gps utlities)
- gps utilties will get fix in standalone on Pro from a) 5 seconds hot, to b) warm start of 20-60 seconds, to c), cold of about one to two minutes
- start tomtom after starting efficasoft gps utilites.
- Tom tomt will report no gps device and no gps fix,
but start walking or driving and you will see in fact tomtom is getting and using a fix and it is fine.
If this testing is correct, and others can verify, what we need for tomtom, and probably igo, (but not garmin, navigon, googlemaps or livesearc) is to determine a gps utiltiy or program that:
a)has the smallest footprint
b)is highly stable
c)does not require a net connection
d) automatically aquires gps (with efficasoft you have to go inot its menu and "start gps"
e) is amenable to running in a string that can also start tomtom
f) is free
Efficasoft: requires two key taps after start, costs
geoterrestrial on today screen: seems a bit unstable to me
Again this is only for tomtom and igo.