c63a16b8e46f2f3ecce6c548663cc3185f011fd6
There are two separate issues here that need to be fixed, both boil down to the fact that adding an imperative (userSetLocale) to the Configuration is a bad idea. Because of this: - We'd never persist the first user set configuration if it was en_US, because of an erroneous call to Configuration.setLocale. - ActivityManager.getConfiguration would sometimes return a Configuration with userSetLocale == true, which means callers with the right permissions would inadvertently persist a locale they didn't want to persist. bug: 18879010 Change-Id: Id330ffde9d2a6e516fd60edc33f5529df719c634
am
eec6dd77: am a87f3555: am d8bd117c: Merge "docs: Add parent calls to WatchFaces snippet." into lmp-docs
am
5fed49f7: am 4d9fcae2: Merge "Allow for a NoOp implementation of DrmManagerClientImpl" into klp-modular-dev
…
am
c598047d: am ca67a249: am bb600de6: am 74147527: am 8505c387: Special case AppCompat to show action bar.
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%