Merge commit '0e6386300c958c5566d09b6a18b4338a6db3e965'
* commit '0e6386300c958c5566d09b6a18b4338a6db3e965':
Add gservices flag for configuring the URL vending redirects to when TOS is inaccessible due to no/bad network.
Changed Postal to StructuredPostal, which is the new type
coming down from GData. This also prepares us for upcoming
data sources that need a structured version. Because of the
number of columns required, we added 3 new DATA columns.
Moved PACKAGE back to Data rows to allow multiple apps to
merge their action entries under a single Contact. Also
renamed to RES_PACKAGE to make clear that these packages are
strictly for loading resources, and do not imply the owner.
Removed RestrictionExceptions since we narrowed the scope
of IS_RESTRICTED for Eclair. Factored out sync columns from
Groups and Contacts into its own interface. Fixed general
warnings in comments.
Merge commit '6fb608ee67c3ad82baf2253b87b63fff8907992a'
* commit '6fb608ee67c3ad82baf2253b87b63fff8907992a':
Issue #1884058 (Need to only record frequency and duration for selected Google apps)
Quick and dirty solution: a new --packages argument allows you to specify an explicit
set of packages to include in the dump. There is also now a new GServices setting
that can provide a value for it.
Merge commit '5628711a6f5674070da674488513d2e1b03c4959'
* commit '5628711a6f5674070da674488513d2e1b03c4959':
Add a Gservices setting to control if we send up multipart protocol buffers
Merge commit '4caac2bb4c8616edf8224408931ffc0e532537de'
* commit '4caac2bb4c8616edf8224408931ffc0e532537de':
Add more logging to track down a monkey bug
This will fix a CNAP-related bug where missing a call from a party with an
"Unknown" number presentation and then trying to log that call will cause
a NullPointerException to be thrown
This is the problem where various things are listening for broadcasts
(such as battery status, PIN/PUK/Network) that an application can send
to cause harm to the system.
Solving this is tricky because many of these broadcasts are sticky,
and I have never figured out how to do permissions with sticky
broadcasts in a sane way. So instead, I am going to punt on the
general problem and just brute force it:
There is new a way for system components to declare specific
broadcast actions to be protected, which means that only the system
and the phone can send them. This is good enough for now. None
of it is exposed in the public API so we can make something a little
less stupid in the future if we ever need to.
Merge commit '8f7c7c0c18987b1045cb73e503f82ce429a0d924'
* commit '8f7c7c0c18987b1045cb73e503f82ce429a0d924':
Add a Gservices setting to set the rate at which the home page refreshes.
Wrote code to support groups and slightly modified existing
group membership definition. Each group has a TITLE, or a
TITLE_RESOURCE which can point to a localized title from
the owning package.
Adds summary Uri with columns that describe the contents of
all returned groups, such as people counts.
Added visibility flag to groups and aggregate tables to
prepare for group management UI.
Also backup development settings MOCK_LOCATION and USB_DEBUGGING.
Backup and restore more of the Audio settings. Won't work yet without a reboot.
Disable Wifi supplicant restore temporarily. It seems to be disabling Wifi due to
permissions problems.
Don't restore Ringtones.
Merge commit '04f0b05ea04a4a13d6a15b36eaa27b2ec364f313'
* commit '04f0b05ea04a4a13d6a15b36eaa27b2ec364f313':
Add a Gservices setting for how many times we should retry before discarding an uphill operation
Merge commit 'dbee95cacff9d2faf30638e64abe26fbeb128787'
* commit 'dbee95cacff9d2faf30638e64abe26fbeb128787':
Make enable/provisioning of the backup service a two-step process
This CL adds the concept of 'provisioned' to the backup manager. No backups
will be scheduled until the user has indicated that backups are to be enabled
*and* has clicked all the way through the setup wizard.
When the user first turns on the backup system, the delay before the initial
backup pass is different from the periodic backup interval. Currently that
initial delay is 12 hours. The intent here is to guess at a less-active time
for performing that first backup pass.
NOTE: currently the backup service defaults to 'provisioned'. Once the real
code goes live in Setup Wizard, this will be changed to default to
not-provisioned until the user has confirmed all the relevant UI.
Merge commit '816cf52abd8f45770f0ac922bbb819184ed4b90f'
* commit '816cf52abd8f45770f0ac922bbb819184ed4b90f':
Fix the DEFAULT_SORT_ORDER value for media files. Changing this
is OK, because existing app will have the old value compiled in
as a literal, and so will continue to (not) work in the same
way as before. Add code to media key generator to give a leading
ascii \001 the special meaning of "sort first".
