11/09/2009, 12:28 PM
First off, the differences between the various aGPS modes is how you find the satellites. That's it. So whether you use aGPS, standalone, or cached, you're using the same satellites and the same data.
Originally Posted by antiphon
Now there could be one of a couple different things here going on.
- Since the tweak, your device is picking up a lot more sats. Because of the reflection from the buildings in down town San Fran, some of those signals are not going to be accurate. So instead of picking up only a couple of the strongest signals (which happen to not be reflected) you're picking up multiple signals and the reflected ones are confusing the device.
- AFLT is causing the positioning to be off.
- It's a problem with Sprint Nav.
So here's how to troubleshoot:
- Eliminate the easiest first, Sprint Nav. Try using Google Maps. Does it do the same thing? Check ##gps# and screen cap and post the results.
- Go back into QPST and uncheck AFTL and AFLT/GPS Hybrid. This will disable the AFLT mode and put you into pure GPS. Try Sprint Nav and see if it does the same thing. If it does, go back to step 1.
Try those and report back.
Keep in mind a couple of things.
Originally Posted by trim81
One, this is the exception, not the rule. The vast majority of people have had nothing but success with this tweak. I've personally applied it on 3 phones now, and seen nothing but good come of it.
Secondly, this very well may simply be a problem with the location. GPS is notoriously unreliable in high rise areas due to the problems with reflection (properly called multipath). There have been whole new applications and formula's that have cropped up for dealing with multipath. It's a complex and not easily solved issue.
Finally, this tweak can easily be undone if it doesn't work for you. If you don't like it, you can easily go back into QPST and undo it, no big deal.