847511 - [B2G][OTA] After running OTA, device is stuck on unresponsive black screen.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[J Zimbrick]

Attachment: Logcat during OTA

Repro Steps:

1. Flash unagi device to build 201303031070201.
2. Perform an OTA update. (ours was to build 20130304070201.)
3. Install the update.
4. Observe that the phone restarts to a black screen with no options to do anything.  Holding the power button will bring up the power menu but all of the options are unresponsive.

Actual Results:

After performing an OTA update the phone displays a black screen, the user is unable to do anything with the phone until the battery is removed and reinserted.

Expected Results:

After performing an OTA update the phone restarts and launches in to the FTU, all buttons are functional.

Repro Frequency:

100%
2/2 Devices

Found on the following unagi build:

Gecko: c11d91e1b575
Gaia: d90ee5a412116f4f1f2e43b6c60700de5923513e
Build: 20130304070201

*Logfile during OTA is attached.

Comment 1

[Jason Smith [:jsmith]]

Marshall - Any ideas?

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Is this the correct logcat?  I think I see the browser being active on this...

Comment 3

[J Zimbrick]

Attachment: Second OTA Logcat

It seems that logcat may have been the wrong one.  Attaching a new logcat that begins at the OTA download and ends on the black screen, (also two presses of the power button while on the black screen.)

Hopefully this helps.

Comment 4

[Dave Hylands [:dhylands]]

From the logcat, I see that update channel changed. There were a couple of bugs related to this: bug 841041, bug 842932. Bug 842932 was only delivered to master.

It appears to have properly uncomrpessed and applied the update. If rebooting the phone boots up normally (you probably need to pull the battery), then I'd say that this is a dup of bug 842932.

Comment 5

[J Zimbrick]

*IMPORTANT*

Typo in step 1.

The correct build number is 20130301070201.

Full build details for step 1:

Gecko: ea3d5929ec68
Gaia: 3ad2a0445acb2057db75eb107ee64288f36c0ac6
Build: 20130301070201

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

The gecko revs in comment #5 are from the mozilla-b2g18 repo. The baked-in update channel for mozilla-b2g18 nightlies was changed in bug 846394, in the build after 20130301070201, from nightly to beta. So that does smell very like the bugs mentioned in comment #4.

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

The test case might be not quite what was intended. Taking a mozilla-b2g_v1_0_1 build before 2013030123xxxx and updating it on nightly to mozilla-b2g18 would make sense, as would taking mozilla-b2g18 >= 2013030123xxxx and updating it on nightly to another mozilla-b2g18. But the build used was too old for the latter test.

Comment 8

[Marshall Culpepper [:marshall_law]]

I've just renomed Bug 842932, since this is the 2nd time this has happened on our releng based update stream. I imagine this isn't supposed to happen frequently, but we really shouldn't be bricking on update channel changes.

@J Any way to confirm if pulling the battery and rebooting makes this problem goes away?

Comment 9

[Nick Thomas [:nthomas] (UTC+12)]

I agree it would be good to fix the channel change issue, but AFAIK this has only affected QA and not actual dogfooders.

Comment 10

[Michael Vines [:m1] [:evilmachines]]

(I don't see enough info here to make a tef? call yet so clearing flag)

Comment 11

[Michael Vines [:m1] [:evilmachines]]

(err..I didn't read the comments well enough!  but yeah, tef- based on comment 9)

Comment 12

[J Zimbrick]

Have not seen this issue since the build it was initially reported on, might have been some sort of one-off wonky build.

Perhaps this one can be resolved for the time being?

Comment 13

[Tracy Walker [:tracy]]

I have seen this flashing 0407 build then updating to today (0412).  It's not totally unresponsive in that you can get the power down screen to shutdown the device.  Then restart it and the device works fine.

see https://bugzilla.mozilla.org/attachment.cgi?id=736907 for log up to black screen.

Comment 14

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Do we have an update here? I'm seeing this issue each day meanwhile again. It's present after the update has been downloaded and an unknown amount of time at the beginning of the uncompression step.

Comment 15

[Dave Hylands [:dhylands]]

Can you provide a logcat for a recent case? It's possible that this is somehow related to bug 876308 (both this bug and that bug would make sense if something else is consuming lots of CPU)

Comment 16

[Wayne Chang [:wchang]]

qawanted for comment 14, is anyone else seeing this?
If anyone encounters this please provide build info and STR.

I haven't had trouble with my OTAs.

Comment 17

[Lukas Blakk [:lsblakk] use ?needinfo]

If this isn't presenting on shipping builds/OTAs it's not a leo blocker, please renominate if that changes.

Comment 18

[Jeni]

Unable to repro issue on 
Unagi Build ID: 20130604070205
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/997cdbf5d012
Gaia: 5534304aee934055f08f21ce93261ba2a596516a

and which OTA to unagi Build id: 20130603070207

also tested Leo Device with and unable to repro issue.. 
Leo Build ID: 20130506105248
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/00c554abfc17
Gaia: 94f03a82bc66ad04352d127747ca226368d96363

OTA to 20130604070205

After performing an OTA update the phone restarts and launches in to the FTU, all buttons are functional.

Comment 19

[BMO Automation]

Firefox OS is not being worked on