Last Comment Bug 713849 - RIL: Figure out how to expose radio and network state to content
: RIL: Figure out how to expose radio and network state to content
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: DOM: Device Interfaces (show other bugs)
: Trunk
: ARM Gonk (Firefox OS)
: -- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: webmobileconnection 753170
Blocks: b2g-ril
  Show dependency treegraph
 
Reported: 2011-12-28 06:32 PST by Philipp von Weitershausen [:philikon]
Modified: 2012-06-25 16:16 PDT (History)
12 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---
+
+


Attachments

Description Philipp von Weitershausen [:philikon] 2011-12-28 06:32:12 PST
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.
Comment 1 Mounir Lamouri (:mounir) 2012-01-04 06:29:49 PST
Maybe we could add those privileged methods to the Network API?
Comment 2 Philipp von Weitershausen [:philikon] 2012-01-04 10:49:29 PST
Also a good idea, since for Wifi, there'd be analogous values (signal strength, SSID, etc.)
Comment 3 Chris Jones [:cjones] inactive; ni?/f?/r? if you need me 2012-01-04 14:36:50 PST
(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.
Comment 4 Mounir Lamouri (:mounir) 2012-01-05 02:10:28 PST
(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.
Comment 5 Philipp von Weitershausen [:philikon] 2012-02-23 06:37:14 PST
Bug 729173 is about exposing information about the mobile network via the WebMobileConnection API.
Comment 6 JP Rosevear [:jpr] 2012-06-19 07:21:38 PDT
Blocks a blocker.
Comment 7 JP Rosevear [:jpr] 2012-06-19 13:12:48 PDT
Need for builtin apps to work.
Comment 8 Philipp von Weitershausen [:philikon] 2012-06-19 18:38:56 PDT
I think that for v1 this bug is covered by bug 729173 and bug 753170. Going to close this.
Comment 9 Stephen Donner [:stephend] 2012-06-25 16:13:24 PDT
John, can you verify this, or find someone else who can/should?  Thanks!
Comment 10 Philipp von Weitershausen [:philikon] 2012-06-25 16:16:18 PDT
(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.

Note You need to log in before you can comment on or make changes to this bug.