Closed Bug 1066742 Opened 10 years ago Closed 7 years ago

In some cases device doesn't stay awake while interacting with it

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: kats, Unassigned)

Details

(Whiteboard: [systemsfe])

+++ This bug was initially created as a clone of Bug #1059923 +++ I wasn't able to get reliable STR for bug 1059923 but I do have STR for another issue that is a subset of that problem (maybe the rest of it is fixed already?). Run a recent B2G build on Flame (I'm using a local build of master code). Boot it up (if it's already running, then reboot it). When it boots to the lockscreen, wait for the screen idle timeout to trigger. When this happens, the screen goes dim. Before the screen turns off entirely, unlock the device and scroll around on the homescreen. Expected results: - When you start unlocking the device, the device brightness goes back to full Actual: - During the unlock sequence and while scrolling around, the device brightness remains dim. After a few seconds the screen turns off even though you're clearly interacting with the device. This seems to only happen on first boot and before I unlock the device on that first boot. If I unlock the device, lock the device, and then wait for the idle timeout, the screen turns off directly without going through a dimming period so the STR don't work.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.