Assigning it to Krishna to update this bug with his findings.

Krishna, any update on this?

Hi Chromium Team,

I'm hoping to see if there has been any update on this ticket. I have currently written a small native kiosk app, its sole job is to sleep the display. I have done so using the following code

const sleepBtn = document.getElementById('sleepBtn');
const stateDiv = document.getElementById('state');


chrome.power.requestKeepAwake('display');
stateDiv.innerHTML = "KEEP AWAKE STATE:<br><br>requestKeepAwake('display')";
sleepBtn.addEventListener('click', () => {

    chrome.power.releaseKeepAwake();
    stateDiv.innerHTML = "KEEP AWAKE STATE:<br><br>releaseKeepAwake()"
    chrome.power.requestKeepAwake('system');
    stateDiv.innerHTML = "KEEP AWAKE STATE:<br><br>requestKeepAwake('system')"
});


Unfortunately this has not worked on Chrome OS 59, 61, 62, 64 and 65. I'm wondering if this an issue with how I have done things. Or whether the issue is still being looked into by Krishna?

Thanks,

Dimitri

Krishna has since moved teams, so this bug is orphaned :(. However, his analysis from the original report seems spot-on. Our documentation of the power management timeouts says:

"For each of above actions, the delay should be specified in milliseconds, and needs to be set to a value greater than zero to trigger the corresponding action. In case the delay is set to zero, Google Chrome OS will not take the corresponding action."

I filed internal bug b/80402143 to figure out what policy exactly we are setting. If it really is all zeros, that will not work.

Over to Sergey as this is a kiosk bug.

Hi Team,

Just wondering the status of this ticket and if there are any updates?

Thanks,

Dimitri

Sergey, can you comment here?

It's under investigation on server side and is tracked in internal bug b/80402143
I asked for updates there.

The policy on server side will be updated to have "Idle" >= "ScreenOff" in this case.

However, the behavior of Chrome OS power management is a little bit strange here.
AFAIU, 0 values for any of these settings means that it will never happen, i.e.more like "infinity" timeout.

But when "ScreenOff" > 0 is clamped to "Idle" = 0 = never, it means that "ScreenOff" is "increased" to infinity instead of reducing to "Idle" value.
In other words, "ScreenOff" > 0 is actually already "less" then "Idle" = 0.
BTW, the same for "ScreenDim" - "ScreenOff" and "IdleWarning" - "Idle" pairs.

Daniel, do you think the delays sanitation should be changed for this case?

Thanks!

Re changing display sanitization, no, I don't think so. Idle is a special case -- the right way to disable it is to set its action to "do nothing" rather than to set its delay to 0. IIRC, this was a conscious decision so there would only be a single way to disable the idle action. powerd doesn't expect to receive 0 idle delays.

Hi Team,

Just checking up on the progress regarding this issue. Is there any ETA for this bugs resolution ?

Thanks,

Dimitri

Hi Guys,

Is there any update on this issue ?

Thanks 

#14: Someone else will hopefully correct me if I'm wrong, but from looking at the internal bug, it appears that a fix was submitted on June 15 and verified to work soon after. I'm not sure about the rollout schedule for the change. Kamila, can you comment about this?

It should've been fixed on server side a couple of weeks ago.

Hey guys,

Great you guys got it working. Do you know what version release this fix is scheduled for ? 

Thanks,

Dimitri

It's fixed for all releases, as it was a server side fix.

verified fixed using M69 dev