Closed Bug 999690 Opened 12 years ago Closed 11 years ago

[B2G][Open_C][1.4] Hard or soft reset sometimes causes device to get stuck on Firefox OS animation screen

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: nkot, Assigned: nhirata)

Details

(Whiteboard: [b2g])

Description: Seen on today's 1.4 Open_C - device sometimes gets stuck on Firefox OS animation screen after fresh flash or if pulled the battery out right after finished FTU. Open_C base - P821A10-ENG_20140410 Gecko/Gaia - from pvtbuilds, mozilla-aurora-flame Flash script - flash_Gg.sh Repro Steps: 1) Manually flash Open_C to BuildID: 20140422000202 2) Complete FTU 3) Pull the battery out 4) Put the battery in 5) Power On device Actual: Unable to pass Firefox OS animation screen, device gets stuck and requires rebasing to recover Expected: Able to pass Firefox OS animation screen and use device Environmental Variables: Device: Open_C BuildID: 20140422000202 Gaia: 26432916d10434103a822f17be4624a342cadfba Gecko: 211431128e5b Version: 30.0a2 Base: P821A10-ENG_20140410 Notes: - device might get stuck on animation screen right after flashing - have to rebase device to recover (!) - doesn't happen on master, only 1.4 Repro frequency: 30%
I have a suspect that it might be the way we flash. 1.4 from gaia repo seems to be working fine. I'm assigning to myself to investigate.
Assignee: nobody → nhirata.bugzilla
Whiteboard: [b2g]
jsmith asked me to test this on the Flame - at least on today's master build I don't see the issue - I flash the phone, run through the FTU - pull battery -> phone restarts fine. I also tried resetting the device using yesterday's Flame build and the device also restarted fine.
It has to do with the script. I think between Peter and I we had this figured out. Please open a new bug if this occurs again.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.