Closed Bug 1032865 Opened 10 years ago Closed 5 years ago

Network location provider should try to send neighboring cell data

Categories

(Core :: DOM: Geolocation, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: hschlichting, Unassigned)

References

Details

The goal here is to send neighboring cell data as part of the location service queries in the NetworkGeolocationProvider, to allow trilateration of the device and provide much better position estimates. Currently only the serving cell is used, as RIL API's were missing to do non-destructive background scanning. This was originally opened as 1010356, which changed scope and was narrowed down to some of the required RIL changes. As part of the investigation two different RIL API's where discovered. As part of 1010356 one of them was implemented, 1032858 tracks the implementation of the other. The already implemented API exposes incomplete cell ids for GSM and UMTS networks. For location queries these aren't actually all too useful. As part of stumbling (984982) these could be used, but the value-add is also low. So I'd wait on 1032858 to get finished and use the new API's to get neighboring cell data for all network types (not just GSM/CDMA) with a much higher chance of getting complete cell ids via these APIs.
Bug 1032858 has landed, is ready to be fixed
Assignee: gkeeley → nobody
Depends on: 1035089
Turns out #1035089 isn't actually a blocker for this, so the implementation can go ahead and even use the newer API's introduced in #1032858.
Note the new function for this is connection.getCellInfoList
Blocks: 1010282

Marking inactive, unless there are new plans in the works to revisit wifi stumbling on Android.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.