The existing DensityContainer already did this for density changes,
repurposed it to handle other Configuration changes. Also renamed
to AutoReinflateContainer.
Bug: 27952059
Change-Id: Ieb572abcbafe49aec73b16e1bcb8c294011afdd3
The following error was thrown, given that Activity is generating a
protected broadcast:
Sending non-protected broadcast
android.intent.action.SHOW_KEYBOARD_SHORTCUTS from system
Bug: 28138503
Change-Id: I50d5212d7776d33ffe6e9df1c5f080205ac4a29d
In particular, don't try to call the k/v wallpaper restore helper's
onRestoreFinished() if we are actually doing a full-data restore.
Bug 28132784
Change-Id: I2eaf748f6d54601f0ca195ae2781aa177daf0b93
If the surface is explicitly hidden while we're changing resizing mode,
we need to discard the preserved surface immediately, otherwise it could
linger around on screen.
Do not mark mAnimatingExit in setTokenVisibilityLocked. This flag can only
be set after client relayouts to invisible. There we set mAnimatingExit and
mAnimating, so that when animation finishes the surface is marked to be
destroyed. If we marke it too early (and not mark mAnimating at the same
time), the surface may get stuck in exiting state.
bug: 28236574
Change-Id: I5cc916dfa698113e1d783a66547e1878469a9879
- fold IpReachabilityMonitor* classes into a single IpReachabilityEvent.
- only log an event for NUD_FAILED Netlink answers.
- distinguish between NUD_FAILED with or without lost of provisioning.
- do not record host ip addresses.
- record interface name instead of interface index when losing
provisioning.
- also return an error code when probeNeighbor fails, and log this error
code in IpReachability events.
Bug: 28204408
Change-Id: I5f0def0ab1ace7e467a0c69b3b82d07ef2252307
There are two types of IMEs:
A. IMEs that have one or more subtypes
B. IMEs that have no subtype
The initial implementation to update hardware keyboard layout per
subtype change of layout (See Bug 25752812) has supported IMEs in the
category A only, and IMEs in the category B are just ignored in both
system and Settings app.
In order to support IMEs in the category B, InputMethodSubtypeHandle and
related methods need to accept null InputMethodSubtype. Technically
this is a straightforward change, because in InputMethodManagerService
we have already used InputMethodUtils.NOT_A_SUBTYPE_ID for those IMEs in
the category B. We also need to update Setting App, which will be done
by a different CL [1].
[1]: I46b9c5b018f08e3eaa4614a0893db0be91652f3c
Bug: 28182650
Change-Id: Ia013784a594ad3beaf30976d047f5ac0fa8185be
Print interval clamp message
only for periodic jobs having
period/flex less than the minimum value.
Bug: 28296128
Change-Id: Id0d7c3b56048582a490bb8214eca491ec2bbdc93
Test all A2DP type variants when checking if an A2DP device is connected
in isBluetoothA2dpOn().
Bug: 28286051
Change-Id: I756d632b12d584d8a27cc1890e758d8accff7120
scheduleCrash() calls into the app process to ask it to nicely show
the crash dialog. If that call fails, rather than just silently
stopping, kill the process right away. It might be out of control.
This also adds an additional check for killedByAm to the flow there
so if the activity manager already has killed it, the dialog won't
be shown.
Bug: 28196243
Change-Id: I979f01074e5890640e7b06e29eeb0d6c38803569
When we attach an activity to an existing
task, and that task is already on top,
disallow changing stacks altogether even
if launch stack id is set.
Bug: 28026847
Change-Id: Ie70f0585a29dc1b85a5093624fede32110be3c76
Code was checking whether the directory for recent_images existed in
many places unnecessarily causing StrictMode violations. Moved the
code to only attempt to check and create the directory before
actually writing to disk.
Bug: b/28195831
Change-Id: I05f77a10f1dafc8cc0b1836b62352d56549ac1ee
