I'm not sure the designed behaviour of keeping the screen on for as long
as the snap decision is on screen is correct. I'm not sure respecting
MAX_INT as timeout value (-1 would make more sense for "never" anyway)
is right either.
The (ab)use case of SIM dialog for this makes it so we want the dialog
to remain on screen until it completes, is dismissed, or the backend
decides to put it away. That makes some sense, but I don't think that
should mean the screen should stay on forever. I agree with the bug
description that it should shut down after the idle timeout. So the
difference would be between how long the different notifications cause
the screen to be on, not that one of them "decides" how long it is on.
** Changed in: unity8 (Ubuntu)
Status: New => Incomplete
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1615001
Title:
lock display when idle timeout not honoured
Status in Canonical System Image:
New
Status in repowerd:
New
Status in repowerd package in Ubuntu:
New
Status in unity8 package in Ubuntu:
Opinion
Bug description:
current build number: 412
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
Test Case:
1. Go to system-settings/battery/lock when idle and set it to 5min
2. Reboot the device
3. Wait
Expected behaviour
Display turns off after 5min
Actual Behaviour
Display doesn't turn off
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
