Closed
Bug 1030216
Opened 10 years ago
Closed 9 years ago
FMD Location Is Either Incorrect or Jumps Around
Categories
(Firefox OS Graveyard :: FindMyDevice, defect)
Tracking
(b2g-v1.4 wontfix, b2g-v2.0 affected, b2g-v2.1 ?)
RESOLVED
DUPLICATE
of bug 1018383
People
(Reporter: elan, Unassigned)
References
Details
(Whiteboard: [2.0-flame-test-run-3])
Attachments
(1 file)
Gecko/Gaia: June 25th STG: https://fmd.stage.mozaws.net/#devices/99f63ebe40e9be8e80d87c3c8338fc33
Reporter | ||
Comment 1•10 years ago
|
||
STR: 0) Sign Into FxA on Device/Web 1) See Location Indicator spin and settle 2) Location was correct once, then, when I invoked sound, it changed to incorrect location 3) I seem to be stuck in a state where device is now only being located, well, in the water Will continue to try to repro to see how varied the results are in a sample size of 10 attempts.
Reporter | ||
Comment 2•10 years ago
|
||
Not blocking until I have a the above repeatable pattern.
Comment 3•10 years ago
|
||
A few of us can hit this when testing find my device. nom'ing for blocking, since this is a highly dependent issue for the FMD feature. We can't have the website be telling the user its 1 mile away from where it should actually be, else they'll be diving into the ocean looking for it. Looking for help from the Geolocation team, as it's likely not FMD specific.
blocking-b2g: --- → 2.0?
Flags: needinfo?(gkeeley)
Comment 4•10 years ago
|
||
This can't block as we have little control over the location information or the configuration of the geolocation stack on FirefoxOS devices.
blocking-b2g: 2.0? → ---
Flags: needinfo?(gkeeley)
Updated•10 years ago
|
Blocks: geo-b2g-2.0
status-b2g-v1.4:
--- → wontfix
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → ?
Summary: Location Is Either Incorrect or Jumps Around → FMD Location Is Either Incorrect or Jumps Around
Comment 7•10 years ago
|
||
There's not much we can do for areas not covered by the MLS database, but MLS results should not jump from good to bad. That sounds like a bug Garvan fixed in 1.4. I'm looking for that fix.
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [2.0-flame-test-run-3]
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 8•9 years ago
|
||
Bug #1018383 implemented a fix for the location jumping.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•