Google has introduced a new security measure for Android devices that prompts an automatic restart if a user has not unlocked their phone for three consecutive days. This initiative aims to enhance data security by preventing unauthorized access to the smartphone. The same feature is anticipated to be rolled out for Android tablets in the future. Apple recently implemented a comparable ‘Inactivity Reboot’ function in iOS 18.1, which automatically reboots iPhones after a 72-hour period of inactivity.
Enhancing Data Security with Automatic Reboot
The newly released Google Play services v25.14 update, which began distribution on Monday, includes the feature that automatically restarts an Android smartphone if it has been locked for three days. Consequently, if the device remains untouched for this duration, it will reboot, requiring the user to enter their passcode upon being picked up again.
Upon rebooting, the user data on the smartphone becomes encrypted, and biometrics are disabled until the user inputs their passcode. This protocol, known as the Before First Unlock (BFU) state, is vital for safeguarding personal information from unauthorized access. After the passcode is provided, user data is decrypted, biometric unlocking is reactivated, and the device switches to the After First Unlock (AFU) state.
This automatic reboot feature serves to protect user data from potential threats, such as theft, by ensuring that the phone is secured after a three-day interval without activity. The BFU state is activated whenever the phone is restarted, adding an essential layer of protection for user information.
While Google’s release notes specify that the automatic restart is implemented for “Phone,” it is expected that similar functionality will soon be available for Android tablets. Furthermore, this feature is suggested to be optional, indicating that users may have the ability to disable it if desired.
Apple’s recent update with iOS 18.1 introduced a related feature that also reboots iPhones left unattended for a period of 72 hours to protect user information. This was notably observed when seized devices rebooted independently due to the newly introduced ‘Inactivity Reboot’ capability.
