This is Gecko part work for bug 874796, user story for enable/disable Cell Broadcast.

In latest update in bug 874796 comment 8, "All channels - emergency and non-emergency channels should be switched on/off with this single option as per agreement with Operator." We'll introduce a new boolean, default false, Settings entry "ril.cellbroadcast.disabled" to turn off Cell Broadcast completely even with non-empty CBMI/CBMID/CBMIR/MMI ("ril.cellbroadcast.searchlist") settings.

Blocking a blocker, marking it leo+ .

Refactor setDebugEnabled to setInitialOptions. We always need a way to pre-set some parameters to ril_work at the very beginning stage. DEBUG flag and CLIENT_ID are two examples. Another new parameter, Cell Broadcast Disabled, is going to be added in the second patch.

Implement "ril.cellbroadcast.disabled" that works as both Settings and Preference. This parameter suggests RIL to disable CB function as possible. On failure to disable/enable CB, the preference will not be rolled back to its original value.

Comment on attachment 759350 [details] [diff] [review] m-c patch 2/2 Review of attachment 759350 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/system/gonk/RadioInterfaceLayer.js @@ +1953,5 @@ > let setting = JSON.parse(data); > this.handleSettingsChange(setting.key, setting.value, setting.message); > break; > + case kPrefenceChangedObserverTopic: > + if (data == kCellBroadcastDisabled) { can we use === ?

1) address review comments 2) fix unable to deactivate CB when search list is completely empty.

https://hg.mozilla.org/projects/birch/rev/2fee4d3f4941 https://hg.mozilla.org/projects/birch/rev/fb94126589a7

https://hg.mozilla.org/mozilla-central/rev/2fee4d3f4941 https://hg.mozilla.org/mozilla-central/rev/fb94126589a7

https://hg.mozilla.org/releases/mozilla-b2g18/rev/077f6ed61541 https://hg.mozilla.org/releases/mozilla-b2g18/rev/bb6c9375f53b

https://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/077f6ed61541 https://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/bb6c9375f53b

Hi Vicamo, why are you toggling on the preference rather than the setting? The situation seems very similar, if not the same, as ril.radio.disabled but the solution is different. Why is that?

(In reply to Michael Schwartz [:m4] from comment #13) > Hi Vicamo, why are you toggling on the preference rather than the setting? > The situation seems very similar, if not the same, as ril.radio.disabled but > the solution is different. Why is that? Because desktop Firefox may not have Settings correctly setup. We map Settings entries to preferences whenever possible so that we may implement that same function on desktop some day.