diff options
| author | Christopher Tate <ctate@google.com> | 2010-08-24 15:37:42 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2010-08-24 17:52:45 -0700 |
| commit | 09dedc998f71c02833950c6476e4d3091c25a8ba (patch) | |
| tree | fa0c889b1c598dca7bf9f852de37ee09813e048f /packages/SettingsProvider/res/values/defaults.xml | |
| parent | 5aa4680eb07fd4ca9212ee29c4fc0659e00c958d (diff) | |
| download | frameworks_base-09dedc998f71c02833950c6476e4d3091c25a8ba.zip frameworks_base-09dedc998f71c02833950c6476e4d3091c25a8ba.tar.gz frameworks_base-09dedc998f71c02833950c6476e4d3091c25a8ba.tar.bz2 | |
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
Diffstat (limited to 'packages/SettingsProvider/res/values/defaults.xml')
| -rw-r--r-- | packages/SettingsProvider/res/values/defaults.xml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/packages/SettingsProvider/res/values/defaults.xml b/packages/SettingsProvider/res/values/defaults.xml index 185d72a..8349fe6 100644 --- a/packages/SettingsProvider/res/values/defaults.xml +++ b/packages/SettingsProvider/res/values/defaults.xml @@ -47,7 +47,8 @@ <bool name="def_networks_available_notification_on">true</bool> <bool name="def_backup_enabled">false</bool> - <string name="def_backup_transport" translatable="false"></string> + <string name="def_backup_transport" translatable="false">android/com.android.internal.backup.LocalTransport</string> + <!-- Default value for whether or not to pulse the notification LED when there is a pending notification --> <bool name="def_notification_pulse">true</bool> |