In reply to @cyb3rko:matrix.org
That's weird

In reply to @obersuppenruehrer:matrix.org
I've had that problem since I started using AM years ago. Only recently came up with the idea to use split apks version and only select Eng locale.

In reply to @muntashir:matrix.org
What's your Android version? I have never received such reports before. I have tried the auto mode with device language set to Spanish. Wasn't able to reproduce it. Yes, handling in-app language setting can literary make you mad (there's write-up on this). But things have since improved with the introduction of framework support in Android 13. However, the implementation is still incomplete.

Android 13, but happens since 11 or 12 on this device. I am 99.999% sure that we've talked about this years ago. Hence my remark "Muntashir has voiced his frustration with Android's localization, too."

PS: My older Android 9 device doesn't have this issue.

In reply to @cyb3rko:matrix.org
I wonder how it's implemented.
Because all other apps including my own just work fine.

In reply to @obersuppenruehrer:matrix.org
Tonight AM[D] has given me a really hard time. I wanted to go back to AMD. The main reason was the improved apk parsing (AM 4b2 has problems parsing some apk files of shady origin that the latest AMD parses fine). The second objective was making some screenshots of the "mixed languages mode." I tried to employ what I learned in my recent struggles with AMD 4b2, but to no avail. I uninstalled my perfectly working AM 4b2, rebooted the device, removed all Wifi Debugging pairs, rebooted the device, paired shizuku again. Then I installed AMD 4b2. On the first start, the initialization stage took almost 3 minutes. I rebooted the device again, which shorted the initialization stage to ~30 seconds.
Then I tried, in vain, for 2 hours to get it paired. On each attempt, it either hung indefinitely at the "Loading..." or simply did nothing when clicking on "Go. "
After 2 hours, I gave up. Uninstalled AMD, rebooted, installed AM 4b2 rebooted, paired Shizuku, and then tried to pair AM 4b2. Again, without success. After 30 minutes, I gave up, uninstalled AM 4b2, rebooted and installed AM 3.7.1, had it paired inless than 2 min, and everything was working fine. The pairing mechanism in 3.7.1 is far superior and more foolproof than the new one in 4b2 Then I did a direct update to AM 4b2 (apks with only en locale), and everything is working again.
Needless to say, I won't touch AMD again anytime soon.

PS: I could kick myself in the rear for forgetting to take screenshots of the "mixed languages mode." 🤕

In reply to @muntashir:matrix.org
In my tests in Android 14 and 15, only app label, components, permissions and their descriptions are affected by the localization issue. This effectively means that the framework, for some reason, is unable to retrieve descriptions in the in-app locale and uses the system local instead.

In reply to @obersuppenruehrer:matrix.org
@muntashir:matrix.org have you dropped the support for APKUpdater? I'm testing it for the first time atm.

In reply to @muntashir:matrix.org
It's literally a no-feature. It only displays an APKUpdater menu item if the app is present in the system. It was added in 2020, I think.

In reply to @obersuppenruehrer:matrix.org
I see, I just learned about it in the AM manual and wondered that the menu item isn't there after install.