razor2k wrote:And I'll just add that GPS on Android pretty much sucks from my experience
I'd have to agree with you on that. About halfway through Pennsylvania on 80, my GPS dropped on my phone(with full signal). However, my car had perfect GPS tracking (I use Waze to supplement my cars anti-social GPS). But, that could also be contributed to by my location in the mountainous hill side
AlanOfTheBerg wrote:This is on a feature request/bug list for Waze (community-built, so it's unofficial) to implement caching of the reports. The "re-report" thing isn't true. You can't report it later because now you've moved past the location.
Yeah, that's why I said to have it short-lived. Useless to report this thing an hour or so later. But, five to ten minutes seems reasonable. And thank you for pointing out that it's in a bug report. I will be checking that out
razor2k wrote:This Is something I have noticed for awhile. Although I believe it may have something to do with where your GPS "thinks " you are at that time.
Sometimes I can be 1000+ feet away and the countdown starts....other times I can go just past the report before it begins counting down.
It's never really bothered me personally....I just attributed it to GPS error. But could there be something to it?
I've noticed it actually start the "time-out" timer perfectly with the report and other times, 1000 ft too early. But, the thing is that it still is counting down the amount of feet until you actually arrive to the reported item.