This patch includes the plus code conversion clean up.
1. change the plus code conversion based on the current and default
number systems retrieved from MCC.
2. for format such as +NANP, replace the '+' with the current IDP (011).
3. comments changes.
- changed the IAccountManager API to use oneway IPCs
- changed the AccountManager to not have to start a thread for any of the calls (versus every call)
Merge commit 'a8dfe24da014b52d7ae93c3fbd7a8b88ec336572'
* commit 'a8dfe24da014b52d7ae93c3fbd7a8b88ec336572':
Adds the ability to configure the mock Geolocation service from DumpRenderTree.
Packages that do not use android.permission.BACKUP_DATA will neither be backed
up nor restored. That permission is currently signature-only. In the future if
access to the backup/restore infrastructure is made available to arbitrary 3rd
party applications, the permission checks (and indeed, the permission itself)
can simply be removed.
Setting max_retires to infinite sets mRetryForever to true and therefore
isRetryNeeded will always be true. This is better than an alternative
which is to set max_retires to a large value such as 2147483647.
The issue is that the plus sign in a dial string is always converted
to the IDP (International Dial Prefix).
This fix implements a plus sign conversion mechanism based on the default
telephone numbering system that the phone is activated and the current telephone
number system that the phone is camped on. Currently, we only support the cases
where the default and current telephone numbering system are NANP.
When performing a set of batch operations, some callers need
to enforce that a query has specific values. For example,
when persisting edited Contact values, we need to assert
that the RawContacts.VERSION matches the version we read out
through queryEntities().
This change adds a new TYPE_ASSERT that uses withValues()
and withSelection(), and checks all values when applying the
batch operation, bailing if any values don't match.
* changes:
Wipe data on backend before a backup run Append the date to 3.txt so that we can see if/when backup failures occurred solely from the device/server state Note that these files will probably be deleted from the tree immediately, to be replaced by the ruby versions.
Append the date to 3.txt so that we can see if/when backup failures occurred
solely from the device/server state
Note that these files will probably be deleted from the tree immediately, to
be replaced by the ruby versions.
Merge commit 'ff6585cbb0e5e42adf056b4a074b9f3683b853c1'
* commit 'ff6585cbb0e5e42adf056b4a074b9f3683b853c1':
Remove flaky MonitorTest#testInterrupt from continuous, and attempt to make
Merge commit '7a07f1797684597a3b932aa0b365049d3e7d6ff3'
* commit '7a07f1797684597a3b932aa0b365049d3e7d6ff3':
After each test, the WebView cache should be cleared, otherwise the cache data will pile up.
- Add copyright headers
- Allow the user to pass options (like '-s FOO') to adb
- Restart device adb as root if needed
- Make test_restore to infer a restore set
Merge commit '8c5b3e2fa60e29e45c97bf83b2aa8c6505987f82'
* commit '8c5b3e2fa60e29e45c97bf83b2aa8c6505987f82':
Change browser reliability test to start a new activity for each url
It turns out we were not returning the density for anything retrieved from a
TypedArray... which basically means any bitmap references from a layout or style...!!!
This is now fixed.
Also fiddle with the density compatibility mode to turn on smoothing in certain situations,
helping the look of things when they need to scale and we couldn't do the scaling at
load time.
Since the search UI is handled by the system process, and
the service calls to show and hide it are asynchronous,
the tests that checked the visibility of the search UI were
very flaky. This change sclaes the tests back to just check
that nothing crashes when showing and hiding the search UI.
Fixes http://b/issue?id=1993675
