Originally, Lock Device would reboot and sleep. Now, it reboots and stays on (asks for the pin).
Sometimes when entering my pin right after a "Lock Device (reboot)", I get a message "Uninterruptible operation pending. Please retry the sleep request in a couple seconds." Once I dismiss it, the system proceeds with mounting PDDB. It's a bit confusing to the user because the user didn't not just request sleep. Furthermore the user may not be aware that Lock Device defers a sleep request for historical reasons.
To improve UX and prevent that message, should we remove the line scheduling that deferred sleep after reboot? It's here: https://github.com/betrusted-io/xous-core/blob/dev/services/status/src/main.rs#L1295
Note that the message never appears after a cold start (Shutdown then plug in). The unexpected behavior occurs only after a Lock Device (reboot), then log in.
Activity
0No activity yet.