| 0e9eeee0dd50325362e2c8132f43f512551e604b |
|
26-May-2018 |
Michael Wright <michaelwr@google.com> |
Add per-device defaults for VIBRATE_WHEN_RINGING
Some devices have hand-crafted, artisanal haptics to go along with the
dulcet tones of the ringer. When making such a device, we really want
our users to have the opportunity to appreciate the fine buzzes and
clicks we spent so long orchestrating, and so this makes it possible to
default VIBRATE_WHEN_RINGING on.
Bug: 79212179
Test: manual
Change-Id: I52bf133345bd3e8b09b591b9bac4711d0d485094
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| cb58a83a19a429b96e577a0546b3c8ccc28fd26d |
|
16-Apr-2018 |
Philip P. Moltmann <moltmann@google.com> |
Change allowed sound triggers to 1000
Test: Looked at settings on fresh device. Saw update. Looked at upgraded
device and saw change from 300 -> 1000
Fixes: 78112231
Change-Id: Iecb5b1250fa8613201ef8a85f8221aa8608785dc
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 7e25b3d9155343c6ee227499a5c29f42ae9d791c |
|
10-Mar-2018 |
Philip P. Moltmann <moltmann@google.com> |
Throttle number of sound trigger operations / day
It is not clear when the day should start. Further a day might have
25 hours in the case of daylight savings time.
Hence a day in this case is the last 24 hours, not a calendar day.
Keeping track of the time of each operation might waste memory as we
don't need that much precision.
Hence keep track how many operations were performed in the last 24
hours in buckets of hours. If the total count reaches a maximum suppress
any further operations.
The maximum is configurable via global settings. It can be updated
by apps that have the appropriate permissions. Hence if the default
value turns out to be incorrect, it can be adjusted after release.
This does not throttle based on battery state as it is better to
completely unload the sound model to not even have a detection event.
Test: atest SoundTriggerDetectionServiceTests (separate CL)
atest android.provider.SettingsBackupTest
Bug: 73829108
Change-Id: Ied8570b60b61b6a055bd2576d1502c1b36424efa
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 18e3eb816887156f40def1c14db434ddde9ec245 |
|
10-Mar-2018 |
Philip P. Moltmann <moltmann@google.com> |
Add SoundTriggerDetectionService
The service is meant to replace the PendingIntent based API. Once all
users of the PendingIntent based API switched the PendingIntent based API
will be removed.
To have as little as possible impact on the whole SoundTrigger framework
the RemoteSoundTriggerDetectionService class implements the same
interface as the PendingIntent based class. Hence the exising code has
very little change. Further once the old code can be removed the amount
of changed (and added) code is limited.
The RemoteSoundTriggerDetectionService -> SoundTriggerDetectionService
is a vanilla as possible service implementation. The special behaviors
are:
- The system holds a wakelock while service operations are in progress
and the service is bound as foreground. Hence the service can e.g.
listen to the microphone.
- Service operations have a certain amount of time they are allowed to
run. Once every operation is either finished or the the operation
exceeded the allotted time, the system calls onStopOperation for each
still pending operation. This is a similar model as for the commonly
used JobService.
Please note that if the time allowed for an operation is 15s and
op1 was run as 0si, and op1 was run at 5s, the service is allowed to run
until 20s. Hence _both_ onStopOperations will happen at 20s. This is
done for ease of implementation but should not give the service more
power than calling onStopOperation exactly 15s after each operation is
triggered.
- If an operation is done before the allotted time is reached, the
service can declare the operation as finished manually by calling
onOperationFinished. This is a call back into the system, hence a
'client' binder is sent to the service. If the operation is finished
by calling this method onStopOperation will not be called.
- As the service instance might be killed and restored between
operations we add a opaque bundle 'params' to each operations. The users
of the API can use this to send data from the start command to the
operations. It can also just be set to null. The params are not meant to
store changing state in between operations. Such state needs to be
persisted using the regular methods (e.g. write it to disk)
- A service can be used for multiple recognition sessions. Each
recognition is uniquelity defined by its sound model UUID. Hence each
operation gets at least tree arguments: Operation ID, sound mode UUID, params
- As a small optimization the params are cached inside of the service
instance.
The time allowed for each operation is in a @SystemAPI global setting,
so the service can make sure it finishes the operations before they are
stopped. It might take some time to deliver the operations via the
binder, hence it is not recommended to try to use every last ms of
allotted time.
Test: atest SoundTriggerDetectionServiceTest (added in separate CL)
atest android.provider.SettingsBackupTest
Change-Id: I47f813b7a5138a6f24732197813a605d29f85a93
Fixes: 73829108
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| d069a888cf32f105bf6843a7083770f5b82af74e |
|
13-Mar-2018 |
Annie Meng <anniemeng@google.com> |
DO NOT MERGE Create a setting for backup/restore agent timeouts
Part of push to make backup and restore agent timeouts configurable. Creates
a Global setting for the current static BackupManagerService timeouts so
that they can be overriden with P/H. We keep the current default values,
which will be updated once we investigate what more appropriate values are.
Remame the constants to better reflect what they're used
for. Next, we will update the framework to use these constants.
This depends on the refactor of how we observe changes to key value
backup settings (ag/3709997).
Bug: 70276070
Test: m -j RunFrameworksServicesRoboTests ROBOTEST_FILTER=BackupAgentTimeoutParametersTest
Change-Id: Id506314ce0c8bd5e4d1d8b4001b26cbad0056c99
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 09da25f00d0d8cd6625b6ba6f184d4a182b04e7f |
|
26-Feb-2018 |
Beverly <beverlyt@google.com> |
Using zen duration preference
Test: make ROBOTEST_FILTER=ZenDurationDialogTest RunSettingsLibRoboTests -j40
Bug: 73741459
Change-Id: Ide76ac8016b84f128c47ad3731eeced25dce8c73
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| da904810f313b1c23635f31533b7d94ced47ba34 |
|
02-Mar-2018 |
Beverly <beverlyt@google.com> |
Update default charging sound to new sound
Test: manual (unmute phone, start charging and hear sound)
Change-Id: I5db9245660d3875f74f9a58073856c51d2c86b5e
Fixes: 73362089
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| eaa78b92a5ef191d8c581811b2d15920011e0e02 |
|
26-Jan-2018 |
Bernardo Rufino <brufino@google.com> |
Add local transport parameters for transport flags GTS test
Added parameters for local transport in secure setting for setting up
local transport to test transport flags GTS test.
Test: GTS test in topic CL.
Bug: 73100304
Change-Id: If654175d91fdf1ea68db0f3320d59b2b770a4db3
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 4af4a6f04243a00866ebb8479c36e3bade8dd2df |
|
16-Jan-2018 |
Mike Digman <digman@google.com> |
Make autorotate off by default for new installs and upgrades
For dogfood testing to monitor usage of new rotate locked mode
Test: manual
Change-Id: I4678a31b4ee8b8ff7f282b453843cae8fb2df7dc
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 7076a31f5a899bae105b5256dc2197d36b29a182 |
|
02-Oct-2017 |
Jacky Cheung <jackyc@google.com> |
Add a configurable default value for MOBILE_DATA_ALWAYS_ON
Some devices (aka watches) don't want the power cost of data
being connected all the time.
Bug: 64685191
Change-Id: I059911eca436d7a28747126f17061a47233bd454
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| cc1e76a4b3b4e19ebc340c93a36a3dfef09598e5 |
|
31-Aug-2017 |
Tim Zheng <timzheng@google.com> |
Add a backup manager constants secure settings.
This change add one secure settings which is a key value list consisting
of 7 individual settings; it also provides a class to get these settings
and use the default values specified in default.xml file when the settings
are missing.
This is the first part of a 2 part change. A subsequent change will use
these settings in backup service manger for setting up backup frequency.
Test: This change builds. Manual tests will be included in part 2 of the
change.
Bug: 63351792
Change-Id: I62baddbf3e0b96af6b7de3dfdeac3479e5b3ded8
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 94bcdbca224188c067c651e034e187def082e8dd |
|
17-Jul-2017 |
Narayan Kamath <narayan@google.com> |
NetworkPolicyManagerService: Allow data saver to be on by default.
This value is read from the global settings provider, and can be
configured via an overlay.
Bug: 63112872
Test: NetworkPolicyManagerServiceTest
Change-Id: If55ea08df1dd8440189f9b46a5606118de99c930
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 09d4ff8960cd3d45988b0c3ff0835d281f0e16b5 |
|
31-Mar-2017 |
Phil Weaver <pweaver@google.com> |
Remove a11y web flags and associated settings
Bug: 35707622
Bug: 28322375
Test: Ran a11y cts. Updated those tests in linked CL to
ignore this feature.
Change-Id: I1dccb3ae4e1f4d6bb832ae1b0edd4dad4a54289e
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 5d0922f78a549533c8fd368a363a82140728a357 |
|
27-Mar-2017 |
Stephen Chen <stewchen@google.com> |
Enable Wifi Wakeup Setting by default.
Bug: 36385983
Bug: 32913119
Test: runtest --path frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
Change-Id: I99f9aea6f85675eb1c92fe16f99755117110636a
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 71934ecb194e9e85a36858a1c52f52c7493d24d1 |
|
25-Mar-2017 |
Guang Zhu <guangzhu@google.com> |
Revert "Enable Wifi Wakeup Setting by default."
Bug: 36385983
Bug: 32913119
Bug: 36604943
This reverts commit abb947ac24b316a188965c341599973a1f7a3de9.
Change-Id: I484534dd6c24f5b2c2839781fc6a71d9e976a859
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| abb947ac24b316a188965c341599973a1f7a3de9 |
|
24-Mar-2017 |
Stephen Chen <stewchen@google.com> |
Enable Wifi Wakeup Setting by default.
Bug: 36385983
Bug: 32913119
Test: runtest --path
frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
Change-Id: Ia9205d28d7c215fd8c407560513036565e36537d
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| fb924fa981f79dac7719a35b63fcfae81bdd421a |
|
22-Feb-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Fix 'Modifying dpm.setSecureSetting call for install_non_market_apps'"
|
| 0b1356ff1f3cd2fd06d770af1ad466822173cc3a |
|
21-Feb-2017 |
Suprabh Shukla <suprabh@google.com> |
Fix 'Modifying dpm.setSecureSetting call for install_non_market_apps'
The previous change was reverted as it broke work profile provisioning.
Clearing binder calling identity before calling into settings provider
should fix the issue.
Test: runtest managed-provisioning
Test: runtest -x services/tests/servicestests/src/com/android/server/devicepolicy/DevicePolicyManagerTest.java
Test: Manually tested that work profile is inflated with expected values
of install_non_market_apps
Bug: 33947615
Bug: 35590590
Change-Id: I3c31a73fef0c25c0e682e18f637272adad39b28d
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 385912ee2d78e0e557704cfd5f8c7dbe2b7fd280 |
|
10-Feb-2017 |
Phil Weaver <pweaver@google.com> |
Deprecate "speak passwords" setting.
This will now be controlled by individual accessibility services.
We'll provide the password information to them, and they can
present or hide the information as it makes sense for their users.
Password information was anyway provided when a headset was
connected.
Bug: 28139568
Test: Manually verified that TalkBack now speaks passwords on the
lock screen and in text views. Since I'm removing functionality
that didn't have tests, it's tricky to have specific tests.
Change-Id: Ic3c724ccce5762ee9dcd9e7dcbd4eae6734dd05e
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 5663e051099cdf442bc3316a88e1a7600c58aaaa |
|
20-Feb-2017 |
Victor Chang <vichang@google.com> |
Revert "Modifying dpm.setSecureSetting call for install_non_market_apps"
This reverts commit 2e7d6d64b9b16ea27634bc0e8843717a465142b4.
Bug: 35590590
Fix: 35590106
Test: runtest managed-provisioning
Test: manual verified that work profile can be inflated
Change-Id: Ie780b94053e65bca2f96b32055937c0c9e8beae8
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| dd903d4f0ee4cebcef03e54f5b07f4bcc14c5dbc |
|
18-Feb-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Modifying dpm.setSecureSetting call for install_non_market_apps"
|
| 2e7d6d64b9b16ea27634bc0e8843717a465142b4 |
|
10-Feb-2017 |
Suprabh Shukla <suprabh@google.com> |
Modifying dpm.setSecureSetting call for install_non_market_apps
Starting from O, install_non_market_apps is deprecated and will not be
checked by the package installer. Device admin apps should be using the
user restriction instead.
Since on managed profiles, the default value blocked install from
unknown sources, the system will set the user restriction on behalf of
the profile owners (if the profile has one).
For non-managed profiles, the user had access to the settings to change
the value of install_non_market_apps. So going forward, any request to
change it's value by dpm#setSecureSetting in such users is going to be
ignored.
Test: Manually tested that:
1. For a profile with PO, when install_non_market_apps was set to 0,
user restriction is set on upgrade
2. For a profile with PO, when install_non_market_apps was set to 1,
user restriction is not set on upgrade
3. After upgrade, newly created managed profiles with PO have user
restriction set
Bug: 33947615
Change-Id: I063e9ee608b52086ffdf8ed2b24e2928574c58cd
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 27d14c46a7528194d5eda468ac16837933f0fe18 |
|
15-Feb-2017 |
Jeremy Joslin <jjoslin@google.com> |
Define a new config key for the recommendation provider app.
Created a new config key and removed the previous key that
was defined in default.xml. Also removed the SettingsProvider logic
as we'll set the default in NetworkScoreService in a follow-up CL.
Bug: 35095406
Test: build and install.
Change-Id: I2893be31fd526af8a66d6d1b7d8978adf7e32c0f
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| c9eb3c46511a80a7ad9d297d232c579886d55a97 |
|
08-Feb-2017 |
Jeremy Joslin <jjoslin@google.com> |
Add a new setting to store the network recommendation app.
Test: manual
Bug: 35095406
Change-Id: I3d0b7f3b977c0862969d61a4e46f12151eb15417
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| e3745eed8b9599de6f413d48a81098209fd41791 |
|
03-Feb-2017 |
Suprabh Shukla <suprabh@google.com> |
Deprecating secure setting install_non_market_apps
Apps targetting Android O or higher should use the new api
canRequestPackageInstalls in package manager. The secure setting
INSTALL_NON_MARKET_APPS which was used is set to 1 to make the
change transparent to apps who are already querying for this setting's
value.
Test: adb shell am instrument -e class\
'com.android.providers.settings.InstallNonMarketAppsDeprecationTest' -w\
'com.android.providers.setting.test/android.support.test.runner.AndroidJUnitRunner'
Bug: 33947615
Change-Id: Ie38d130bfccd022483a566270fce071acbdb00b7
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| c837ebb2c155bd2e0cd6a3203051770c7746ce4b |
|
03-Dec-2016 |
Stephen Chen <stewchen@google.com> |
Merge "Add Settings.Global.WIFI_WAKEUP_ENABLED flag." am: d758ce1586 am: d738140b8d am: a4d7d45df9
am: 50905a474f
Change-Id: Idc7bc3e35343b06adebb035cc00b555db54289c5
|
| a4d7d45df936ec35e9663e15da8abc0e6432ceb5 |
|
03-Dec-2016 |
Stephen Chen <stewchen@google.com> |
Merge "Add Settings.Global.WIFI_WAKEUP_ENABLED flag." am: d758ce1586
am: d738140b8d
Change-Id: Icb8eb81b2021ee12eccd9158974353120228e7c0
|
| d738140b8d8868c0c295fdab97b3a5998c9aa2f7 |
|
03-Dec-2016 |
Stephen Chen <stewchen@google.com> |
Merge "Add Settings.Global.WIFI_WAKEUP_ENABLED flag."
am: d758ce1586
Change-Id: I1bf1effbb635d57980728555587e8056f630edb9
|
| 8ca96c1f3c89181119919eaab3b81322d3988e66 |
|
17-Nov-2016 |
Stephen Chen <stewchen@google.com> |
Add Settings.Global.WIFI_WAKEUP_ENABLED flag.
Set the flag default to false. This addition is for the
Android Wi-Fi Snooze project:
https://docs.google.com/document/d/1zewDZ6Ne-qH7zKFDtcSx55f9jPauZwT5VvOs1uVNXf8/edit#
Bug: 32920000
Bug: 32913119
Test: runtest --path
frameworks/base/packages/SettingsProvider/test/src/com/android/providers/settings/SettingsProviderTest.java
Change-Id: I597d5dd643e8044315cc6d7553ae5740485a0552
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 7b62df8556ff6febd8137b9a8bcd755b1f93a1f9 |
|
30-Nov-2016 |
vinodkrishnan <vinodkrishnan@google.com> |
Revert "DO NOT MERGE Wear Fwk: Disable Animations for A11y"
This reverts commit 8500f26d51e2ba0de7b6cd18bec5f85e5ca40e1d.
Change-Id: I6408fa3f307d7611443e26b24d3876c1a1f92fdc
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 8500f26d51e2ba0de7b6cd18bec5f85e5ca40e1d |
|
27-Oct-2016 |
Vinod Krishnan <vinodkrishnan@google.com> |
DO NOT MERGE Wear Fwk: Disable Animations for A11y
- When Accessibility is turned on, Android Wear devices become unusable.
Add an option to disable animations, will be disabled in an overlay.
Bug: 24985771
Change-Id: If5fc44705d56579b305abd48a0d820f306b9be10
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 909bbd31177ebc131f91453a9aa206baec4afb9a |
|
21-Oct-2016 |
Vinod Krishnan <vinodkrishnan@google.com> |
Fwk: Only chime when docked and accessbility is on am: cf11ceab65
am: ccf3baf6c5
Change-Id: I685dc2ef179087600e4d3c5776448ece338901b7
|
| cf11ceab652a146c72fde1fef53d69ceee9bf651 |
|
21-Oct-2016 |
Vinod Krishnan <vinodkrishnan@google.com> |
Fwk: Only chime when docked and accessbility is on
Bug: 32036947
Change-Id: I5786abe827735cc3a4bc1d52baacaa19bccaae77
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| ec7a118950543dfa89cb2c85cc1c79443d93e200 |
|
18-Oct-2016 |
Keun-young Park <keunyoung@google.com> |
add default overlay for END_CALL_BEHAVIOR
- for automotive, default END_CALL_BEHAVIOR should be 0.
- automotive product should have overlay overriding it.
- default value is the same as now
bug: 31926624
Test: manual (check dumpsys window policy)
Change-Id: Ice7b3c1374dfccf8a03c13c73201fa1615acab5f
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 1609e309063720dc582b6139f7ac4d57b2c9b89a |
|
14-Sep-2016 |
Andre Eisenbach <eisenbach@google.com> |
Enable Bluetooth by default am: 8c18431be8 am: 4c18d82084
am: 10a9dc7e04
Change-Id: I4e9e10e4d4b29eb03140cc686b1acc3ecf5a0a7a
|
| 4c18d82084a7491e4598d2f93e824e6cf46696bd |
|
10-Sep-2016 |
Andre Eisenbach <eisenbach@google.com> |
Enable Bluetooth by default
am: 8c18431be8
Change-Id: Iebcaf699361494d92c59935f96c6e859fba96003
|
| 8c18431be868e0960e80638c1a974d71a0df05b4 |
|
07-Sep-2016 |
Andre Eisenbach <eisenbach@google.com> |
Enable Bluetooth by default
Bug: 29446913
Change-Id: I6d42810cb3f99617b886f6c643f8c66c42c1d017
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| ea35e07e1b71dd22309baefdd1d621f6f91ad2f0 |
|
04-Aug-2016 |
Andre Lago <andrelago@google.com> |
[Settings] Added setting SYNC_PARENT_SOUNDS
Added a setting that specifies wether a managed profile's ringtones
should be the same as its parent
Change-Id: I90e20cee111640404c3758030f41d5b2b5af1c28
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 96e9cc5700c63c872f29f488129daf34f95292d2 |
|
13-Jul-2016 |
Anthony Hugh <ahugh@google.com> |
Add panic detection to back button
Adds "panic" detection to the back button. Implemented solution
uses 4x button presses in a short duration to detect for "panic".
The value used to determine the duration between key up and key down
that still count as a multi-button press is configurable via the
Settings Provider.
BUG: 28027764
Change-Id: Ibf1370ff3cb539a9a54002a8704922744a3ca5d7
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 71f85e91941029cb554cc4a0dc2b0e8d17b3c478 |
|
20-Jul-2016 |
Dan Sandler <dsandler@android.com> |
Decrease default longpress timeout to 400ms.
If the device being upgraded happens to have a timeout of
500ms it will be reset to 400. If the value is something
else it will be left alone upon upgrade.
Bug: 30159825
Change-Id: Ifec70e458ce0199b61d36f7504aea02b4a974990
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 3d9805d50281882b4420ee2d4ede8a8bdd94d455 |
|
07-Jul-2016 |
Mahaver Chopra <mahaver@google.com> |
Added UM.DISALLOW_OEM_UNLOCK, Removed Global.OEM_UNLOCK_DISALLOWED.
Currently we used global setting to restrict user from enabling oem
unlock. As global settings can be chagned using adb, using user
restrictions instead.
Bug: 29893399
Change-Id: Ic83112a4838b8279bf50408a29ae205e0b8639ee
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| dc20ba69bf5f6e1017202555b6159abaf67b855c |
|
26-Apr-2016 |
Steven Ng <stevenckng@google.com> |
Add a Global setting for disabling OEM unlocking setting
+ By default, OEM unlocking setting is enabled.
+ Add a check to prevent oem unlock being flipped if the setting isn't
enabled.
Bug: 28163088
Change-Id: I087d8d5a1d99a611a8f66ff71a92ec9ea1da4e9f
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| de16b869308b1d667743bac3deba5d7b2b3c5889 |
|
05-Mar-2016 |
Prathmesh Prabhu <pprabhu@google.com> |
SettingsProvider: Add default value for SHOW_IME_WITH_HARD_KEYBOARD.
Allow OEMs to override default behaviour wrt. showing IME with a
hardware keyboard is connected. Current behaviour remains unchanged.
BUG: 27503877
BUG: 27484734
Change-Id: I7ed70b195c3ae98471e413b3eecc5d8fcd3dee26
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| bd17928afcbead00b498a75a92a0a32a6cca7fee |
|
18-Dec-2015 |
Bryce Lee <brycelee@google.com> |
resolve merge conflicts of 6b9e5bf0c2 to master.
Change-Id: Idada49313619533bfeb375ee232c942589457fa4
|
| ec85f34812b0f66715ad5ae4d1485f98a690746c |
|
16-Dec-2015 |
Bryce Lee <brycelee@google.com> |
Add setting for declaring disabled bluetooth profiles.
Bug: 25900899
Change-Id: I420a7c590d72ba10f3e466d15dccfdbb520e810a
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 269c11eee1ceed0b5959dce3f5d139ea3ac02ce8 |
|
03-Dec-2015 |
Suprabh Shukla <suprabh@google.com> |
Added default config to enable adding users from lockscreen
A config value is added for enabling/disabling the ability
to add users while screen is locked. The config value, currently false,
is read and applied to the setting only if the user has not set the
value as true/false explicitly.
Bug-Id: b/24662310
Change-Id: Ie00ab0952c64cbc9805794bc0dde350920750026
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| cd86ebf1c965c191f46b6480145c9d217a7d841e |
|
30-Sep-2015 |
Fyodor Kupolov <fkupolov@google.com> |
Check multi-user support in isUserSwitcherEnabled
isUserSwitcherEnabled now returns false if multi-user is disabled(
supportsMultipleUsers() returns false).
Removed GUEST_USER_ENABLED setting and replaced with DPM.getGuestUserDisabled
check. It currently always returns false, but will be replaced with an actual
policy check.
Bug: 17571233
Change-Id: I41853e8b321b2537952cac5d92e88bfdb8cbd9a8
/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
|
| 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
|