| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Way back in API 1 we defined Settings.System.DEFAULT_NOTIFICATION_URI
which redirects through SettingsProvider before finally ariving at
the real underlying ContentProvider, usually MediaStore.
With new SELinux rules, we're no longer allowing the system_server
to hold open FDs to shared storage devices, which causes these
proxied openFile() calls to fail.
To work around this, teach MediaPlayer to resolve the final ringtone
Uri without going through the system.
Bug: 18226181
Change-Id: I40c68617c952c0bb3e939e5084f5b68a35e31ae3
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Also remove hidden APIs to get/set the preference.
Bug: b/17673255
Change-Id: I8957b0380bf617c953f6665cbfdcc77c3be78411
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since it now hides the display setting, force the user to opt-in
again.
Bug: 18104538
Change-Id: I4cac947f7a35ba0f578d059542401dcc5d169307
|
|/
|
|
|
|
|
|
|
| |
To prepare for controlling from settings.
While here, add lock to app settings to backups.
Bug: 16957435
Change-Id: I059140cd07a7a0d5ceb4e0bfe5e0176cb96629d3
|
|
|
|
|
|
|
|
|
|
| |
When the max stream volume is configurable by
a system property, the default stream volume should
be set accordingly.
Bug: 17507571.
Change-Id: I9d9378292fc7b9c9e32acc55a275cc0ae5b203d4
|
|
|
|
|
|
| |
VoLTE without VT.
Change-Id: I233b003af57a550f2f51b12213700ab0451039e5
|
|\
| |
| |
| | |
Change-Id: I9e4cabd2d8a34a348ae888f096c8d3c35226e960
|
| |
| |
| |
| |
| | |
Bug: 17684570
Change-Id: I64a9c9c0620049cdfcca0150648fa201281f7178
|
| |
| |
| |
| |
| | |
Change-Id: Idcc94d2f5b04a7eea17b530c4a8ff7f8b76fff38
Auto-generated-cl: translation import
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The 'global' table only exists in the owner-user db instance; make
sure to apply global-setting update steps only when bringing up that
instance.
Bug 18069830
Change-Id: I843eabe710d9487de94690921d61adb181b45ed2
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Change-Id: I1232fd67bffa5401e778116a418bbc20902f2723
Auto-generated-cl: translation import
|
|/
|
|
| |
Change-Id: I2ec37478e2bef5b15b157e490f75d5dda5f97117
|
|\
| |
| |
| |
| |
| |
| | |
removing users" into lmp-dev
* commit '7caa51e6ec6443d5c1fdb96f7e42508b074b4278':
Fix issue #17811029: Settings provider race when removing users
|
| |
| |
| |
| | |
Change-Id: Ia40d0a9c161b765d1340db5390d0acdbfc050b81
|
|\ \
| |/
| |
| |
| |
| |
| | |
redirecting to user 0." into lmp-dev
* commit '3de09018a9611b1791cc29ed5200b7d9694189a9':
SettingsProvider should use correct cache when redirecting to user 0.
|
| |\
| | |
| | |
| | | |
0." into lmp-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
SettingsProvider reads secure and system settings for managed
profiles from user 0 instead. However it still checks the cache
for the managed profile not user 0.
Bug: 17736586
Change-Id: I15d44b8a5779b01e6b9032e528dc34f5c5602449
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
Window Manager" into lmp-dev
* commit 'c338784bf6bfcce3cd7db40f46b0e6c815e9ed3a':
More work on issue #17656716: Unhandled exception in Window Manager
|
| |\ \
| | | |
| | | |
| | | | |
into lmp-dev
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix Slog.wtf to not acquire the activity manager lock in its code
path, so that it can never deadlock. This was the original intention
of it, but part was missed.
Now we can put back in the code to detect when strict mode data is
getting large (a little more targeted now to the actual problem),
and use Slog.wtf to report it. And as a bonus, when this happens
we will now clear all of the collected violations, to avoid getting
in to the bad case where IPCs start failing. So this should be
good enough for L to fix the problem, with wtf reports for us to
see if the underlying issue is still happening.
Finally, switch a butch of stuff in the system process from Log.wtf
to Slog.wtf, since many of those are deadlocks waiting to happen.
Oh and fix a crash in the settings provider I noticed in APR.
Change-Id: I307d51b7a4db238fd1e5fe2f3f9bf1b9c6f1c041
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit '4d82c46ef5df06e1b92f3574e41b38a62ec0e607':
Implement auto-sleep functionality.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added a new SLEEP_TIMEOUT setting which governs how long the device will
remain awake or dreaming without user activity. By default this
value is set to -1 which maintains today's existing behavior.
We basically represent the time we are allowed to be dreaming as a new
kind of user activity summary state called DREAM, similar to BRIGHT
and DIM. When the sleep timeout expires, the state is cleared and
the dream ends.
Bug: 17665809
Change-Id: I59aa7648dcec215f1285464fc1134934a09230e5
|
|\ \
| |/
| |
| |
| |
| |
| | |
lmp-dev
* commit 'eb5fb0236f3ed0c8068d5e65f2396047ae69f78b':
Return masked location mode for managed profiles
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If there's a user restriction on location sharing in a
managed profile, always return empty string for location
providers so that location can be disabled by the admin
even if the primary user has location enabled.
Also fix an incorrect update of the cache. Shouldn't update
the primary user's cache when the caller is the managed profile.
Bug: 17478855
Change-Id: Icab3459ae351c5cfc287e21df6a5ba1df9dfbdb4
|
| |
| |
| |
| |
| | |
Change-Id: If5c2ca9461d0d7846374fda66e3d091dfa8f05e7
Auto-generated-cl: translation import
|
| |
| |
| |
| |
| | |
Change-Id: I4e30e9bfaa1032d9e2cd8ca170945b4c4f16d597
Auto-generated-cl: translation import
|
|\ \
| |/
| |
| |
| |
| |
| | |
into lmp-dev
* commit 'c9a016dd4eefd01ab6acc916d2a1bad854933e58':
Always give wifi a chance to quiet down during restore
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Not just when the current scan-always setting is on.
Bug 17571997
Change-Id: Idc56c9682c18f5e23c0bde98736522a79583af5e
|
| |/
| |
| |
| |
| | |
Change-Id: Iea95517012e1ac1c31a11f63c34f9f431118d2f3
Auto-generated-cl: translation import
|
| |
| |
| |
| |
| | |
Change-Id: I52d4c3489b8135587f47a3020a77fdd6c9f7fde4
Auto-generated-cl: translation import
|
|/
|
|
|
| |
Change-Id: Ia765d51a6deaec56fac570e3f887bdf298825744
Auto-generated-cl: translation import
|
|
|
|
|
| |
Bug: 17490408
Change-Id: If1cc25a341eed4e41a7bf170bab077203fa19d15
|
|\ |
|
| |
| |
| |
| |
| |
| | |
b/17428259 | Change device name to default to model name
Change-Id: If9f0a30f2362574d32fc69c0880c01ec7a3edb9f
|
|/
|
|
|
|
|
|
|
| |
Cloning of settings to managed profiles could fail due to security restrictions. This caused
Settings app crash. Instead the exception is now caught inside SettingsProvider, logged,
and we leave the app running.
Bug:17450158
Change-Id: I7525d634e57701db304117f4b2035faf53977836
|
|
|
|
|
|
|
|
|
| |
When users upgrade to L, don't restore into a state that would force
zen mode to follow suit. A user's first encounter with zen mode
should be via the UI.
Bug:16826161
Change-Id: I4eb63dce37d88f3a91b5034b3393eed2b768562c
|
|
|
|
|
|
|
|
|
|
| |
1. Removed setting from Settings.System class.
2. Added settings database migration step to change "SIP_ASK_ME_EACH_TIME"
to "SIP_ADDRESS_ONLY" as the "ask me each time" option no longer makes
sense given the new phone accounts settings.
Bug: 17321422
Change-Id: I3df1be4fcda44f2097c49af44508ac1fce72a24b
|
|\
| |
| |
| | |
lmp-dev
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add a notification for those users that teaches them how to re-enable
the notifications.
Bug: 15934899
Depends-On: Ie0bcc207c4f331def207e588bbad36b8986fe114
Change-Id: I4a169e268042cfcaa4ad80cdf205904f9c90e76d
|
|/
|
|
|
|
|
|
|
|
| |
1. Persist microphone mute state.
2. Set mute state for correct user.
3. Check for settings restrictions as the correct user.
Bug: 17177502
Bug: 16701642
Change-Id: Id8b6cd90c5caceb67fbec862f90aac7ec7a00b3c
|
|
|
|
|
|
|
|
| |
There is only one instance of the Settings ContentProvider, running in the user 0.
So it should be marked as singleUser.
BUG: 17133716
Change-Id: I426667ddbc8e682e7ea81f04633c0ad4f42782cb
|
|
|
|
|
|
|
|
|
| |
Reset the auto-brightness setting to default since the behavior
of the feature is now quite different and is being presented to
the user in a new way as "adaptive brightness".
Bug: 17114082
Change-Id: Ica63f4caaaf50ad95dc9df88bb376f79782976f7
|
|
|
|
|
| |
Bug: 16840500
Change-Id: I73fbe5c2cff665ccb637abb9039d57f377d9df53
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All reads of those specific settings will go to the primary user.
Inserts to primary also go to managed profiles in order to notify
any observers.
This enables Location settings to be shared by both profiles.
Also some other settings related to IME and Accessibility since
those services are shared across the profiles.
Bug: 16457210
Change-Id: Ib8fd697b5c78027fcbaf245d82dda5e6d6aab4f0
|
|
|
|
|
| |
Bug: 15331132
Change-Id: Ia80ccb2cfdf60116bd50601e60ff131619eafcc5
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also, note that this method never worked. Locale
settings were stored with underscores (like Locale.toString)
but matched against AssetManager.getLocales() which
returned language-tag like output.
bug: 10090157
(cherry picked from commit fd138cd81a689ff46e6ae90e46adcdc53f3c5442)
Change-Id: Ifc81ac902c297387dba8c40aba0656e18af57c86
|
|
|
|
| |
Change-Id: Iac5489639edae2373ed0ce92f7d0fe22629a249a
|