Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Reimplementation of touch screen and keypad locking subsystem
Legacy automatic locking is replaced with two state machines. One deals with time based delayed locking after display off and another one that deals with proximity based locking after display off. Exceptional ui states - where the display is turned on to handle things like calls, alarms and notifications - have a state machine of their own. Each exception type can also utilize display on linger, i.e. the display can be kept on a while after the exceptional state has already ended. The keypad, touchscreen and doubletap event enable / disable logic for legacy devices is also implemented as a single state machine. The basic logic was smoketested on a old nemomobile image with N9 and N950 devices, but there might still be rough edges at corners. The two separate ON -> DIM -> OFF engines in tklock and display modules have been joined to a single engine at display module. Mere activity is no longer used to unblank the display. This requires explicit display on request. The power key and double tap handling has been modified to handle this. The pocket mode is removed. It needs to be re-implemented when/if low power mode display can be supported again. The N9 specific display on statistics gathering was removed as it requires Nokia specific libcal and we are unlikely to have that available in nemomobile. The late suspend is delayed for one second after reaching display off state. This should give UI side time to handle display off actions before suspend rather than after resume. If setUpdatesEnabled D-Bus method calls take unexpectedly long time, a led pattern is activated. This should allow us to tell apart black screens that result from ui / dbus freeze from other causes. [mce] Reimplementation of touch screen and keypad locking subsystem
- Loading branch information
Showing
10 changed files
with
7,848 additions
and
7,947 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
[LEDPatternHybris] | ||
|
||
# Patterns used for the hybris hardware; | ||
# Please prefix pattern names with Pattern to avoid name space clashes | ||
# | ||
# [0] Priority (0 - highest, 255 - lowest) | ||
# [1] ScreenOn | ||
# 0 only show pattern when the display is off | ||
# 1 show pattern even when the display is on | ||
# 2 only show pattern when the display is off, including acting dead | ||
# 3 show pattern even when the display is on, including acting dead | ||
# 4 only show pattern if the display is off, or if in acting dead | ||
# 5 always show pattern, even if LED disabled | ||
# 6 Like 0, but automatically disable after display on | ||
# [2] Timeout in seconds before pattern is disabled, 0 for infinite | ||
# [3] OnPeriod in milliseconds | ||
# [4] OffPeriod in milliseconds | ||
# [5] RGB24 as hexadecimal number | ||
# | ||
# Note: If blinking is enabled, only full intensity colors are applicable | ||
# i.e. red, green, yellow, blue, magenta, cyan or white should be used. | ||
|
||
PatternBatteryDisplayBlank=0;5;0;100;100;ff0000 | ||
PatternBatteryDisplayUnblank=0;5;0;100;100;00ff00 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.