The new per-app languages introduced in Android 13 are NOT being respected for LOCKED_BOOT_COMPLETED. So, for apps like alarms, reminders, etc. the user may be presented with the wrong languages until the device is unlocked. Further complicated for alarm/reminder apps that respect Direct Boot mode, as this makes it possible for the alarms to go off on Android N+ prior to unlocking after a reboot.

Find attached a sample app that will publish a LOCKED_BOOT_COMPLETED notification while locked, and then a BOOT_COMPLETED notification after unlocked.

Steps to reproduce with sample app:

launch app and grant notification permission on an Android 13 or 14 device
change app language from phone's Settings > Apps > (this app) > Language (only supports English/French languages, so change to French unless that is the default-default)
make sure the device has a lock security password, pattern, etc.
reboot the device, notice the LOCKED_BOOT_COMPLETED notification and error logs
unlock the device and notice the BOOT_COMPLETED notification and logs

Notes:

For Pixel phones and Emulators both LOCKED_BOOT_COMPLETED/BOOT_COMPLETED are in the same device-default language (see attached image Screenshot_Emulator_Android13_20231106_143126 - tested on Android 13 Emulator, and Pixel 6 phone w/Android 14)
For Samsung phones LOCKED_BOOT_COMPLETED will be in device-default language, BOOT_COMPLETED will be in app's selected language (see attached image Screenshot_SamsungS23Plus_Android13_20231102_124552 - tested on Samsung S23+ w/Android 13)
The difference between these 2 seems to be that Samsung kills the process almost immediately after the LOCKED_BOOT_COMPLETED, while Pixel phones & Emulators can keep the process alive longer, so a new process isn't created for the BOOT_COMPLETED call

Desired Behavior

For Android 13/14 the per-app language preference should be moved to Device encrypted storage so they are available for app's supporting Direct Boot mode and LOCKED_BOOT_COMPLETED
For Android 12 and under, ContextCompat.getContextForLanguage() and similar resources should also support Device encrypted storage
Please also migrate existing language selections so the user's language isn't reset when the storage moves - ie. using Context.moveSharedPreferencesFrom(), Context.moveDatabaseFrom(), or similar

The sample app has been shared with android-bugreport@google.com and is available at: https://drive.google.com/file/d/1m2CCTdAypxcJBvIGmcSWevao08mbHs9X/view?usp=sharing

Issue 309393568

Links (5)

Issue metadata