Closed Bug 1077399 Opened 10 years ago Closed 9 years ago

Fennec prevents screen turning off and locking

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(firefox34 unaffected)

RESOLVED FIXED
Tracking Status
firefox34 --- unaffected

People

(Reporter: glandium, Assigned: wesj)

References

Details

(Keywords: regression)

Since a few days (I think), when fennec is the foreground application: - the screen won't turn off automatically on idle - when the screen it turned off manually, turning it on doesn't bring the unlocker, and just brings me back to fennec. I noticed this a couple days ago on a local build and have reproduced on nightlies. I haven't searched for a regression range.
Wes, this sounds like a keyguard thing… any thoughts?
Flags: needinfo?(wjohnston)
Blocks: powah
tracking-fennec: --- → ?
[Tracking Requested - why for this release]: regression
tracking-fennec: ? → 35+
Sounds a bit like bug 1072091. Are you using Fennec in Guest mode? We may also do this if your phone is just not securely locked (i.e. swipe to unlock).
Flags: needinfo?(wjohnston)
> Are you using Fennec in Guest mode? I don't think I am. What is guest mode? > We may also do this if your phone is just not securely locked (i.e. swipe to unlock). Indeed, it's swipe to unlock. That doesn't make it fine to prevent locking, though. I do rely on the lock screen showing up to see the clock and notifications on it. That doesn't work when the last thing I did was to use nightly.
glandium, can you test in 34?
Flags: needinfo?(mh+mozilla)
Assignee: nobody → wjohnston
It doesn't happen on current beta.
Flags: needinfo?(mh+mozilla)
We turned off the lockscreen on Aurora. Since this feature is behind a nightly flag now (and won't be turned on for 36), I don't think its worth tracking a release.
tracking-fennec: 35+ → ---
Fixed by backing out the keyguard mode.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.