Closed Bug 909266 Opened 12 years ago Closed 11 years ago

[wasabi] Roaming preference setting will not be saved if reboot DUT right after change the setting.

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+, firefox29 fixed, b2g-v1.3 verified)

VERIFIED FIXED
1.3 C1/1.4 S1(20dec)
blocking-b2g 1.3+
Tracking Status
firefox29 --- fixed
b2g-v1.3 --- verified

People

(Reporter: echu, Assigned: arthurcc)

References

Details

(Whiteboard: [FT:RIL])

Attachments

(3 files)

Attached file before reboot logcat.
Roaming preference setting cannot be saved after reboot. It will be restored back to "Any". * Build Number Gaia: f94d4a9b56e8cc253089fe5ff680eb3cde303243 B-D 2013-08-26 02:13:16 Gecko: f216c745e68da490fd5591991398092d56d35294 BuildID 20130826061633 Version 26.0a1 * Reproduce Steps 1. Set Roaming preference to any item other than "Any". 2. Reboot device. * Expected Result New roaming preference setting should be saved even reboot device. * Actual Result Back to "Any" * Occurrence rate 100%
blocking-b2g: --- → koi?
Blocks: 890809
Whiteboard: [FT:RIL]
Assignee: nobody → arthur.chen
Need to fix it in v1.2
blocking-b2g: koi? → koi+
Update title, it's the same as bug 913326 that setting is not saved if reboot right after udpating the setting.
Summary: [wasabi] Roaming preference setting will be restored back to "Any" item after reboot DUT. → [wasabi] Roaming preference setting will be saved if reboot DUT right after change the setting.
Move to v1.3 since no requirement for CDMA in v1.2
blocking-b2g: koi+ → 1.3?
according to triage result, changed to 1.3+
blocking-b2g: 1.3? → 1.3+
Target Milestone: --- → 1.3 Sprint 6 - 12/6
This is similar to bug 913326. Does gecko keep the setting?
Flags: needinfo?(htsai)
No, gecko doesn't...
Flags: needinfo?(htsai)
Summary: [wasabi] Roaming preference setting will be saved if reboot DUT right after change the setting. → [wasabi] Roaming preference setting will not be saved if reboot DUT right after change the setting.
Target Milestone: 1.3 Sprint 6 - 12/6 → 1.3 C1/1.4 S1(20dec)
As we stop using mozSettings to control the hardware and gecko does not store the hardware states after restart, we need to store the user preferences in mozSettings and call gecko API accordingly when restart. For example, voice privacy in bug 913326, roaming preference in the bug, preferred network types...etc. Instead of having a helper for each API, I would like to introduce a more generic helper in the patch. The behavior of the helper is the same as the one created in bug 913326 (VoicePrivacySettingsHelper) bug with more generic methods. Could you help provide some feedback? Thanks.
Attachment #8351357 - Flags: feedback?(alive)
Attachment #8351357 - Flags: feedback?(alive) → feedback+
Comment on attachment 8351357 [details] Link to https://github.com/mozilla-b2g/gaia/pull/14957 Alive, Jose, could you help review the patch? Thanks! As comment 8, I added a generic SettingsHelper and replaced the original VoicePrivacySettingsHelper with it. The logic of SettingsHelper is almost the same VoicePrivacySettingsHelper but with more general APIs.
Attachment #8351357 - Flags: review?(josea.olivera)
Attachment #8351357 - Flags: review?(alive)
Comment on attachment 8351357 [details] Link to https://github.com/mozilla-b2g/gaia/pull/14957 (In reply to Arthur Chen [:arthurcc] from comment #10) > Comment on attachment 8351357 [details] > Link to https://github.com/mozilla-b2g/gaia/pull/14957 > > Alive, Jose, could you help review the patch? Thanks! Sure, but I'd like to remark that I don't have a CDMA to test the patch. > As comment 8, I added a generic SettingsHelper and replaced the original > VoicePrivacySettingsHelper with it. The logic of SettingsHelper is almost > the same VoicePrivacySettingsHelper but with more general APIs. LGTM, thanks for the work. Left some comments, check them out please.
Attachment #8351357 - Flags: review?(josea.olivera) → review+
Thanks for reviewing! master: 3b603d6adb6b92df347f953e22e4c5f35927c97d
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I was not able to uplift this bug to v1.3. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1.3, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1.3 git cherry-pick -x -m1 3b603d6adb6b92df347f953e22e4c5f35927c97d <RESOLVE MERGE CONFLICTS> git commit
Flags: needinfo?(arthur.chen)
v1.3: 2df82d7715cd44d2b6a580e6b7854b3017d4c6a9
Flags: needinfo?(arthur.chen)
Verified on Wasabi Gaia 7fc5eb67ff0aedbeb6874f670891e8e9b4505a16 Gecko 2b1732ba02eb74ec81f54f19cd9ef81da6c12844 BuildID 20140116100919 Version 28.0a2
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: