Closed Bug 843660 Opened 12 years ago Closed 12 years ago

[B2G][Settings][Device Information]: Phone data not veiwable in settings>device information>more information

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.1 fixed)

VERIFIED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.1 --- fixed

People

(Reporter: amaxwell, Assigned: cjones)

References

Details

(Keywords: regression, Whiteboard: smoketest)

Attachments

(2 files)

Description: After updating build from Unagi Build ID 20130220093954 to Unagi Build ID: 20130221070203, OTA, device has missing OS Version, Firmware Revision, Hardware Revision, MAC Address, Platform Version, Build Identifier, and Update Channel. Repro Steps: 1) Updated, via OTA, from Unagi Build ID 20130220093954 to Unagi Build ID: 20130221070203 2) Go to Settings>Device Information>More Information 3) Observe device information Expected: Device information present and viewable Actual: Only IMEI, ICCID, and Git Commit data are available Repro frequency: 100% Environmental Variables: Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/effe37a77f18 Gaia: bb633c6f2deb829b2f3d5b9e7bac7fa24467d02a
Attached image Screen Shot
flagging for triage, as this is a regression, plus having this data available is useful to the user to report issues back to support line.
blocking-b2g: --- → tef?
Keywords: regression
Whiteboard: smoketest
Verified issue on Flash build, as well
Also a security issue - briefly enable Remote debugging for manual update - reboot - Remote debugging option not selected in UI; "Ok, it's off!" - $ adb lolcat -> fail, Remote debugging is still on
Severity: normal → critical
I don't know why yet, but then this bug occurs we don't call presetPanel() for the transitioning panel. I incidentally fixed that with what should be an optimization, but it breaks back navigation for another unknown reason.
Attached patch FIxSplinter Review
I don't quite understand the original patch, but this fixes the bug.
Attachment #716689 - Flags: review?(etienne)
Attachment #716689 - Flags: review?(21)
cjones, does this fix it for l10n languages as well? or is this an english only bug?
Assignee: nobody → jones.chris.g
Simply revert the change made by attachment 715105 [details] [diff] [review] solves the problem. The patch moved the "presetPanel" function from the "loadPanel" function to the "lazyLoad" function, which cause the sub panels not initialized when loaded.
Comment on attachment 716689 [details] [diff] [review] FIx Review of attachment 716689 [details] [diff] [review]: ----------------------------------------------------------------- r=me I filed bug 844027, because this is madness.
Attachment #716689 - Flags: review?(kaze)
Attachment #716689 - Flags: review?(etienne)
Attachment #716689 - Flags: review?(21)
Attachment #716689 - Flags: review+
Comment on attachment 716689 [details] [diff] [review] FIx Review of attachment 716689 [details] [diff] [review]: ----------------------------------------------------------------- r=me I filed bug 844027, because this is madness.
(In reply to Arthur Chen [:arthurcc] from comment #9) > Simply revert the change made by attachment 715105 [details] [diff] [review] > solves the problem. The patch moved the "presetPanel" function from the > "loadPanel" function to the "lazyLoad" function, which cause the sub panels > not initialized when loaded. Yep but does the display/sound panels work then? (with the proposed patch both the display/sound panels and the more info panel works)
You are right... revert the patch brakes display/sound panels :( Let's use the current patch.
blocking-b2g: tef? → tef+
There's room to be smarter about how we load settings values for undisplayed subpanels, but we critically need to fix this regression. https://github.com/mozilla-b2g/gaia/commit/0cacf1a7e57baaf5d6698c98a4dd8c7041d8d4ae
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
This patch does not apply on v1-train. This might work: cd gaia git checkout v1-train git cherry-pick -x 42fc37735805d493499f1f3e92223b9e41d39ae0 <fix merge conflict> v1.0.1: 42fc37735805d493499f1f3e92223b9e41d39ae0
Flags: needinfo?(jones.chris.g)
What a mess ... this fix depends on having everything bug 840322 landed :/.
Flags: needinfo?(jones.chris.g)
looks like all of the required changes were cherry picked to v1.0.1 [1] but not v1-train. Time to go down the git log rathole! [1] https://bugzilla.mozilla.org/show_bug.cgi?id=840322#c59
So what happened was that all four commits of 840322 landed on v1.0.1 but only three of four were landed on v1-train. Oddly, this bug is blocking-b2g:-, but was landed on v1.0.1 anyway. I have confirmed that landing the one commit that's not on v1-train does allow this bug to land cleanly. I've asked akeybl to clarify what the desired outcome of 840322 is regarding branch landings. Chris, should I push a delete (i.e. patch -R) on 42fc37735805d493499f1f3e92223b9e41d39ae0 for now?
I'm very desperate to take 840322 so let's wait for ex-post-facto approval, if something went wrong in the landing. (/me not sure anymore)
All data is now visible except Firmware Revision on: Unagi Build ID: 20130226070204 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/819504e27351 Gaia: 823ae4703347ceb585f5d2de764d9d4138a6e892
Firmware Revision data not visible as reference in comment 21
Status: RESOLVED → REOPENED
Keywords: smoketest
Resolution: FIXED → ---
v1-train: 11205fdbbb2514fa6c052c9a85e2f4c5456b6f6e
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Keywords: smoketest
Resolution: --- → FIXED
reopening per comment 22
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
was comment 21 testing gaia 1.0.1? incapacitated by govt work ATM so would appreciate help sorting this out.
This was broken before bug 840322 landed [1], so it's a separate old regression. Please file. [1] https://github.com/mozilla-b2g/gaia/commit/e162592daddad128ebf8d60c0beb564ca6d633c8
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
I still don't see this change in v1.0.1, is this not uplifted yet?
it should be : $ git branch -a --contains 42fc37735805d493499f1f3e92223b9e41d39ae0 remotes/b2g/v1.0.1 If you still see the issue could you please file a new bug ? This will help with commits...
Blocks: 852755
Resolved all data except "Firmware revision" on unagi build 20130319070203 Refer to https://bugzilla.mozilla.org/show_bug.cgi?id=852755 for firmware revision data
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: