This user never gets a badge, and secondary users will
see a security exception attempting to fetch it for
USER_ALL notifications, such as USB and battery state,
which are posted by USER_SYSTEM.
Bug: 28743335
Change-Id: I65aeb1cf2192811055f8cd94df0b7e292c5c1acf
Calling Configuration.setLocales with emtpy LocaleList may change the
layout direction to LTR. To clear the locales in Configuration without
layout direction change, introduce hidden API to Configuration.
Bug: 28695661
Change-Id: I47c339dffb83099bd329ddb60237dab27b05f593
am: a781232656
* commit 'a78123265658380b3968773a5f575b0ba1b4620e':
Put launch adjacent activity in a new task if the activity does exist
Change-Id: I3f08450d7cbb248467ba34e3a28c2b1225b92d31
am: a3aaa5ee25
* commit 'a3aaa5ee2558ac5a6b6ca0b309dc9eea4c51bf14':
Back up / restore the 'mono audio' setting
Change-Id: Ie20918c1a8306342de7a5e2201d3e55fff39500c
am: 6c2bc3db95
* commit '6c2bc3db95dde4e4dff9d04266c3b87c8a6af306':
Nav bar: fix tablet density change issues
Change-Id: I1a78b8cc86c3fef24cdddbd07c0dfafb61bca471
am: 538c22630b
* commit '538c22630b3ffd3c9efd544552d5a7fb3ae876a8':
Only broadcast screenshot error to the current user.
Change-Id: I0a0f1e04f9cc4bfcca3a9d1c93afad44759c6476
For the launch adjacent case we only want to put the activity in
an existing task if the activity already exists in the history.
Bug: 28828326
Change-Id: I1a6fdd6779cb20f8c0d9b7d94635b21718f4ac1b
am: 53b5df43b4
* commit '53b5df43b49b191e442c4d2c7b9a9cba3ebdcf92':
Rename PROPERTY_WORK_CALL to PROPERTY_ENTERPRISE_CALL based on API review
Change-Id: I92a8e1e1452ecc80d422c0905a4b86089d24e80b
When merging backed-up configurations with the current supplicant
configuration, we read both configurations into a instance of
WifiNetworkSettings. No EAP configurations should be restored as
per b/25725016, however existing EAP configurations that already
reside in wpa_supplicant.conf (presumably configured in SUW)
should not be removed in the process.
This CL adds a parameter to the "readNetworks" method to allow it
to select whether or not EAP configurations should be read in. It
is used to allow the "restoreWifiSupplicant" method to copy in EAP
configurations from the existing wpa_supplicant.conf, but not out
of the backup data.
BUG: 28873992
Change-Id: I8b3e0c1a6629b3f1ca5055b1b2190e6b3ca4c033
- Re-inflate the contents of the NavigationBarInflaterView
- Call up to parent to notify the contents has been reinflated
- Fix how default tunable is handled, so that the resource is
reloaded on density change
Change-Id: If25f68d01eedd3319b0c270e1cf80ac382eea637
Fixes: 27227522
This is distinct from and in addition to the limit on the number of
distinct notifications. This includes many updates to a single
notification.
Bug: 28693065
Change-Id: I5ec0911716cace91d3ad85435a5c6123b290b3a2
The purpose of DISALLOW_CONFIG_VPN is to stop users from configuring
VPN, not from using it at all.
The key difference being that if the admin already enforced a VPN then
that setting should be respected (but it still shouldn't be tamperable).
Bug: 28733079
Change-Id: Ib8cab5657a9d5819a019093da3812cd8c2ca4050
am: 761f70d5a6
* commit '761f70d5a6b926780db3bba95ee1e01b4d8d95be':
Add support for ICU data pinning in the Zygote
Change-Id: I7468ed57102b4eafdf9beb92119cd72b2aadfee2
All short codes are used by DCB on Google Play. Fixed default pattern for countries added recently.
Internal bug b/27911552.
Change-Id: I9b4a2bb30f2c6de058cc2adb75b67c4f69182198
Signed-off-by: Vasco Brito <vascob@google.com>
When transformation method is set via API, text direction heuristics has
to be reset since for PasswordTransformationMethod it is set to LTR. Not
resetting it causes inconsistencies with the remaining of the TextView.
Bug: 28562779
Change-Id: I225e35e39bde60d4296852ff17b107d5b7b99f8a
Originally we went with the meta-data approach to make unbundling
easier, however with the amount of platform changes that the config
ended up relying on it would be better to focus on exposing it through
the platform.
Bug:28763009
Change-Id: Iaf80001b1980220cd2e1e05faf2dc86af41700e1
We handled stale wakelocks (wakelocks that disappear from /d/wakeup_sources)
differently in previous version of Android. They would be set stale, but still be
updated with their previous counts (they would never disappear).
The method setStale has been replaced with endSample(), which is semantically different.
Once a SamplingTimer has endSample() called, it expects any future calls to update() to
be a new sample, meaning the entire amount passed to update() is included in the kernel
wakelock's total. Since stale wakelocks were never removed from the list, this would
increase by large amounts when nothing had actually changed.
This was exacerbated by the fact that there was a bug where the last wakelock in
/d/wakeup_sources was never parsed, so if the order ever changed, this "stale" wakelock
would suddenly re-appear and the entire amount reported would be charged to the wakelock,
instead of just the difference since the last update.
All this was exposed when we added support to handle wakelocks that would disappear and
reappear with smaller values, meaning the kernel had pruned them from its accounting and
reset them.
Bug:28601080
Change-Id: Ic96027f7d580dac5e20aa73d67e5cedac4ccabeb
am: eaad66b697
* commit 'eaad66b697b3605c1b5b75bb203ea308dee2589c':
fix dashboards page. the src attributes were being modified by the devsite parser, so i renamed those attributes then rename them again at runtime. bug: 28801246
Change-Id: I3a8035cfb8cb03315cb47344f432e88b4dcac205
