We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-01-04 03:33:23 +0200 |
While reading something on the screen inactivity timeout hits really easily without indication. Proposing dimming of display e.g. 10s before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading.
2 | No.2 Revision |
While reading something on the screen inactivity timeout hits really easily without indication. 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen or alternatively dimming of display e.g. 10s before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading.reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
3 | No.3 Revision |
While focusing to reading something on the screen inactivity timeout hits really easily without with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display e.g. 10s (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
4 | No.4 Revision |
While focusing to reading something on the screen inactivity timeout hits easily with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
5 | retagged |
While focusing to reading something on the screen inactivity timeout hits easily with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
6 | retagged |
While focusing to reading something on the screen inactivity timeout hits easily with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
7 | retagged |
While focusing to reading something on the screen inactivity timeout hits easily with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
8 | retagged |
While focusing to reading something on the screen inactivity timeout hits easily with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!
While focusing to reading something on the screen inactivity timeout hits easily with 2-3 seconds dimming followed by display off and locked. Dimming is difficult to notice when the display brightness is set to the lowest value (e.g. reading in the dark).
Proposing usage of sensors to identify user near the screen (e.g. 30 cms) or alternatively longer, more visible dimming of display (e.g. 10s) before display is turned off and locked for power saving. This would indicate the user to touch the screen should she wish to continue reading. Longer timeout would allow more time to react. Sensor usage is preferred approach because it removes the need to tap the screen which can lead to unwanted activation of an UI element, e.g. link.
Edit: edited proposal based on the comments. Thanks a lot!