TomTom saw this behavior while testing the app on the road using a Flame 1.3 and 2.0. "If we lose GPS signal for a long time, like in a tunnel and when GPS signal returns the position is never updated again through navigator. The position watch stays active but the position never gets updated again when GPS signal returns." This is blocking their turn-by-turn navigation feature.
ni? doug as he is subject-matter expert I know about geolocation.
Help from Vishy to find ni?. This is a bad bug that might not have been found because we are not developing and testing our own maps app.
Can't repro. Just tested this on Flame with m-c build. This is using the mozilla geo stack, using the 'Geoloc' engineering build test app which has a watchPosition() test. Stuck the phone in the dryer -not running :)- where I know no GPS signal is reaching the device, and pulled it out after a minute or so and GPS watchPosition updates continued. Confirmed geolocation was non-network geolocation based on accuracy reported <30m. May be a QC geo stack bug. Adding qawanted to see if we can get this checked on a Flame with QC geo/ril modules.
This was tested on a Flame 1.3.
harald is tom tom still seeing this behavior?
Flags: needinfo?(vkrishnamoorthy) → needinfo?(rdandu)
Naoki, Can we test this scenario on Flame with QC Geolocation stack? From Garvan's comment 3 it was not reproducible on latest Master with Moz Geolocation stack.
Flags: needinfo?(rdandu) → needinfo?(nhirata.bugzilla)
Flame 1.3 has old code and geolocation has changed since then. We need to test on a newer build. I haven't seen this on the newer builds as of yet. Still testing when I can on this scenario. Fred, please use an aries or flame device with the newer 2.6 builds on it please.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.