| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Fix tests to account for fixes made in ICU 50. Add some additional tests.
Bug:
Change-Id: I7d1fb0588f56b58da5c5177823ed5c16c4603e24
|
|\
| |
| |
| | |
jb-mr2-dev
|
| |
| |
| |
| | |
Change-Id: I81c749401c54c9f3facc921b7bc4e778a33ea22e
|
|/
|
|
|
|
|
|
|
|
| |
Switch from using native code registered as sqlite callbacks to using
JNI wrappers for accessing ICU AlphabeticIndex. Stop using specialized
sort keys for Simplified Chinese because ICU code can correctly label
the characters directly.
Bug:
Change-Id: I0568b3a406495c147c7b9b3e72835d11d93f9d16
|
|
|
|
|
|
|
|
| |
Switch from using hard coded tables copied from ICU to calling ICU
Transliterator directly for Pinyin transliteration.
Bug:
Change-Id: I87aae623dfe049a90cee213182275aa51a7dcd9c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When contacts provider internally recurses into itself, we need
to clear the binder calling identity before doing so, so that it
is consistent with the calling package name we will now be using.
Note that this also means that we won't be doing any further
permission checks against the original caller for these internal
provider calls... which is probably more correct anyway, because
we've already done the permission check on the original incoming
URI and we wouldn't want that to now fail due to some permission
strangeness on another URI it is using internally.
Change-Id: Icc3903287f91f35959a80168a6c107b1803f93a8
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix issue of contacts appearing under wrong label--sort contacts by
sort key, not by label.
Fix handling of labels that require more than the first character
(eg Czech 'CH') by using entire sortkey--not just the first letter--
to determine label.
Bug:7351596
Change-Id: Iaabc63041540f621220d0463df3e0850684caa94
|
| |
| |
| |
| |
| | |
Change-Id: Ic347ccd02c4a6a9956824df0ee18a869e69ddce9
Auto-generated-cl: translation import
|
| |
| |
| |
| | |
Change-Id: I899c3ae507a0e4feb95c8142b09b92e1fd87eefe
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 6987476
Change-Id: I99816c32938b5b3db5f79d816d91d814ab9dca6c
|
|/ /
| |
| |
| |
| | |
Bug: 7942098
Change-Id: I0c43b6e78471631f6400d836311ec84658f063c9
|
|/
|
|
|
| |
Bug: 5930716
Change-Id: Ic7cfffae5de878be683d27f92ccb5b034dc217c3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previous CL I9cbdf10d21c79f53bc621bacb7eeeb95a6a2435f fixed missing
punctuation at the start when searching without punctuation. (e.g.
{hello})
This CL fixes the case where leading punctuation is missing if you searched
with a leading punctuation. (e.g. {'hello}). The content provider
uses a different code path when it detects multi-words and snippeting
is actually done in sqlite using the FTS snippet method. The check for
multi-word was treating {'hello} as two words.
This means that multi-word searches will still have this issue as it still
uses the sqlite snippet method. Leaving this to a separate CL since it's
a riskier change.
Bug: 5929143
Change-Id: I4c2451b2e8eb47d5831e6ef6cfcca538ff3599b9
|
|
|
|
|
| |
Bug: 7709971
Change-Id: I1a7eff95ff76e21b3b29535f09c95591469b707f
|
|\
| |
| |
| |
| | |
* commit '75a0a0b0ece29241b4712126af53841d5dcdb442':
Change default sort order for email queries.
|
| |\
| | |
| | |
| | |
| | | |
* commit 'dacd5de146b413de86d38b6f56a3fe0b2af4b155':
Change default sort order for email queries.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Prioritizing "default" emails over last used emails.
- Added ordering for same domain emails as last order by.
Bug: 7183241
Bug: 7346215
Change-Id: I6a8ba3cfe08792693eec4896f16853a88713bc3f
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit 'b036f6745c97e7bd654ee1b44122ceece917dd47':
Rebuild SQLITE_STAT1 table after drop operations.
|
| |\ \
| | |/
| | |
| | |
| | | |
* commit 'f5c0020b87709f9c4c3de66a49c0893e2c2adebb':
Rebuild SQLITE_STAT1 table after drop operations.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The SQLITE_STAT1 table has the estimated number of rows for each table and
index, which is used to calculate a query plan for queries.
The problem is that, DROP TABLE and DROP INDEX appear to remove the
corresponding row from the stats table. This could cause SQLite to choose
inefficient query plans.
This CL will make sure to rebuild the stats table after such operations.
Added a new boolean paramter rebuildSqliteStats to all methods that
exectue DROP TABLE/INDEX. If it's set, they'll call updateSqliteStats() to
rebuild the contents.
Bug 7426624
Change-Id: I1c373b902856d1a24b6c0c8379899a235ee284c4
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Switch com.android.internal.util.Objects to com.google.common.base.Objects.
Technically this change is not necessary for the provider but it nice to
use the same code everywhere. And since the provider already has a
dependency on guava anyways, this doesn't hurt.
Bug: 6948882
Change-Id: I565d65f00b1f25c4ae1bf3c8086c10ab2f31dfd5
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | |
| | | |
jb-mr1-release - do not merge
* commit '1e6561ddfc941d51592a4285c8fe2d054ed29f02':
|
| |\ \
| | |/
| | |
| | | |
* commit '17f1fe1a960db78c84aaa753c784a4df513a1d3d':
|
| | |\ \
| | | |/
| | | |
| | | | |
Change-Id: I8819d77d2cd0f33d9f4e5553a5b2d4639fe4ec47
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
locale safe"
* commit '94fc236d199460bddc390ce7f384b446c14df622':
Make CONTACTS_AS_MULTI_VCARD locale safe
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
* commit '0e014723e6d5d2acc3d59b78cee9a6d1fbfef1e9':
Make CONTACTS_AS_MULTI_VCARD locale safe
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* commit '2a9d1fab1669d2962aa830872f063c1180fbea94':
Make CONTACTS_AS_MULTI_VCARD locale safe
|
| | | |\ \ \ |
|
| | | |/ / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
SimpleDateFormat was used with the default locale to build
SQL statements; this is unsafe for some locales. Switched
to Locale.US.
Change-Id: I7307b12e1f3d796e1bb4a73d97918d0162ca971e
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | | |
* commit 'ffed1ede87553f8d6a104a5e92945fd5fa4557f9':
|
| |\ \ \ \ \
| | | |_|_|/
| | |/| | |
| | | | | | |
Change-Id: Ib983813de597b2eabfc0e4657a5945c8791a5c88
|
| | |\ \ \ \
| | | |_|_|/
| | |/| | | |
|
| | | |\ \ \ |
|
|\ \ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Passing CancellableSignal from ContactsProvider2.queryLocal to
GlobalSearchSupport.handleSearchSuggestionsQuery,
GlobalSearchSupport.addSearchSuggestionsBasedOnFilter and
SQLiteDatabase.rawQuery.
Search App needs this change to cancel queries for search suggestions which are
no longer valid due to some user action.
Change-Id: Ie019afff31bf49ba96a88899e829813075ab141e
|
|\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| / / / / / /
| |/ / / / / /
| | | | | | | |
* commit '0a78ee3aeeb33711d44993be61e3d48f78e2d640':
Make sure to rebuild search index on locale changes...
|
| |\ \ \ \ \ \
| | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
* commit 'd2f6ad6d50b5570327f8cca3b2d2bdcaec36ea90':
Make sure to rebuild search index on locale changes...
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
so that search will still work even after changing the locale.
- Rebuild the search index upon locale changes, as it contains
locale-sensitive data.
- Also make sure to update the in-memory collator in NameNormalizer
upon locale changes.
- Rebuild the search index on the next db upgrade in order to fix the
search index which already contains invalid data.
Bug 7251461
Change-Id: Id579a67de792a52a0091bf76d7c5d374f76f1639
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
* commit '54658c3ede6c33fe5e62f9895fa509776973002e':
Make sure to invalidate fast index cache when
|
| |\ \ \ \ \
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
* commit '9ff2587608416b4378767141ad396f51f23040a7':
Make sure to invalidate fast index cache when
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
aggregation changes.
Bug 7249008
Change-Id: I6022dca2e56a6a4cdfcde4d936289881a40d1012
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | | |
* commit '863474b4a1a118d1d9181cf46f3466ccd0efa6b2':
|
| |\ \ \ \ \
| | | |/ / /
| | |/| | |
| | | | | | |
Change-Id: Ibdb66a3b7b73717c90a2b08f6c2d2cf6c237b8ce
|
| | |\ \ \ \
| | | |/ / /
| | |/| | | |
|
|\ \ \ \ \ \
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
* commit 'a78c7b6f1168f12d46dc0f880124c3cf3b7d80eb':
Remove Secure setting usage.
|
| |\ \ \ \ \
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
* commit '7b4a5d522df5282cd7dac655b4c673c06d1f449b':
Remove Secure setting usage.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: 7232230
Change-Id: Ie40bda16e24df96530c80506a74747a4b2c16cb5
|