| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Make sure that pm.getHomeActivities() returns the activity metadata
as well, so that the caller can trace the reference
* Add a public canonical name for that metadata key
Bug 10749961
Change-Id: Ic4d0750d61001ffe5af180398f042afa30eea1ce
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a bundled app is upgraded, only reprocess ungranted 'system'
permissions if the bundled apk is privileged.
Also adds the 'privileged' flag to the dumpsys flag summary.
Bug 10503183
Change-Id: Ic6560fc904e5970fc871a155c898744a6607f851
|
| | |
| |
| |
| |
| |
| | |
Bug 10184643
Change-Id: I72c5177c621c24fac34bf8744eb6c5108b6d3464
|
| | |
| |
| |
| |
| |
| |
| |
| | |
To support improved home-app selection UX in Settings.
Bug 9958444
Change-Id: I106090784618bf7bea6fce28f4f9b9fb8480d310
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This provides group membership to the FUSE daemon, since system
packages like NFC and Bluetooth hold sdcard_rw.
Bug: 10610659
Change-Id: I7428e999cfa4087ffe220b9d8bd80827191ab997
|
| | |
| |
| |
| |
| |
| |
| | |
Restrictions challenge is only to be used by device admins.
Bug: 10461761
Change-Id: I3db1249e2ce99f386602de59ed930302bb0a97fb
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Otherwise this would result in NPE, and packages.list would never
be updated.
Bug: 10577538
Change-Id: I35a4407dbc283ab20a4c45a2ea1a14b04044c98c
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Keep track of last chosen activity for a particular intent, similar
to how it is tracked for "Always" choices.
Pre-select the last chosen activity if previously the user picked
"Just once".
Downgrade "Always" to "Last chosen" if there's a new kid on the block,
instead of removing it entirely.
Add methods to set and get last chosen entry.
UI - switch from Grid to List.
Bug: 9958096
Change-Id: Ied57147739a3ade1d36c3a7ec1e8ce77e5c5bb16
|
| |/ /
| |
| |
| |
| |
| |
| | |
This causes all restriction pins to be reset.
Bug: 10535070
Change-Id: Ia2abf904505514d7e555b420c2b032a0094e0643
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Changed PackageManager to read a config value that indicates if
the default ResolverActivity should be replaced by a custom version.
This config value can be replaced via an overlay.
Bug: 10081151
Change-Id: I6f1c59d053b89fabf52bcda620eb5d4026406701
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Write supplementary GIDs to packages.list for lower-level system
components to parse.
WRITE_EXTERNAL_STORAGE also implies sdcard_r GID. Switch to always
enforce READ_EXTERNAL_STORAGE permission. Update permission docs to
mention new behavior.
Change-Id: I316ba4b21beebb387ac05c80980ae9b38235b37d
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Provide developer APIs to discover application-specific paths on
secondary external storage devices. Covers files, cache, and OBB
directories. Apps will not have write access outside their package-
specific directories on secondary devices, so only primary storage is
exposed through Environment.
Creation of .nomedia files will be handled by FUSE daemon in future
change.
Change-Id: Ifcce6201a686d80269d7285adb597c008cf8fa7c
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The FUSE daemon is using packages.list to map from package name to
appId after it drops permissions, so create a new "package_info" GID
to grant read access.
Also switches FileUtils to use Libcore.os.
Change-Id: I9451ca4e90e8a985526805c6df0888a244a1db36
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
Bug: 10024554
Change-Id: I742e918840a98dd83d713bdf7a43a919674e65fe
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since the Restrictions feature was removed, some cleanup code was
added to unblock apps. But the cleanup is causing some runtime exceptions
due to happening too early in the boot up sequence. Moved the cleanup
to after boot_completed broadcast is received.
Bug: 10212758
Change-Id: Id42eff16b54c24ea48cf8b3a81f77ea801264edd
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
Bug: 10200097
Change-Id: I4d95cd49a21e8f4f6b2c141d1205f81622c395b5
|
| | | |
| | |
| | |
| | | |
Change-Id: I7808cafc1f74c47fcd9d9a4b6a90fb50951457b1
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
A little grossness for now to support dual booting Dalvik and Art.
While I was here, removed isDexOptNeeded calls for boot class path which already return false.
Change-Id: Iaaaf21b7733c1791e7bd8ae27e84c47463f9e9c9
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note that it is *intentional* that even a privileged app cannot
add new privileged permissions via unbundled update. The set of
privileged permissions granted is strictly limited to those used
by the apk file installed as privileged.
Bug 10027033
Change-Id: I974bae0671c1962e4526d51dd9a0c53bcd27323e
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is an extension from the existing data/etc/perferred-apps
facility. Now applications pre-installed on the system image
can declare which intents they would like to be considered the
preferred app for. When the system firsts initializes, or the
application settings are reset, these are used to configured
the current preferred app settings appropriately.
You use this with a new <preferred> tag under your activity,
which indicates which intents you would like to be the preferred
handler for. The syntax for this is written much like an
intent filter, however semantically it is not really an intent
filter and so has some important differences:
- You can not use globbing patterns (for SSPs or paths).
- You can use only one action (if you use more than one it
will only use the first one, so be careful).
Semantically what this is actually used for is a template
from which to generate a set of Intent objects, which are used
to probe the current environment in order to see if there are
multiple activities that can handle the Intent and, if so,
generate a new preferred setting for that pointing to your app.
As an example, here is how the preferred tag might be written
for the Maps application:
<preferred>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="http" />
<data android:scheme="https" />
<data android:host="maps.google.com" />
<data android:path="/" />
<data android:pathPrefix="/maps" />
</preferred>
<preferred>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="geo" />
</preferred>
From this, we generate the following set of potential Intents
to be matched, all with ACTION_VIEW, CATEGORY_DEFAULT+CATEGORY_BROWSABLE:
Change-Id: I7fd42aec8b6109c7dd20012529662362f1b7437a
http://maps.google.com/
http://maps.google.com/maps
https://maps.google.com/
https://maps.google.com/maps
geo:
|
| |/ /
| |
| |
| | |
Change-Id: I80e08b38b5e32f3cb1af51398907510508ec199f
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since this is an operation that could take a few seconds to run and needs to be
completed even if Settings dies, best to do it in the user manager.
Refactored PIN challenge/setup UI with a field to verify existing pin
when changing to a new one.
Change-Id: I0b7df5b2ccb7f343aa9282a9245d3bc2b577a794
|
| | |
| |
| |
| |
| |
| |
| | |
The new apk will now correctly allow system permissions to an app
placed in the privileged install dir via 'adb push' on the fly.
Change-Id: Ie4284d12628e08d9562d18eee6a7e8f74ae6295e
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
To help with development, change comments to Javadoc and adding some
links.
Change-Id: Id97febd978f14bace8242d8e0610b1166a13265b
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Partially fixes the mess that was caused by #9681399
Change-Id: Iaabe15c87d1b002f0b2210b34adcc31b8fb4329c
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make the constant KEYSET_NOT_FOUND so that other source code components
can use that as the sentinel value directly instead of -1
Change-Id: If89de5fb312d55e360b96aadbc6effcd480043b2
|
| |/ / /
| | |
| | |
| | | |
Change-Id: I2348e75e95581b1e5acf1c52b83948e46547a19e
|
| |/ /
| |
| |
| |
| |
| | |
Add the list of aliases defined to the dumpsys output.
Change-Id: I8bba20fba8dd123f749372cab7b8f038aa47331f
|
| | |
| |
| |
| | |
Change-Id: I43e18e824e62b3ec54964ace1485a45616b962f2
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Introduces a new "blocked" state for each package. This is used to temporarily
disable an app via Settings->Restrictions.
PIN creation and challenge activities for use by Settings and other apps. PIN
is stored by the User Manager and it manages the interval for retry attempts
across reboots.
Change-Id: I4915329d1f72399bbcaf93a9ca9c0d2e69d098dd
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Bug 9470309
Change-Id: Ibc0c8b2fa01da1bd5f5b6ed5530a6bd9a1384846
|
| |\ \ \
| |/ /
|/| /
| |/
| |
| |
| | |
to an updated system app"
* commit '3c0cd0b54064f81a6a74d895707453fb0132719c':
Avoid adding FORWARD_LOCK flag to an updated system app
|
| | |\
| | |
| | |
| | |
| | | |
* commit '3e7d0344399ac2f607fddde32c1a5e54228a38f9':
Avoid adding FORWARD_LOCK flag to an updated system app
|
| | | |\ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Consider the following case:
1. An app exists in /system/app or /vendor/app. (i.e, it's a system app)
2. If the app would be updated as a forward-lock app by downloading from
market(google play), then it would be installed in /data/app-private.
3. Moreover, if it would be updated by the whole system image (i.e, FOTA
or something like that), then the app would be applied a FORWARD_LOCK
flag.
The app SHOULD NOT have a FORWARD_LCOK flag. Because the resource path
of such app does not refer to the proper resources to access.
Change-Id: I0750f69a93a3115f4201029796b598507de3555f
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When an application's user data is cleared, the keystore entries need to
be cleared as well. Previously we were only clearing entries when the
application was uninstalled for all users. Now we cover the case of
multiuser as well.
(cherry picked from commit 6fd1c85d7f909580582e5ebc357564331ecef283)
Bug: 8566369
Change-Id: Id4df5e50661b676b8f6507b915764400982c01a0
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Only call keystore if outInfo is not null
(cherry picked from commit 3b9933d0c2f2b9a2e973dca296ee45a69087e31c)
Bug: 8568820
Change-Id: I764980fd396dbc637732ad290eea2bd11036ec28
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
One problem this turned up is, because FastPrintWriter does
its own buffering, a lot of code that used to use PrintWriter
would fail -- if it pointed to a StringWriter, there was no
buffering, so it could just immediately get the result. Now
you need to first flush the FastPrintWriter.
Also added some new constructors to specify the size of buffer
that FastPrintWriter should use.
Change-Id: If48cd28d7be0b6b3278bbb69a8357e6ce88cf54a
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 9532748
Change-Id: I3cce41de74783a121d2cd4f7b0ea6dfa03e3d7c5
|
| |\ \ \ \ |
|