ReversalHatchery

their service is very cheap, though. but yeah if you can selfhost it, and expose it to family that's good

what problems did you experience, on what hardware? works fine here

now that I look into it other phones of theirs are interesting too. I mean 3" with jack and IR, and still a lot of memory.

unfortunate that o far none of them have clean rom support

Previously it was just societal expectations but apparently it's not that anymore.

since when is going to the dentist the only societal expectation? since when is that a societal expectation at all?

• education lot of places that force you to install spyware for the online exams
• banks that intentionally break their websites on "unsupported" systems
• workplaces where people work with computers, basically generally, becausre of ms office and supervision software

I was trying to show that android is not really Linux. it has lots of changes both to the kernel and the userspace

but at least it was a good excuse to destroy apps relying on linux procfs (/proc)

to a similar extent as windows is DOS

here is the low-level documentation on sleep on linux, and the ways you can initiate it: https://docs.kernel.org/admin-guide/pm/sleep-states.html#standby

I would try if setting mem_sleep to any of its values and then sleeping fixes the issue. read this file first to know which options are available on your system, and what is the current default.
if none of them works, try to write freeze or standby into the state file to see of any of them works, in case your system does not do sleeping by writing mem into this file.

if this is a firmware issue, hopefully one of the ways that don't involve the firmware could work until a better solution is found.

the Arch Wiki has mostly the same info but with more (or different) details: https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate

it also mentions what are your options if deep sleep (which is real sleep) does not work.

let us know what results you got

I don't think anybody requires you to do so. you do that for your own health

so you use the integrated graphics of the ryzen, right? you can check in KDE's info center, to make sure

windows may have a workaround for your hardware. It's relatively common for popular hardware to not work according to specifications, unfortunately, and that results in all kinds of mundane behaviour like this

logs are mostly at 2 places.

kernel logs are read with the dmesg command. use the --follow parameter if you want it to keep printing new messages.
dmesg does not save logs to disk.

broader system logs are read with journalctl. use -f for it to keep printing. the journal records kernel messages, but it only shows them when you specifically request it. you can find the param for that in man journalctl.
the journalctl (journald actually) saves logs to disk. but if you don't/can't shut down the system properly, the last few messages will not be there.

some system programs log to files in /var/log/, but that's not relevant for now.

if you switch to a VT as the other user described, you should see a terminal prompt on aback background. log in and run dmesg --follow > some_file, some_file should not be something important that already exists in the current directory. switch to another VT, log in, and run sleep. try to wake up. see if you could have waken up, and if not check the logs you piped to the file, maybe post it here for others to see.

also, what did you do after setting the deep sleep kernel param? did you rebuild the grub config, and reboot before trying to sleep with it? that change only gets applied if you do those in that order.
there's an easier way to test different sleep modes temporarily, let me know if it would be useful