Quote:
Originally Posted by Humpa
I get the same results with or without GPSGate. I have TomTom Navigator 6 installed, and I can only get a lock on satellites if I start GMM or LiveSearch first. And then after closing GMM, whatever 3rd party app I'm using will soon lose the lock again. But I use the term "GPS lock" loosely. GMM and LiveSearch get a good fix, but every other app I've tried just get random lat and long values every second - and they seem completely random and all over the globe every second.
|
Skywing, the author of the Valhalla Legends GPSserver, has a detailed article on how Verizon has locked down the GPS chip here:
http://www.uninformed.org/?v=10&a=4&t=txt
From reading his article it sounds like the GPS chip goes to sleep unless it has a successful periodic challenge/response exchange with a GPS application. It then starts sending out encrypted GPS data. Skywing's GPSserver does two things - it handles the periodic challenge/response exchanges required to keep the GPS chip awake and sending out encrypted data and it also decrypts the GPS data which it then forwards through the Windows Intermediate Driver. So I suspect what's happening is that running just TomTom (or any other GPS app that utilizes com ports for GPS Data) never even wakes up the GPS chip which is why it never gets a lock. But if you run GMM or Live Search (or any other app that utilizes the Windows Intermediate Driver for GPS data) first the GPSserver wakes up the GPS chip which causes TomTom to get a GPS lock. But the data on the Com port is still encrypted which causes the location to be random. If you then close GMM or LiveSearch the GPSserver stops handling the challenges/responses with the GPS chip and the GPS chip goes to sleep causing TomTom to lose GPS lock.
Using GPSgate to forward the decrypted GPS data from the Windows Intermediate Driver to a virtual Com port sounds like it should work but apparently isn't for some reason.