| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Manual formatting is to complicated to do.
Fixes: 28852429
Change-Id: Ibab723b82a2b14ad94a3038dffccc96f86ba8ee4
|
|\
| |
| |
| | |
nyc-dev
|
| |
| |
| |
| |
| | |
Bug: 26677796
Change-Id: I563541f0a42564b854af0f8037c1d4741c79a2ac
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change ensures the app name is properly bolded in
the premissions request UI even if it is a substring
of "Allow" :)
bug:28719607
Change-Id: I5a313f67c19a2d882732b1c97f0dbee5782b22f5
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 294b6406798c59e9db5ffa99d042f9b8c6ca6f90.
Change-Id: Ifb48eb1fbdb0499743f4ca88adbd5ed77cfa4cf8
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If an app requests a permission in a group we were auto granting it all
permissions from the group declared as used by the app. The intended
behavior is that we grant only the requested permission and requesting
a permission from a group where a permission is already granted results
in an auto-grant. The intended behavior was to prevent coding around
permission groups which a volatile by design. Now if apps target SDK
above M we provide the intended behavior, otherwise for apps targeting
M we provide an unchenged behavior.
bug:28347872
Change-Id: I493714b2c2581340b01b12ce6fedf80f9d3deec5
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The only permissions a user can control for a legacy app in
runtime style without crashing the app are the ones defined
by the platform because we have app ops only for these and
also we contorl the access to data guarded by them.
bug:27102458
Change-Id: I63d02e169dc82e9f3638b8e8f99ed8d95ae7d325
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The PackageInstaller app manages side-loading apps as well
as permission management. It should be updatable, hence
should rely on system APIs to talk to the platform. This
is the first step of defining an API boundary.
Change-Id: I37aea1e5cc3195b8b636af6790af45fe5a9765cd
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reworked all the permission UIs on TV to mesh with the rest of the
settings rendered as leanback-styled side panels with title bars.
The permissions consist of the following components:
* Each individual app permission listing
** Listing of all the permissions together with the apps using
those permissions
Bug: 27344882
Bug: 22481180
Change-Id: I4ab05efd9a4ea6fab7971b89f13d65591a2be8ee
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Added a menu item to link for the help center article for app
permissions.
Bug: b/22096093
Change-Id: Ic810bbcc64b20ab6ee21140f0bb3ea055c10813a
|
|/
|
|
|
|
| |
bug:21891813
Change-Id: Id9a694d14ecd80c8c04dc28b34cdda3e9119bfb3
|
|\ |
|
| |
| |
| |
| |
| |
| | |
bug:23899558
Change-Id: I37bf080d54fc4fff5dfcc9f8240b95c82fed56d2
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In a permission review mode we show UI for the user to review
new permissions for apps that do not support the new runtime
permission model. The review is shown on an app launch. It is
possible for the user to modify permissions in the settings
UI before launching an app.
This change ensures that the default value in the review UI
reflects the user choice in settings. Specifically, the review
UI shows the permission toggle in a granted state if the user
expressed no opinion or granted the pemrission in settings
(initially permissions are shown as revoked in settings as a
review is pending - granting a permission from settings doesn't
void the pending review). However, if the user grants and then
revokes a permission in settings, (expresses an opinion the
pemrission should be revoked) the default state of the
permission
toggle is off.
bug:26741436
Change-Id: I021175df00e334e73aa01363d2c5645e2fe16b90
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 437a6bfedb33daf66592bbed8595025f3e707850.
Change-Id: I5a46f94aadb0ab6dcbe85761f3b1390749b8b1cf
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In a permission review mode we show UI for the user to review
new permissions for apps that do not support the new runtime
permission model. The review is shown on an app launch. It is
possible for the user to modify permissions in the settings
UI before launching an app.
This change ensures that the default value in the review UI
reflects the user choice in settings. Specifically, the review
UI shows the permission toggle in a granted state if the user
expressed no opinion or granted the pemrission in settings
(initially permissions are shown as revoked in settings as a
review is pending - granting a permission from settings doesn't
void the pending review). However, if the user grants and then
revokes a permission in settings, (expresses an opinion the
pemrission should be revoked) the default state of the permission
toggle is off.
bug:26741436
Change-Id: Iae6ae497dfba46ba1399fbf66fb60e70c37f0420
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only platform defined runtime permissions have corresponding
app ops, hence there is no way to disable functionality guarded
by app defined permissions. Therefore, app defined permissions
should not show in the review UI.
bug:27102458
Change-Id: Iedc7c4de9216007176b87cfecaeed69dbadc2068
|
|/ /
| |
| |
| | |
Change-Id: I285e326994268fc5b561e4a445ac2af326a64397
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
bug:24079113
Change-Id: Ide1aa1667370f6b8d00ff269ef28992589656e9a
|
|/
|
|
|
|
|
|
|
| |
And fixed a bug where the admin disabled summary is shown even
if the admin has not set a permission policy.
Bug: 25603665
Bug: 27263775
Change-Id: I8cbbc4c326669a656ad5aef53896b388d556a74f
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are some permissions that were removed from the platform
and guard nothing but legacy apps may be checking them before
calling APIs. Hence, these apps should get the permissions as
expected despite them being a no-op. To address this the platform
declares removed permissions as normal permissions that are hidden
such that legacy apps can always get them. These permissions are
not shown in the UI. Play needs a way to filter out these
permissions like the platform as they have permissions UI too.
bug:23361760
Change-Id: Ieecf69f70551d987f5fac1f128b7f7a0c242c378
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
bug:23314383
Change-Id: I4b41b9941f147eefc5f3fc2c520aba7afabd26a0
|
| |
| |
| |
| |
| |
| | |
bug:26973205
Change-Id: Ibae1b971ceb1ea0d831435b9d5166482199e9184
|
|/
|
|
|
|
|
|
|
| |
We get an NPE if an app that delcates no permissions as used
requests runtime permissions.
bug:21011604
Change-Id: Id0cac6dcbd78ef849a1eafa522b8a06e61b21a1b
|
|
|
|
| |
Change-Id: I0fbe8ac8670b9fa4eb1fa35693856b47fdc974a4
|
|
|
|
| |
Change-Id: I427fd1e1c99153484944ee9955ae79ee9e2c23ef
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, if admin has enforced setPermissionGrantState to denied or granted,
we disable the option and add a summary that the option is disabled by
admin. With this change, a padlock will also be added in this case.
Change-Id: I58080c914fabab045282eb3cc491901676fffaed
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
am: eccff95e32
* commit 'eccff95e32dbf09f0fe6df033daf09e8d3c4212e':
Revert "Make request permissions dialog layout robost"
|
|\ \ \
| |/ /
|/| |
| | | |
Change-Id: I325541269f5a0f7c1fde7a57042543e769bed218
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The old implementation was relying on a fixed window size
where the content is positioned by a custom layout manager.
It is possible however that subsequent permissions requests
do not fit in the window as its size is computed based on
the content of the first permissions request. There were
also cases where the content is chopped after a rotation
as the dialog size width was not re-evaluated while it should
be. Further, animation from one permission request state
to another was not properly done resulting in content
being chopped off in some cases.
The current approach is to have a dialog width for the
content activity but the height is as tall as the screen
allowing us to fit arbitrary large permission request
content. Also we are resetting the fixed width on a
configuration change so the dialog is robust to adjust
size as needed.
bug:24679384
bug:25755378
Change-Id: I4d23f81d8e59ce23bf9a27155ebb5ec6e2e6752c
(cherry picked from commit c6dc4bb52b07886346b02b326c5c32a8299ed73e)
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
am: 41d260fe98
* commit '41d260fe9854819ca04a3b5908e6ab889bf3ffc4':
Revert "Make request permissions dialog layout robost"
|
| | |
| | |
| | |
| | | |
This reverts commit ecaeae17f52d6562d23dfec91e44bc3c0b4a6d13.
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
am: b0a98d2e47
* commit 'b0a98d2e4778e39b62b3731cbc27cf6fdb541e24':
Make request permissions dialog layout robost
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
am: 816baf3566
* commit '816baf35660c3c46ffcb9be7ec72d343fb0e1400':
Make request permissions dialog layout robost
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the min width of a dialog changes in portrait vs landscape
it was possible that a part of the request permissions dialog
is chopped off. The custom content layout manager was using a
fixed width and changing orientation may lead to a dialog
width lesser than the fixed width of the layout manager.
Another problem was that if the above occurs and the window
width changes then the window may not be tall enough to fit
the content. To address this we have to do a gross move and
re-add the window to the window manager, so it can be resized.
Another issue was that if the "Don't ask again" checkbox is
shown not for the first but say the second permission request
(in the case of multi-permission request in one API call) the
content was chopped off as the height measurement for how much
the content needs to be was restricted by the parent measure
spec. Now we measure with no restrictions to accommodate the
whole content.
The way reqeust permissions dialog is implemented is problematic
as it is a dialog styled activity which means we may need to
resize its window. It is better to implement it as a fullscreen
activity that has a custom content layout mangar that makes
the content look like a dialog. Since this is risky at this
point we do targeted fixes to address the above issues.
bug:24679384
Change-Id: If51a360ba17dfb71b66dcf841ea47c17606eba27
|
| | |
| | |
| | |
| | |
| | |
| | | |
bug:26032074
Change-Id: If6566411e08b3a27eecc2ca559c2b902dc8c1e65
|
| | |
| | |
| | |
| | | |
Change-Id: I17ae37d84c0d78bcfcaa848efb17f46c7f7c915a
|
| | |
| | |
| | |
| | | |
Change-Id: Ifc88b2fa259d2d22bea6b5500cded2714ad4da85
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
am: 2a6f5d0fc6
* commit '2a6f5d0fc6b3fc65120ba7ed13f81af2d59eb11f':
Fix build
|
| | |
| | |
| | |
| | | |
Change-Id: I2a3e235bb13f1920c14f6776ee3a1ef7285ea548
|