Age | Commit message (Collapse) | Author |
|
sparse-9583930-L95100000958584662 into tm-d4-release.
COASTGUARD_SKIP: I5620b0c507322026f3e64aac0c411b6b1373610a
COASTGUARD_SKIP: I56c2fc14f906cdad80181ab577e2ebc276c151c1
Change-Id: I80ea76405e3ce87f9d22603bd61a6a203e468179
|
|
into sparse-9583930-L95100000958584662.
SPARSE_CHANGE: I56c2fc14f906cdad80181ab577e2ebc276c151c1
Change-Id: I5620b0c507322026f3e64aac0c411b6b1373610a
|
|
This adds validation that the package name passed to
setApplicationRestrictions is in the correct format. This will avoid
an issue where a path could be entered resulting in a file being
written to an unexpected place.
Bug: 239701237
Merged-In: I1ab2b7228470f10ec26fe3a608ae540cfc9e9a96
Change-Id: I56c2fc14f906cdad80181ab577e2ebc276c151c1
(cherry picked from commit 1b9b59c63bffc675a042cba6cd666831abef2c3e)
Merged-In: I56c2fc14f906cdad80181ab577e2ebc276c151c1
|
|
'googleplex-android-review.googlesource.com/20653054', 'googleplex-android-review.googlesource.com/20082616', 'googleplex-android-review.googlesource.com/20747371', 'googleplex-android-review.googlesource.com/20482625', 'googleplex-android-review.googlesource.com/21342999'] into tm-d4-release.
Change-Id: Iaa7a52dbdf5a81f02c6abcb89ab13c43fc030e6f
|
|
Bug: 263449831
Fixes: 263449831
Test: atest service.incremental_test
Change-Id: Ia3da6ca047c46807cbd72ef797bb4b300c38efb3
(cherry picked from commit 96cac56f51fdac09d7e542d4dfa852b91b53e99b)
Merged-In: Ia3da6ca047c46807cbd72ef797bb4b300c38efb3
|
|
name
This change makes sure that the extracted component name in a
MediaButtonReceiverHolder matches the Media Session owner's package
name. This avoids incorrectly routing media button events and potential
security issues.
Bug: 244312001
Bug: 238177121
Test: atest CtsMediaBetterTogetherTestCases
Change-Id: Ifac9cf53889222e31d18c14c1e096ee68c0a346c
(cherry picked from commit 185c3e252397bfa37592edbb5b2f5ae97db92eda)
Merged-In: Ifac9cf53889222e31d18c14c1e096ee68c0a346c
(cherry picked from commit 48c388277880e56ab5cc29e145e4d00aa383ce01)
Merged-In: Ifac9cf53889222e31d18c14c1e096ee68c0a346c
|
|
Bug: 251778420
Test: wiped phone and verified that only a toast was shown before setup
Test: atest ClipboardListenerTest
Change-Id: I7d5b0c0cda2191e487468f52a7ad345ba8b54a86
Merged-In: I7d5b0c0cda2191e487468f52a7ad345ba8b54a86
(cherry picked from commit 14a958756ff5725093199e68d04d22a85badcc16)
Merged-In: I7d5b0c0cda2191e487468f52a7ad345ba8b54a86
|
|
Prior to this CL, WorkSources would Parcel their list of WorkChains as
-1 if null, or the size of the list followed by the list itself if
non-null. When reading it back in, on the other hand, they would check
if the size was positive, and only then read the list from the Parcel.
This works for all cases except when the WorkSource has an empty but
non-null list of WorkChains as the list would get written to the parcel,
but then never read on the other side.
If parceling a list was a no-op when empty this wouldn't be an issue,
but it must write at least its size into the parcel to know how many
elements to extract. In the empty list case, this single element is left
unread as the size is not positive which essentially corrupts any future
items read from that same parcelable.
Bug: 220302519
Test: atest android.security.cts.WorkSourceTest#testWorkChainParceling
Change-Id: I2fec40dfced420ca38e717059b0e95ee8ef9946a
(cherry picked from commit 266b3bddcf14d448c0972db64b42950f76c759e3)
Merged-In: I2fec40dfced420ca38e717059b0e95ee8ef9946a
|
|
The autosizing logic seems to have inadvertent side effects. Will remove
this for now.
The autosizing logic was added in ag/20612038. I'm opting to fix forward
because other changes were added into that CL.
Fixes: 261552438
Test: open up bouncer.
Change-Id: I44c41c93ad235b09fc6e4e9966b24c6b4fdcd915
(cherry picked from commit 70fec19e8ea4014dabe8bf0cfb9bac54cce99158)
Merged-In: I44c41c93ad235b09fc6e4e9966b24c6b4fdcd915
|
|
This adds validation that the package name passed to
setApplicationRestrictions is in the correct format. This will avoid
an issue where a path could be entered resulting in a file being
written to an unexpected place.
Bug: 239701237
Merged-In: I1ab2b7228470f10ec26fe3a608ae540cfc9e9a96
Change-Id: I56c2fc14f906cdad80181ab577e2ebc276c151c1
(cherry picked from commit 1b9b59c63bffc675a042cba6cd666831abef2c3e)
Merged-In: I56c2fc14f906cdad80181ab577e2ebc276c151c1
|
|
sparse-9589702-L50800000958550213 into tm-d4-release.
COASTGUARD_SKIP: I0e66506ece75eee97a5c0b21a4e2517101e453ca
COASTGUARD_SKIP: I92e5ab81f3ab9ddbb707a27215a97a08835a6323
Change-Id: I2dc48a9b716372e1362ee0751c3dfd29f90f27c7
|
|
into sparse-9589702-L50800000958550213.
SPARSE_CHANGE: I0e66506ece75eee97a5c0b21a4e2517101e453ca
Change-Id: I92e5ab81f3ab9ddbb707a27215a97a08835a6323
|
|
This reverts commit f4837869e7997e0cd12ee4ab612c7d75e4b3c500.
Reason for revert: suspect b/268591932 culprit
Change-Id: I0e66506ece75eee97a5c0b21a4e2517101e453ca
(cherry picked from commit c5ad66601a8b15d289ff1d2603efdce35d3dabd2)
Merged-In: I0e66506ece75eee97a5c0b21a4e2517101e453ca
|
|
into tm-d4-release.
Change-Id: I3c7b607fbe6ac663fb9123079f23b7e06fb6ca94
|
|
The 4-hour idle timeout is scheduled when the device is locked (by
manually pressing the power button or after the screen timeout). This
usually happends when Keyguard decides to show up.
In the face non-bypass case, Keyguard is already shown and its state
will be reset after locking device. The idle timeout should also be
scheduled in this case.
Additionally, check if any non-strong biometrics are enrolled and
enabled. If not, do not schedule the idle timeout when the device is
locked.
Bug: 244743493, 261813434
Test: On a device with UDFPS, manually
(1) set up face auth, (2) unlock with face auth and stay on
Keyguard, (3) lock device, and verify that the alarm for idle
timeout is scheduled properly by "adb shell dumpsys alarm"
Test: On a device with side FPS, manually
(1) set up fingerprint (no face auth), (2) lock device, and verify
that no alarm is schedule for idle timeout, (3) swipe up to show
bouncer, and verify that the string on bouncer properly shows
"Enter your PIN" while side FPS can also be used for auth.
Repeat steps 2-3 after enabling face auth and then deleting it.
Change-Id: I8404927e8155f40496ac1740e4a6b7b38458f1f5
(cherry picked from commit f766281fafc48ce68dcd657c98cb39e33ef425c4)
Merged-In: I8404927e8155f40496ac1740e4a6b7b38458f1f5
|
|
sparse-9565633-L11900000958535598 into tm-d4-release.
COASTGUARD_SKIP: I2cf299f2aead4d5e524fd0367376df708902e8b3
COASTGUARD_SKIP: Ia3da6ca047c46807cbd72ef797bb4b300c38efb3
Change-Id: I392050757d60a9a5ecca28b519829c063819d64a
|
|
into sparse-9565633-L11900000958535598.
SPARSE_CHANGE: Ia3da6ca047c46807cbd72ef797bb4b300c38efb3
Change-Id: I2cf299f2aead4d5e524fd0367376df708902e8b3
|
|
Bug: 263449831
Fixes: 263449831
Test: atest service.incremental_test
Change-Id: Ia3da6ca047c46807cbd72ef797bb4b300c38efb3
(cherry picked from commit 96cac56f51fdac09d7e542d4dfa852b91b53e99b)
Merged-In: Ia3da6ca047c46807cbd72ef797bb4b300c38efb3
|
|
into tm-d4-release.
Change-Id: I0f7b3e9b4029d8ccce34fb712a5ceb65408d0a63
|
|
new priority for auth screen. this allow to request higher refresh rate for screens where auth possible, and avoid swithcing rate when LHBM mode is activated
Test: atest DisplayModeDirectorTest
Bug: b/263908377
Change-Id: I2c19941dd9507d7e9171e30f6f433384ef620a92
(cherry picked from commit cf4d352d6e900ed12e27b29e940fa8bffd66071c)
Merged-In: I2c19941dd9507d7e9171e30f6f433384ef620a92
|
|
'googleplex-android-review.googlesource.com/20690268'] into tm-d4-release.
Change-Id: Ie780e373a3fd3b6f02a70b893a1856d9f20fb4d5
|
|
Test: Auto + manual
- Add work profile -> QS tile is added
- Remove work profile -> QS tile is removed
- Reboot the device -> QS tile is in place
- Reorder tiles, reboot the device -> order is persisted
Fixes: 234639083
Change-Id: I4481a3f28f9d1f0c30618afaf78179e0033f50fb
(cherry picked from commit a240e7eebe6fc81f123150a362c493a6f93b9d2c)
Merged-In: I4481a3f28f9d1f0c30618afaf78179e0033f50fb
|
|
Found a couple of responsive issues and fixing them.
1. Numpad key digits had a min size of 32 sp. This would look off when
we maximize the display size and go into half folded on a foldable
device. I set the text to autosize with a max size of 32sp.
2. Userswitcher anchor was squished in password security method on
tablet. I removed some clipping in order to fix this.
Fixes: 261062809
Test: Open password view with max display and normal display sizes for
tablet.
Test: Half fold on foldable for pin view in bouncer.
Change-Id: I78fbbb231c35118bef65660b7ca5562d77dad16b
(cherry picked from commit 230dcab138f069b89215161ce368b124f8bbe8ee)
Merged-In: I78fbbb231c35118bef65660b7ca5562d77dad16b
|
|
sparse-9548814-L50200000958429818 into tm-d4-release.
COASTGUARD_SKIP: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
COASTGUARD_SKIP: I5281561a69909ce30323e1b74e259c058baa46a3
Change-Id: Ib050b975d4afb842d40c06932e8e7d99b6c5d616
|
|
into sparse-9548814-L50200000958429818.
SPARSE_CHANGE: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
Change-Id: I5281561a69909ce30323e1b74e259c058baa46a3
|
|
For some unknown reason, the merged imsi list might contain
duplicated items. Deduplication for better error handling.
Test: NetworkPolicyManagerServiceTest
Bug: 243015487
Fix: 261225039
Change-Id: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
Merged-In: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
(cherry-picked from aosp/2198759)
(cherry picked from commit a4b025f771c7908524a72b2c12b987772d25645c)
Merged-In: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
|
|
into tm-d4-release.
Change-Id: I85953848acc3d7b85ea4538cdba4597d353484c3
|
|
For some unknown reason, the merged imsi list might contain
duplicated items. Deduplication for better error handling.
Test: NetworkPolicyManagerServiceTest
Bug: 243015487
Fix: 261225039
Change-Id: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
Merged-In: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
(cherry-picked from aosp/2198759)
(cherry picked from commit a4b025f771c7908524a72b2c12b987772d25645c)
Merged-In: I69d332ee0acde6cdd7582d1aa18c82576f7090f2
|
|
'googleplex-android-review.googlesource.com/20870165', 'googleplex-android-review.googlesource.com/20946885'] into tm-d4-release.
Change-Id: I279294d403982f76c06a96d2a9ac7e3e50a31844
|
|
This CL refactors the way the ActivityLaunchAnimator and
DialogLaunchAnimator handle the visibility of the animated View when
that View implements LaunchableView.
Before this CL, a View that is animated would always end up being
VISIBLE, even if something made that View INVISIBLE or GONE before or
during the animation. That is because our animation code would sometimes
change the visibility of the View, using View.setVisibility.
After this CL, when animating a LaunchableView, all the visibility
changes made to the animated View are done using
View.setTransitionVisibility instead. That way, a LaunchableView can
track all calls to View.setVisibility only and restore the last
visibility that was set on the View at the end of the animation. Doing
so ensures that all calls made to View.setVisibility have the expected
result once the animation is done.
Bug: 264728445
Test: DialogLaunchAnimatorTest
Change-Id: I5848d42ef94952ecf058d4e895164389e37e0311
(cherry picked from commit 9ecb3db788b9f6be586c0f4f90c19d6337a7cd1b)
Merged-In: I5848d42ef94952ecf058d4e895164389e37e0311
|
|
This was mistakenly removed in ag/16792104.
Fixes: 264672007
Test: manually check that when UDFPS is enrolled,
the preferred refresh rate is used on keyguard
Test: atest NotificationShadeWindowControllerImplTest
Change-Id: I6e98bf8f889c24d7da04fe0a7f4c93ab394b8032
(cherry picked from commit ceed101fdfa076a72e58eb713a5ab474b49e0d95)
Merged-In: I6e98bf8f889c24d7da04fe0a7f4c93ab394b8032
|
|
This CL fixes the View that is used when showing the Foreground Services
dialog.
Test: Click the FGS button when the Security button is also shown.
Bug: 264728445
Change-Id: Id686279bbfc1e47e28da894342688d44183ebf42
(cherry picked from commit 0e7b6e534c1a818d1539e12d2febe2d26b7fa026)
Merged-In: Id686279bbfc1e47e28da894342688d44183ebf42
|
|
Change-Id: I84892820461f00149e1adb6b9c203af534a1c162
|
|
- When invalidating an existing external interface, we also need to
unregister any listeners to ensure that binder death recipients are
unlinked. Otherwise, a crash in the process for the old listener
can cause the current listener to be unregistered.
Bug: 242377577
Test: atest WMShellUnitTests
Change-Id: Ibb77ac19e4ebc616b8977db70d6269e3b930848e
(cherry picked from commit 9a81477e866ad1837cc7fdbaad80b15cdbafc936)
Merged-In: Ibb77ac19e4ebc616b8977db70d6269e3b930848e
|
|
Change-Id: I121e21e71585c8964e65753956b1d635369600cc
|
|
UserManager.getUserSwitchability was calling telecomManager.isInCall
method to see whether there is an ongoing phone call. Since the call
was made from client side, it was causing a SecurityException when
switcing users via adb command and breaking CtsMultiUserHostTestCases
tests. This CL moves all the logic from UserManager to
UserManagerService, and calls telecomManager.isInCall() with
Binder.clearCallingIdentity.
Bug: 257538981
Bug: 261505371
Fixes: 260184263
Test: atest CtsMultiUserHostTestCases
Merged-In: Idfca1fcb89688d08878b908ceed9c64f1e7091d3
Change-Id: Idfca1fcb89688d08878b908ceed9c64f1e7091d3
(cherry picked from commit 2f17ef912ee8cc321d54b08acb119d1ad641b756)
(cherry picked from commit e2062736eced6afdaa40b557f8c32461ae896020)
Merged-In: Idfca1fcb89688d08878b908ceed9c64f1e7091d3
|
|
tm-d4-release.
Change-Id: If9faf6dfb81ac1964ebcdb74e9b907a9892151c1
|
|
Bug: 258672042
Test: atest CtsPermission4TestCases
Change-Id: I1d484ed7c72d4ae73f4cbec47522a18ae9088f6e
(cherry picked from commit 297388e374f0a1e5b7f52961a81246c2fecb81e6)
Merged-In: I1d484ed7c72d4ae73f4cbec47522a18ae9088f6e
|
|
system apps
This is a roll forward of two reverted changes combined into one:
commit b6d04416628ab29df57efcd738332912d9260cea
commit e5e51116fb767162966a8e0d23fafb4f0ff46e86
It additionally fixes an issue where in multi-user profiles (such as a guest user), rules would be incorrectly identified as not created by the system and would therefore fail to be created in settings.
Bug: 257477671
Bug: 245236706
Bug: 242537431
Test: NotificationManagerServiceTest; ZenModeHelperTest; manually verified that it's possible to create zen schedules from guest mode
Change-Id: I0c4c705cfe5fc875151958957daaf8657fbc21a7
(cherry picked from commit 7261cdd30bf18965d421fc28c68c61e380bc952d)
Merged-In: I0c4c705cfe5fc875151958957daaf8657fbc21a7
|
|
This reverts commit b6d04416628ab29df57efcd738332912d9260cea.
Reason for revert: broke DND schedules in multi-user mode b/257477671
Change-Id: Idf32ab7ebd132ee460504976ba31252fd4da47fa
(cherry picked from commit 9223d270f5474dc4387ad3e6afd4cb660927bfc8)
Merged-In: Idf32ab7ebd132ee460504976ba31252fd4da47fa
|
|
sparse-9486377-L84200000958167518 into tm-d4-release.
COASTGUARD_SKIP: I021fd5ca302677995575def1859437ff5dc3f0b0
COASTGUARD_SKIP: I1d484ed7c72d4ae73f4cbec47522a18ae9088f6e
COASTGUARD_SKIP: I0c4c705cfe5fc875151958957daaf8657fbc21a7
COASTGUARD_SKIP: Idf32ab7ebd132ee460504976ba31252fd4da47fa
Change-Id: Ib5bbac72ea50678f571e0cdaf29daa43cef28d2a
|
|
sparse-9486377-L84200000958167518.
SPARSE_CHANGE: Idf32ab7ebd132ee460504976ba31252fd4da47fa
SPARSE_CHANGE: I0c4c705cfe5fc875151958957daaf8657fbc21a7
SPARSE_CHANGE: I1d484ed7c72d4ae73f4cbec47522a18ae9088f6e
Change-Id: I021fd5ca302677995575def1859437ff5dc3f0b0
|
|
Bug: 258672042
Test: atest CtsPermission4TestCases
Change-Id: I1d484ed7c72d4ae73f4cbec47522a18ae9088f6e
(cherry picked from commit 297388e374f0a1e5b7f52961a81246c2fecb81e6)
Merged-In: I1d484ed7c72d4ae73f4cbec47522a18ae9088f6e
|
|
system apps
This is a roll forward of two reverted changes combined into one:
commit b6d04416628ab29df57efcd738332912d9260cea
commit e5e51116fb767162966a8e0d23fafb4f0ff46e86
It additionally fixes an issue where in multi-user profiles (such as a guest user), rules would be incorrectly identified as not created by the system and would therefore fail to be created in settings.
Bug: 257477671
Bug: 245236706
Bug: 242537431
Test: NotificationManagerServiceTest; ZenModeHelperTest; manually verified that it's possible to create zen schedules from guest mode
Change-Id: I0c4c705cfe5fc875151958957daaf8657fbc21a7
(cherry picked from commit 7261cdd30bf18965d421fc28c68c61e380bc952d)
Merged-In: I0c4c705cfe5fc875151958957daaf8657fbc21a7
|
|
This reverts commit b6d04416628ab29df57efcd738332912d9260cea.
Reason for revert: broke DND schedules in multi-user mode b/257477671
Change-Id: Idf32ab7ebd132ee460504976ba31252fd4da47fa
(cherry picked from commit 9223d270f5474dc4387ad3e6afd4cb660927bfc8)
Merged-In: Idf32ab7ebd132ee460504976ba31252fd4da47fa
|
|
Change-Id: I64313a21ae4ffe09bff8cff418c3ad0686b617a6
|
|
- remove brightness mode code from PowerManager
Bug: 161868123
Test: Make sure that switching auto-brightness mode still works correctly.
Test: atest PowerGroupTest
Test: atest PowerManagerServiceTest
Change-Id: Ie8bed709c14a715d2f834eb4404463727f4dab13
Merged-In: Ie8bed709c14a715d2f834eb4404463727f4dab13
(cherry picked from commit 6b7bee1c4b23857831783dc3691b45fe235b21f8)
Merged-In: Ie8bed709c14a715d2f834eb4404463727f4dab13
|
|
sparse-9473884-L18000000958116576 into tm-d4-release.
COASTGUARD_SKIP: Ie8bed709c14a715d2f834eb4404463727f4dab13
COASTGUARD_SKIP: I09bc1904b39626407df7e40344a7b7d87db0a702
Change-Id: Ib9298092332b7a9e186a662cec2d764bcf92d160
|
|
SPARSE_CHANGE: Ie8bed709c14a715d2f834eb4404463727f4dab13
Change-Id: I09bc1904b39626407df7e40344a7b7d87db0a702
|
|
- remove brightness mode code from PowerManager
Bug: 161868123
Test: Make sure that switching auto-brightness mode still works correctly.
Test: atest PowerGroupTest
Test: atest PowerManagerServiceTest
Change-Id: Ie8bed709c14a715d2f834eb4404463727f4dab13
Merged-In: Ie8bed709c14a715d2f834eb4404463727f4dab13
(cherry picked from commit 6b7bee1c4b23857831783dc3691b45fe235b21f8)
Merged-In: Ie8bed709c14a715d2f834eb4404463727f4dab13
|