Created an attachment (id=1106651) log PR Reporter:邢艳 contact:0752-2639551(61551) DEFECT DESCRIPTION: >MS stay in idle with screen always light up even set screen timeout as 1 or 2 minutes. REPRODUCING PROCEDURES: 1.Enter settings->display->screen timeout, set timeout as 1 or 2 minutes. 2.Place MS in idle,MS will stay in idle with screen always light up.--ko PS: 不是必现但很容易遇到，附件为log。 EXPECTED BEHAVIOUR: >MS should light off after screen timeout. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:

Hi Danny: Please help check what information is needed for checking the issue. Thanks!! Shawn

Dear mozillla， 看我这附上新抓的这份log，往/sys/class/leds/lcd-backlight/brightness这个节点里写的值怎么从128每次往上加3的，正常的情况是从255每次减3到屏灭，请帮忙看一下在什么情况下会出现从128每次往上加3的情况，谢谢！ 陈欧平 0752-2611532

Created an attachment (id=1108644) 打印出往lcd backlight节点里写数据的log

Created an attachment (id=1108644) 打印出往lcd backlight节点里写数据的log

Created an attachment (id=1108644) 打印出往lcd backlight节点里写数据的log

Hi reporter, In this case, there are two possible root causes: 1. Someone request screen wakelock and never release it 2. The screen timeout is not set properly. For case 1, I will suggest you to add log after request SCREEN wake lock and wake unlock. It can dig out who request wake lock but never release it. For case 2, I think you did some modifications on screen_manager.js because I saw the UI and timeout value are different from Mozilla. Could you share us what you modify? Moreover, it will be better if you can provide b2g-info when issue happened. We can know which application is running at background by b2g-info. Thanks, Danny

Created an attachment (id=1115282) screen_manager.js

Created an attachment (id=1115282) screen_manager.js

Created an attachment (id=1115282) screen_manager.js

Hi,danny, For case 1, how can I add a log for wake lock and wake unlock, and where to add? For case 2, I have add a attachment of file screen_manager.js, pls help us to check it? 陈欧平 0752-2611532

Hi,danny, For case 1, how can I add a log for wake lock and wake unlock, and where to add? For case 2, I have add a attachment of file screen_manager.js, pls help us to check it? 陈欧平 0752-2611532

Hi,danny, For case 1, how can I add a log for wake lock and wake unlock, and where to add? For case 2, I have add a attachment of file screen_manager.js, pls help us to check it? 陈欧平 0752-2611532

(In reply to sync-1 from comment #14) > Hi,danny, > For case 1, how can I add a log for wake lock and wake unlock, and where to > add? > For case 2, I have add a attachment of file screen_manager.js, pls help us > to check it? > > 陈欧平 > 0752-2611532 For case 1, please grep the keywords "requestWakeLock('screen')" in your gaia source tree and try to add log after request screen wake locks and unlock. Forc case 2, I didn't find obvious reason to cause this problem, suggest you can add log when timeout is changed, it should be after https://github.com/mozilla-b2g/gaia/blob/v2.0m/apps/system/js/screen_manager.js#L144 And, it will be better if you can provide the STR in detail.

Here is SAMPLE of debug patch, please must write your owned patch because I am not sure where did you request screen wake lock.

Dears,

Dears, We add logs in https://github.com/mozilla-b2g/gaia/blob/v2.0m/shared/js/idletimer.js and find that the 'onidle' doesn't report when the issue happen. Maybe we should check why it have not report 'onidle' after 'onactive'.

(In reply to Ray REN from comment #18) > Dears, > > We add logs in > https://github.com/mozilla-b2g/gaia/blob/v2.0m/shared/js/idletimer.js and > find that the 'onidle' doesn't report when the issue happen. Maybe we should > check why it have not report 'onidle' after 'onactive'. Hi Ray, Did you add log when acquire/release screen wake lock? When screen wake lock is held, idletimer won't report onidle. May I know more information when issue happened? such as STR and what's application is running at background? Thanks,

(In reply to Danny Liang [:dliang] from comment #19) > Hi Ray, > Did you add log when acquire/release screen wake lock? When screen wake lock > is held, idletimer won't report onidle. May I know more information when > issue happened? such as STR and what's application is running at background? > Thanks, Hi Danny, I will add logs and give the result ASAP if reproduce.

Created an attachment (id=1124596) b2g-info和wakelock信息

Created an attachment (id=1124596) b2g-info和wakelock信息

Created an attachment (id=1124596) b2g-info和wakelock信息

Hi,danny, 请尽快帮忙看看，以及下面我们要从哪方面分析。 谢谢!

Created an attachment (id=1124590) 问题复现log

Created an attachment (id=1124590) 问题复现log

Created an attachment (id=1124596) b2g-info和wakelock信息

Created an attachment (id=1124596) b2g-info和wakelock信息

Created an attachment (id=1124596) b2g-info和wakelock信息

Created an attachment (id=1124596) b2g-info和wakelock信息

Created an attachment (id=1124596) b2g-info和wakelock信息

Hi reporter, Did you add log to record screen wake lock according to comment 15/16? If yes, please provide the log for analysis. Moreover, the wakelock information you provided is useless. We are checking the screen wake lock, not CPU wake lock, so you won't see anything in /sys/power/wake_lock when screen wake lock is held. Best regards,

Dear Danny, you may reproduce as following steps: 1. restart the phone. 2. Click the phone in lockscreen when the phone start up and the lockscreen is in transition dimming. 3. The screen will always light up. We have modified the function "getActiveApp" in file https://github.com/mozilla-b2g/gaia/blob/v2.0m/apps/system/js/app_window_manager.js as following.please check. Thanks. getActiveApp: function awm_getActiveApp() { return this._activeApp || (exports.homescreenLauncher ? exports.homescreenLauncher.getHomescreen() : null); },

(In reply to Ray REN from comment #33) > Dear Danny, > > you may reproduce as following steps: > 1. restart the phone. > 2. Click the phone in lockscreen when the phone start up and the lockscreen > is in transition dimming. > 3. The screen will always light up. > > We have modified the function "getActiveApp" in file > https://github.com/mozilla-b2g/gaia/blob/v2.0m/apps/system/js/ > app_window_manager.js as following.please check. Thanks. > getActiveApp: function awm_getActiveApp() { > return this._activeApp || (exports.homescreenLauncher ? > exports.homescreenLauncher.getHomescreen() : null); > }, I tried to reproduce it on woodduck v2.0m and flame v2.0, but I cannot. Could you try to review related code you modified and see if any regression?

(In reply to Danny Liang [:dliang] from comment #34) > I tried to reproduce it on woodduck v2.0m and flame v2.0, but I cannot. > Could you try to review related code you modified and see if any regression? Dear Danny, We can reproduce on flame v2.0 and build id: 20141117111119. It also can reproduce as following steps: 1. restart the phone. 2. After start, don't do any operations until it go into idle status. 3. click pow key,don't do anything.The screen will always light up.

(In reply to Ray REN from comment #35) > (In reply to Danny Liang [:dliang] from comment #34) > > I tried to reproduce it on woodduck v2.0m and flame v2.0, but I cannot. > > Could you try to review related code you modified and see if any regression? > > Dear Danny, > We can reproduce on flame v2.0 and build id: 20141117111119. > It also can reproduce as following steps: > 1. restart the phone. > 2. After start, don't do any operations until it go into idle status. > 3. click pow key,don't do anything.The screen will always light up. Great! I can reproduce it by above test steps, keep NI and will update later.

After investigation, I can make sure flame v2.0 have this issue but v2.2 didn't. Now I am checking if any bug fix on v2.2 and we need to pick it up on v2.0, will update if any finding.

My last finding might be gecko hold screen wake lock but cannot narrow down the problem. Didn't find the possible fix on v2.0m, low the priority due to we didn't encounter this issue on v2.2. Keep monitor and will update if any further finding.

Problem not affect 2.2. 2.0 Mark as wontfix.