Closed Bug 1028186 Opened 10 years ago Closed 10 years ago

Homescreen lock timeout is broken

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1028374

People

(Reporter: zrzut01, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243



Actual results:

Screen locks after 10 seconds every time regardless on user activity when it is sert in the Settings for 1 minute


Expected results:

It sould locks after 1 minute of user inactivity as previously.
First occurs on this FOTA:

Alcatel One Touch Fire production (got from T-mobile Poland)
B2G version: 2.1.0.0-prerelease master
Platform version: 33.0a1
Build Identifier: 20140619160200
Git commit info: 2014-06-19 11:45:36 135a13ea
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
I do reproduce this on Flame.
blocking-b2g: --- → 2.1?
Seems like it regressed since yesterday.
QA Wanted to check 2.0.
Status: UNCONFIRMED → NEW
Component: Gaia::Homescreen → Gaia::System
Ever confirmed: true
Keywords: qawanted
Additional information, after phone is unlocked by Power Button and Screen Timeout is changed to different period of time the set screen timeout stands unless screen is locked back with Power Button. When unlock it back the bug occurs again.
I have the same effect with the current nightly builds of geeksphone on my keon.
Hi Mac

Thank you for your contribution by submitting this bug; unfortunately I am closing it as a dupe of 1028374. While it is true that your bug was written first, the other bug has more information including STR (steps to reproduce), repro frequency, firmware version and a logcat attached; as well as having a bit more traction (movement toward fixing). Please don't let this discourage you from filing future bugs and your efforts are appreciated.
Status: NEW → RESOLVED
Closed: 10 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
blocking-b2g: 2.1? → ---
You need to log in before you can comment on or make changes to this bug.