So that the binned brightness sensor immediately updates
the brightness rather than using its 2-3 second debouncing logic.
This prevents a delay in reporting brightness updates when the
device's proximity sensor stops being covered.
Test: atest DozeScreenBrightnessTest
Fixes: 200768925
Change-Id: Ib1158894d4f7b303247feacd24664f628663d733
rename renounce fine location data to include location data
Bug: 210923726
Test: cts
Merged-In: Ic2ce84f51bf394031903ae180788216cfa910fc0
Change-Id: Ic2ce84f51bf394031903ae180788216cfa910fc0
This reverts commit 8a0497caf98385fe3dfb4eb64ec7df1bff10a92e.
Reason for revert: DroidMonitor: Potential culprit for Bug 222015750 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Change-Id: Ie2add444135faf605d11cf770f085b4fc52a01e2
am skip reason: Merged-In I43d7177c509501efd65e32ab3ad000d17d6ffb6c with SHA-1 598a193f7f is already in history
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2040764
Change-Id: I413af93abd089096f814fe11d7a612896d431749
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Regression from ag/17456722 that setting the shadow radius when leaving
away from PiP would result in screen dimming.
Change to apply shadow radius when entering / moving / resizing PiP only
Bug: 227607130
Test: follow the reproduce steps in bug
Change-Id: Ie4d4dba94a1c66da52825798df60ebf3f971aa32
Consent dialog string update from "Only this time" to "Allow one-time access".
This codebase is the continuity of the implementation ag/16618162 to
obtain user consent.
Bug: 193708292
Test: CtsVerifier
Ignore-AOSP-First: pending fix for logcat privacy issue
Change-Id: I27c16ec89d097d52e649c961b80ffb1284680202
This was previously deprecated in favor of preferredDisplayModeId.
However, display modes include specific resolutions
so we would still need an API for the valid use-case
of specifying only a preferred refresh rate.
Bug: 227627158
Bug: 224915081
Test: built locally
Change-Id: Ic7c711d03d3ccc7a5193b26ca38159f048777927
The top complications will move first, and then the bottom
complications.
Test: locally on device
Test: atest ComplicationLayoutEngineTest
Bug: 220307939
Change-Id: I0d88caa2c2eb3eb03294379a9356e7ffd8856c30
process state
Bug fix to retrieve process state by calling getUidProcessState() rather
than calling getUidImportance()
This codebase is the continuity of the implementation ag/16618162 to
obtain user consent.
Bug: 193708292
Test: CtsVerifier
Ignore-AOSP-First: pending fix for logcat privacy issue
Change-Id: I55afc2a11744eeb5da83222b953b539c1bc60b05
If a job is started as an EJ, we should stop it once the EJ quota is
finished, regardless of remaining regular quota. If we don't, then the
job would get EJ privileges even though the app shouldn't be getting
them anymore.
Bug: 224533485
Test: atest CtsJobSchedulerTestCases:JobThrottlingTest#testRestrictingStopReason_ExpeditedQuota_noCharging
Test: atest CtsJobSchedulerTestCases:JobThrottlingTest#testRestrictingStopReason_ExpeditedQuota_startOnCharging
Test: atest CtsJobSchedulerTestCases
Change-Id: Ib11023c4e3c05f2b3512bd069bda953fdd9bd0b9
Propagate the clipData from the clipboard URI to the app receiving
the REMOTE_COPY intent (including URI permissions). Also limits
to a configurable component.
Bug: 217724692
Bug: 217739484
Test: manual, using test app implementing REMOTE_COPY
Change-Id: Ie9f700c2dc546960334c3a0f5051f75d08b897cb
* changes:
Only invoke listener once physical address becomes known
Don't remove devices on onHotplug()
Assign local device portId 0
Set device type on first message received
Some callbacks want to know when the bouncer
starts transitioning to show (ie: UDFPS animations)
while other callbacks only care if the bouncer
actually fully showed (ie: running face auth).
We want to make sure we don't over-trigger
face auth, so only request face auth when
we know the bouncer is fully shown rather
than in the middle of a transition to potentially
showing the bouncer (sometimes it can be quickly
cancelled).
Test: atest SystemUITests
Fixes: 226967764
Change-Id: Ifca6fb1861992a78815066571019226322260279
am skip reason: Merged-In I377cab85a1b39ef2887b452d1ffcdc5b00a8d5ab with SHA-1 c55590c810 is already in history
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2047905
Change-Id: I7a5305e6060aa0d601e922f0cc829105d3065b2a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Right now the big picutre bitmap was loaded at 480px from URI and unrestricted from any other source. This adjusts that size to always consistently restrict it to 358dp, which is the maximum size of notifications.
Bug:210690571
Bug:218845090
Test: Manually on device
Change-Id: I9586488ba307e19bdc8c1af6f8c99cd369cd94c9
BroadcastDispatcher and BroadcastSender will handle this on background threads and avoid jank.
Bug: 224545601
Test: Tested ScreenshotView functionality on a physical device
Change-Id: I3b1c0d3f14dc4e1010a2e8754aac57755ce726cc
