Prevent rtcwake to go to crust when not expected
If you unlock the phone in rtcwake, then the next rtcwake will put the phone back to crust cause last wake up reason still is rtc. To prevent this, we also check the last state and expect it to be crust. Signed-off-by: Stacy Harper <contact@stacyharper.net> Signed-off-by: Anjandev Momi <anjan@momi.ca>
This commit is contained in:
parent
4c0b70442c
commit
41c15b192e
1 changed files with 4 additions and 4 deletions
|
@ -11,11 +11,11 @@ finish() {
|
|||
|
||||
sxmo_screenlock.sh updateLed
|
||||
|
||||
if grep -q rtc "$UNSUSPENDREASONFILE"; then
|
||||
if grep -q crust "$LASTSTATE" \
|
||||
&& grep -q rtc "$UNSUSPENDREASONFILE" \
|
||||
&& [ "$(sxmo_screenlock.sh getCurState)" != "unlock" ]; then
|
||||
# Going back to crust
|
||||
if [ "$(sxmo_screenlock.sh getCurState)" != "unlock" ]; then
|
||||
sxmo_screenlock.sh crust
|
||||
fi
|
||||
sxmo_screenlock.sh crust
|
||||
fi
|
||||
|
||||
exit 0
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue