1036496 - [B2G][2.0]Device displays black screen on launch after flashing to 07/09 build

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect)

Description

[Ross Kuhlman ([e-mail])]

Device displays non-interactable black screen after flashing to 2014-07-09 build. The only part of the OS that the user is able to interact with is the long-press power menu.

OTA-ing to the latest build is successful however.

Repro Steps:
1) Update a Flame to BuildID: 20140709000201

Actual:
Black screen is displayed instead of lockscreen. User is unable to access device.

Expected:
Lockscreen is displayed and functions as expected.

v2.0 Environmental Variables:  (Variables obtained from OTA version)
Device: Flame v2.0
20140709000201
0b5f757da75a
1dd043857399c713e3b509c0ed31bdf20326f08b
v122

Notes:
OTA works appropriately

Repro frequency: 100%
See attached: logcat

Comment 1

[Peter Bylenga [:PBylenga]]

Since OTA works, could be related to First Time Experience.  Build in question was obtained from:
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-aurora-flame/2014/07/2014-07-09-00-02-01/

Comment 2

[Johan Lorenzo [:jlorenzo]]

I flashed my 512MB Flame this morning and it was working. I've just tried again, I am not able to repro. I am running the exact same version as the one you indicated.

On how many devices have you seen the black screen?

Comment 3

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue did not occur on Tinderbox 2.0 builds (engineering of normal) only on the nightly builds.

Aurora Nightly Regression Window:

Last working 
Environmental Variables:
Device: Flame 2.0
BuildID: 20140708160201
Gaia: 16d99f67c376378df850343667cee43af87c24a6
Gecko: 558d378d7364
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


First Broken 
Environmental Variables:
Device: Flame 2.0
BuildID: 20140709000201
Gaia: 1dd043857399c713e3b509c0ed31bdf20326f08b
Gecko: 0b5f757da75a
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0



Last working gaia / First broken gecko  - Issue does NOT occur
Gaia: 16d99f67c376378df850343667cee43af87c24a6
Gecko: 0b5f757da75a

First broken gaia / Last working gekko - Issue DOES occur
Gaia: 1dd043857399c713e3b509c0ed31bdf20326f08b
Gecko: 558d378d7364

Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/16d99f67c376378df850343667cee43af87c24a6...1dd043857399c713e3b509c0ed31bdf20326f08b

Comment 4

[Michael Henretty [:mikehenrty][:mhenretty]]

I'll take a look.

Comment 5

[Peter Bylenga [:PBylenga]]

(In reply to Johan Lorenzo [:jlorenzo] from comment #2)
> I flashed my 512MB Flame this morning and it was working. I've just tried
> again, I am not able to repro. I am running the exact same version as the
> one you indicated.
> 
> On how many devices have you seen the black screen?

We had 11 people see it, I used the flash method you used and did not see the issue.

Comment 6

[Michael Henretty [:mikehenrty][:mhenretty]]

I flashed the build in comment 1, and was also unable to reproduce this. Are you limiting your RAM? Also, can you attach the logcat?

(In reply to Peter Bylenga from comment #5)
> (In reply to Johan Lorenzo [:jlorenzo] from comment #2)
> > I flashed my 512MB Flame this morning and it was working. I've just tried
> > again, I am not able to repro. I am running the exact same version as the
> > one you indicated.
> > 
> > On how many devices have you seen the black screen?
> 
> We had 11 people see it, I used the flash method you used and did not see
> the issue.

What flash method did you use when you saw the issue vs the flash method you used which didn't reproduce?

Comment 7

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

I couldn't reproduce this using the flashing method they are using.  We're rechecking on their end.

Comment 8

[Peter Bylenga [:PBylenga]]

So after more investigation we determined there was an error in the extraction of today's gaia. After re-downloading the build from pvt to our local server we don't encounter the issue.

The difference between the flashing methods is the one that worked was re-downloading the build from pvt.  The flashing method we use works fine now that we've re-downloaded the build.