5 ms·
This was the issue I had doing anything interesting on Android in the past. It just randomly kills things so you can't do much more serious stuff than web brows
by msgodel 1y ago
This was the issue I had doing anything interesting on Android in the past. It just randomly kills things so you can't do much more serious stuff than web browsing/social media on it.
I suppose normal GNU/Linux might have this issue as well if you run an OS with lots of background services that randomly consume large amounts of RAM or if your desktop environment does. I don't so outside of kind of insane environments like raspberry pi zeros or weird situations on servers I don't typically run into this. (and no. It's not 2010, phones are normal PCs not a weird embedded environment.)
- pfcd 1y ago> phones are normal PCs not a weird embedded environment It's the opposite.
- msgodel 1y agoNope. My last laptop has lower specs than modern phones.
- pfcd 1y agoThat doesn't mean they are "normal PCs". Define what is a "normal PC" to you, then. Is it just specs?
- heavyset_go 1y agoYour PC is built on a standardized architecture, your mobile device is its own bespoke SoC and requires unique, and often proprietary, methods just to boot and discover components. It's the reason you can use any amd64 ISO to boot Linux on your PC, but each individual embedded device needs its own special image that is custom to that board, and often a custom Linux fork.
- heavyset_go 1y agoAndroid app scheduling is different than what not-Android Linux does. oomkiller might kill stuff in high memory pressure situations, but Android does a bunch of dynamic loading and unloading all the time. See also https://developer.android.com/guide/components/processes-and-threads https://developer.android.com/guide/components/processes-and...