GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
353 stars 20 forks source link

OS crashes when default system language is changed to English (Pseudo-Accents) #3392

Open chic0ry opened 6 months ago

chic0ry commented 6 months ago

Experienced this issue on my Pixel 8. Immediately after changing default system language to English (Pseudo-Accents), screen is no longer visible. It's possible to use the side buttons to reboot, but the lock screen appears only as a partial flicker (see below). The phone eventually wears itself out and displays the recovery option.

https://github.com/GrapheneOS/os-issue-tracker/assets/163559909/6ebe3a80-6b53-4247-b47c-3c7a882d2257

FID02 commented 6 months ago

It seems to be one of the pseudolocales that get activated when a user enables Developer options.

FID02 commented 6 months ago

Pixel 6a, GrapheneOS 2024032100

  1. Enabled Developer options

  2. Settings > System > Languages > System languages: added the English pseudolocale and set it as default Launcher then crashed. Attempting to view the system log caused Log viewer to crash. Impossible to do anything other than navigate in Settings.

  3. Captured a system log by switching back to English US in the same session. I can send this if needed.

  4. Did step 2 again and rebooted. I could unlock the lock screen. Launcher kept crashing. Was able to use the navigation bar to switch back to English US and reboot the phone. Phone otherwise unusable.

Pixel 6a, stock PixelOS AP1A.240305.019.A1

Performed steps 1 and 2 and did not experience any crashes or issues. Rebooted phone, no issues.

Might be an issue for developers who want to test their apps with pseudolocales on GrapheneOS. End-users shouldn't need to use this feature...

@chic0ry Are you able to boot into safe mode?

chic0ry commented 6 months ago

@FID02 I did not try safe mode, just rebooted several times and eventually did a factory reset from recovery mode.

Yes, developer settings were enabled so most people may not encounter this, although fwiw I had to enable developer mode in order to use Camo Studio, which is pretty popular.

MarekSurek commented 6 months ago

Same issue too but on custom rom, you must format data. If you have TWRP you can backup pictures etc to pc.