Google clarifies what’s taking place with Android’s auto-reboot function

Earlier this week, Google quietly revealed — through its Google System Launch Notes web page — that it was rolling out a brand new auto-reboot feature to Android units. The function, as described, works equally to Inactivity Reboot in iOS 18.1 or the auto-reboot function in GrapheneOS. If an Android machine has been locked for 3 consecutive days, then it’ll be mechanically rebooted.

Late final month, Android Authority contributor AssembleDebug tore down the Google Play Services app and found a reference to this auto-reboot function, recognized internally as “inactivity reboot.” He discovered proof that the function is tied to Advanced Protection Mode, a brand new function in Android 16 that gives a approach for the system and for third-party apps to know when customers are enrolled in Google’s Superior Safety Program. Superior Safety Mode will function a one-click option to allow sure safety features within the OS and in suitable third-party apps.

As a result of Google has but to truly present a UI for enabling Superior Safety Mode in Android 16, we speculated that Google was not, in reality, rolling out this new auto-reboot function. At this time, we found that Google has quietly up to date the wording on the Google System Launch Notes web page to verify that the function isn’t really rolling out. Moreover, the brand new wording confirms that the function will probably be non-compulsory as soon as it does roll out.

Earlier than:

[Phone] With this function, your machine mechanically restarts if locked for 3 consecutive days.

After:

[Phone] Allows a future non-compulsory safety function, which can mechanically restart your machine if locked for 3 consecutive days.

Whereas the up to date wording doesn’t affirm whether or not the auto-reboot function will solely be obtainable on sure Android variations, it ought to ease some normal considerations in regards to the function. Some customers apprehensive it might disrupt their secondary Android units by stopping them from persistently operating background duties or checking notifications. Fortuitously, Google confirmed the auto-reboot function is non-compulsory, so customers who want their units to all the time be on-line can maintain it disabled.

Google hasn’t publicly offered a rationale for why it made this function, but it surely’s simple to guess why. Most Android units right now use an encryption scheme known as file-based encryption (FBE). FBE was launched again in Android 7.0 Nougat, changing the older full-disk encryption (FDE) scheme. Below FDE, your entire userdata partition is encrypted with a single key derived from the person’s lock display screen credential (PIN, sample, or password), which the person should enter throughout boot to decrypt the partition. In distinction, FBE encrypts completely different information utilizing completely different keys. This permits some apps supporting Android’s Direct Boot function to function even earlier than the person decrypts the principle userdata partition after booting up.

When an Android machine utilizing FBE first boots up, it enters a state known as Earlier than First Unlock (BFU), the place the vast majority of the userdata partition stays encrypted. Nonetheless, as soon as the person enters their PIN, sample, or password for the primary time, the machine transitions to the After First Unlock (AFU) state, totally decrypting the userdata partition. As a result of this decrypted information may be invaluable to hackers or authorities businesses, they typically attempt to receive already unlocked units to carry out digital forensics. The auto-reboot function goals to fight this by forcing units again into the BFU state if they continue to be locked for 3 consecutive days—an indicator the machine could be held for such functions.

Most customers received’t want a function like this, but it surely’s good to see Google implement it regardless. Android is the world’s most generally used working system, so there are undoubtedly some individuals who want this auto-reboot function. Hopefully Google rolls it out quickly.