Closed Bug 1033924 Opened 11 years ago Closed 7 years ago

[Flame] when geolocation coordinates are not available, FMD website shows spinning wheel indefinitely

Categories

(Firefox OS Graveyard :: FindMyDevice, defect)

Product:
Firefox OS Graveyard
Component:
FindMyDevice
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: njpark, Unassigned)

References

Details

(Whiteboard: [NPOTB])

Device: Flame When FMD is enabled on outdoors, the geolocation values are retrieved regularly. (gaia debug trace shows I/GeckoDump( 1443): [findmydevice] updating location to (43.84201574, -79.52919404) message every 10 seconds roughly) On the FMD website, refreshing the page sends the push notification to the device, and the device location is updated. When the page is not refreshed, the push notification is sent to the device roughly once every minute, and the phone updates its location once every min as well. When the device is moved to a location where GPS signal is not reachable, (I put it inside the washing machine in the basement) then it does not seem to respond to the push notification. The website shows spinning wheel indefinitely. Once the device is moved to the area where GPS signal can be reached, it sends out multiple location information at once it seems. The device location is updated correctly on the website. the logcat shows the following: /GeckoDump( 956): [findmydevice] findmydevice got push notification! I/GeckoDump( 956): [findmydevice] command t, args [60] I/GeckoDump( 956): [findmydevice] findmydevice got push notification! I/GeckoDump( 956): [findmydevice] command t, args [60] I/GeckoDump( 956): [findmydevice] findmydevice got push notification! I/GeckoDump( 956): [findmydevice] command t, args [60] I/GeckoDump( 956): [findmydevice] findmydevice got push notification! I/GeckoDump( 956): [findmydevice] command t, args [60] I/GeckoDump( 956): [findmydevice] findmydevice got push notification! I/GeckoDump( 956): [findmydevice] command t, args [60] (at this point, the device is moved to outdoors) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193372, -79.52920167) I/GeckoDump( 956): [findmydevice] updating location to (43.84193629, -79.52921047) I/GeckoDump( 956): [findmydevice] updating location to (43.84193628, -79.52921088) If the FxA account is logged in for the first time and FMD is activated in a location where GPS signal is weak or not present (i.e. inside the office building), then the geolocation icon does not appear in the status bar of the phone, and on the website, spinning wheel is shown indefinitely. Moving the phone near window sometimes updates the device with the location. - On a side note, if a phone gets reset on Developer menu, and logs into FxA account aferwards, it gets assigned with a new device id, even if this account was used on the same phone before the reset. This causes the website to list more than one device in the menu. - Even if geoloc values are not available, it still responds to lock, ring and erase command Question: - If geolocation values are not available due to the location constraint, should the FMD website display spinning wheel indefinitely as it does now?(Or should it time out after a while) - Can geolocation values be retrieved from cell data or wifi signal? (or is it the scope of 2.0?) I will try it with buri device tomorrow and report the differences.
We should probably report better status to the user for this case.
blocking-b2g: --- → 2.1?
See Also: → 1053452
removing for 2.1, server side fix, need to track this via github. ni? edwin to cross post issue.
blocking-b2g: 2.1? → ---
Flags: needinfo?(edwong)
Whiteboard: [NPOTB]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.