7ab4b7fd500c3c21b0329faa29e74eac4ef638af |
|
27-Jul-2015 |
Martijn Coenen <maco@google.com> |
Resource for setting default NFC payment component. Bug: 22756856 Change-Id: If97e0faead995fb95893a128c1890b61bbe86ce5
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
27bbb2d0a1c8a3bb38768511ac840c3388b0fb03 |
|
31-Mar-2015 |
Jason Monk <jmonk@google.com> |
Add control for double tap to wake setting Bug: 16875464 Change-Id: Ic1ad910dd38acbc68ef040b2acdf3696ec2c2e4e
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
584a44517950204a04ef01345be70b33d8ba43f9 |
|
22-Oct-2014 |
Bryce Lee <brycelee@google.com> |
[Theater Mode] framework implementation through global setting Bug: 17684570 Change-Id: I64a9c9c0620049cdfcca0150648fa201281f7178
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
05af6adb8d4fd5ea069c9aead5a877da9085daa8 |
|
01-Oct-2014 |
Jeff Brown <jeffbrown@google.com> |
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
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ad59c43072a3e053eecb2cca831488dc49a3af33 |
|
13-Sep-2014 |
Jeff Sharkey <jsharkey@android.com> |
Fix boot loop when deriving device name. Bug: 17490408 Change-Id: If1cc25a341eed4e41a7bf170bab077203fa19d15
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
550021ec5a2c8d741506c3fe5d1ee85139bc794a |
|
11-Sep-2014 |
Jerome Poichet <jpoichet@google.com> |
Update default device name to MODEL only b/17428259 | Change device name to default to model name Change-Id: If9f0a30f2362574d32fc69c0880c01ec7a3edb9f
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
cd8f4f71fc75b4f57d21c4e9f80f1107101ca369 |
|
28-Aug-2014 |
Chris Wren <cwren@android.com> |
Disable lockscreen notifications for secure users on upgrade. Add a notification for those users that teaches them how to re-enable the notifications. Bug: 15934899 Depends-On: Ie0bcc207c4f331def207e588bbad36b8986fe114 Change-Id: I4a169e268042cfcaa4ad80cdf205904f9c90e76d
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
49e057d7eedb44f5397781254acab4e0ef08a9cf |
|
13-Aug-2014 |
Adrian Roos <roosa@google.com> |
Play "device trusted" sound when onTrustInitiatedByUser fires Bug: 16840500 Change-Id: I73fbe5c2cff665ccb637abb9039d57f377d9df53
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
52e5701eea2da526191e997f9df5c41ef1e1c938 |
|
23-Jul-2014 |
Dan Sandler <dsandler@android.com> |
Move LOCK_SCREEN_SHOW_NOTIFICATIONS to per-user Settings.Secure. Bug: 15331132 Change-Id: Ia80ccb2cfdf60116bd50601e60ff131619eafcc5
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1e9c21871e81642669079cd290ef47818a3165bd |
|
12-Jun-2014 |
Amith Yamasani <yamasani@google.com> |
Guest user first iteration Setting for controlling if guest is enabled on the device. Setting to hint to apps that they should skip showing first use clings. User switcher handles creation and deletion of the guest user. Some tweaks to the user switcher to show some feedback and make the icons circular. Change-Id: I187dc381d2ee7c372ec6d35e14aa9ea4dfbe5936
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
a20dda4a6eedeee1dcaf105d76c8d7d126ce0f1b |
|
28-May-2014 |
Jeff Brown <jeffbrown@google.com> |
Add support for wake gestures. Bug: 15137158 Change-Id: I171c3269a7a16a00083e16e1cc4c7c1c2b98c05e
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
147b4d75e1d4ca795d45ffe51d83efd19a754cf2 |
|
13-May-2014 |
Jerome Poichet <jpoichet@google.com> |
Adding device name A new global settings to name a device. This will centralize the notion of device name/nickname and should be used by Cast, Bluetooth, TV Remote and other advertising applications/services. Change-Id: I2294deb5c0d1002fb2fc158f62a2d5643d90d749
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1cdd7dda61b30358c843e534394c32f24bc5271f |
|
28-Feb-2014 |
Chris Wren <cwren@android.com> |
enable heads up notifications Bug: 13208692 Change-Id: I3682ecb30c6997c578b76a578b79a8d13a6e6323
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
82a6c5c5ff04ab26fde4b3094a8f25da95a0f5f4 |
|
20-Feb-2014 |
Dan Sandler <dsandler@android.com> |
Default Settings.Global.LOCK_SCREEN_SHOW_NOTIFICATIONS=1. Change-Id: I849d4def1dcf220c226349f1591a8ba00b603854
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
91beb94c65716f78a120cff93e3bb78a190500b4 |
|
23-Jan-2014 |
Christopher Tate <ctate@google.com> |
resolved conflicts for merge of a5bb65aa to master Change-Id: Ib286d5194f68c55cfd2e5c17a5eb89ea32add574
|
2c4254e4765b4fa675c268550e66a3d4341282bc |
|
11-Dec-2013 |
Oskar Grönqvist <oskar.gronqvist@sonymobile.com> |
Set Settings.Global.WIFI_SCAN_ALWAYS_AVAILABLE default value To be able to customize the "WiFi scan always available" setting we need to set a default value. Change-Id: I3673f2613ab9b6a947aed7e29d4cc876140c2180
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
c02c4a7c5b393c5527de17faca759ff00be61ce5 |
|
07-Jan-2014 |
Mike Lockwood <lockwood@google.com> |
SettingsProvider: Allow disabling immersive mode confirmation for specific packages Change-Id: I2fac06cbe3321d7384278d875c91128bcc15d629
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
dea6462aab31049d1f1055314491bc33a6f16b0d |
|
23-Sep-2013 |
Daniel Sandler <dsandler@android.com> |
Don't wake users up with low battery sounds. Battery sounds will always play when the screen is on, and then for Settings.Global.LOW_BATTERY_SOUND_TIMEOUT milliseconds after the screen goes off. After that, low battery alerts will be pushed out the airlock until the screen comes back on again. If battery sounds are suppressed via this mechanism you'll see a log line like: V/PowerUI ( 3161): screen off too long (5779ms, limit 5000ms): not waking up the user with low battery sound The default value of LOW_BATTERY_SOUND_TIMEOUT is a settings provider resource: R.integer.def_low_battery_sound_timeout. Bug: 10487557 Change-Id: Iddd42038aa630631dc8f1833f20fcc5a0c646681
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
c1b3d21306f9b48a385ca2d817820bafe9e450fc |
|
08-Jan-2013 |
Dianne Hackborn <hackbod@android.com> |
am 53d99836: am 26c00dec: am b2d3904b: Merge "Setting the default value for dock audio" * commit '53d998368c6c6107c6d18de945f4dfee482e6f91': Setting the default value for dock audio
|
26c00decb4c0352913396851c2b42a8705976614 |
|
07-Jan-2013 |
Dianne Hackborn <hackbod@android.com> |
am b2d3904b: Merge "Setting the default value for dock audio" * commit 'b2d3904b0d0f02b3eddef1d228724b99962cba56': Setting the default value for dock audio
|
729f6685f9dfb7a1813a89dbf2298024d9da3813 |
|
18-Dec-2012 |
Dmytro Dubovyk <dmytro.dubovyk@ti.com> |
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>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ace7404de8b9a5bd7566027a8a90d36d099a46f4 |
|
12-Dec-2012 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of d7337fb9 to master Change-Id: I51dedcc5ee521e62ad6101c0b09e4f881b8c4bf0
|
84e2756c0f3794c6efe5568a9d09101ba689fb39 |
|
07-Dec-2012 |
Jeff Brown <jeffbrown@google.com> |
Play a tone when wireless charging begins. 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
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
dcf03f39725deec68f644f6162fdfcc884dc9964 |
|
16-Nov-2012 |
Jianzheng Zhou <jianzheng.zhou@freescale.com> |
Refactor getPersistedNetworkPreference 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>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ed108f3d125b0a4cc465057e3514caf781cdea19 |
|
18-Oct-2012 |
John Spurlock <jspurlock@google.com> |
Frameworks base: Promote dream setting defaults to config. So that: - the values can be shared (to fix assoc bug) - the values can be customized in product overlays Bug:7373284 Change-Id: I37f037082523a3d975f6014f36afa28c60117372
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
7f1c248e80c747663396c6112bd637b0ee558dcb |
|
05-Oct-2012 |
John Spurlock <jspurlock@google.com> |
Fix upgrade case for Settings.Secure.USER_SETUP_COMPLETE. 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
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
89d5546d7fd3a3bb19820c42e8b4527013dd6545 |
|
19-Sep-2012 |
Jeff Brown <jeffbrown@google.com> |
Add support for remembering Wifi display devices. 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
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1cf70bbf96930662cab0e699d70b62865766ff52 |
|
06-Aug-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Screen magnification - feature - framework. This change is the initial check in of the screen magnification feature. This feature enables magnification of the screen via global gestures (assuming it has been enabled from settings) to allow a low vision user to efficiently use an Android device. Interaction model: 1. Triple tap toggles permanent screen magnification which is magnifying the area around the location of the triple tap. One can think of the location of the triple tap as the center of the magnified viewport. For example, a triple tap when not magnified would magnify the screen and leave it in a magnified state. A triple tapping when magnified would clear magnification and leave the screen in a not magnified state. 2. Triple tap and hold would magnify the screen if not magnified and enable viewport dragging mode until the finger goes up. One can think of this mode as a way to move the magnified viewport since the area around the moving finger will be magnified to fit the screen. For example, if the screen was not magnified and the user triple taps and holds the screen would magnify and the viewport will follow the user's finger. When the finger goes up the screen will clear zoom out. If the same user interaction is performed when the screen is magnified, the viewport movement will be the same but when the finger goes up the screen will stay magnified. In other words, the initial magnified state is sticky. 3. Pinching with any number of additional fingers when viewport dragging is enabled, i.e. the user triple tapped and holds, would adjust the magnification scale which will become the current default magnification scale. The next time the user magnifies the same magnification scale would be used. 4. When in a permanent magnified state the user can use two or more fingers to pan the viewport. Note that in this mode the content is panned as opposed to the viewport dragging mode in which the viewport is moved. 5. When in a permanent magnified state the user can use three or more fingers to change the magnification scale which will become the current default magnification scale. The next time the user magnifies the same magnification scale would be used. 6. The magnification scale will be persisted in settings and in the cloud. Note: Since two fingers are used to pan the content in a permanently magnified state no other two finger gestures in touch exploration or applications will work unless the uses zooms out to normal state where all gestures works as expected. This is an intentional tradeoff to allow efficient panning since in a permanently magnified state this would be the dominant action to be performed. Design: 1. The window manager exposes APIs for setting accessibility transformation which is a scale and offsets for X and Y axis. The window manager queries the window policy for which windows will not be magnified. For example, the IME windows and the navigation bar are not magnified including windows that are attached to them. 2. The accessibility features such a screen magnification and touch exploration are now impemented as a sequence of transformations on the event stream. The accessibility manager service may request each of these features or both. The behavior of the features is not changed based on the fact that another one is enabled. 3. The screen magnifier keeps a viewport of the content that is magnified which is surrounded by a glow in a magnified state. Interactions outside of the viewport are delegated directly to the application without interpretation. For example, a triple tap on the letter 'a' of the IME would type three letters instead of toggling magnified state. The viewport is updated on screen rotation and on window transitions. For example, when the IME pops up the viewport shrinks. 4. The glow around the viewport is implemented as a special type of window that does not take input focus, cannot be touched, is laid out in the screen coordiates with width and height matching these of the screen. When the magnified region changes the root view of the window draws the hightlight but the size of the window does not change - unless a rotation happens. All changes in the viewport size or showing or hiding it are animated. 5. The viewport is encapsulated in a class that knows how to show, hide, and resize the viewport - potentially animating that. This class uses the new animation framework for animations. 6. The magnification is handled by a magnification controller that keeps track of the current trnasformation to be applied to the screen content and the desired such. If these two are not the same it is responsibility of the magnification controller to reconcile them by potentially animating the transition from one to the other. 7. A dipslay content observer wathces for winodw transitions, screen rotations, and when a rectange on the screen has been reqeusted. This class is responsible for handling interesting state changes such as changing the viewport bounds on IME pop up or screen rotation, panning the content to make a requested rectangle visible on the screen, etc. 8. To implement viewport updates the window manger was updated with APIs to watch for window transitions and when a rectangle has been requested on the screen. These APIs are protected by a signature level permission. Also a parcelable and poolable window info class has been added with APIs for getting the window info given the window token. This enables getting some useful information about a window. There APIs are also signature protected. bug:6795382 Change-Id: Iec93da8bf6376beebbd4f5167ab7723dc7d9bd00
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
16e119e798cd1e6dd94114bc910b2c1fd92b88e5 |
|
06-Sep-2012 |
rich cannings <richc@google.com> |
Add secure setting for package verification Framework changes to store and read a secure setting for package verification. Default is on/true. This setting will be turned on/off via the Settings app. Bug: 7082362 Change-Id: I6f93d3136add8af0dbbdc664f0473c5f5b7e3fee
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
8de24dca68a34828277bf661d72110a3a3191165 |
|
05-Sep-2012 |
Dmitry Shmidt <dimitrysh@google.com> |
Restore original default Wifi sleep policy (always) BUG: b/7092819 Change-Id: I6ee6755fd04df2f0169f8602e60542c3591038f3 Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
4e724c842378e84b8744db657a8e8c8ae09fa264 |
|
29-Aug-2012 |
John Spurlock <jspurlock@google.com> |
Change default setting for dreams to 'when docked' Bug:7078718 Change-Id: I4ec74cc9562ab728d6f86938758ede74c241c63b
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
c88a80a1d7a35eaefb54d17b60e9d3a07b800e82 |
|
29-Aug-2012 |
Jean-Baptiste Queru <jbq@google.com> |
am 15e099cc: am 0e0942c7: Merge "Default WiFi sleep policy setting" * commit '15e099cc09589f963933f046d7267552ba3ffad8': Default WiFi sleep policy setting
|
7e07147ecec50549272b4ec2f4f364102d7f379c |
|
23-Aug-2010 |
Erik Ljungberg <erik.ljungberg@sonyericsson.com> |
Default WiFi sleep policy setting Creates a defult.xml setting for WiFi sleep policy. It is now possible, through device overlays, to change the default sleep policy to e.g. never in order to improve user experience of WiFi. Change-Id: Ie459b8e70fdbc7c605452fe0692d7bc26460e939
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1a868b7981ca5f52e893fdf9f8f538c9d5ce241d |
|
22-Aug-2012 |
John Spurlock <jspurlock@google.com> |
Add framework support for multiple dreams. Bug:7028665 Change-Id: I4fba6b8e39dc07af4490c621ac3bc7b3867371b2
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
fdb7c36a108e6a7887de6611b3f1541e3009f2d5 |
|
06-Aug-2012 |
Daniel Sandler <dsandler@android.com> |
Migrate Dreams default settings to DatabaseHelper. Also switch Dreams on for all charging devices by default. Change-Id: Iccbcc2906d55214320b2f467e88ba9cb188f4886
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
3ff50a0a8ae3293a206b775878d1f677b0451375 |
|
21-Jun-2012 |
alanv <alanv@google.com> |
Change hard-coded URL for accessibility script. The old version of the script is broken and is cached due to an error in our gstatic configuration. We had to change the name to avoid hitting the cached version on external proxies. Bug: 6702042 Change-Id: I0e5ee8b3a6ae8c7ba11f5760f2f99d4b5614ac97
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
79f5a0416fe76d5063b4d9995edd84a49b77995e |
|
13-Feb-2012 |
Mike Lockwood <lockwood@google.com> |
WifiStateTracker: add support for overriding DCHP max retry count in an overlay Bug: 5551068 Signed-off-by: Mike Lockwood <lockwood@google.com> Conflicts: packages/SettingsProvider/res/values/defaults.xml Change-Id: I6a6519316a87bd1af39ea9dc51e0d312011135ef
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
d3c5e1eca12f4ca618e3f671dc6fae48307ec895 |
|
06-Jan-2012 |
Mike Lockwood <lockwood@google.com> |
Allow disabling network stats support in a resource overlay Bug: 5771240 Signed-off-by: Mike Lockwood <lockwood@google.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
2395527c9bb1cdc3bcd3dfcbc8b72b90ed3e7080 |
|
21-Oct-2011 |
Mike Lockwood <lockwood@android.com> |
SettingsProvider: Allow overridding default value for Setttings.Secure.DEVICE_PROVISIONED Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
7bef73900b075fc0a9078d418964ca8e7210d565 |
|
20-Oct-2011 |
Mike Lockwood <lockwood@android.com> |
SettingsProvider: Add support for overriding lockscreen.disabled default value Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
4b797dd8c1d059510b12957acc3bd0b236308bb3 |
|
20-Oct-2011 |
Mike Lockwood <lockwood@android.com> |
Allow overriding default STAY_ON_WHILE_PLUGGED_IN setting value in an overlay Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
3ca5a74c17a27e44ce13b39bc2f63edaa88c3ef5 |
|
07-Dec-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Make the URL for the JavaScript based screen-reader used by WebView configurable. The URl from which to inject a screen-reader for WebView accessiblity support should be configurable because: 1) The accessibility engineering team should be able to point devices to a staging build of the screen-reader; 2) We would like to be able to change this URL via the Google services mechanism. bug:5718543 Change-Id: I3d4d343f1c93e0e0173f04b2912949fe8a3566b9
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
55f937abe1a4fedb86c2679c66f0b5220ec3780e |
|
05-Dec-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding a system preference whether to speak passwords in accessibility mode. By default we do not speak passwords if the user has no headset. However, many users find this too restrictive and would like a way to enable password announcement. While we cannot speak the passwords all the time ,to avoid leaking them, we expose a preference so each user can choose the option that best works for him/her. bug:5712607 Change-Id: I6eb0c40834abe5297f7dc74be02d180a5bef0174
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
994da2ad3242407fd822e6b35e3d302a3667d9c3 |
|
10-Nov-2011 |
Tom Taylor <tomtaylor@google.com> |
Revert "Add new secure setting for controlling Messaging notifications" This reverts commit 03da2f00aac04e6565a02cf5a9bf6bb1ec926930. Committer: Tom Taylor <tomtaylor@google.com> On branch revertsetting Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: api/current.txt modified: core/java/android/provider/Settings.java modified: core/java/android/provider/Telephony.java modified: packages/SettingsProvider/res/values/defaults.xml modified: packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java We've decided not to disable messaging notifications with a secure setting. Instead, all the work will be done within the messaging app itself. Change-Id: Icde6894e76da1007b6026c8ec7dc56e488453c06
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ea54b7608584bc0535c9e89417778c3e95b50975 |
|
08-Nov-2011 |
Robert Greenwalt <robdroid@android.com> |
Merge "Wimax : wimax framework related open source." into ics-mr1
|
148c7d0de720a92632aa6ed10a39bfc38b427239 |
|
13-Oct-2011 |
tk.mun <tk.mun@samsung.com> |
Wimax : wimax framework related open source. Integrate wimax network related changes into Android Framework. - In Connectivity service, start wimax service. - 4G icon display in StatusBarPolicy. - DHCP renew add. - Add radio for wiamx Change-Id: I2d9012247edfdf49d71ca7e1414afd0006f330ca Signed-off-by: tk.mun <tk.mun@samsung.com> bug:5237167
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
03da2f00aac04e6565a02cf5a9bf6bb1ec926930 |
|
07-Nov-2011 |
Tom Taylor <tomtaylor@google.com> |
Add new secure setting for controlling Messaging notifications Bug 5552615 We're adding a new intent to allow 3rd party apps to disable the Messaging app's notification. We want any app to be able to query the setting of whether sms notifications are on or off, but only allow system apps, particularly the Messaging app, to change that setting. Other apps can change the setting by firing off an intent which brings up a dialog activity in the Messaging app that'll let them turn off Messaging notifications. Change-Id: I4d2721191b86010efb383a24c28d911496440657
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
8d32a01bd24b8a0d1a98f0581b3394a78fab8242 |
|
09-Aug-2011 |
Nick Pelly <npelly@google.com> |
Add NFC to airplane mode NFC now observes airplanes mode, and is by default toggleable in airplane mode. Change-Id: I5f19d35422c9eb1cffb0b5e0631b3f3c5eeaedcf
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
42722bfa136f5616872a2c4e199813e804621c81 |
|
22-Jul-2011 |
Amith Yamasani <yamasani@google.com> |
Volume panel changes. Combined volume panel only in tablets. On phones show active volume. Added dummy assets for ring+notification icon. Deprecated the NOTIFICATION_USES_RING_VOLUME. Now they are always tied together. Audio manager changes still required to ensure that. Initialize all feedback sounds to true. Change-Id: I3ad7890c9be9334eedb5f3b709a4b6995fe24638
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
a28a16d1c2b58999d757a4cd3bc66a2f3499a2eb |
|
28-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updating the data base upgrade/creation code for the new touch exploraion setting. 1. Update the database creation/upgrade code to take care of the new setting to enable touch exploration. 2. Made the tocuh exploration settings persistent to the cloud. Change-Id: Ie24e9184b4a21869432d11d207cb6464fadbac3b
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1324f22d8dc1a26fe481fd33511bdae04c81ac14 |
|
13-Jun-2011 |
Mike Lockwood <lockwood@android.com> |
Settings: Remove unused USE_PTP_INTERFACE setting Change-Id: I743b81379053caece38c19c59bc76d6cda763d45 Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1a84fd1fb7a51f3fe4f8865e1cdd09f3490f696c |
|
02-Jun-2011 |
Jeff Brown <jeffbrown@android.com> |
Add a preference panel for mouse speed. Bug: 4124987 Change-Id: I3ce175d268a1d043cf5878481261b1049a15a149
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
54d068ec6af0ee6d261a135400efe6816c6f5ffe |
|
02-Mar-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Add system wide management of core settings bug:3505060 Since we want to have some settings that are used very frequently by many applications (long-press timeout is one example) these should be managed efficiently to reduce lookups from different processes because in the case of a cache miss a disk I/O is performed. Now the system manages such core settings and propagates them to the application processes. Change-Id: Ie793211baf8770f2181ac8ba9d7c2609dfaa32a7
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
d99d0dc43a3c26c77dd22e405efbdf0753d8309e |
|
01-Feb-2011 |
Paul Westbrook <pwestbro@google.com> |
Enable retrieving default download manager settings Enable retrieving the default download manager settings from a resource, when the SettingsProvider database is created The default setting for these values is -1, which will cause DownloadManger to not enforce a limit. Bug: 3341145 Change-Id: I25294d0f75fb0bdf20d4bef54457056c25c31add
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
43dee06479d96d51e895704a9ee480232224c761 |
|
20-Jan-2011 |
Amith Yamasani <yamasani@google.com> |
Set the default state of NOTIFICATIONS_USE_RING_VOLUME. Bug: 3365600 This doesn't affect upgrades, only new installs. Don't backup/restore NOTIFICATIONS_USE_RING_VOLUME anymore as it doesn't work well across device types and can wedge the device into a state where you can never hear notification sounds. Change-Id: I703e1db539eb4ac45b273f46ada0b4bbf3b981bb
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
bfc3ce78f4b9b4a720e48b3cc276e81a3fa8cfb2 |
|
13-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updating the WebView accessibility key bindings after discussion with the access-eng team Change-Id: I39a303864b94a8a11b6cded9b8bb23041ad91502
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
b01c3d2bf2d81d30b6b0b1f8012a2bcbbad5acd2 |
|
11-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
WebView accessibility key bindings do not allow mapping of all meta keys. Exception when turning off acessibility and having a WebView showing content. bug:3341772 1. Now a key in the binding is represented as a long with 32 MSB for modifiers and 32 LSB for keyCode. bug: 3340732 1. Added check in the WebView key handling code to diable the accessibility injector/injected script in case accessibility is been disabled after loading the content. Change-Id: Ic3746dff16ec77ba682a5b139cec0e6afd8fc839
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
c93fb656dc9393f194c623dc897c5352d9192544 |
|
06-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
bug:3325039 Making the cursor ring movement send accessibility events. 1. Added a mechanism to select the cursor ring content if accessibility is enabled - This is achieved by sending an event to the WebCore thread (if accessibility is enabled) to select the content of the cursor when the latter moves. Added code in WebViewCore to select the given node and notify the UI thread for the selection markup which is delivered of the accessibility injector which manages sending accessibility events. This is relevant for adding accessibility to WebView if JavaScript is not enabled. (If JS is enabled we inject a screenreader written in JS). 2. Fixed the event delegation to the accessibility injector since it should be able to consume key events of interest and perform some action which leads to sending appropriate accessibility event. In the previous implementation it was possible that the injector consumes the event but the latter was bubbled up. 3. Added function to scroll the selection into view while moving it around based on user commands. Note: This is a part of two project commmit. Change-Id: Ibb81d0468726efbe3bf6e3add1b19c69e3206638
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
b73617de462579f7c12c25a4c2747c576f00f6a2 |
|
17-Aug-2010 |
Daniel Sandler <dsandler@google.com> |
Rotation lock. IWindowManager now supports two new methods, freezeRotation() and thawRotation(), that allow a caller to temporarily stash the device's current rotation as the default rotation (when no other constraints are present). The system bar uses this to implement a user-accessible rotation lock by calling freezeRotation() and then turning off accelerometer-based display rotation; unless overridden by an app, the display will continue to appear in the frozen rotation until the rotation is unlocked by the user (either via the rotation lock icon in the system bar or by checking "rotate screen automatically" in Settings). Bug: 2949639 Change-Id: Icd21c169d1053719590e72401f229424b254622f
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
174718b28d29f82e2e4a59a3199b28c477e54470 |
|
30-Sep-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
3012761 Please fix problems with your strings Change-Id: I429632381e862b2ad1e9e22402ef17863458d88f
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ad450be78bb99a965b6aeb7cec04f865da59f052 |
|
17-Sep-2010 |
Amith Yamasani <yamasani@google.com> |
Add an AUTO_TIME_ZONE setting so that we can switch timezones while keeping correct time. Have the NITZ provider honor the new setting before updating the time zone.
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
585f13f8dec4cbf55b3bc04d95425d647f0577b2 |
|
10-Aug-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility support for WebViews Change-Id: Ibb139192bae4d60fd53a7872b19c06312bb41558
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
2c24516e58c2ac8d166b1866a6b5b2085b4f321e |
|
31-Aug-2010 |
Jake Hamby <jhamby@google.com> |
am 04bc8070: am 6659284d: Allow Bluetooth radio to be toggled in Airplane mode. Merge commit '04bc807057d1c336a5d1340595b790eee4c5b372' * commit '04bc807057d1c336a5d1340595b790eee4c5b372': Allow Bluetooth radio to be toggled in Airplane mode.
|
6659284d68bb04539891456700c8da2d0bae7d09 |
|
25-Aug-2010 |
Jake Hamby <jhamby@google.com> |
Allow Bluetooth radio to be toggled in Airplane mode. Add "bluetooth" to the list of toggleable radios. Because this string is in the Settings DB, I had to bump the version number. Why is this in the settings DB anyway, rather than a carrier config option? I also discovered that the SystemUI package copied the entire contents of res/values/defaults.xml from SettingsProvider, when I originally tried to update the unreferenced SystemUI version of the setting. To prevent future confusion, I removed all of the values from the SystemUI version of res/values/defaults.xml. Change-Id: Ib8a75c85b9db5c1963b65538ee2765d5087e67d2
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
eabe8bfaf8c45289a4cfd880f4107d1a9b17e38b |
|
31-Aug-2010 |
Mike Lockwood <lockwood@android.com> |
Add settings option for running MTP server in PTP mode. This can be used as a compatibility workaround for host operating systems without MTP support. Change-Id: If4f1856206056ca8e40c3ffbfa382f185c413598 Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
09dedc998f71c02833950c6476e4d3091c25a8ba |
|
25-Aug-2010 |
Christopher Tate <ctate@google.com> |
Make the default backup configuration "disabled; local transport selected" By default out of the box, an Android build will have the backup mechanism in its "disabled" state and pointed to the LocalTransport test transport. We do not want retail devices built without the Google backend to have backup enabled out of the box; it would cause them to gradually grind away the cache partition for no good reason. On those devices with this change, developers would need to enable backup manually (possibly using the normal Settings UI; more probably using the 'bmgr' shell tool), but would no longer also have to manually configure the active transport name. Device vendors producing Google-enabled products will simply use resource overlays to configure the default state and transport name for their builds. When building a product that points to the Google backup transport by default, the "def_backup_enabled" boolean resource should still be set to 'false' -- the Google backup disclosure activity supplied by GSF will take care of enabling the backup services if the user opts in to it. (Basically, vendors will never have to overlay the def_backup_enabled resource -- the default value of 'false' is correct for any retail device regardless of whether it can use the Google backup transport.) In the SDK build, the default transport will remain the local one, but the default enable state overridden and set to "true". This is the ideal situation for developers: all aspects of the backup mechanism immediately operative with no manual configuration needed. Change-Id: I866f8f627b023b338bc7757e61604e6d8a901a34
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
40e472521a544f26cb6956995788f7c36fff1404 |
|
08-Apr-2010 |
Suchi Amalapurapu <asuchitra@google.com> |
Fix 2579461 Move install location values to secure settings. Diable attribute for UI. Set default value to auto. Add command line interface to set install location via pm. Change-Id: I80e97b3d24845adad7102f40dcbe238f00efa406
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
089262dc022d87e31eefc536025be6c015c7ebde |
|
10-Mar-2010 |
Suchi Amalapurapu <asuchitra@google.com> |
Dont include code size for apps on sdcard. Use constants defined in PackageHelper for user preferences to install auto, internal, external. Set default install location to external. Update settings db version number Change-Id: Ib5110c9377990e20a48cee923e55898dfddfd1e6
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
1c7fa4836bfa7ff61f176461ca0557e90f714121 |
|
10-Mar-2010 |
Daniel Sandler <dsandler@google.com> |
Add VIBRATE_IN_SILENT to the settings database & backup. Change-Id: Id31e24ef0536278ccb66b22bba7ed2b47eb1a371
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
8c9233fba2d73ed9f9cfe38a9be6294c3da2a3ca |
|
08-Mar-2010 |
Daniel Sandler <dsandler@google.com> |
Correct path to LowBattery.ogg. Bug: 2320026 Change-Id: Idede20701c5a3d0e60bd327a869b1adf1577db21
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
00f58438bdb506d84015df45b5b3ff1594aab1d2 |
|
24-Feb-2010 |
Eric Fischer <enf@google.com> |
Filenames of sound effects are not translatable.
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
63e1d264a751519b465f9be84f648d338a095cd1 |
|
24-Feb-2010 |
Daniel Sandler <dsandler@google.com> |
Turn off lock screen sounds by default. This change also fixes a typo that was suppressing the dock sounds. But: so as not to surprise anyone, this change defaults dock sounds off as well. Will need to add UI somewhere to turn them on (Spare Parts?). Bug: 2465483 Change-Id: Ic2cccb416d5616a84363debb740bf5897f0831c4
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
0e9d2af2d60b381ba52d0c25e583b3d2a9906051 |
|
25-Jan-2010 |
Daniel Sandler <dsandler@google.com> |
New user interface sound effects: - Low battery. (http://b/2320026) - Dock/undock events. - Keyguard lock/unlock events. New system settings have been created to turn these on/off and to specify the relevant sound files. [Production notes: The provided low battery sound and dock sounds were synthesized; the lock screen sounds are processed samples of a ballpoint pen click mechanism.] Bug: 2320026 Change-Id: I374285b0f94f59c7555bb8816580f5a8c802e90d
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
117818e4f171b1fd9daa05349c48f61388f04567 |
|
09-Feb-2010 |
Suchi Amalapurapu <asuchitra@google.com> |
Add new manifest option for install location Change recommendAppInstallLocation api add code to parse new attribute. Define flags in PackageInfo Add new settings attributes for enabling setting and value for install location Some tests The policy for install location: if explicitly set in manifest as internal only we try to install the app only on internal storage. if set to preferExternal, we try to install it on sdcard if possible. If not we fall back to internal. If the user enables setting SET_INSTALL_LOCATION(which will always be set to false in final release builds) and sets a prefered location, we try to honour it.
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
87734d3bc118cba8f42845ddd51f10edadb84abf |
|
08-Jan-2010 |
San Mehat <san@google.com> |
Settings: Add settings for MountService prefs and bump DB version to 46 Adds 4 new Settings: Secure.MOUNT_PLAY_NOTIFICATION_SND - Play notification sound on events Secure.MOUNT_UMS_AUTOSTART - Auto-start UMS when host detected Secure.MOUNT_UMS_PROMPT - Show notification when host detected Secure.MOUNT_UMS_NOTIFY_ENABLED - Show notification while UMS enabled These settings are also added to the Settings backup list Signed-off-by: San Mehat <san@google.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ae3ed706702a5ebe6ffcc08b941b1401c9a24b89 |
|
02-Dec-2009 |
Amith Yamasani <yamasani@google.com> |
Add new setting for notification light pulsing. Bug #2238250 New System setting and code to set the defaults on upgrade.
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
075a18d607c3aa8386b4d06aea22f4bfacbe447b |
|
26-Sep-2009 |
Dianne Hackborn <hackbod@google.com> |
Turn on haptic feedback by default. Change-Id: I85efeca1a0aca91992e28236077c668e0d14cbbb
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
bfe319e06aa56c081d0d94d64a8181291d7f7388 |
|
21-Sep-2009 |
Dianne Hackborn <hackbod@google.com> |
Turn animations on by default. Add API to skip the animation for a particular start activity, so that a latter better one can be used. Fix Theme.NoDisplay to actually work. Fiddle with various animations: don't do a different animation for task switching, try a scale animation for switching in/out of the wallpaper. Adjust the animation duration so that at normal speed we have something more like the slower animation option (so slow is now the default). Change-Id: Ieba9f3db0bd9a762a19b327a3ecccbc7b547893d
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
951764b97010dfa073126f52b43ea1bdf1b35998 |
|
27-Aug-2009 |
Dan Murphy <D.Murphy@motorola.com> |
Add automatic lighting control framework Add changes to have the ability to turn on and off the automatic light sensing for the device. This is fully configurable and is by default not present. Vendors should override the ALS setting to enable the automatic lighting controls. These changes will add a check box to the Brightness settings menu to give control to the user to allow the device's display lighting to be controlled via the slide bar or the auto lighting system. If the user selects auto then the slide bar will become invisible. Manual mode will present the slide bar to the user. Change-Id: I146a6d75b99b08c9b839218ce6b85adf21f9fd73 Signed-off-by: Dan Murphy <D.Murphy@motorola.com> Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
bd5ddf01e4d629982fa8bb667d4be7c5ec3aa79f |
|
30-Jul-2009 |
Mike Lockwood <lockwood@android.com> |
Wifi: Add support for enabling Wifi while in airplane mode. If the new system settings value for AIRPLANE_MODE_TOGGLEABLE_RADIOS contains RADIO_WIFI, then the user will be allowed to enable Wifi while in airplane mode. Turning on airplane mode will still disable Wifi, but the user will be free to reenable it in the Settings app. Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
f7573bd2b7bb63d78fa8f0003ba49be10b128753 |
|
28-Jul-2009 |
Eric Fischer <enf@google.com> |
resolved conflicts for merge of cdb9e971 to master
|
2bfe11af6f715656b60fc9ac4566e74da9b98390 |
|
28-Jul-2009 |
Eric Fischer <enf@google.com> |
Mark the the airplane mode internal strings as not translatable. Bug 2017552
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
575d1af980f4b4866325bfc487455f54606cf49e |
|
03-Jul-2009 |
The Android Open Source Project <initial-contribution@android.com> |
resolved conflicts for merge of cf098294 to master
|
cf098294da7a820d5c30d8ed2006ed5446ee1da9 |
|
02-Jul-2009 |
Dianne Hackborn <hackbod@google.com> |
Move backup state to settings, change permission checks to use symbol. This changes the backup service to use the settings provider instead of system properties, correspondingly making it off by default and allowing specific devices to define the transport. Also tweaks the permission checks to use the permission symbol instead of raw strings. This requires some corresponding changes in the vendor projects.
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
bcab8df83e6e769a7cbcc742e72b47d665998793 |
|
25-Jun-2009 |
Mike Lockwood <lockwood@android.com> |
Settings: Add preference to enable/disable assisted GPS. Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
79a6b3b4491269dfe004de361ca14761ffba4aa7 |
|
19-May-2009 |
Mike Lockwood <lockwood@android.com> |
Settings: Disable network location service by default, enable GPS instead. Network Location Provider requires user opt-in, so it should be disabled by default and only enabled if the user agrees to the terms of service and privacy policy. Use GPS as default location provider instead. Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
ba87e3e6c985e7175152993b5efcc7dd2f0e1c93 |
|
13-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake_rel/...@138607
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
d24b8183b93e781080b2c16c487e60d51c12da31 |
|
11-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@130745
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|