The latest pixel devices (since 6 I think?) already provide accees to a /dev/kvm device, so maybe you could even run a normal Ubuntu server VM on your phone for hosting these services.

I guess he means that raspberry pi doesn’t run a mainline kernel

deleted by creator

I think the admin of c/selfhosted is the admin of Lemmy.world

I think those kind of vulnerabilities are pretty rare, though.

Not really… If you go read the security bulletin from google, you will see every month that there are a couple of issues fixed on closed source components https://source.android.com/docs/security/bulletin/2023-07-01

Also vulnerabilities related to kernel code, I highly doubt most ROM “developers” are actually backporting security fixes for that specific device’s kernel branch/source.

You can update your phone with custom ROMs, but it won’t update the closed source components of it(device drivers, bootloader, etc…). If a vulnerability is found in one of those components, it’s unlikely that it will get parched

GrapheneOS uses exec spawning by default, but it’s pretty trivial to disable and it does speed things up (at a slight cost to security).

Even with that option disabled the slow down was significant enough. Maybe the mid-range chip used in the Pixel 5 wasn’t helping, but still… Overall the phone felt significantly quicker when switching back to stock.

I think using AOT rather than JIT compiling might be the cause of the slow installs, but I’m not sure (and I’ve not really noticed a problem myself).

That’s it, I remember reading in their forums one of the mods(or devs?) mentioning this.

I ran GrapheneOS on a pixel 5 but ultimately went back to stock.

GrapheneOS was considerably slower on my phone. Apps took a bit longer to loader, but the worst was installing APKs, it takes so much longer compared to stock. Some apps (e.g. revolut) took more than 5 minutes to install, it was crazy.