Quote:
Originally Posted by TC1
Again, I'm going to have to disagree. All because something is on Wikipedia doesn't mean it's accurate. I'm a BSEE with over 25 years of digital chip, computer, software, and network design. I've talked to developers trying to crack the Sprint GPS issues.
You might get a better understanding of how aGPS works if you look at the mGMAPS web site. Look how the author there wrote the app, and for Sprint phones he specifically says "The QJAE GPS API (Sprint) was updated to prefer assisted-GPS over standalone GPS. This sacrifices accuracy for quicker fixes and more stable GPS positioning." Meaning that, yea, the application magically (as you put it) switches over to the aGPS system to get the lat and long coordinates if the stand-alone GPS receiver can't supply them.
Let's just leave it at we agree to disagree.
|
And just because one self-proclaimed expert says something doesn't mean he's accurate either.
aGPS may use triangulation as part of its data sources, but that doesn't mean that all triangulation (or more accurately trilateration) methods = aGPS. What Google is using for this system is not requiring any use of any aGPS chipset. The program only needs the phone to pass on some tower information. Which means that it isn't requiring any intervention on the part of the assistance server for it to function. Which would be why Google is able to offer this service without getting permission from Sprint, Verizon, AT&T, etc.
If you don't trust Wikipedia, then maybe another article might educate you better.
http://www.gpsworld.com/gpsworld/art...l.jsp?id=12287