1059923 - Device gets stuck in a state where the screen display is super dim

Status: RESOLVED WORKSFORME

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

Description

[Kartikaya Gupta (email:[e-mail])]

Running a local B2G build of recent master code on a Flame. Boot it up, and unlock the lock screen. The wait for the screen timeout to expire (around a minute by default) at which point the screen starts to dim. While it is in the middle of dimming but before it has gone completely off, interact with the device (e.g. try scrolling the homescreen). This prevents the device from locking, but it leaves the device with the display really dim. At this point you can't un-dim without going into the settings and manually adjusting the dimness. Even turning the display off and back on doesn't fix it.

It's easy to get into this state because if I see the screen start to dim but I don't want it to lock then my instinct is to touch the screen to keep it awake. But this just screws me over and leaves me in a bad state.

Comment 1

[Gregor Wagner [:gwagner]]

Is this a regression?

Comment 2

[Chris Kreinbring [:CKreinbring]]

Unable to repro on the latest Flame 2.2, Flame 2.1 and Flame 2.0.  Tapping the screen as it dims in preparation to turn off causes it to immediately return to full brightness.
Leaving the QAWanted tag for someone else to attempt.

Flame 2.2
BuildID: 20140903062451
Gaia: 52670853c17fc0d3d33065c667c0ce124c93b98f
Gecko: 5e9826980be5
Platform Version: 35.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Flame 2.1
BuildID: 20140903085050
Gaia: fbb297c39aab5f17b179533d2a9a6c5166b2c197
Gecko: 31dad821234e
Platform Version: 34.0a2
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Flame 2.0
BuildID: 20140903060552
Gaia: d056733f8a7a1a152f5458b323f092c47dbffa48
Gecko: 5137a70489dd
Platform Version: 32.0
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 3

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

Note, we set the brightness on every boot before the settings takes over [1]. There is a discussion about this behavior here https://bugzilla.mozilla.org/show_bug.cgi?id=1044330#c12. If this code path is indeed causing a bug, we might reconsider the path forward in that bug.

1.) https://github.com/mozilla-b2g/gaia/blob/eea2b4a159d5dfded2ccbf723e43abe8ae52a93d/apps/system/js/screen_manager.js#L157

Comment 4

[Kartikaya Gupta (email:[e-mail])]

Btw I've run into this issue a few times now. If QA is unable to reproduce I'll try to get more specific STR - there must be some other factor that is important here. It might only happen the very first time the screen dims after booting up the device; I don't remember if that was the case when I ran into it.

Comment 5

[Alberto Pastor [:albertopq]]

Unable to repro either with a Flame on 2.2:

gecko: 8d45e2920d2f34f0f148a750b8ad3bd605effde3
gaia: 2351cb1e0de68b3d323d5eb8a20644c0786542b9

Comment 6

[Alberto Pastor [:albertopq]]

Could you please provide more information on how to reproduce?

Thanks!

Comment 7

[Kartikaya Gupta (email:[e-mail])]

Hm, I tried reproducing this a few times just now and wasn't able to. I'll close this for now and reopen once I have more reliable STR. Sorry for the waste of time.

Comment 8

[Pi Wei Cheng [:piwei] (inactive)]

Removing qawanted tag due to bug being closed out.