Age | Commit message (Collapse) | Author |
|
19500970, 19816377, 19815899, 19868476, 19990545] into tm-d1-release.
Change-Id: I4dfa773e37f3ba5cfa03724287c13f70daf2a301
|
|
After PUK unlock, multiple calls to
KeyguardSecurityContainerController#dismiss() were being called from
the KeyguardSimPukViewController, which begins the transition to the
next security screen, if any. At the same time, other parts of the
system, also listening to SIM events, recognize the PUK unlock and
call KeyguardSecurityContainer#showSecurityScreen, which updates which
security method comes next. After boot, this should be one of PIN,
Password, Pattern, assuming they have a security method. If one of the
first dismiss() calls comes AFTER the security method changes, this is
incorrectly recognized by the code as a successful
PIN/pattern/password unlock. This causes the keyguard to be marked as
done, causing screen flickers and incorrect system state.
The solution: every call to dismiss() should include a new parameter
for the security method used. If there is a difference between this
parameter and the current value in KeyguardSecurityContainerCallback,
ignore the request, as the system state has changed.
Fixes: 238804980
Bug: 218500036
Test: atest KeyguardSecurityContainerTest
AdminSecondaryLockScreenControllerTest KeyguardHostViewControllerTest
KeyguardSecurityContainerControllerTest
Change-Id: I7c8714a177bc85fbce92f6e8fe911f74ca2ac243
Merged-In: I7c8714a177bc85fbce92f6e8fe911f74ca2ac243
(cherry picked from commit 37aeb26b0ae28a48c1ed40f008d5808d8a84be23)
(cherry picked from commit 3d89cc5df6729cab8d98c967d73e03e23048d52b)
Merged-In: I7c8714a177bc85fbce92f6e8fe911f74ca2ac243
|
|
Previously were unable to add new zen rules because rules added via the settings pages were getting registered under package "com.android.settings", which then were not considered "system rules". These rules should have package android, so when we can trust the caller (via checking that the caller is system) we should be taking the package name from the owner of the rule.
Bug: 245236706
Bug: 242537431
Test: NMSTest; manual
Change-Id: Id69b671592396ac3304862dadbe73de328a8e27a
Merged-In: Id69b671592396ac3304862dadbe73de328a8e27a
(cherry picked from commit b8c4819ec24a0ab8af72c10055ef02d5fa10a194)
Merged-In: Id69b671592396ac3304862dadbe73de328a8e27a
|
|
Bug: 239495492
Bug: 243924784
Test: atest ScopedStorageHostTest#testCheckInstallerAppAccessToObbDirs
Change-Id: Id96c854c0b31e94d367dccd125ad5c14523cdc79
Merged-In: Id96c854c0b31e94d367dccd125ad5c14523cdc79
(cherry picked from commit 33e2c5008b925c6e4349788be1aba19a6d19aa99)
(cherry picked from commit 3a3cc4d91994ffa1da76ca8ff36c0eff929d545a)
Merged-In: Id96c854c0b31e94d367dccd125ad5c14523cdc79
|
|
This change both prevents any rules from being unable to be written to disk and also avoids risk of running out of memory while handling all the zen rules.
Bug: 242703460
Bug: 242703505
Bug: 242703780
Bug: 242704043
Bug: 243794204
Test: cts AutomaticZenRuleTest; atest android.app.AutomaticZenRuleTest; manually confirmed each exploit example either saves the rule successfully with a truncated string (in the case of name & conditionId) or may fail to save the rule at all (if the owner/configactivity is invalid). Additionally ran the memory-exhausting PoC without device crashes.
Change-Id: I110172a43f28528dd274b3b346eb29c3796ff2c6
Merged-In: I110172a43f28528dd274b3b346eb29c3796ff2c6
(cherry picked from commit de172ba0d434c940be9e2aad8685719731ab7da2)
(cherry picked from commit d4b5212eb6d6f9ecb967d8403d1d8dd63cf69afb)
Merged-In: I110172a43f28528dd274b3b346eb29c3796ff2c6
|
|
Test: Manually install app apks targeting Q and verifying that AR permission is not auto-granted
Test: atest ActivityRecognitionPermissionTest
Bug: 210065877
Change-Id: I0d4a8d01db7b60f7c82642b875cdee3f600e7548
(cherry picked from commit 41dc761e081d8c6de48ddc3b960e12e4fd24c8b7)
Merged-In: I0d4a8d01db7b60f7c82642b875cdee3f600e7548
|
|
instead of checking that of the configuration activity, which is potentially spoofable. The package name is verified to be the same app as the caller by NMS.
This change removes isSystemRule (called only once) in favor of checking the provided package name directly.
Bug: 242537431
Test: ZenModeHelperTest, manual by verifying via provided exploit apk
Change-Id: Ic7f350618c26a613df455a4128c9195f4b424a4d
Merged-In: Ic7f350618c26a613df455a4128c9195f4b424a4d
(cherry picked from commit a826f9bd15d149305814a835fb5d1a3921a085f5)
Merged-In: Ic7f350618c26a613df455a4128c9195f4b424a4d
|
|
This is a partial backport of ag/19532036. It fixes a bug where a
LazyValue might have been pointing to a parcel which was already
recycled.
Bug: 240138318
Test: atest android.os.cts.ParcelTest android.os.cts.BundleTest
android.os.BundleTest android.os.ParcelTest
android.os.BundleRecylingTest
Test: Running PoC app from linked bug
Change-Id: I3acf7127fdf373ee8b38a55702ae315be499601c
Merged-In: I8a878a6d0055b04b2611909b4b17977ba5677a4f
(cherry picked from commit d2f9cc6342141cdb39f08a229d548d7b29cadd86)
Merged-In: I3acf7127fdf373ee8b38a55702ae315be499601c
|
|
Bug: 237540408
Test: BuzzBeepBlinkTest#testA11yCrossUserEventNotSent
Change-Id: I62a875e26e214847ec72ce3c41b4f2fa8e597e07
(cherry picked from commit a367c0a16a9070ed6bee3028ac5bbc967773ee8f)
Merged-In: I62a875e26e214847ec72ce3c41b4f2fa8e597e07
|
|
The new Intent was delivered to a non-exported activity while
#navigateUpTo was called from an Activity of a different uid.
Bug: 238605611
Test: atest StartActivityTests
Change-Id: I854dd825bfd9a2c08851980d480d1f3a177af6cf
Merged-In: I854dd825bfd9a2c08851980d480d1f3a177af6cf
(cherry picked from commit 4c355690494f17c8ebdecbc8b1a1eaef21ffc0f3)
Merged-In: I854dd825bfd9a2c08851980d480d1f3a177af6cf
|
|
It was shown that given a large phoneAccountHandles that are
over 1 mb, a TransactionTooLarge exception can be silently thrown
causing an empty list to be returned.
In order to prevent this behavior, all Lists that return a
PhoneAccountHandle or PhoneAccount have been switched to
ParceledListSlice.
bug: 236263294
Test: manual #1 - bug exists without fix,
manual #2 - bug is fixed with patch,
4 new CTS tests in
android.telecom.cts.PhoneAccountRegistrarTest
Change-Id: I025245b2a6f8cfaca86f268851a9d8f0817e07dd
Merged-In: I025245b2a6f8cfaca86f268851a9d8f0817e07dd
(cherry picked from commit 76c4d2d0b11397875b8c094b54016a178750c73d)
Merged-In: I025245b2a6f8cfaca86f268851a9d8f0817e07dd
|
|
Change-Id: I28060188d28fec50f926e95e6144d925f6cf2a25
|
|
This change early-exits from the sendEventToVpnManagerApp()
method if the profile was not a VPN app.
Otherwise the sendEventToVpnManagerApp() will call
getRedactedNetworkCapabilities() which will call
AppOpsManager#checkPackage() eventually.
And AppOpsManager#checkPackage() will check if the given package
is the same as the given uid. In this case, VPN sends
"[Legacy VPN]" as the package and sends 1000 as the uid, but
there is no package named "[Legacy VPN], so the SecurityException
is thrown.
Bug: 236315805
Test: atest FrameworksNetTests:VpnTest
Change-Id: I486398111106b1a9551fb29f92ba7b4fe85f68c1
Merged-In: I486398111106b1a9551fb29f92ba7b4fe85f68c1
Merged-In: I228f62a5e09017dbf985a614f2e42434238a220c
(cherry picked from commit a7ec0cbe45dd75301b19290174ecf2da6421cf97)
Merged-In: I486398111106b1a9551fb29f92ba7b4fe85f68c1
|
|
tm-d1-release.
Change-Id: I05bfc498ef31b9de90e378bd9269fc51e55acbe7
|
|
Only with face unlock + bypass enabled, when dragging down the shade
over keyguard, the end motion event was forcing the shade to collapse
again, due to an incorrect check on the keyguard state. Use the
KeyguardStateController.isShowing() method instead, which is a more
accurate check on keyguard state.
Fixes: 242813247
Test: All combinations of face unlock enabled/disabled, notifications
visible on lockscreen on/off, notification redacted on/off, face
bypass on/off
Change-Id: I99c6ced66f3269dbf4e6df1d078d7c793492c157
(cherry picked from commit e11a139facc0fca468cbb971aa4a5965fe9040a4)
Merged-In: I99c6ced66f3269dbf4e6df1d078d7c793492c157
|
|
Test: widgets appear correctly
Bug: 237256275
Change-Id: I864ac1ba8ac771c326dc215ae4e712ceb0b6057b
(cherry picked from commit 4f359bd7655ba6d4f647bb62b877b721f25bbeb5)
Merged-In: I864ac1ba8ac771c326dc215ae4e712ceb0b6057b
|
|
add config indicate Output Switcher's version for supporting different
feature on remote devices operation.
Test: build pass
Bug: 241448326
Change-Id: Ic09daff5ec63d1124a518ff3edc6bb059b150b80
(cherry picked from commit 56473a5946a430b6ab0be2f16a03f2386d91e4fb)
Merged-In: Ic09daff5ec63d1124a518ff3edc6bb059b150b80
|
|
Bug: 241448326
Test: verified on device, atest MediaOutputAdapterTest
Change-Id: I5d2ab2e1a6cb8341871305a729d8584ca15c4dcc
(cherry picked from commit 9673316c56288ac8c5b055f1124f9f51cdb5aba6)
(cherry picked from commit 2e1bb637d29e4e98c160cfdecfab0c41fb39ac1f)
Merged-In: I5d2ab2e1a6cb8341871305a729d8584ca15c4dcc
|
|
Change-Id: I3ec45d9c0bee4db21d04b13c408ebad430edfc81
|
|
If an Icon carries package designator, LocalImageResolver has now
ignored it. This could lead to loading of a wrong icon in cases where
the ID collided with the same ID in android package.
This is fixes that corner-case.
Bug: 241066484
Test: atest LocalImageResolverTest - the new test checks for pkg
correctness and fails on devices without this cl
manual test: bluejay device with known, reproducible resource
collision in media player notification. In reproducible case,
icon appears as a broken block.
After applying this patch, small icon in media notification loads
correctly for the collision case.
Change-Id: Ic79c0d4acb1d347a24282972e009a5a079ce6c21
(cherry picked from commit 32f176e4705694c9d0272eba22887cf6d4f7b783)
Merged-In: Ic79c0d4acb1d347a24282972e009a5a079ce6c21
|
|
Change-Id: Ib86d3a14af3ce36bcb2aa57f33b81abbd9647cd4
|
|
This means that a single package with multiple different condition providers or configuration activities will correctly have all of their zen rules associated with the same package rather than each owner/activity having their rules counted separately.
Bug: 235823407
Test: ZenModeHelperTest
Change-Id: I35daf9a24f546ae25a78a2d841be39072cdc5641
Merged-In: I35daf9a24f546ae25a78a2d841be39072cdc5641
(cherry picked from commit f4e69394eee569ac3ec5748094b9ce88a91c278c)
(cherry picked from commit aa14df0e501e7c0642bde6c89db72c017d2de0d4)
Merged-In: I35daf9a24f546ae25a78a2d841be39072cdc5641
|
|
AccountManagerService.
Bug: 169762606
Test: atest AccountManagerServiceTest
Change-Id: I80fabf3a64c55837db98ff316e7e5420129c001b
(cherry picked from commit 0adcadb0b28310bac568def4da2cbaf16843bcea)
(cherry picked from commit cf62c760d4c002f562ddd5f372abe5bccda8a6ad)
Merged-In: I80fabf3a64c55837db98ff316e7e5420129c001b
|
|
This reverts commit 705019b5fcea333b3041a0a56a0c4e61c41e1b76.
Reason for revert: adding merged in this time
Merged-In: I005b43979d1c708fd505c8b33ae0c8cb03ddbb35
Bug: 234441463
Change-Id: I5ecfdf77e56d9a50ca5cc8031ce83313b8d4ee5d
(cherry picked from commit e2ceb6acfae4daa6fb095ca4031324f9f4d0fa96)
Merged-In: I5ecfdf77e56d9a50ca5cc8031ce83313b8d4ee5d
|
|
Change-Id: Iff9618e92aa056598e22d628a8a00a16a451d373
|
|
The implementation of shared-element transitions takes the
ActivityOptions from the calling activity and sends them to
another activity. This means that any sensitive information
passed into ActivityManager via ActivityOptions can make its
way to an unrelated app. Recently a RemoteTransition object
was added which includes some sensitive information.
This CL strips the sensitive information from the activity
options before sending it to anonther app.
Bug: 237290578
Test: atest ActivityManagerTest#testActivityManager_stripTransitionFromActivityOptions
Change-Id: Ifa08fc195698f02bf70ca386178c67f6ba4a14ea
(cherry picked from commit 0d03e6f1fc66fefb5409ac93ff49fa922f81664c)
Merged-In: Ifa08fc195698f02bf70ca386178c67f6ba4a14ea
|
|
This reverts commit 0b3ad39abf059b3e6e3088ab9d3ac6c43c29a2d5.
Reason for revert: Broke NexusLauncherTests:MemoryTests
Change-Id: Ibc8e9f516054f017e9db2e5608cf6806531ab554
(cherry picked from commit d1b32da8453c931099038e9f5c48793c9dcfa722)
Merged-In: Ibc8e9f516054f017e9db2e5608cf6806531ab554
|
|
Change-Id: Ic65419febec0a5f17342ac99ffc28dff8495b5dd
|
|
In most cases, mTileList contains the same information as the Settings
value, so there's no need to retrieve it before modifying it. Keep track
of that with a dirty flag.
This way, we reduce the number of blocking calls in the main thread (as
that's the thread that processes the tiles).
Test: manual, factory reset
Test: existing QSTileHostTest
Test: performance metrics are back to baseline
Fixes: 240256263
Change-Id: Idebd37d1458c80330b60802729575219b6a7b49a
Merged-In: Idebd37d1458c80330b60802729575219b6a7b49a
(cherry picked from commit 4da071e035b647f498936bdb2b557aa08bd9df0f)
Merged-In: Idebd37d1458c80330b60802729575219b6a7b49a
|
|
QSTileHost had three problems that caused a race condition:
* Calls to add/remove tiles could come and be executed in any thread.
* Different paths to add/remove tiles used different ground truths on
what tiles were currently active.
* The list of tiles contained in mTileSpecs was not necessarily the
same as the visible tiles.
This caused the following problem:
* If two tiles (usually CustomTile) were removed roughly at the same
time, only one of them would actually be removed from the Setting, as
both of them would race to remove from the same list. This caused...
* There would be leftover tiles that cannot connect to a TileService
and therefore show empty UI.
The solution is as follows:
* Make sure that all operations that modify the tiles are performed in
the main thread.
* Make sure that all operations that modify the tiles use the same
truth for the current state.
* Make sure that mTileSpecs always reflects the setting at the end of
onTuningChanged. This means that tiles that are destroyed or removed
will never be in this list.
Test: atest com.android.systemui.qs
Test: manual, start Guest user and notice that there are no blank tiles.
Fixes: 235561921
Change-Id: I6ffbb7510e6854f18bc427d1ae1e782918c799dc
Merged-In: I6ffbb7510e6854f18bc427d1ae1e782918c799dc
(cherry picked from commit 7f2bb15f4e40c0e1d1d0b2308444f4f9f449bd3f)
(cherry picked from commit 6098b8f68bc21d84ddde92f12a1550401666aa12)
Merged-In: I6ffbb7510e6854f18bc427d1ae1e782918c799dc
|
|
Change-Id: I855d3ecf2e65f1a1db16ff75cb614b33c2794492
|
|
Do not add starting window on the activity if no task exists in
the activity.
Also add an error log for the activity without task.
Bug: 233153876
Bug: 240032099
Test: atest SplashscreenTests ActivityRecordTests
Change-Id: Iea264cd8b605443c695165c1136d56b86ffd4eb1
Merged-In: Iea264cd8b605443c695165c1136d56b86ffd4eb1
(cherry picked from commit 24697fe3fdf92cac03b553892a3e1d17ae30c8a1)
(cherry picked from commit ea100e579e067fe117b42803e9a776419490bf48)
Merged-In: Iea264cd8b605443c695165c1136d56b86ffd4eb1
|
|
Change-Id: I55332eee472e82a0e4d4be366aad37cea53f808e
|
|
Test: Manual
Bug: 241084172
Change-Id: If51313b03dc40442ad6c42603f77579e77b0c873
Merged-In: If51313b03dc40442ad6c42603f77579e77b0c873
(cherry picked from commit bfd27670aea5ffecb97f210cde819cc71dafce6e)
Merged-In: If51313b03dc40442ad6c42603f77579e77b0c873
|
|
Bug: 241311958
Change-Id: Ifacce48334b869b96f4ab59275d0a90d5db7d334
(cherry picked from commit 8bfe04b55f0f8520604987a6d8ca218274823614)
Merged-In: Ifacce48334b869b96f4ab59275d0a90d5db7d334
|
|
Change-Id: I327c246df4037e7555bc9956f36b5eb6496139d8
|
|
- Don't expand shade if touch started from KG and then
ended when KG was not longer showing. This can happen
if the security setting is set to swpe to open,
and the user transitions to the SHADE. Then, the touch can
be canceled if a window is transitioning to landscape.
- Don't propagate notification panel expansion to the bouncer
when the device is unlocking with biometric (MODE_DISMISS_BOUNCER).
Since KeyguardBouncer.EXPANSION_VISIBLE = 0 panel expansion, calls
during the unlock transition to collapse the notification panel
unintentionally end up showing the bouncer.
- If the KG isn't showing and the bouncer is in transit, reset the
bouncer expansion to HIDDEN.
Test: open fruit ninja (which is locked to landscape)
and swipe to unlock, notice that panel does not expand on unlock
Test: unlock using udfps by sliding finger from slightly below/diagonal
of the UDFPS sensor (so that the bouncer transition begins), and then
successfully authenticate with UDFPS => observe the bouncer UI doesn't
flash on the screen after successful authentication.
Test: atest StatusBarKeyguardViewManagerTest
Fixes: 240487038
Fixes: 240763673
Merged-In: I9e1fb108147ffb4c812ea2b94a50d6201eaf008a
Change-Id: I9e1fb108147ffb4c812ea2b94a50d6201eaf008a
(cherry picked from commit d63046028f304650e6b280da76a133f66b54915f)
Merged-In: I9e1fb108147ffb4c812ea2b94a50d6201eaf008a
|
|
Change-Id: I7494c987b0b31662e506def4ea11d17f884d1830
|
|
The reset() call only executes if the keyguard is visible,
and causes it to reset the visible views (it can not show/hide
the keyguard). However, if the keyguard is going away because
of a launching occluding activity, and was previously insecure,
this will cause us to decide that the views should be in SHADE
state rather than KEYGUARD state, and re-render them accordingly.
This causes the shade to flicker under the launching activity.
This reset is not needed, as the status bar state change will
change to SHADE after the launch animation occurs (or will be
forced back to KEYGUARD if the unlock animation is cancelled).
Fixes: 238294986
Test: launch controls from LS affordance with/without face unlock, with/without AOD
Change-Id: Ib0622655ef6f51e1bcc9a98a5ce8f4e7feacb2fe
(cherry picked from commit fac6505c97b2cc1f8fb02b3fba04131d240e181f)
Merged-In: Ib0622655ef6f51e1bcc9a98a5ce8f4e7feacb2fe
|
|
See b/203044476#comment27 for before/after videos.
Test: Manual
Bug: 203044476
Change-Id: Ie80187a5ca9b61b8178bbe977bf252db654d9fa4
Merged-In: Ie80187a5ca9b61b8178bbe977bf252db654d9fa4
(cherry picked from commit 07d87012c17752ff949968be7d31b6fb0998ce36)
Merged-In: Ie80187a5ca9b61b8178bbe977bf252db654d9fa4
|
|
Extended handover rule to support the scenario that
handover should be blocked when source network goes
out of service.
Test: Basic testing + Wifi calling handover test + atest DataNetworkControllerTest
Bug: 234095834
Change-Id: I68c23f970af2a554ab438f630363be4591664cbb
(cherry picked from commit d9ac485b1f804746a51da7f4f14578548fa4f5a7)
Merged-In: I68c23f970af2a554ab438f630363be4591664cbb
|
|
Change-Id: Iff83722cb76a68ed9013c5b2b850942887448af1
|
|
|
|
tm-d1-dev
|
|
tm-d1-dev
* changes:
Clear ActivityRecord#mDismissKeyguard flag after app launches.
Clear ActivityRecord#mDismissKeyguard flag after app launches.
|
|
The bug demonstrated that only the top radius was getting into a dirty state. When I saw this function was resetting the bottom roundness and never touching the top roundness, it was clear that we just needed to set the top roundness. Even though it's hard to reproduce the issue where top roundness is incorrectly huge, it's trivial to reproduce the issue where the top roundness is incorrectly small, and this fix definitively addresses that state.
Test: post auto-groupable Heads Up notifications. Notice after grouping that child rows now never have any internal corner radii.
Fixes: 227433308
Merged-In: I3cd1aa23ad8333f35ec837edd39bc12aeb1573b6
Change-Id: I3cd1aa23ad8333f35ec837edd39bc12aeb1573b6
(cherry picked from commit ef4782f55d7c00493fe6cd9e10c2a082c2a819e3)
|
|
into sc-v2-dev am: dc8ae7665a am: a824844cdf
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/19505172
Change-Id: Id7de444318f392c3d8e9735df2dd78834fc79eee
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into sc-v2-dev am: dc8ae7665a
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/19505172
Change-Id: I489c233fea52fff948c5b4d92cd61163904e974d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into sc-v2-dev
|
|
Change-Id: I17afecf1d7646bc70f6f46c872621d6250414391
|