Per-app Language Picker Doesn't Work After Reboot/Locked (Android 13/14) [309393568]

Obsolete

Bug

Status Update

No update yet.

Description

se...@gmail.com

created issue #1

Nov 6, 2023 11:14PM

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

Screenshot_Emulator_Android13_20231106_143126.png

Restricted

110 KB

View

Download

Screenshot_SamsungS23Plus_Android13_20231102_124552.jpg

Restricted

939 KB

View

Download

Comments

vi...@google.com <vi...@google.com> Nov 7, 2023 02:31PM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> #2Nov 7, 2023 04:28PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Screen Record of the Issue
Please capture screen record or video of the issue using following steps:

adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

se...@gmail.com <se...@gmail.com> #3Nov 7, 2023 07:11PM

Bug report from Android 13 Emulator: https://drive.google.com/file/d/1AyugNTwPnfFU0b1NXAB8_5FHWHoIh9ej/view?usp=sharing

Screen recording: https://drive.google.com/file/d/1C3zziUg7J0n6tDHXKSRFjJC9SPdpnqQ8/view?usp=sharing

Also, note the 2 screenshots included in the original post, and how Samsung S23+ behaved differently than Emulator/Pixel 6. The issue was just exacerbated by Emulator/Pixel's process & memory management compared to Samsung. However, storage being moved to Device encrypted storage would fix it on all devices...

se...@gmail.com <se...@gmail.com> #4Nov 7, 2023 07:13PM

Also, when I mentioned Pixel devices above --- this is not a Pixel Emulator, it's a physical Pixel 6 phone running Android 14. (While the Emulator is running Android 13.)

Thanks!

vi...@google.com <vi...@google.com> #5Nov 8, 2023 06:54AM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

se...@gmail.com <se...@gmail.com> #6Nov 8, 2023 02:27PM

Thanks!

sh...@miniclip.com <sh...@miniclip.com> #7Feb 20, 2024 02:49PM

Any update?

se...@gmail.com <se...@gmail.com> #8May 3, 2024 06:09PM

Can we get an update on this? Last update was 6 months ago...

vi...@google.com <vi...@google.com> #9Sep 3, 2024 02:35AM

Status: Won't Fix (Obsolete)

Thank you for your feedback. We are closing the issue as “won't fix obsolete”. If this issue still exists in a current Android build, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.

se...@gmail.com <se...@gmail.com> #10Sep 3, 2024 02:38AM

Ummmm? How is this obsolete? I've asked for an update, waited for an update... now I need to open a new issue? It's still a valid bug...