| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Protect app widget broadcasts from abuse.
In this case the app was sending an APPWIDGET_UPDATE broadcast
without specifying a target, which (a) should not be allowed (you
should not be able to send updates to other apps), and (b) resulted
in every single potential app widget in the system being launched...
which was about 75 of them.
Change-Id: I9d48733610ce6d5a7c32e69a3e06b9f33bd79a34
Signed-off-by: Dianne Hackborn <hackbod@google.com>
Tested-by: Moritz Bandemer <replicant@posteo.mx>
|
|
|
|
|
| |
Change-Id: I22188668bd4b2d82dcfb13d0b656db324b858858
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|
|
|
|
| |
Change-Id: I0d7809e7ae408c4762982599576be9a78d54a2dc
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|\
| |
| |
| | |
configurable." into cm-10.1
|
| |
| |
| |
| | |
Change-Id: I1be0be2753b479e6d2e4fc8e17d971d03ce01bb7
|
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes five errors when building the Java docs. It also
removes two obsolete lines.
Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
Change-Id: I814411cbc8d16eaed99a1389f5487529e36e647b
|
| |
| |
| |
| |
| | |
Change-Id: Ibbe544a9f025d71ad416bc01cee2145b62d7b2d4
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
|
| |
| |
| |
| |
| |
| |
| | |
Per request by Google, move the install-time checks entirely
inside PMS.
Change-Id: I01f2a9084dfe7886087b1497070b0d7f2ad8479e
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The location of policy files has changed from
/data/system to /data/security.
Also, a name change to mmac enforcing property
name to place it under persist.mmac. namesepace.
Adds api's for getting and setting the MMAC
enforcing mode.
Change-Id: I0e9468fe651cd6ec018d5c85d35d693e55479e89
|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
api/current.txt
core/java/android/app/admin/DevicePolicyManager.java
Change-Id: I1df507ced67fbcab8fdcde9cce78705b5e54e346
|
| |
| |
| |
| | |
Change-Id: I01f2a9084dfe7886087b1497070b0d7f2ad8477e
|
| |
| |
| |
| | |
Change-Id: If2e076312b0e411145c1cd900f3ae20d998a0f24
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These calls, added to the Device Admin API, will allow Device Admin apps
to change various SELinux settings, including:
* Toggling SELinux enforcing and permissive modes
* Toggle SELinux booleans
* Load a new SELinux policy file (sepolicy)
* Load new SELinux context files ({property,file,seapp}_contexts)
In order to use these APIs, a Device Admin must first request
USES_POLICY_ENFORCE_SELINUX, then become a SELinux Admin by calling
setSELinuxAdmin(). All other set* calls relevant to SELinux are guarded
by a check against whether the admin is a SELinux Admin.
Otherwise, the style of the set* calls are very similar to the other
calls setting device policy in the Device Admin API. That is, these
calls change the Admin's internal state and then call a sync method to
update the device's state to the Admin's state.
Change-Id: I01f2a9084dfe7886087b1497070b0d7f2ad8476e
|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
core/java/android/provider/Settings.java
Change-Id: I01f2a9084dfe7886087b1497070b0d7f2ad8474e
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch set allows the PMS to parse the
mac_permissions.xml file which contains the
seinfo values. Each package that is installed
on the device will be assigned an seinfo value
based on policy. This seinfo value will help label
the app process and data directory. Modifications
also include, adjustments to ApplicationInfo.java
to store the seinfo tag per package, adjustments
to installd to communicate the seinfo tag to
libselinux, and finally a set of unit tests.
Signed-off-by: rpcraig <rpcraig@tycho.ncsc.mil>
Change-Id: I61ad1ea12fb6a9a6d0b108ec163bc4bf4c954b58
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Id70cb1bce15b7de127e4291e9482ab3fd7270f9f
|
|\ \
| | |
| | |
| | | |
cm-10.1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will allow the user to select wether or not to use the
rotation settings for the lockscreen. This is dependent
upon the rotation setting being checked.
Signed-off-by: Michael Bestas <mikeioannina@gmail.com>
Change-Id: Ibd7c69b0af1e0a7d91b985f2b21ea0b5bc619a70
JIRA: CYAN-339
|
|/ /
| |
| |
| | |
Change-Id: I8be01ad6251ca25e4d00ebffd876bb6ce7f3c283
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
As we can't restore the contents of the cursor window, we need to keep
it on deactivation so we can restore it on requery().
Change-Id: I06f688bbe9120c307bdc3ddbc3833416becdec82
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I41b76c5e01c82a2f8e67b33133a76947877a2814
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: Ic59f370a6e78390c9b2b1510e0ec85b2f4af9146
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 6923539
Change-Id: I49aac145e8e80a5af7475cfe93ef4a353d2d3fe6
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Bug 8460775
Change-Id: Ib16d740a001adf4f9cb9ccaa31066ac7cadfb430
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
JIRA:CYAN-1566
Change-Id: Iae3dd9914b1685c6bf1e39e421372ce0bdfb93cc
|
|/ / /
| | |
| | |
| | |
| | | |
Change-Id: I8a5e1d15d17d56089158b24f9a4b246ae6e60285
JIRA:CYAN-1550
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add fix so ordered broadcasts are delivered to system
apps first in the event of a tie. This works around
the issue where terrible apps steal SMS notifications
from the broadcast queue to simply prevent notifications
that could otherwise be removed by a toggle.
Change-Id: I4fff0c584f8fce9c5f2f4fe86a82fe6480c307c7
|
|/ /
| |
| |
| | |
Change-Id: I55d0768c9eeecb7dcce97c6d6390e339d678d0c4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It doesn't really make sense to store the (non-persistent) state of the
torch in a (persistent) setting. As the torch is sending a broadcast
anyway, make that broadcast sticky and use it to convey the state.
Also unify the torch constants (actions, extras, activity names) at a
common place.
Change-Id: If845bef27cc79990794aa748dce18cfea3bac1f5
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patchset 2: Add CM Copyright
Patchset 3+4: Rebase
Patchset 5: Some optimizations
Change-Id: Ic8281e4c6fef6d2f4c56fc01acfe6e54b4c8f51c
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
|
| |
| |
| |
| | |
Change-Id: I6072ed2d3ac05382f9cabbada0c42cea6cbe2422
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I0e434b989c16f5871ce56c7e3041ff3c7a436c73
|
|\ \ \
| | | |
| | | |
| | | | |
state" into cm-10.1
|
| |/ /
| | |
| | |
| | | |
Change-Id: I09213c987580f47a6c3618edb469edabda96230c
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Introduce a new privacy feature which allows the user to run an
application with reduced visibility into his or her personal data.
* Adds a per-application flag and simple API to determine if this flag
is enabled for the current or calling process.
* This flag can be used by content providers to decide if they should
return a limited/empty dataset.
Change-Id: Id7c54d728e63acb2b02a2a9322930b54949f6c5d
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I374cc93364c88b8b29c88345deccf297234ff624
|
| | |
| | |
| | |
| | |
| | |
| | | |
Remove extraneous "hours" argument in the <10 minutes case
Change-Id: I5a5913d2e0744f5783f8422cddc30603c7bd703f
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Append it at the end of everything to make it less obtrusive to
agent parsers, and append the CM device identifier so we can present
smarter choices when our sites are accessed.
Change-Id: I1e60d13be4cca9043e434a31bfc4fa08e01a12c0
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Change Ib3c1e1aad05827df646aa18645cce19dffb7551f fixes the inability
to display more that 2-digit hour values, but also changes the behavior
of <10 minutes display by zero-padding the minutes. This makes
the Chronometer widget look different, and breaks Holo CTS.
Fix it so that for values under 600 seconds, the minutes don't
get padded
Change-Id: I34eb7f22e728c55bf3313ed1987ac32969cd5ed0
|
|
|
|
|
|
|
| |
Add data structure mWifiTriggers to store triggers per profile.
Add network change listener to switch to profile
Change-Id: I97e360d7783d3b0e2bbd70fe7a9a866d8c0fa7cd
|
|
|
|
|
|
|
|
|
|
|
|
| |
PackageManagerService's context is for user 0, so if the theme provider
for other users was invoking the getInstalledThemePackages() method, the
themes provider crashed as it doesn't have the INTERACT_ACROSS_USERS
permission.
Fix that (and simplify code) by making getInstalledThemePackages()
return the installed themes for the current user, which was probably the
intent anyway.
Change-Id: I02002cee005b74128f3b2f7cc7a93b9b8514f1f3
|
|
|
|
| |
Change-Id: Ie52247d5c23c8f840ababc880dd41992049cefd1
|
|
|
|
|
|
|
|
|
|
| |
We don't need "next" button under 24-hour format any more.
So, we changed from "next" button to "done" in IME option
when setting minute under 24-hour format
AOSP commit: https://android-review.googlesource.com/#/c/54121/3
Change-Id: Ic9b1673248183060ba7279b63648a85dc39ca3b9
|