| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
App." into cw-f-dev
|
| |
| |
| |
| |
| |
| | |
Test: Manually tested on a permission test apk.
Bug: 34157400
Change-Id: Ia2ce3ac6c567f869535ec92a896c6d0fd9ec6318
|
|/
|
|
|
|
| |
Test: Manually test with a testing apk.
Bug: 34157556
Change-Id: I78ffbfa2fbbff14fb05242d7979cd226b1725ba7
|
|
|
|
|
|
|
|
|
| |
Test: Manually tested on sawshark_sw where WRITE_CONTACTS and
READ_CONTACTS are shown separately for Android Wear App. Also
tested on sawshark where only one "Contacts" group shown on
behalf of WRITE_CONTACTS and READ_CONTACTS.
Bug: 33856934
Change-Id: I299c54e38236d039204a01d8113f427b1fc71c43
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If permission review is enabled toggling bluetoth on or off
results in a user prompt to collect consent. This applies
only to legacy apps, i.e. ones that don't support runtime
permissions as they target SDK 22.
Also added a configuration resource which controls whether
permission review mode is enabled. By default it is not and
an OEM can change this via an overlay. For now we also keep
the old mechanism to toggle review mode via a build property
which is still used and will be removed when clients have
transitioned.
bug:28715749
Change-Id: I3783fa99f3fca881a4b60ea1e7c0f68098302ae4
|
|\
| |
| |
| |
| |
| |
| |
| | |
6dfb1f6553 am: 18817ebb89
am: d49c29ae9a
Change-Id: I6507b6707dccaaa2c8cad30d9b1b044ca426c02c
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
6dfb1f6553
am: 18817ebb89
Change-Id: I5f2254900247fda33ca2b48b38428f01ef11b914
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 6dfb1f6553
Change-Id: I78ed7c841680ed3d82835bca2394384311e6d8b1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixed packageinstaller crash when selecting additional permissions for
an app e.g. "Live Channels". setHeader should not be called in onCreate
since it will update title UI which is initialized in onCreateView in
SettingsWithHeader.java.
Also, updated the UI for AdditionalPermissionsFragment for each
individual app to include the app banner and title in the heading.
Change-Id: Idfc12a28b38b84fcc5d97de4f85ada968e122d40
Fixes: 32338150
Test: Visual inspection of the permission UI
(cherry picked from commit c6d15a867dbbf9cb730e409a7b7426baeb64ac9f)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When the permissions UI is showing we are hiding the
system alrert windows that can overlay it in an attempt
to redress the UI. It is however, also possible to use a
toast window to overlay the permissions UI. This change
makes sure we hide the toasts in addition to system
alert windows when the permissions UI is showing.
bug:30087538
Change-Id: Ifb9ecf4593ca24b628212f0737d574a537f0cccd
(cherry picked from commit cc5e0323e83d6124f45ca75f55bc58793b550035)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
BUG=32427299
Change-Id: I04c229919c24c09131244fc8acb2c64d8902bc80
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: df52c788da
Change-Id: I2444b6612f988b5ac8ff6de351ef53f3b9516255
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Test: Simulated OK result from settings and triggered run-once
workflow
Fixes: 32105068
Change-Id: I9f6c3b56b09d520d2bc9c6eeb6c75f151e3f1aff
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 31779188
Change-Id: I655d8a38a478e0fe863b6e52611f9f43d77240bf
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 31779188
Change-Id: I41aecafefaeaaa15f70f43334df3ff367b3a312c
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 29250733
Bug: 31779188
Change-Id: I814db5f94bdb840b04c5e8d9e12b565cfcd5fbc1
|
|\ \ \ \ \
| |/ / / /
|/| / / /
| |/ / /
| | | |
| | | | |
am: b4090d16e4
Change-Id: I605d0e80afe0057dc10fa022b68f04e6d6cc2460
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also scroll the whole dialog if the screen is too small to for the
dialog.
Test: Executed steps in the bug. Dialog looks fine. Also toyed around
with display scaling and font scaling to make sure dialog always looks
ok (but might scroll) on very small displays.
Fixes: 31442798
Change-Id: I74328afde38ec2170a14aaa8e77675ad2164460e
(cherry picked from commit 3a5c306e5b6bf2285980aa34cb8eb00fbcf5ea2c)
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 435a65b477
Change-Id: Ib82f212f4ae8a8c3a5258c072ffb9ed13d28ff62
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
So that when we return from the settings app we do not have distinguish
between file and content-uri based install anymore
Test: Manually went through the following workflows:
- Install from file
- Unknown sources is already enabled
- Unknown sources is not enabled yet
- Return 0 from settings
- unknown sources was enabled
- unknown sources was not enabled
- Return -1 from settings
- unknown sources was enabled
- unknown sources was not enabled
- Install from content URI
- Unknown sources is already enabled
- Unknown sources is not enabled yet
- Return 0 from settings
- unknown sources was enabled
- unknown sources was not enabled
- Return -1 from settings
- unknown sources was enabled
- unknown sources was not enabled
Fixes: 31328285
Change-Id: I1d23f2ba9a835f7bffc59108565b286aeb675411
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Handles IllegalArgumentException from the deletePackage call.
It's unclear right now what the root cause of this crash is,
but we will follow up with that in a future release.
BUG: 31425541
Change-Id: I24eba7c06f090dd6dcd2f75268cd6be1d1f2f500
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 9137038766
Change-Id: I728b7ff5bc46436dfced714a8ff5dd422e2e70a9
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 30056625
Change-Id: I1ffc7ba88ea5f99591b66c08e72ea07d60ab82d5
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 31301246
Change-Id: I2d93ee0e8913b8bd696730bb9d24535c6f9ac817
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: d7d3b73bd6
Change-Id: I4a72e89f7a05c72ab7e47c01fc76ff5099e34a94
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 30056625
Change-Id: Ie8e46fc7a2c340fb04b64feb331af0d882fe9672
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 5fe91f8d06
Change-Id: I49fa46b1b8a43d74a1fa29f551f173da12c37960
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 30056625
Change-Id: Ie8e46fc7a2c340fb04b64feb331af0d882fe9672
|
| |\ \ \ |
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
am: 46b1bd8335
Change-Id: I8f21255ec9c6869d5c787a98879efc6c43f2d599
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 30770664
Test: Manual -
1. Disable one app
2. Go to Settings -> Apps -> menu -> App permissions
3. to check the visibility of that app.
Don't show disabled app in the PermissionAppsFragment.
Change-Id: I0d97f7011c13c9a78e988901285f10ca9e5b2cd8
(cherry picked from commit 92c2b41b91bffcc5ef1dbbe37ef66720753180ad)
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
am: 9610c8fc89
Change-Id: Ie8bfd90027696f8706312d5a1c4ae7629b68aab2
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 30770664
Test: Manual -
1. Go to settings -> Apps -> Menu -> App permissions
2. Click one permissions folder.
3. Observe the sequence of apps.
4. Click the "show system" menu.
5. Observe the sequence of apps.
Now the system apps and user apps are merged and sorted by alphabetic
order.
Change-Id: I45c933f9be30f138085f46f9515c38bf998bfb9a
(cherry picked from commit b7ea973e7ad8e8c0a5dad420e0fc705efc92ec0b)
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 4b1e2d8d07
Change-Id: Ied08d511e64a39b6e4851306294f1a3361502b78
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is apparently possible for an activity to get
a configuration change callback when its view is
no longer attached to the window manager. Check
if a view is attached before removing it from the
window manager.
bug:30389560
Change-Id: I384401742eca61d140c7590eb5c67150a15da83b
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This changelist moves around the check for permissions and features,
so that apps that do not have the right features, do not trigger a
permission granting notification.
Such apps are, for example, MotoConnect and other device-specific
apps, that are synced to all devices but should not be installed on
devices that do not match.
At the moment, these show a permission but installation will fail
silently later on.
Bug: 30582992
Change-Id: Ia75591d90f2c056378e256f98fe7db61ede4c7b2
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
am: d2c348e31f
Change-Id: Ibdb4032495389d6fb6a0e029be99966d3b3c5f59
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the app uses no permissions and requested a runtime permission,
the latter is reported granted while it is correctly not granted.
Now we initialize everything as denied in case we exit eraly as
the app does not use any permissions.
bug:30747277
Change-Id: I08dbf086e7c3d5f66b6831c54910fbb4f0943388
|
|\| | |
| |/ /
|/| |
| | |
| | |
| | | |
am: 8fdd3b3144
Change-Id: Id78c42b62d0a7d1aa9a0b4d3e0f2250db33477a5
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the first permission of a several permission request is
denied with prejudice the rest of the denied permissions in
the sequence are also incorrectly denied with prejudice
even if the user didn't select "don't ask again".
bug:30653785
Change-Id: Ib942dd3c692d1c3a09dc1a64f2947ded0f193923
|
|/ /
| |
| |
| |
| | |
BUG: 30067232
Change-Id: I98ff09ce150d8c597ec7f4b1f1b86ec0997e7c02
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
An incorrect fix for a security bug where apps with
overlay access can redress the permission message added
a secure button implementation that refuses interaction
if the window is covered. While this was fixed in M
branches we did not merge the change in NYC because
we now hide all overlays. However, the app op which
controls overlays allows privileged apps to bypass the
app op. It is fine to have priv apps overlay stuff on
top of the permissions UI except that the allow button
show be clickable. This change removes the offending
code.
bug:29879858
Change-Id: I9d0b5e62b5ef029069e37f34dbcd90d4909d966b
|
|\ \
| | |
| | |
| | | |
into nyc-mr1-dev
|
| | |
| | |
| | |
| | |
| | | |
Bug: 30104199
Change-Id: I97a16938c36b4dadc9167652f6297acf829366e9
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the permissions UI is showing we are hiding the
system alrert windows that can overlay it in an attempt
to redress the UI. It is however, also possible to use a
toast window to overlay the permissions UI. This change
makes sure we hide the toasts in addition to system
alert windows when the permissions UI is showing.
bug:30087538
Change-Id: Ifb9ecf4593ca24b628212f0737d574a537f0cccd
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
... when installing app via packageInstaller.
This allows the apk to have some limited control over where it will be
installed.
Change-Id: Id5140e7d2a2e3b8dd59815a0febf5c05cee08fbf
Fixes: 30056625
|
| |
| |
| |
| |
| |
| |
| |
| | |
- flag is passed in from https://critique.corp.google.com/#review/126666577
Bug: 29641183
Change-Id: I1becbb446d824331430eb37d99bdbc7a36dd13db
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the permission apps screen we have a menu item to show/hide
system apps. It is possible that no system app uses the permission
making the menu item do nothing. We don't add the menu item if
no system app uses the permission.
bug:29395895
Change-Id: I1756981b2f711fc7a886bd4227196fef1a3cea03
|