RIL: Figure out how to expose radio and network state to content

RESOLVED FIXED

Status

()

Core
DOM: Device Interfaces
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: philikon, Unassigned)

Tracking

Trunk
ARM
Gonk (Firefox OS)
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(blocking-kilimanjaro:+, blocking-basecamp:+)

Details

The RIL exposes information such as signal strength, operator name, etc. And then there's also the state of radio (Radio on? SIM card present? Network present? etc.) These aren't really settings since they're not manipulable.

Gecko-internally these are or will be exposed by nsITelephone (to be renamed to nsIRadioInterfaceLayer) so that the network manager (bug 697355) and others can observe them. Content will want to observe some of them, too, though, to display warnings such as "No SIM Card installed", update signal strength, show operator name, etc. Currently this is exposed on navigator.telephony where it doesn't belong.
(Reporter)

Updated

6 years ago
Version: 12 Branch → Trunk
Maybe we could add those privileged methods to the Network API?
Also a good idea, since for Wifi, there'd be analogous values (signal strength, SSID, etc.)
(In reply to Philipp von Weitershausen [:philikon] from comment #0)
> though, to display warnings such as "No SIM Card installed", update signal
> strength, show operator name, etc. Currently this is exposed on
> navigator.telephony where it doesn't belong.

They don't belong there because we want other apps to be able to access them, like status bar?  OK, makes sense.

(In reply to Mounir Lamouri (:volkmar) (:mounir) from comment #1)
> Maybe we could add those privileged methods to the Network API?

Do you mean as part of the privileged network-management API, or the unprivileged network-status API?  The4 former sounds OK to me.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #3)
> (In reply to Mounir Lamouri (:volkmar) (:mounir) from comment #1)
> > Maybe we could add those privileged methods to the Network API?
> 
> Do you mean as part of the privileged network-management API, or the
> unprivileged network-status API?  The4 former sounds OK to me.

As part of a privileged part of Network API.
Bug 729173 is about exposing information about the mobile network via the WebMobileConnection API.
Depends on: 729173

Comment 6

5 years ago
Blocks a blocker.
blocking-basecamp: --- → ?

Comment 7

5 years ago
Need for builtin apps to work.
blocking-basecamp: ? → +
blocking-kilimanjaro: --- → +
I think that for v1 this bug is covered by bug 729173 and bug 753170. Going to close this.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Depends on: 753170
Resolution: --- → FIXED
John, can you verify this, or find someone else who can/should?  Thanks!
(In reply to Stephen Donner [:stephend] from comment #9)
> John, can you verify this, or find someone else who can/should?  Thanks!

This bug has had no patch landed. Nothing to verify.
You need to log in before you can comment on or make changes to this bug.