| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: I342b8ac8062b4a9c6bf73261c605596d235605e1
|
| |
|
|
|
|
|
|
|
|
| |
These shouldn't be automatically removed since apps are currently
granted these by default for compatibility. Users have to explicitly
remove them rather than granting them. Apps would need to be aware of
them and request them from the user to treat them like the standard
permissions.
Change-Id: I060947a3b78d3dea7f9632346ba91eb41f44e5d6
|
| |
|
|
| |
Change-Id: I229f2ec4c480f7dcd75bf37f999a96e6f02961b6
|
| |
|
|
|
|
| |
ported from 10: fc8c816e07ce39583774db8fe668e0505b6aa504
Change-Id: Ib6ed8e94c9a5d4800b686713b488fcfa20684629
|
| |
|
|
|
|
| |
ported from 10: a1204e6126189810018ff5540858536a1c58ac37
Change-Id: I75c5e9d9a97c8dbb792b6e9034fb7f74018ab970
|
| |
|
|
|
|
| |
ported from 10: a07271ed7e45239369f2ca33496d939d2e9cbd08
Change-Id: I227d932bdbd6410d0342badd8cb965bfb81f35b8
|
| |
|
|
|
|
| |
ported from 10: 6c4f112dde47f21ce5a583f5bd8b217db6de5c02
Change-Id: Iec6f4a5ad9570a854cb7afa717f93aa9c70d27b4
|
| |
|
|
|
|
|
|
| |
getInitializedValue
Test: on branch aosp-android11-gsi: $ atest AutoRevokeTest
Fixes: 171371510
Change-Id: Ie0e2d036f1877c157f3d0c21ed3361c5feffa4ce
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
staging/lineage-18.1_merge-android-11.0.0_r32
Android 11.0.0 Release 32 (RQ2A.210305.006)
* tag 'android-11.0.0_r32':
Import translations. DO NOT MERGE ANYWHERE
Import translations. DO NOT MERGE ANYWHERE
DO NOT MERGE: Don't run auto-revoke on Automotive
Import translations. DO NOT MERGE ANYWHERE
Import translations. DO NOT MERGE ANYWHERE
Import translations. DO NOT MERGE ANYWHERE
DO NOT MERGE: Hide overlays over uninstall confirm dialog
DO NOT MERGE: Hide overlays over uninstall confirm dialog
Import translations. DO NOT MERGE ANYWHERE
Import translations. DO NOT MERGE ANYWHERE
Import translations. DO NOT MERGE ANYWHERE
Remove dismiss button from permission dialog
RESTRICT AUTOMERGE Don't allow tapjacking permissioncontroller
RESTRICT AUTOMERGE Don't allow tapjacking permissioncontroller
RESTRICT AUTOMERGE Don't allow tapjacking permissioncontroller
Remove showing the "allow" button for "allow one time" on automotive
Change-Id: Ie9d9dcedab4e648df536e73f08f1b13b5a2a8c71
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 155214596
Bug: 174873777
Test: See job isn't scheduled on boot via --
adb shell dumpsys jobscheduler | grep AutoRevokeService
Change-Id: I2340e97b253724faadf75e7f9b64c78443160eb3
|
| | |
| |
| |
| |
| |
| | |
Bug: 171067302
Test: Manually
Change-Id: I6173090dcf8e5a1c1297f5459bf369ac402556e3
|
| | |\
| | |
| | |
| | | |
into rvc-qpr-dev
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There appears to be cases where permission dialogs show
"Allow one time", "Allow while in foreground", and "deny".
The current code, since we don't want to show one time
permissions on automotive, would change that to
"Allow", "Allow while in foreground", and "deny",
where "Allow" and "Allow while in foreground" do the
same thing. It should really just have "Allow while in
foreground" and "deny".
Test: m cts, cts-tradefed,
run cts -m CtsPermission3TestCases
run cts -m CtsPermissionTestCases
run cts -m CtsOsTestCases -t android.os.cts.AutoRevokeTest#testUnusedApp_getsPermissionRevoked
Bug: 169797619
Change-Id: I6d24c0708576239fd6f58c9e38ae60c6e3472631
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This partially reverts commit fe4bf10f7e0b73215fbbcde99a01b09368ebfa46.
This restores the implementation of onGetPermissionUsages from the
aforementioned commit and updates it to work with the permission usage
forward-port in commit a48389aaa41370f5b799964d4a435a2533aea4c3.
Implementing this API is necessary to fix the permissions dashboard
entry point being empty in Settings.
Change-Id: If5e0cba6c87c1f1c7ef2550aeac405ccba7b3227
|
| |/ /
| |
| |
| |
| |
| |
| | |
This usage dashboard is in a usable state and helps track down rogue
apps, so remove the warning.
Change-Id: Ie51e56655cd5d69687dbdc7a2a5216bd6cf3559d
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| | |
Test: Manual
Bug: 168553482
Change-Id: I395206ad173d91e0db39627346b80d2f5c2e1aeb
Merged-In: I395206ad173d91e0db39627346b80d2f5c2e1aeb
|
| |\ \
| |/
|/|
| | |
present"" into rvc-qpr-dev
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit fc0c23abf62c2e0878f420449e84eae8a0a74116.
Reason for revert: Not in QPR
Bug: 168209929
Change-Id: I925ec9a062c425e26bbb180ed5325a39a51c6485
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Bug: 162547999
Test: Go to Camera while mic is not in use, verify camera shows subtitle
and icon
Change-Id: I3af931e7c8f1116ee6ffe0fbd435277d1982c572
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The flag will be pushed to all users. Until then, this change allows
Droidfood Daily to use the feature.
Test: Manual
Bug: 168209929
Change-Id: I6358c1f1d624e8f7c7f31677ab5499bcbe3090df
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Bug: 166837151
Fixes: 167431234
Test: Open the privacy chip twice quickly. It should load both times
Change-Id: Id828a89c805b527c2b1457d5469fa6626c07065d
Merged-In: I2837d48b3e0c985d3023bf75f3876e0e97a0d9ae
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure the ReviewOngoingUsageFragment waits for non-stale phone call
ops, add logs to ops, logging state, remove unneeded accept method
Bug: 166837151
Test: Make a phone call, click the privacy chip, then leave the call,
wait 10 seconds, and go to another app that uses camera/mic, click the
chip- phone call should not be there.
Change-Id: I3a5362a8a5061c8373c2cec6fd73f9d9d11d4c18
Merged-In: I2837d48b3e0c985d3023bf75f3876e0e97a0d9ae
|
| |
|
|
|
|
| |
Bug: 162547999
Test: Created system usage and then started dialog
Change-Id: I96e9a3ed34a4f48f4c1f74b1f5feb32dba055f75
|
| |
|
|
|
|
| |
Bug: 162547999
Test: Looked at UI
Change-Id: I8660671a6f2d68bc5c86d45474d4c883d7daa462
|
| |
|
|
|
|
| |
Bug: 162547999
Test: Starte phone call and launched ReviewOngoingUsageFragment
Change-Id: I57a9c269303769769f9debbe227b153d78abc61e
|
| |
|
|
|
|
| |
Bug: 162547999
Test: (with follow up change)
Change-Id: Ia56a3034b3eab336a2f087adde31dbb70dd0473d
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Test: atest ReviewOngoingUsageFragmentTest
Bug: 162547999
Change-Id: Ic564a552a88d355b6003f811e9f97da47a935c4e
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Test: Build and check flags of Google app
Bug: 162547999
Change-Id: I2fac256f4939d53be01df1d150e06c524a3a8177
|
| |\ \ \
| |_|/
|/| |
| | | |
into rvc-qpr-dev
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ensure that the Auto revoke fragment doesn't crash if it tries to show
the load icon, which happens if the data does not load within 200ms
Fixes: 163535875
Test: Intentionally delay the loading of the auto revoked packages,
verify fragment does not crash
Change-Id: Ic391d81527e91528e11a9e052020e6ae746ea6c9
|
| |/
|
|
|
|
| |
Test: Looked at dialog
Bug: 162547999
Change-Id: Iab1904620475be46a3acfc1d51ac830db3a1354e
|
| |\
| |
| |
| | |
rvc-qpr-dev
|
| | |
| |
| |
| |
| |
| |
| | |
Test: Recorded audio in background and could not open review-ongoing
usage dialog1
Bug: 162547999
Change-Id: Ica9eb877d2122d785ed16e7581325082efbdc1f7
|
| |\ \
| |/
|/|
| | |
inprocess" into rvc-qpr-dev
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use shared preferences instead of settings.secure for the "show
assistant microphone usage" switch. Also moves the assistant user
sensitive tests to be in-process.
Fixes: 162901322
Test: atest AssistantRoleUserSensitiveTest, select the
GooglePermissionController tests
Change-Id: I9ce5c5a1938cf114254e660160d38bdbc541b5e7
|
| |/
|
|
|
|
|
|
|
|
|
| |
- Change string of title
- Special string for mic + camera as this is the only string showing up
in public builds
- Subtitle for usage items
Test: Looked at screen in differnet configurations
Bug: 162547999
Change-Id: I08a0651cd72976548c83cb03f79204cfbedc1f71
|
| |
|
|
|
|
|
|
|
|
|
| |
Update the user sensitive flags of the current assistant whenever it is
added or removed from the role, only when the device config flag is set.
Adds camera/mic icon flags, and only shows location on
reviewOngoingUsageFragment when permission hub is enabled.
Fixes: 159998363
Test: manual
Change-Id: Ice52dc044c34b31e6930f461008fbeafa70b1e3b
|
| |
|
|
|
|
|
|
| |
Test: Looked at usage of emulators com.android.camera2 which stops
accessing camera onPause.
Bug: 161007415
Change-Id: I85b3cebf07bac6412fa1710e6a7f4a8a179406cd
|
| |
|
|
|
|
|
|
|
| |
Update the user sensitive flags of the current assistant whenever it is
added or removed from the role.
Fixes: 159998363
Test: atest AssistantRoleUserSensitiveTest
Change-Id: I38cbf8d050026bbb3dedb716fe78b759b086e95f
|
| |
|
|
|
|
|
|
|
|
| |
- Change and emphasize usage warning
- remove system apps from UI
- Show accounts in debug UI
Test: looked at UI
Bug: 161007415
Change-Id: I5b1ba82522ed1c8bc412de0783f6a24e26da2a66
|
| |
|
|
|
|
| |
Bug: 161007415
Test: Did not see feature without flag, saw fature with flag enabled
Change-Id: Ia369c466388a8b6a2daf888e8426721ef75db898
|
| |
|
|
|
|
| |
Bug: 161007415
Test: Looked at the PermissionUsage screen
Change-Id: Ib5da3b0fc62b28a128107b171534d2a94592d2f9
|
| |
|
|
|
|
|
|
|
| |
Resurrect the fragment, its data model, and allow the
PermissionController to handle its intent
Test: Manual
Bug: 159998363
Change-Id: I9a95528e333982e4f80a8c8805bedb58d6f77bf6
|
| |
|
|
|
|
|
|
|
| |
The condition which creates the NPE is invalid but we should prevent the
process from crashing.
Test: Build
Fixes: 160907517
Change-Id: Idc7fdb63d6ed1e7f9bd4c14b3decc72189323273
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we send ACTION_MANAGE_APP_PERMISSION and don't get a matching form
factor, we're going to reset the intent action and then just try to
launch the same thing again. This is not going to go well and can break
a device until the framework gives up and kills PermissionController.
The solution is to just add a TV case to the same place as the Auto one
that already exists here.
Test: atest android.permission3.cts
Test: atest android.permission2.cts
Test: atest android.permission.cts
Test: atest android.os.cts.AutoRevokeTest
Bug: 155356284
Change-Id: I1830737cdfd933060f800c44b9e599ae7c65d6a1
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously the dialog was not showing up at all and the parent was
dismissing itself. We can't use getChildFragmentManager() for this and
need to set the parent view as a target fragment instead.
We exit the permission setting sub-screen once we get the state change
callback, either from feedback loop on the model or indirectly from the
dialog changing something.
If there is no change, we stay on the same screen.
Test: atest android.permission3.cts
Test: atest android.permission2.cts
Test: atest android.permission.cts
Test: atest android.os.cts.AutoRevokeTest
Bug: 155356284
Change-Id: I3af8f2a6eb4cd85447684c5930249c93a5c84d1e
|