summaryrefslogtreecommitdiffstats
path: root/packages/SettingsProvider
Commit message (Collapse)AuthorAgeFilesLines
* LockscreenPattern : Toggle dots/error pattern visibility (1/2)Danesh M2013-03-011-0/+2
| | | | | | | | | | | Give user ability to hide error pattern / dots. Part 2 : http://review.cyanogenmod.org/#/c/33004/ Patchset 2 : Minor formatting Patchset 3 : Cleanup commit msg Change-Id: I2af7403b0f72c72e13dd1dec73f8d335ff4029bf
* Feature : Volume adjust sound preference 1/2StevenHarperUK2013-02-181-1/+0
| | | | | | | | | | | | | | This patch allows the users to choose if they want the audible tone when adjusting the volume The new preference is in Settings | Sound Volume adjust sound Play sound when adjusting volume with hard keys The Checkbox is defaulted to ON (1 in defaults.xml) Look for 2/2 for the Settings, Sound Panel Change Change-Id: I705c23065706317760ba60efc1a71f3ba6082bbd
* Merge commit 'android-4.2.2_r1' into mr1.1-stagingRicardo Cerqueira2013-02-153-4/+38
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: core/java/android/os/Trace.java core/java/android/widget/Toast.java core/res/res/values-cs/strings.xml core/res/res/values-el/strings.xml core/res/res/values-iw/strings.xml core/res/res/values/config.xml core/res/res/values/symbols.xml media/java/android/media/AudioService.java packages/SystemUI/res/values-sv/strings.xml packages/SystemUI/src/com/android/systemui/statusbar/phone/NotificationPanelView.java packages/SystemUI/src/com/android/systemui/statusbar/policy/BatteryController.java packages/SystemUI/src/com/android/systemui/usb/StorageNotification.java policy/src/com/android/internal/policy/impl/keyguard/KeyguardHostView.java policy/src/com/android/internal/policy/impl/keyguard/KeyguardMessageArea.java policy/src/com/android/internal/policy/impl/keyguard/KeyguardViewManager.java policy/src/com/android/internal/policy/impl/keyguard/KeyguardViewMediator.java services/java/com/android/server/NotificationManagerService.java services/java/com/android/server/power/ElectronBeam.java Change-Id: I60b8ddf20a1d7bcf9dc7b1a4ed841aaa4d953294
| * Don't update global table when upgrading secondary users' database.Amith Yamasani2012-12-121-11/+13
| | | | | | | | | | Bug: 7722149 Change-Id: I0c1373cba316b924701136579083274eb6c9b1da
| * Play a tone when wireless charging begins.Jeff Brown2012-12-112-1/+22
| | | | | | | | | | | | | | | | | | | | | | 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
| * Cleaner initial boot.Dianne Hackborn2012-11-281-1/+12
| | | | | | | | | | | | | | This does some cleanup of the initial boot, especially when booting in "no core apps" mode for encryption/decryption. Change-Id: Ifb3949f580e52f54559e603c4b0b104f6bac2f6c
| * Quiet down a lot of logging.Dianne Hackborn2012-11-271-2/+2
| | | | | | | | | | | | | | Also fix a little problem where the USER_STARTED broadcasts were not being sent as ordered broadcasts(!). Change-Id: I3aa3e0a9b3900967cdd2d115ee103371b0a50c41
* | Czech: fixed translation, added new stringsOndrej Zima2013-01-241-1/+1
| | | | | | | | | | | | | | | | patch #2 - fixed typos patch #3 - some fixes and translated unintentionally untranslated strings Change-Id: I288bf43a027286c4c08f2a7761fc2bc19b77f04c
* | Allow setting a per-device default configuration for STATUS_BAR_BATTERYRicardo Cerqueira2013-01-162-0/+6
| | | | | | | | | | | | | | Batteryless devices (like TV-connected mediacenters/STBs) don't need the battery icon there at all. Change-Id: Iac7e1b0b813c260bc78f4733409a30da7bda248d
* | Framwork: Add support for variable size pattern lockscreen (Part 1/2)Rowan Decker2012-12-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Part 2: http://review.cyanogenmod.org/#/c/28534/2 Forward port of: http://review.cyanogenmod.org/#/c/20613/ The default size has been replaced with a constant PATTERN_SIZE_DEFAULT=3 It now parses the longInt as a byte, no longer requiring a get/set Int function. Negative numbers and sizes over 127 do not make sense, so a byte works well. In addition the logging has been removed. Patch Set 1-2: Initial port Patch Set 3-5: New implementation using seperate file for non standard sizes Patch Set 6: Use AOSP code style Patch Set 7-9: Remove static code Patch Set 10: Correct a comment Change-Id: Ia06fc5a7dc2819f78843fddcf1470d85ebe2ad13
* | Do not set the network mode differently for LTE+CDMANaveen Kalla2012-11-271-4/+0
| | | | | | | | | | | | | | | | | | | | | | 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 Conflicts: packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java
* | implement noise suppression for phone calls (1/2)Daniel Hillenbrand2012-11-241-0/+3
| | | | | | | | Change-Id: If51532bd8220fab8722bbb594f70515f9d74b49b
* | Squashed commit of the theme engine support.Ricardo Cerqueira2012-11-241-5/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | | | Updated 4.2 support for the old T-Mobile theme engine, as usual needs the provider and switcher apps installed as well. I'm finally dropping the 400+ commit history on this, since everybody else keeps picking it up from CM as a single patch anyway... But for the record, nothing of this would be possible without Josh, Ed, and the rest of the TMo guys who wrote and maintained it until 2.2: amit chabra <amit.chabra@t-mobile.com> Amit Kohli <amit.kohli@t-mobile.com> Chris Cogar <chriscogar@t-mobile.com> Dirk Sigurdson <dirk.sigurdson@t-mobile.com> Ed Carrigan <edward.carrigan@t-mobile.com> Gaurav Sharma <gaurav.sharma3@t-mobile.com> Hui Feng <hui.feng@t-mobile.com> John Ritz <john.ritz1@t-mobile.com> Josh Guilfoyle <josh.guilfoyle@t-mobile.com> Mark Roberts <mark.roberts48@t-mobile.com> Pankaj Kumar <Pankaj.kumar6@t-mobile.com> Samuel Cheung <samuel.cheung@t-mobile.com> Sergey Ten <sergey.ten6@t-mobile.com> Change-Id: I7148d51be48f28a2dc4bdf9ec9018f04b268ffc4
* Import translations. DO NOT MERGEBaligh Uddin2012-10-2248-1104/+0
| | | | | Change-Id: I51415c91026c1ea461f1b1239a75ec999fd7fe0c Auto-generated-cl: translation import
* Frameworks base: Promote dream setting defaults to config.John Spurlock2012-10-192-21/+11
| | | | | | | | | So that: - the values can be shared (to fix assoc bug) - the values can be customized in product overlays Bug:7373284 Change-Id: I37f037082523a3d975f6014f36afa28c60117372
* Defer wifi bounce following restore for 1 minute...Christopher Tate2012-10-091-41/+80
| | | | | | | | ...to allow network-reliant restore actions by apps to get underway. Bug 7304761 Change-Id: Ia1d2321ef86609588efbc7add043c24a12ec6a20
* Add an upgrade step for settings moved to global.Amith Yamasani2012-10-081-18/+37
| | | | | | | | | | | | 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
* Merge "Fix settings restore" into jb-mr1-devChristopher Tate2012-10-051-2/+4
|\
| * Fix settings restoreChristopher Tate2012-10-051-2/+4
| | | | | | | | | | | | | | | | Now with more fix. Bug 7249405 Change-Id: Ib8bc2e9c5b054054f4aaacf14af8d5a0d05d6e3a
* | Merge "Make sure settings writes are permission checked correctly" into ↵Christopher Tate2012-10-051-52/+45
|\ \ | |/ |/| | | jb-mr1-dev
| * Make sure settings writes are permission checked correctlyChristopher Tate2012-10-051-52/+45
| | | | | | | | | | | | | | | | | | | | | | | | The last bit of undoing the earlier tangle around query results having observers under the calling user's identity. We do *not* want to drop calling identity in the call() processing; we want the table-based permission checks at the point of the underlying db operations to be performed against that identity. Bug 7265610 Change-Id: Ie0c9331ebd0918262a0a32b5b03b876fc2a92ca3
* | Fix upgrade case for Settings.Secure.USER_SETUP_COMPLETE.John Spurlock2012-10-052-1/+31
| | | | | | | | | | | | | | | | | | Existing primary users were never being marked as complete, causing things that relied on this (e.g. showing the quick settings panel) to break. Bug:7282088 Change-Id: I9c8622f3cd0fb99a44477946d3db22fa2cbbc6fc
* | Settings (and general) restore fixesChristopher Tate2012-10-041-2/+8
|/ | | | | | | | | | | | | | | | | | Pro tem, we ignore wifi configuration data when restoring system settings. This is not ideal, but it *does* mean we do not bounce wifi off and on again during the extended restore process, which in turn means we don't interfere with things like the Play Store's download of applications. We do continue to back up wifi configuration, and will start using that data again when the new implementation that restores AP configurations without having to bounce wifi comes to pass. Also, this CL fixes a longstanding bug in BackupDataInput.skipEntityData() that was being reproduced reliably once settings restore was skipping the wifi-related entities in the restore stream. Bug 7249405 Change-Id: I61520a9a116b66ebdf95734d09d9afd46406df01
* Make sure to check write perms after rewriting destination tableChristopher Tate2012-10-041-1/+3
| | | | | | | | | | | The write-permission check must occur after any destination-table rewriting, otherwise any application would be able to write to any global setting, by supplying a fraudulent "system" namespace in the uri, but with a key name that will be redirected to global. Bug 7289965 Change-Id: I122098a64e40d14e00d3cb6608c50aeb74faf7ce
* Merge "Rewrite raw insert()s and some raw query()s of moved-to-global keys" ↵Christopher Tate2012-10-031-1/+22
|\ | | | | | | into jb-mr1-dev
| * Rewrite raw insert()s and some raw query()s of moved-to-global keysChristopher Tate2012-10-031-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Settings put*() APIs fix up references via the old namespaces, but the raw insert() interface didn't. Now it does. Also, when possible we fix up direct query() operations on the old namespace to point to the correct one. At present that is only done for query() operations with Uris of the form content://secure/adb_enabled There is no rewriting done on queries of the form content://secure WHERE name='adb_enabled' since the app-supplied WHERE clause can be arbitrarily complex. Bug 7267568 Change-Id: I5c8cecbea7f5b1da6247a53b1428d3effb0bbca5
* | Merge "Use myUserId() only in registerContentObserver()" into jb-mr1-devChristopher Tate2012-10-031-1/+11
|\ \
| * | Use myUserId() only in registerContentObserver()Christopher Tate2012-10-031-1/+11
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The reason for this is a bit subtle: we want to guarantee that when a content observer is registered using the public API, it is *always* bound to the host user's view of the data behind the observed Uri, never the calling user's. Now, the reason it was the calling user in the first place is that the Settings provider (and potentially any singleton provider) needs the observers underlying Cursors returned from query() to be tied to the caller's user, not the provider's host user. In order to accomplish that now that the public-facing behavior is always tied to the host user, the concrete class that implements the Cursor type handled by the Settings provider has been extended with a new hidden API for setting a notification observer tied to an arbitrary user; and then the provider explicitly downcasts the query result's Cursor to that class in order to register the notification observer. We can do this safely because this is platform code; if we change the way that these underlying cursors are constructed, we can just fix this point of call to follow along. If they get out of sync in the future, the Settings provider will scream bloody murder in the log and throw a crashing exception. Bug 7231549 Change-Id: I0aaceebb8b4108c56f8b9964ca7f9e698ddd91c8
* | fix settings data base upgrade for ringer modeEric Laurent2012-10-031-4/+20
|/ | | | | | | | | Ringer mode setting was moved from System to Global group but a db upgrade cleanup step was missing. Bug 7128886. Change-Id: Id20994fe74575afa2b68154a620aa3c8807e8304
* Make settings backup/restore work in the new multi-user worldChristopher Tate2012-10-022-175/+77
| | | | | | | | | | | | | | 1) Properly handle restores of settings elements that have been migrated to the new global namespace 1) Back up and restore the new global settings namespace 3) Make sure to back up / restore the global entity ENABLE_ACCESSIBILITY_GLOBAL_GESTURE_ENABLED Bug 7249405 Change-Id: Ibfa9930ea4d0e16c7635697e8c631b155e4c0cb2
* Migrate more System and Secure settings to Global.Jeff Sharkey2012-10-022-20/+67
| | | | | | | | Includes telephony, WindowManager, PackageManager, and debugging settings. Update API to point towards moved values. Bug: 7231764, 7231252, 7231156 Change-Id: I5828747205708872f19f83a5bc821ed0a801cb79
* Attempt to fix missing lock soundsJim Miller2012-10-011-4/+6
| | | | | | bug 7254629 Change-Id: I65eee674fe014a0e84d5ec20ead81abdec38f890
* Move bluetooth priorities from Secure to Global.Jeff Sharkey2012-10-011-1/+59
| | | | | Bug: 7231171 Change-Id: I836fdc2cfb8d67f984b4715559b9e92d0dc41c95
* Migrate more Secure settings to Global.Jeff Sharkey2012-09-272-25/+102
| | | | | | | | Migrate networking, storage, battery, DropBox, and PackageManager related Secure settings to Global table. Bug: 7232014, 7231331, 7231198 Change-Id: I772c2a9586a2f708c9db95622477f235064b8f4d
* First step towards cleaning up Global settings.Jeff Sharkey2012-09-262-96/+96
| | | | | | | Remove all @Deprecated @hide settings, and clean up any stragglers. Bug: 7232125 Change-Id: Ibf67093c728d4a28565129b923edb1701d3b2789
* Merge into jb-mr1-devJean-Baptiste Queru2012-09-251-1/+2
|\ | | | | | | Change-Id: Idf183be6a41ff37add5141a20e96d5190396d1a4
| * fix argument parser for global settings URLsDoug Zongker2012-09-241-1/+2
| | | | | | | | | | | | | | | | Make content://settings/global/setting_name URLs work like system and secure URLs. Bug: 7212535 Change-Id: I33e388a0cc80309453714eab726ce45b3f8fef73
* | Fix issue #7215984: java.lang.RuntimeException: Unable to create...Dianne Hackborn2012-09-241-7/+2
|/ | | | | | | | | | | | | | | | | | | ...service com.android.systemui.SystemUIService: java.lang.NullPointerException - Don't acquire the activity manager lock in handleIncomingUser(), there is really no need to do so. - Rework the settings provider client side cache code to not hold locks while calling into the provider. I also changed the way the settings provider uses system properties so that there is one property for all users. We can't do one per user, since the system property name space is limited with a fixed size. And we don't really need to do that; the worse that happens by combining all users is that if one running user changes one of its settings, all other running users will think they need to reload settings when they go to fetch them next. Change-Id: I13b90b832310d117eb6d721aacd122cfba7d749a
* Multiuser awareness in content observer infrastructureChristopher Tate2012-09-201-51/+53
| | | | | | | | | | | | | | | | | | Content observers are registered under the calling user's identity, not under the provider host's identity (unless the caller is using the new permissioned entry points that allow observers to be registered for a different user's view of the data). The most important implication of this is that when the settings provider is directly queried, the Cursor returned to the app is wired for change notifications based on that calling app's user. Note that it is not possible to use query() / insert() to read/write data for different users. All such manipulations should use the standard get* / put* methods in Settings.*. Bug 7122169 Change-Id: If5d9ec44927e5e56e4e7635438f4ef48a5430986
* Add support for remembering Wifi display devices.Jeff Brown2012-09-192-0/+4
| | | | | | | | | | | | | | Add a setting to globally disable Wifi display. Fixed a bug where the wifi display broadcast receiver was running on the wrong thread. Removed the wifi-display QuickSettings dialog, all functionality has been moved to Settings. Bug: 7178216 Bug: 7192799 Change-Id: I9796baac8245d664cf28fa147b9ed978d81d8ab9
* Settings provider needs to send notifications as itselfChristopher Tate2012-09-181-1/+6
| | | | | | | ... and not as its ultimate caller, who may be a less-privileged application. Fixes bug 7188309 Change-Id: Iffd37b8da84f683bf665bf3d48c0b7fbc8dd721d
* Per-user content observer APIsChristopher Tate2012-09-171-3/+5
| | | | | | | | | | | | | | | | | | | | Callers with INTERACT_ACROSS_USERS_FULL permission can now observe content for a given user's view (and can notify content uri changes targeted to a specific user). An observer watching for UserHandle.USER_ALL will see all notifications for the given uri across all users; similarly, a notifier who specifies USER_ALL will broadcast the change to all observers across all users. The API handles both USER_ALL or USER_CURRENT, and explicitly forbids any other "pseudouser" designations. This CL also revs the Settings provider to notify with USER_ALL for changes to global settings, and with only the affected user's handle for all other changes. Bug 7122169 Change-Id: I94248b11aa91d1beb0a36432e82fe5725bb1264f
* Fix default population of wifi settingsChristopher Tate2012-09-141-8/+9
| | | | | | | | | | | | | | | | | Various wifi settings that are explicitly defaulted did not get their default code properly converted to refer to the correct settings database table. A collection of moved-to-Global settings that had not yet been marked @deprecated in the Secure.* namespace are now so marked. Also updated the namespace used to refer to wifi settings from the Wifi Service. These changes are cosmetic, but they do eliminate a number of runtime log messages. Bug 7153671 Change-Id: I9e5b6464d025cfb480ef97373996e38e82f90593
* Merge "Fix Settings writes to a different user" into jb-mr1-devChristopher Tate2012-09-141-74/+70
|\
| * Fix Settings writes to a different userChristopher Tate2012-09-131-74/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Oops. Stacked bugs: first, the desired user handle was not properly being passed from the call() entry point to the database operations; then on top of that, the client-side cache management was still looking in the local user's cache for the data, so a request to read a different user's settings would return the local user's instead if that key was already known to the local user's cache. Reads and writes of a different user's settings are now uncached, so they're relatively much slower. They're rare, however, so this is not something to worry about unless we encounter a real world case where it's a significant factor. This CL also adds a bit of cross-user settings read/write testing to the existing provider suite. These new tests caught both the known wrong-user-write bug and discovered the client-side cache bug, so yay. Finally, the existing wholesale mutual-exclusion approach would deadlock in certain circumstances due to the fact that the settings database creation code might have to call out to the Package Manager while populating the bookmark/shortcut table, and the Package Manager would then call back into the settings provider in the course of handling that request. The synchronization regime has been significantly tightened up now: now the database code [which is known to deal with concurrency itself] is allowed to cope with multiple parallel openers of the same db; this allows the settings provider to avoid calling out to other parts of the system even implicitly while its internal lock is held. Change-Id: Ib77d445b4a2ec658cc5c210830f6977c981f87ed
* | Settings db upgrade steps only apply to the owner userChristopher Tate2012-09-131-63/+74
|/ | | | Change-Id: Ib74b42bcc2554edf721199f31f563daa9fc227a2
* Merge "Core accessibility settings should not be cleared on restore." into ↵Svetoslav Ganov2012-09-121-11/+21
|\ | | | | | | jb-mr1-dev
| * Core accessibility settings should not be cleared on restore.Svetoslav Ganov2012-09-121-11/+21
| | | | | | | | | | | | | | | | | | | | | | | | 1. The core accessibility settings required for a blind user to use the device should not be overwritten on restore. There could have been enabled via a global gesture from setup wizard, hence the user definitely needs them. Restoring disabled values for these settings render the device useless unless sighted help is sought. bug:7138401 Change-Id: Idc593889aa61fada65b0407623720517c827df53
* | Moved a few telephony settings from Secure to GlobalChristopher Tate2012-09-122-1/+24
|/ | | | | | | Also tidy up the bookkeeping for a few settings that were earlier moved to Global without the redirect tables being fixed up. Change-Id: I69275db3b2636cd6ba9c8c51b88e97d8ba4b7b7d
* Set up default (random) Android IDs for all usersChristopher Tate2012-09-111-18/+29
| | | | | | | | | | | Also correct some now-misleading terminology in a permission-check log message, and fix a bug in which a system component trying to write to a secondary user's settings would wind up writing the owner's settings instead. Bug 7132405 Change-Id: I5b8fafc35720390a01652e386ab5b7c0ad751abe
generated by cgit v1.1 at 2025-02-10 04:52:58 +0000