821462 - [Updates] Phone won't wake from sleep after applying an update when USB connected (with Media Storage enabled)

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect, P2)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

This has happened twice now on 12-6 update and 12-12 update.  I have the phone plugged in so it's charging, USB media storage is enabled, and downloading the update starts as expected but by the time it completes, the screen is dark and I cannot wake the phone up.  I have to take out the battery, restart the phone, and then see that there is indeed a new build ID in Device Info.

Expected:

* If we are not supposed to either have the phone plugged in to USB and/or have media storage enabled then I would expect a warning of that when starting an update
* I would expect also to see an "apply update" option once it has completed downloading - again, if this is not what is intended then at least a sign that the phone is up to date on reboot might help here.

Comment 1

[Joe Cheng [:jcheng] (please needinfo)]

Triage: BB+, P2, C3 - severe usability issue

Comment 2

[Etienne Segonzac (:etienne)]

Might sound silly, but have you tried being really patient with the phone?
I mean pressing the power button *only once* then wait for ~10 sec.

Because if the phone eventually turns on (like I saw during my testing) this is probably due to the uncompressing/staging process having a too high priority. And I think we have plans to make that better.

Comment 3

[Marshall Culpepper [:marshall_law]]

(In reply to Lukas Blakk [:lsblakk] (away until Jan 14th, contact [e-mail]) from comment #0)
> * If we are not supposed to either have the phone plugged in to USB and/or
> have media storage enabled then I would expect a warning of that when
> starting an update

Media storage should only affect FOTA updates for now. dhyland's patches in Bug 785124 will also move OTA updates to the /sdcard by default, but this new code will also lock the /sdcard so the attached PC can not mount it. In other words, with this patch, a warning shouldn't be necessary.

> * I would expect also to see an "apply update" option once it has completed
> downloading - again, if this is not what is intended then at least a sign that
> the phone is up to date on reboot might help here.

When the platform sends the event for the install prompt, it also starts a 10 minute timer that automatically restarts b2g to apply the update when no response is received.

The assumption here is that either the device is not being used actively, or worse b2g has entered into a bad state where the user can't even see the prompt (which is what sounds like you're running into).

Do you happen to have a logcat capture from when this happened? I'm curious if this is indeed the update "apply" process eating up CPU, or something else.

Comment 4

[Etienne Segonzac (:etienne)]

(In reply to Marshall Culpepper [:marshall_law] from comment #3)
> Media storage should only affect FOTA updates for now. dhyland's patches in
> Bug 785124 will also move OTA updates to the /sdcard by default, but this
> new code will also lock the /sdcard so the attached PC can not mount it. In
> other words, with this patch, a warning shouldn't be necessary.

Probably safe to get out of gaia's umbrella :)

Comment 5

[Andrew Overholt [:overholt]]

(In reply to Marshall Culpepper [:marshall_law] from comment #3)
> Do you happen to have a logcat capture from when this happened? I'm curious
> if this is indeed the update "apply" process eating up CPU, or something
> else.

Can someone provide a logcat to Marshall?

Comment 6

[mlevin]

Could not reproduce. Performed the following steps:

Steps:
1. Started with Unagi build 20121126071306.
2. Plugged in Unagi to laptop via USB.
3. Enabled USB Mass Storage on Unagi.
4. Connected to Wifi.
5. Unagi found an update.
6. Prior to starting the download of the system update, set the screen timeout to 1 minute.
7. started the download of the system update.

Result:
Unagi screen went dark during the system update.
Short pressed the power button to wake up Unagi after waiting sufficient time for the full download.
Unlocked Unagi from the lock screen and saw the "Install Now" screen. 
Chose "now" and Unagi updated without any errors.

Conclusion:
Resolved/Worksforme

Comment 7

[mlevin]

Need to change this back to as close to "NEW" status since I was only suppose to comment on my findings of this bug, and not change the status. The original status was "NEW".

Comment 8

[JP Rosevear [:jpr]]

Lukas, did you see this on the 12-26 update?

Comment 9

[Tony Chung [:tchung]]

Environment: successful testing from 1/2 -> 1/3 OTA update, with USB setting connected. 

If this is truly FOTA related only, we need to create an environment to test this in; which is not a easy to setup case at this moment.  i'll leave myself assigned as qa-contact until we have a testable environment for FOTA updates.

Comment 10

[Andrew Overholt [:overholt]]

I'm taking this off the blocker list since it doesn't seem to be reproducible.

Marshall, if your update test infrastructure can help here, let's try to reproduce there.

Comment 11

[Lukas Blakk [:lsblakk] use ?needinfo]

Sorry, I was away on vacation and have not repro'd this - as Tony mentions in comment 9 we'll need a FOTA test env set up but this isn't a blocker for v1.0 afaict.

Comment 12

[Jeni]

Unable to repo on 
Unagi Build ID: 20130530070213
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/11b55d3ada71
Gaia: ac293ce59acc3bede083fad1b973794fa8bf0253

Following steps on comment 6 when screen went to sleep while downloading update was able to wake up, unlock and view what was happening with no issues.

Comment 13

[Jason Smith [:jsmith]]

Closing per comment 12. Reopen if you can still reproduce.