Replying to Avatar Vitor Pamplona

Playing with the default Debian VM on Android 15 made me really appreciate what the OS does for app developers. Since the VM runs in low level and goes around most Android protections, it can use 100% of the CPU and completely freeze the entire phone for minutes. You cannot do that on an app. Even if devs want to. The app UI might freeze, but the rest of the OS stays normal, other apps work, music plays, bluetooth is on, notifications still show up.

I can see Android killing the VM when there is too much is going on. I can also see Android killing all the other apps to allow the VM to do its thing when it needs more memory/CPU.

I am not sure how the Android team will square these conceptual differences. Will they move all the protections from the Java-based VM down to native or will they just allow people to brick their own phones for the first time via VMs?

Exciting times ahead.
Avatar
DeveRoSt 10mo ago

Allowing them to brick there phone. Because it is there phone, they should be allowed to.

Reply to this note

Please Login to reply.

Discussion

Avatar
Vitor Pamplona 10mo ago

Not exactly. People want the OS to keep the Phone safe from themselves. Because they know they are always fucking something up. OS need to stay working at all costs.

Avatar
DeveRoSt 10mo ago

No, it should have an option "allow me to brick my phone" and it should be disabled by default, but everybody should have the option to enable it on own risk.