In practice, a lot of apps provide English resources as their default resources, so assume that English is always supported. With this change, users can safely set secondary locales after English in their preferred locale lists. Such settings would help the apps (and parts of the system that are aware of multiple locales) consider the user's familiarity with the secondary locale or the user's preference for glyphs forms in the secondary locale. This change makes sure that no app unintentionally switches to such secondary locales. Note that this doesn't break from the tradition of previous releases. Traditionally, if the user had set the system locale to English, they would get the default resources when the app didn't explicitly provide English resources. This will continue to be the case where the user's locale list has English in it before another supported language. (English will be the first locale in most cases.) Bug: 26192817 Change-Id: I2c1a003760299157786c1b3f9fb116ce18db3b8c
…
…
…
Description
No description provided
Languages
Java
77.3%
Kotlin
9.2%
PowerBuilder
6.6%
C++
5.5%
AIDL
1%