CryoByte33

I'm already very aware of the article, and have to do some testing around memory locking, but many of the tweaks made aren't beneficial "wholesale". For example, setting the CPU...

Unfortunately there isn't a way to differentiate game data that's been "broken" versus data that just exists on an SD card that isn't inserted. That said, you could use the...

That just means that your copy of the binary isn't the latest one, no worries there 🙂

Try deleting the /home/deck/.cryo_utilities folder and reinstall, the installer needs to be reworked to compensate for failures elsewhere in the process, sorry 😅

That means that CU is lifting a bottleneck and allowing your hardware to work harder, rather than being limited. You can reduce the thermals by locking the framerate to your...

I don't think this is a good idea, please see #87 🙂

Did you format your drive manually? The KDE formatter also uses the directory currently in the code (by default), so I assumed it would be safe to assume it was...

I'm not sure what the issue is if you're just using a basic password with only alphanumeric characters. Did you set the password for your current user or for the...

> I don’t really understand this, but I did it as in the description, set the password via the command line using passwd. I have now demolished the system (there...

I must have missed this, sorry. Have you disabled THP in CU2? It should be set to "madvise" when you do so, since that's the default behavior. If not, can...