| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since they need certificates that are not backed up/restored; restoring
them is not that useful.
Bug: 6544151
Change-Id: Ida1a98dc4f01ec1883ce7f76e52f87a27cc814cc
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 10130785
uncanonicalize() can return a null now, so abort restoring the ringtone
in that case.
Change-Id: I28765818c8d3e1fb3f271afdfe66ebc955cfcefe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use the new content provider API to canonicalize Uris.
If the provider doesn't support it, don't save the value,
unless it's a silent ringtone.
Bug: 10130785
Change-Id: Id08bb2812b9b2a7036a25801d1997661b0017629
|
|/
|
|
|
|
|
|
|
|
| |
The calling package is important for ContentProviders that want to
grant Uri permissions as a side effect of operations, so offer it
through a new API. Validates the provided package against the
calling UID before returning.
Bug: 10626527
Change-Id: I7277880eebbd48444c024bcf5f69199133cd59e4
|
|
|
|
|
|
|
|
|
|
| |
In creation/deletion cycling we can wind up racing and attempting
to establish the Android ID on first access *after* the user has
already been deleted. Cope gracefully with this outcome.
Bug 10608503
Change-Id: I169d5052e5a2e354ce0e1f61258e45e31f5ba171
|
|\
| |
| |
| |
| |
| |
| | |
default value"
* commit '9fe49fc56ef39facf7b3be5f66256bd15a87961f':
Set subscription_mode in the database to a default value
|
| |
| |
| |
| |
| |
| |
| |
| | |
If ro.telephony.default_cdma_sub is set, use that to set the
default CDMA subscription source in the database. If that is not set
use the default preferred value defined in the source code.
Change-Id: I11fff596a5fe721c64f192c889672326517dc43d
|
|\ \
| |/
| |
| |
| |
| |
| | |
differently for LTE+CDMA"
* commit 'e2be065142dc22f1eea033334f6ba4cf16559e56':
Do not set the network mode differently for LTE+CDMA
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
LTE+CDMA"
* commit 'f313da5bfe1953fef509ba6bab7f654516a71509':
Do not set the network mode differently for LTE+CDMA
|
| | |\
| | | |
| | | |
| | | |
| | | | |
* commit 'aff0ac4d202934dde7765f7418ea2ad38b0c2faa':
Do not set the network mode differently for LTE+CDMA
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ro.telephony.default_network can be set if needed to set a different
value for LTE+CDMA. No need to hardcode preferred network mode in the source code.
Change-Id: Iae65f72a6a3bc31d500c5ecec87368a6f2a5d117
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
generated, dump it to dropbox" into jb-mr2-dev
* commit '3f0decd7dff8b4c12544c24b2d19a41d4eaacd03':
When a new user AID is generated, dump it to dropbox
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 9595851
Change-Id: I6fde757eed84d7914db180e80c9d68448b3e5780
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"signatureOrSystem" permissions are no longer available to all apps
residing en the /system partition. Instead, there is a new /system/priv-app
directory, and only apps whose APKs are in that directory are allowed
to use signatureOrSystem permissions without sharing the platform cert.
This will reduce the surface area for possible exploits of system-
bundled applications to try to gain access to permission-guarded
operations.
The ApplicationInfo.FLAG_SYSTEM flag continues to mean what it is
says in the documentation: it indicates that the application apk was
bundled on the /system partition. A new hidden flag FLAG_PRIVILEGED
has been introduced that reflects the actual right to access these
permissions.
At some point the "system" permission category will be
renamed to "privileged".
Bug 8765951
Change-Id: I6f0fd9cdb9170e076dfc66d83ecea76f8dd7335d
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
turning off wifi" into jb-mr2-dev
* commit '1bc14ed9c3bb0fae28c2cdf9319b2f5f892409eb':
Need to explicitly disable scan-always when turning off wifi
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... when you want wifi to be really most sincerely off, because
settings restore is about to rewrite the conf file.
Bug 9032154
Change-Id: I6a3a34ac3f14ec43aa9d9cc0159fca6168ccd0a2
|
|/ /
| |
| |
| | |
Change-Id: Ic6008d4c9f8b9cd9fd4efec070260227af70559c
|
| |
| |
| |
| |
| |
| |
| |
| | |
Make sure that apps that have access to restricted accounts can see them.
If they don't have access, they shouldn't be able to add a new account either.
Show an error message in the account picker if the user/app is not authorized.
Change-Id: I117c0b14d7d06c5ac4e66506df156b174567f5f3
|
| |
| |
| |
| |
| |
| |
| |
| | |
Created constants for these in UserManager and current.txt. Also created
an accessor for individual user restrictions that takes the restriction key
(removing individual methods for particular restrictions).
Change-Id: Ibb5517cbcdffadd3925f52cbe67d7d525813faa9
|
| |
| |
| |
| |
| |
| | |
And add support for respecting it.
Change-Id: Ia5cf9134c5f5741c3f55afadbe54f862da7bfe5b
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
DatabaseHelper"
# By Yevgen Pronenko
# Via Android Git Automerger (2) and others
* commit '3c239d7e8d78570b1e17ad968c408506e73a8f3f':
Disable usage of WAL in DatabaseHelper
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
# By Yevgen Pronenko
# Via Gerrit Code Review (1) and Johan Redestig (1)
* commit '88ba2f48a2d1193f3877575b2589897a7804aa75':
Disable usage of WAL in DatabaseHelper
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
According to SQLite documentation, WAL can not be used when database
partition is not accessible for writing (even when the client just
performs read operation).
However, such situation may happen when the partition is full.
As SettingsProvider should always be able to read a value of ANDROID_ID
from corresponding database, this commit disables usage of WAL.
Without this we risk ending up in a situation where /data is full
and the phone is unable to boot properly.
Change-Id: I1f79bbcd8d0f64bf35dc9d7b846bcfb2664d2eac
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
insertForUser takes a specified user and attempts to adjust that user's
settings, first looking at their existing settings to determine the difference.
However it was querying the settings for the calling user, rather than for
the user whose settings were being changed.
Also add a test that exercises the fix.
Change-Id: I6ed6fd79154ac1b6e6ab880769ac9081dfff6b80
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also fix a build.
And fix a bug that I think was introduced in the multi-user work
that removed the permission check for writing to settings...!
Change-Id: I5945682faa789ffc78fd3546c0df7d03693f106d
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit d1ed3cea37e4156eab14b7dc8207a520c9eab700
Change-Id: I622ef034526f8f006a5a233e72487b062020e4f6
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 0a9c7c144671f70f5f1af222050bd3ec6b11fe41
Change-Id: I8da530a6d0a57163522d5a63326e787a8d22ecbf
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I8cbc4f03223d289547e3f3f6d1f528ad5b4f6f72
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently we have an "enhance web accessibility" setting that has to be
enabled to make sure web content is accessible. We added the setting to
get user consent because we are injecting JavaScript-based screen-reader
pulled from the Google infrastructure. However, many users do not know
that and (as expected) do not read the user documentation, resulting in
critique for lacking accessibility support in WebViews with JavaScript
enabled (Browser, Gmail, etc).
To smoothen the user experience now "enhance web accessibility" is a
feature an accessibility plug-in can request, similarly to explore by
touch. Now a user does not need to know that she has to explicitly
enable the setting and web accessibility will work out-of-the-box.
Before we were showing a dialog when a plug-in tries to put the device
in a touch exploration mode. However, now that we have one more feature
a plug-in can request, showing two dialogs (assume a plug-in wants both
features) will mean that a user should potentially deal with three
dialogs, one for enabling the service, and one for each feature. We
could merge the dialogs but still the user has to poke two dialogs.
It seems that the permission mechanism is a perfect fit for getting
user permission for an app to do something, in this case to enable
an accessibility feature. We need a separate permission for explore
by touch and enhance web accessibility since the former changes the
interaction model and the latter injects JavaScript in web pages. It
is critical to get user consent for the script injection part so we
need a well-documented permission rather a vague umbrella permission
for poking accessibility features. To allow better grouping of the
accessibility permissions this patch adds a permission group as well.
bug:8089372
Change-Id: Ic125514c34f191aea0416a469e4b3481ab3200b9
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug 7273591
Change-Id: I5790f9d18ddf22282144be1c2d96dd4d706caa14
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
dock audio"
* commit '53d998368c6c6107c6d18de945f4dfee482e6f91':
Setting the default value for dock audio
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | | |
* commit 'b2d3904b0d0f02b3eddef1d228724b99962cba56':
Setting the default value for dock audio
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There was no default value for parameter "dock_audio_media_enabled"
in global settings and because of that it couldn't be obtained before
Settings app first start and improper actions, such as FORCE_NONE
sending to AudioSystem instead of FORCE_ANALOG_DOCK, were taken.
This patch sets default value to 'true'.
Change-Id: Idbe343519db15f806f3a237e8b39f8420b9edde1
Signed-off-by: Dmytro Dubovyk <dmytro.dubovyk@ti.com>
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
when upgrading secondary users\' database." into jb-mr1.1-dev
* commit '68c308607b01bafd31c91572a81f4563e2199260':
Don't update global table when upgrading secondary users' database.
|
| | |
| | |
| | |
| | |
| | | |
Bug: 7722149
Change-Id: I0c1373cba316b924701136579083274eb6c9b1da
|
|\ \ \
| |/ /
| | |
| | | |
Change-Id: I51dedcc5ee521e62ad6101c0b09e4f881b8c4bf0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only plays a tone if the battery level is below 95% which
is the same heuristic used when determining whether to turn
the screen on.
Use new low battery and wireless charging sounds on Mako.
Bug: 7371658
Change-Id: Ia4527ec398d024ee418a4287e1fcbf0ec83bcc24
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
Optimize for updating mNetworkPreference according to device's networkAttributes
setting from overlay config.xml when connectivityservice start.
Change-Id: I90286332d4f453038f1ddac7dd9d1265d96b4859
Signed-off-by: Jianzheng Zhou <jianzheng.zhou@freescale.com>
|
| |
| |
| |
| |
| |
| |
| | |
This does some cleanup of the initial boot, especially when
booting in "no core apps" mode for encryption/decryption.
Change-Id: Ifb3949f580e52f54559e603c4b0b104f6bac2f6c
|
|/
|
|
|
|
|
| |
Also fix a little problem where the USER_STARTED broadcasts
were not being sent as ordered broadcasts(!).
Change-Id: I3aa3e0a9b3900967cdd2d115ee103371b0a50c41
|
|
|
|
|
| |
Change-Id: I51415c91026c1ea461f1b1239a75ec999fd7fe0c
Auto-generated-cl: translation import
|
|
|
|
|
|
|
|
|
| |
So that:
- the values can be shared (to fix assoc bug)
- the values can be customized in product overlays
Bug:7373284
Change-Id: I37f037082523a3d975f6014f36afa28c60117372
|
|
|
|
|
|
|
|
| |
...to allow network-reliant restore actions by apps to get underway.
Bug 7304761
Change-Id: Ia1d2321ef86609588efbc7add043c24a12ec6a20
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason, the original step didn't work for some testers. This re-applies the move, which
should be no-ops if the entries are already in the right table.
Bug: 7254629
Also moved a few more entries to the global initialization section. Otherwise they would write
into the wrong table.
Change-Id: Ic0f5c4e09680f5687d08dccf78063508b9c0584c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now with more fix.
Bug 7249405
Change-Id: Ib8bc2e9c5b054054f4aaacf14af8d5a0d05d6e3a
|
|\ \
| |/
|/|
| | |
jb-mr1-dev
|