Closed Bug 863395 Opened 12 years ago Closed 12 years ago

[B2G][inari][comril] Unable to turn on device after powered it off nor reboot

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
blocker

Tracking

(b2g18 unaffected, b2g18-v1.0.1 affected)

VERIFIED WORKSFORME
Tracking Status
b2g18 --- unaffected
b2g18-v1.0.1 --- affected

People

(Reporter: nkot, Unassigned, NeedInfo)

Details

(Keywords: smoketest)

Attachments

(2 files)

Description: The user is unable to turn on device after powering it off, Firefox OS splash screen appears for a second and then screen goes black, requires to flash device to recover Repro Steps: 1) Updated to Inari Build ID: 20130418070206 2) Turn on device 3) Longpress the power button to bring up reboot menu 4) Select Power off 5) Longpress the power button to turn on device Actual: Firefox OS splash screen appears for a second and then screen goes black Expected: Device is turned On successfully, homescreen is launched Environmental Variables: Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0c76ef5f8677 Gaia: 64d5096e1746bd4b08bc1bf69844d164ac961970 Notes: Repro frequency: 100%, 3/3 devices
blocking-b2g: --- → leo?
Attached file logcat
Turns out that it does turn on, it has a black screen and doesn't display anything.
It doesn't happen on leo w/ a leo build.
Using Commercial or Mozilla RIL? If Commercial RIL does it happen with Mozilla RIL as well? I think it might just be an issue with the Commercial RIL - doesn't seem to happen on Ikura using: Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/e0bab06d5d36 Gaia 9f537aa216f3c12725c8d1c5c9603370b6bc1c46 BuildID 20130418230203 Version 18.0
From what I can tell, the inari device is for v1.0.1 ship - so bumping to tef? for now while more investigation occurs.
blocking-b2g: leo? → tef?
(In reply to Marcia Knous [:marcia] from comment #4) > Using Commercial or Mozilla RIL? If Commercial RIL does it happen with > Mozilla RIL as well? > > I think it might just be an issue with the Commercial RIL - doesn't seem to > happen on Ikura using: > > Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/e0bab06d5d36 > Gaia 9f537aa216f3c12725c8d1c5c9603370b6bc1c46 > BuildID 20130418230203 > Version 18.0 Marcia, doesn't happen with Mozilla RIl, only Commercial RIL (tested on both on 4/18)
It happens to me on an Inari with the following build : Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/0c76ef5f8677 Gaia 64d5096e1746bd4b08bc1bf69844d164ac961970 BuildID 20130418070206 Version 18.0 I am able to turn on the phone again, I see the logo and then a blank screen. Adb shows that the device is on but the screen is completely blank, and flashing a new build on it is a failure.
blocking-b2g: tef? → leo?
Summary: [B2G][inari] Unable to turn on device after powered it off → [B2G][inari][comril] Unable to turn on device after powered it off nor reboot
This blocks our testing on the inari device; if it crashes, or reboots we have to reflash the device. Could someone in releng please take a look into this?
Also seen on Unagi, V1.1.0, 2013-04-19-070205 build, COM_RIL Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/82fdff82a2d0 Gaia a24cf9f35f7414402edda3aef16f1fdcea21d785
Note: for Inari, black screen occurs in 3/19 build after flash. Not sure if we want to track that separately or with this bug.
Severity: normal → blocker
I could be mistaken but I believe that the unagi should be expected as there were a lot of MMS changes and there is a mismatch of comril and gecko.
Can we reproduce this issue with Ikura device? Thanks.
Flags: needinfo?
blocking-b2g: leo? → tef?
This is working for me on ikura with 1.0.1 build, qawanted to check if this has been fixed in 1.0.1. Please renominate if this still occurs.
blocking-b2g: tef? → ---
Flags: needinfo?
Keywords: qawanted
i've tried this yesterday on a 20130426 nighty build. once you flash a nightly Inari build with commercial RIL, it only shows the FFOS splash screen and hangs there. if i remove the system/b2g/distribution directory and reboot, the device comes up correctly. Unfortunately, doing this step means i'm reverting back to mozilla RIL. So the moz ril build starts up the build, but the commercial RIL leaves me stuck on splash screen. Build tested: Commercial RIL: ril01.00.01.019.087 Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/54285d67454b Gaia c47ef39de04e634d847cc86b6acc616fabce69eb BuildID 20130426070207 Version 18.0 Mvines or vincent, any thoughts?
Flags: needinfo?(vyoung)
Flags: needinfo?(mvines)
You're probably suffering from the uncontrolled landing of bug 828307
Flags: needinfo?(mvines)
Keywords: smoketest
Hmmm...yeah that Gecko/cRIL combo is actually really close. Is there *any* way I can get access to your builds? That would make debugging so much easier.
(In reply to Michael Vines [:m1] [:evilmachines] from comment #16) > Hmmm...yeah that Gecko/cRIL combo is actually really close. Is there *any* > way I can get access to your builds? That would make debugging so much > easier. i've provided michael with a hamachi and inari build from today's nightly. John O'Duinn's looking into how mozilla can share future builds with you guys. And the public manifests already exist as needed. Let us know anything else on how we can help you help us. Thanks.
(In reply to Daniel Coloma:dcoloma from comment #13) > This is working for me on ikura with 1.0.1 build, qawanted to check if this > has been fixed in 1.0.1. Please renominate if this still occurs. Working fine on latest Inari v101 commercial RIL. Going to remove keyword "qawanted". Tested on: Environmental Variables: Commercial RIL Inari Build ID: 20130502070201 Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/5c1d67e0c242 Gaia: 11477c127ae9be5051e4cfbcbf3da1d4150f9967
Keywords: qawanted
This seems to work for me now. I am guessing that the ril's didn't match. Gecko http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/5c1d67e0c242 Gaia 11477c127ae9be5051e4cfbcbf3da1d4150f9967 BuildID 20130502070201 Version 18.0 Inari
Seems to work correctly now in turning on. FYI, if you are getting stuck while flashing, try flashing ics before flashing the commercial ril. You should be able to flash the commercial ril build after.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
verified that issue does not repro on: Inari Build ID: 20130603070207 Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/4785b1353fd7 Gaia: 4de4354e3a99f151a834743c7b03a041ac8db12f
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: