The previous CL wrongly restores all priority to nice 0.
This CL changes two things:
1. It remembers and restores the previous priority.
2. If the thread has priority of < -2. Do not set it to -2.
BUG: 29930920
Change-Id: I927e060d789c9bbf92f6a166f44317d9db0f5205
bug: 26562461
fixes: 30109912
SeekBar clips out the area of the thumb when drawing its track. This
creates a clip region, since a rect has been subtracted.
This changes region transform support in computing final clip to
properly support any rect-to-rect transform (such as 90 degree rotation)
when applying a clip region.
Change-Id: Ib3bbc52637e59e00b3a7e7d5c4c40555e26c578b
Most devices running Android N support only software-based key
attestation, so added several notes to the pages describing this
tool to help developers understand how to tell whether a device
supports only software-based key attestation and the associated
effects of this support level.
Bug: 28851641
Change-Id: I16c8ad7702814eba1e4b8b3ee7e9a569d08c3ff4
Detect it when a developer accidentally uses @string/... in string fields
and log an error rather than publishing shortcuts with wrong values.
Bug 30140672
Change-Id: I98a60afd7f52282019a94a7a8c30a85ea4c7806b
If the primary user has a managed profile:
When setting the clipboard in the primary user:
The uris of the primary user's clipboard must not have an
embedded userId.
BUG:28572936
Change-Id: I1eb505c4518cc16a6513b950f6c2b1232a22426d
- Removed Secure.ACCESSIBILITY_DISPLAY_COLOR_MATRIX, it's not desirable
to persist the actual color transformation matrix.
- Refactored all SurfaceFlinger transforms to DisplayTransformManager,
which allows color transforms to be set independently from the a11y
manager service.
Bug: 30042357
Change-Id: Iefa477dedb66aac90e1218e327802a3fab6899ed
Block the user from entering safe boot mode if the DISALLOW_SAFE_BOOT
policy is set.
Bug: 26251884
Change-Id: I4945d5d676928346c11ea305a5b6a2e1a42e94e6
When Tethering.stopTethering(<wifi>) is called, we set
mWifiTetheringRequested to false and request the AP be torn down.
Previously, we would discard WIFI_AP_STATE_CHANGED_ACTION Intents,
because mWifiTetheringRequested was set to false. This would in
turn cause us to leave tethering enabled, because we only tear down
tethering upon noticing that the interface is going down
(as signalled by WifiManager via this Intent).
In the past, this was covered up because we would tear down tethering
when the interface was taken down. Now that we rely on SoftApManager
to notify us of AP state, we need to pay very close attention to what
is being said about the state.
Bug: 30124308
Test: Can toggle tethering on and off reliably on shamu, bullhead,
angler with no SIM. Can toggle tethering on and off on a marlin
with T-Mobile SIM.
Change-Id: If46a8ee11cf4c07c5cc336523f5e5f00273500ec
When process the stop list we remove an activity that was previously
waiting for visible and is now visible from the list and also hide
its windows if it is finishing. However, we don't transition it to the
stopped state because it was waiting for visible. If it is finishing
and the windows are hidden then it makes sense to transition it into
the stopped state since it will not be visible to the user again.
Bug: 30058392
Change-Id: Iac81e2877716ae58d05aed42e1433190a2f70428
This patch adds APF filtering of ARP replies for interfaces with APF.
- when the interface has no IPv4 address, broadcast ARP replies with a
0.0.0.0 target ip are dropped (GARP), ARP requests with a 0.0.0.0
target ip are dropped.
- when the interface has an IPv4 address, broadcast ARP replies to a
different ip are dropped (including GARPs to 0.0.0.0), ARP requests to
a different ip are dropped.
Bug: 29404209
Bug: 30080487
Change-Id: I82613eb865c7f38b6260997fe2caf2aff382ad78
