Thread Previous • Date Previous • Date Next • Thread Next |
On 29/02/16 21:29, Thomas Voß wrote:
so, if the app was coded perfectly, and the last known good position was 5 hours old and miles away, it would give the app the last known position, and the app would then decide it is too old, subscribe for updates and wait for a fix. That is the absolute best an app or web page can do if the platform is working as designed, make the human wait, or use a bad location. The app can't be written better because getting the first fix needs to be pushed back in time to shortly before the app starts. Incidentally giving a rubbish first fix also often means downloading a page full of completely the wrong map tiles, which means more making the human wait.With all due respect, this is not a bug in the platform. Are you, 2 other people, and others experiencing an issue? Certainly. Is the only way to fixing it to periodically wake up the phone? I don't think so as other mobile platforms get the job done without doing that. Did we make sure that no other layer in the stack is keeping around stale cached updates for longer than it should? I would be surprised, to be honest.
Alan.
Thread Previous • Date Previous • Date Next • Thread Next |