New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 795484 link

Starred by 4 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Screen LCD doesn't turn off

Reported by ruch...@samsung.com, Dec 16 2017

Issue description

Steps to reproduce the problem:
1. Set screen timeout to 15 or 30 secs.
2. Open chrome
3. Observe

What is the expected behavior?
Screen LCD should be turned off.

What went wrong?
Screen LCD doesn't turn off after screen time out.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 62.0.3202.94  Channel: n/a
OS Version: O-OS
Flash Version: 

Device : SM-G965F_EUR
Android version : O-OS
Chrome version : 62.0.3202.84
 
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Labels: Triaged-Mobile Needs-Feedback
Tested the issue in Android and could not reproduce the issue. Observed the LCD turned off.

Steps Followed:
1. Set creen timeout to 15 secs
2. Launched Chrome
3. Observed the LCD turned off.

Chrome versions tested:
63.0.3239.111

OS
Android 7.0.0

Android Devices
7.0.0; SM-J710F Build/NRD90M

@ruchi: Could you please upgrade you Chrome to the latest #63.0.3239.111 and check if you still face the issue? If so let us know the device name and confirm is this device specific?

Thanks!!



dumpState_G960USQU0AQLD_201712161552.zip
4.5 MB Download
We have encountered one more similar issue, on Great device N950U
on same Chrome Version 63.0.3239.111

Ca you please recheck at your end?
Hello,

We see a lot of issues of chrome acquiring wake lock in the device and it can be seen in the logs below:-

01-11 18:19:33.149  1557 D PowerManagerService: [api] applyWakeLockFlagsOnReleaseLocked : userActivityNoUpdateLocked is called : SCREEN_BRIGHT_WAKE_LOCK        'WindowManager' ON_AFTER_RELEASE (uid=1000 pid=1405 ws=WorkSource{10125})
01-11 18:19:34.427  1557 D PowerManagerService: [api] acquire WakeLock flags=0x2000000a tag=WindowManager uid=1000 pid=1405 ws=WorkSource{10125} pkg=android



01-11 18:22:58.267  1000  1405  1502 I PowerManagerService: [PWL] On : 6570012 (248743 ms ago)
01-11 18:22:58.267  1000  1405  1502 I PowerManagerService: [PWL]  mStayOn: false  mWakeLockSummary & WAKE_LOCK_STAY_AWAKE: 20  mUserActivitySummary: 0x4
01-11 18:22:58.268  1000  1405  1502 I PowerManagerService: [PWL]  SCREEN_BRIGHT_WAKE_LOCK        'WindowManager' ON_AFTER_RELEASE ACQ=-3m24s473ms (uid=1000 pid=1405 ws=WorkSource{10125})

Also this issue is reproducible by the below process

Using a Device in a case and was browsing a web. Left a phone idle and screen timeout did not kick in. Screen is active when touching the screen. Did not lock up.

Performing the above steps multiple times will reproduce this issue
dumpState_G960USQU0ARA8_201801111823.zip
4.4 MB Download
Cc: dskiba@chromium.org
Similar issue is reported by Android folks too: b/72481202
Cc: boliu@chromium.org

Comment 8 by boliu@chromium.org, Feb 14 2018

chrome has legitimate use for wake lock. eg if a tab is playing video or audio, it could hold the wake lock to ensure these things keep going, so this all depends on what you are doing with chrome at the time, eg what pages do you have loaded etc

I tried 62.0.3202.94 with wikipedia home page, and there is no wake lock.
Components: UI>Browser>Mobile

Sign in to add a comment