We forgot to post anything about the suspend issue
Currently we only support S3
suspend (aka Suspend-to-RAM
). Meanwhile the old Intel Atom tablets or most recent devices are only support s2idle
(aka Suspend-to-Idle
). Either linux handling s2idle
really buggy on the device, or our Suspend HAL handle it really buggy. Whatever the case is, you should not using it on BlissOS for now
To know if your device support s2idle
and disable suspend if true:
- On a terminal app like Termux open /sys/power/state
$ cat /sys/power/state
freeze mem disk
If it have both
mem
& freeze
then might support both S3
and s2idle
. If it only have freeze
then you might only support s2idle.Next, to further check. You can read
/sys/power/mem_sleep
$ cat /sys/power/mem_sleep
s2idle [deep]
If you have
deep
and it's in the square brackets, then yes you support S3. If the brackets pointed to s2idle then you can use echo deep > /sys/power/mem_sleep
or switch it on BIOS Settings. There is a Sleep State
option, usually it will say Linux
or Windows
in which Linux
is actually S3.- If you have
mem
, chances are S3 is already the default sleep state. If it doesn't , edit grub and boot withSLEEP_STATE=mem
- If you only have
freeze
or you don't want to use suspend, boot with SLEEP_STATE=none
The device will immediately wake up instead of suspend
More info about sleep state on Linux you can read here
https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html
>>Click here to continue<<