Google System updates make your Android devices more secure and reliable, and give you new and useful features. They include updates from Google to the Android operating system, Google Play Store, and
I’m generally aware of all that, but I don’t see how it answers the question. Why can’t you just stop all app processes, unmount the relevant partitions, clear any memory containing cryptographic keys etc. but not actually reboot?
Rebooting just seems like a very roundabout, slow and inefficient way to get back to that initial state you describe. Is there something e.g. the bootloader does that cannot be replicated on a running phone and is essential for securing it again after the first unlock?
Rebooting just seems like a very roundabout, slow and inefficient way to get back to that initial state you describe.
It’s exactly what the reboot process is designed to do; return you to that fully encrypted pre-boot state. There would be no purpose to implementing a second method that does the exact same thing.
its done that way because at a reboot all memory is lost, and it can’t happen that something slips through because there is a bug or some miscalculation
I’m generally aware of all that, but I don’t see how it answers the question. Why can’t you just stop all app processes, unmount the relevant partitions, clear any memory containing cryptographic keys etc. but not actually reboot?
Rebooting just seems like a very roundabout, slow and inefficient way to get back to that initial state you describe. Is there something e.g. the bootloader does that cannot be replicated on a running phone and is essential for securing it again after the first unlock?
It’s exactly what the reboot process is designed to do; return you to that fully encrypted pre-boot state. There would be no purpose to implementing a second method that does the exact same thing.
its done that way because at a reboot all memory is lost, and it can’t happen that something slips through because there is a bug or some miscalculation