| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the user does not want to enable "unknown sources" and clicks
"cancel" the whole installation should finish.
Fixes: 28683865
Change-Id: I2582141ea777e5b2e14dd690b3c3fb8039cff2d4
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 51b7ac8dc1
* commit '51b7ac8dc1b2e6ccb2d3af2f1c1d84b529977e3a':
Fine tune UI of package installer.
Change-Id: I0b2407e42d74ac3c15b3926f202b327de5561c9a
|
| |\ \ \ |
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes two screens in the case no permissions are required.
- Do not remove tabs, just make them invisible. This is required to push
the "OK" and "CANCEL" button to the bottom
- Show spacer under text as this looks prettier.
Fixes: 28746145
Change-Id: Ia312b476c7e3944709ed3f8fd71d12268559257f
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: f63739bb3f
* commit 'f63739bb3f5de9927171b84630ec5872ba85fa6c':
Fix app install flow
Change-Id: I37bdfd9f7e005d57eb90e46f87f4cabcfaa6519c
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A regression was introduced when we added support for
installing apps from content URIs. Since we stage the
APK in the cache folder we changed the flow to wipe
the cached version when the PackageInstallerActivity
finishes or gets an installation result, so we started
the InstallAppProgress activity for result but the latter
may be called with the forward result flag which is
incompatible with start activity for result. This change
delegates clearing the staging file in the cache folder
to the InstallAppProgress activity.
bug:28551937
Change-Id: I0d9978aff60b7fab6b64fe7bf889ef30f9b2fd7c
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The default directory for PackageInstaller moved from
/data/user/foo to /data/user_de/foo. Not sure on the exact reason
why, but it has something to do with the file based encryption
changes in N. This was causing the temp APK file that we were
passing to PackageManager for installs to be in an invalid location.
This resulted in failed installations.
This is OK though because we never really wanted to use a temporary
file. We were using it due to limitations in the PackageInstaller
APIs. Since implementation, new APIs have been added to allow us
to pass a stream through instead.
This CL updates the install logic to use the stream API instead.
Because this code path is being deprecated and replaced, I've opted
to do the bare minimum needed to keep this code operational. I've
also borrowed installation code from Wearsky/Finsky codebase to
make it easier and more reliable.
BUG: 28021618
Change-Id: Ia245abf56649e350e99cf48d2b503906d3cd855c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This does not implement correct onDestroy->onCreate behavior but mends
it for the common case.
We now handle all configurations changes, hence onDestroy->onCreate is
very rare. We also just abort quickly if we actually had a
onDestroy->onCreate instead of crashing.
This is a temporary fix.
Bug: 28588511
Change-Id: Ief56c8b866f2561b13253f66a7f79517fc2132cb
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We were returing a null PermissionGroup object to a place
where this was not expected by design. The reason for that
was an incorrect fix for b/28241097. This CL reverts the
introduced regression and adds a null check just in case.
bug:27102458
Change-Id: I78f8107d0adf6bb2da5d8e11c5f3cf3c00fe36a2
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The message now depends on the state of mAllUsers flag in
UninstallAppProgress activity:
- This app is required for some users or profiles and was uninstalled for
others (if mAllUsers==true)
- This app is needed for your work profile and can't be uninstalled
(if mAllUsers==false)
Bug: 28240714
Change-Id: Ia060aebd112d3e4c5fcaee02a777140f085abf87
|
| |
| |
| |
| |
| |
| |
| | |
IPackageManager.
Bug: 28207146
Change-Id: Idc75427005c7998de4edd30245fa00a68ba816ba
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Change-Id: Iba35b172c03e971d2ef9864ddb86534f163b5993
|
| |
| |
| |
| |
| |
| |
| |
| | |
This actually covers most apps and flashing a screen for such a short
time is just flicker.
Bug: 24263165
Change-Id: I82469cad8277599677a5cf11ef975492d22f6d8d
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 26932948
Change-Id: I7552eaad562c2772c02cfa6f13cb044b6db17a19
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Added a menu item to link for the help center article for app
permissions.
Bug: b/22096093
Change-Id: Ic810bbcc64b20ab6ee21140f0bb3ea055c10813a
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 26932948
Change-Id: Ic8bcec523fc6cd0db847a4575724fbe465e65c5d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Checked the wording of the content of the dialogs and I think the
title does not add any information. Design guidelines discourage
dialog titles.
- Removed unused dialog type
- Removed now unused strings
- Spell corrected a string
Bug: 5526317
Change-Id: I7d125d92ef3a2fb3fd6fd402af8d2422c0d8b869
|
|/ /
| |
| |
| |
| |
| | |
bug:21891813
Change-Id: Id9a694d14ecd80c8c04dc28b34cdda3e9119bfb3
|
|\ \
| |/
|/|
| | |
nyc-dev
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apps can define permissions in the platform groups. If a legacy app
deifines a permission in a platform group we were showing the permission
twice because we failed to group the custom permission in the platform
group when building the UI.
bug:26142772
Change-Id: I263bff8631e14395c9000e5e54b0e160969e1eb2
|
|\| |
|
| |
| |
| |
| |
| |
| | |
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
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Show "Manage users" button when a secondary user is blocking the uninstall.
Bug: 24616123
Change-Id: I61f1d9814dccc9f9e8acbce97d8ef681f5ec8944
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
- Remove a way to implicitly call Wear install service
- Also make the Service take in the package as the data, just like the
activities in PackageInstaller
Change-Id: I0c4c9cebbb7396e025cab81eed835ab1a941ca01
|
| |
| |
| |
| |
| | |
Bug: 27645571
Change-Id: I824198b0eefea08ee3f0fa4f4f9267a557d21166
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When starting the installer without a URI, it would crash. Don't
do that.
Bug: 26450627
Change-Id: I2b0d452c12c0fc695326200617c5284f60a9e45b
|
|/ /
| |
| |
| |
| |
| |
| | |
Inform about data deletion and also about other users.
Bug: 26694521
Change-Id: Ib1ab8ca58e111cfbad6895f296e567e289ce34d8
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
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
|