app_Settings

Go to file

Edgar Wang 90e095dbe3 Fix LaunchAnyWhere in AppRestrictionsFragment

If the intent's package equals to the app's package, this intent
will be allowed to startActivityForResult.
But this check is unsafe, because if the component of this intent
is set, the package field will just be ignored. So if we set the
component to any activity we like and set package to the app's
package, it will pass the assertSafeToStartCustomActivity check
and now we can launch anywhere.

Bug: 223578534
Test: robotest and manual verify
Change-Id: I40496105bae313fe5cff2a36dfe329c1e2b5bbe4

2022-04-06 17:51:07 +08:00

libs

Update new API for checking the embedding status

2022-01-12 15:00:07 +08:00

protos

[Settings] Code refactor - NetworkModePreference

2022-03-21 00:18:55 +00:00

res

Merge "Warnings at top of per-app settings page" into tm-dev

2022-04-01 17:40:09 +00:00

src/com/android/settings

Fix LaunchAnyWhere in AppRestrictionsFragment