- 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
am: 3053c3f
* commit '3053c3f2a94b24ceeed9c46cb84045c285d3523b':
Set BugreportProgressService to run on foreground.
Change-Id: Ib5b92dfcaf3dca5710abc19f261fed8017fcae1f
am: 0a67c6a
* commit '0a67c6abd579605f2b11b92072d4e7552f70c7e5':
docs: Small edits to Vector Asset Studio Support Library support b/28199128
Change-Id: Idb825df3824d43663b7824b1689abbdcf0279bdc
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
am: 665189f
* commit '665189f92646d34bf02082120cba3c62aa718770':
Don't back up wallpapers that we've been told not to
Change-Id: I60eb02a9b1ab8da966d964c62a6dccf52d873e94
As a workaround for b/27870771, convert fatal exception into a
warning.
Duplicate calls to finishPendingSequence with the same sequenceId
are seen in user crash reports, but with no further context and
inability to reproduce after testing various hypothesis, just
warn about it happening.
Bug: 27870771
Change-Id: Icd7d408887e04b94092689ce61809d6c664d8e3a
BugreportProgressService do not persist the user-provided
information (like details and screenshot paths), so if it's killed by
the framework, that info is lost.
Running it as foreground mitigates the changes of it being killed.
BUG: 27431998
BUG: 28291423
Change-Id: I2f58507beb38309628f2f19d3f7f950d07eca16f
am: 5a6c58e
* commit '5a6c58e00202ed83cd60a02cd6a79da65598b655':
Do not prematurely update position while bounds animating.
Change-Id: I7ad0d28dbe7e4224c7ce50fb6996ccec98d7fd4b
am: 54c4374
* commit '54c4374b4a67fdfbda936e7f4a8a9538e16c3557':
Fix bug where fingerprint for wrong userId was attempted to be removed.
Change-Id: Ib762515ea86e8dc9eb475f1a3f0eb472da6447c4
Calculate the baseline power usage for the device when it is in suspend and idle.
The device is drawing POWER_CPU_IDLE power at its lowest power state.
The device is drawing POWER_CPU_IDLE + POWER_CPU_AWAKE power when a wakelock is held.
The device is drawing POWER_CPU_IDLE + POWER_CPU_AWAKE + POWER_SCREEN_ON when the screen is on.
Bug:27533512
Change-Id: Idcb587390bc8159fcbd6625cca4cb1aca19976d6
In addition, now that the full uncropped wallpaper image is being
backed up, we now handle that via the full-data backup path instead
of key/value. Restore still knows about legacy data that gets
delivered via the older key/value mechanism.
This change also has the effect of removing the size limitations
around wallpaper restore acceptance. Any size source imagery is
valid, as crop & scale are rerun in a device-appropriate way
after the restore.
Bug 25453848
Bug 25727875
Change-Id: Idc64a2eaab97a8ecc9d2b8ca5dc011f29cab324d
