Fix tests broken by proguard

Bug: 3466915
Change-Id: If506bba3142c7b8fd8ef3a8033693925f51da2ca
Trim parts of the contact name before joining.

This fixes sorting of names that start with a space.

Bug: 3395927
Change-Id: I6d8d8d5047526e64081a33bd008cfb531c3f7328
Moving updateRawContactDisplayName from aggregator to dbhelper

This is done in preparation for a fix of

Bug: 3488074
Change-Id: I0456a6925a76a4974d7a76ab4dce326f5637d871
Displaying name prefix in the list and detail panel

Bug: 3488074
Change-Id: Ieb13337edbec01dcbd9581500420f47213f972e5
Preserving dot in name prefixes like "Mr." and "Prof."

Change-Id: Ife9324d8429961468a6ef3074feb374a63b989f0
Add test for vCard.

Need I0da5af56bf04e8eafbef376668a09002cb62d3f5

Very simple one. Definitely we need more, but this is
first step anyway.

Bug: 3156956
Change-Id: I715c2b14c5175f1ff46fd75cf6790262712d5bc2
Use old version of vCard composition method

Must be after I91b65f881e1712ecf82c2e119a92bc70c43c623c

Bug: 4066223
Change-Id: I2667a91d90b1ce985a354a5a37de75bb8156cff8
Use new interface for vCard export

Bug: 4066223
Change-Id: Ie21c8966b0bb5b73b3afd18bfe7c142b523413c4
Add "primary account" support.

Two query params "PRIMARY_ACCOUNT_NAME" and
"PRIMARY_ACCOUNT_TYPE" allow users to supply
a primary account associated with the query, which
enables contacts provider to optimize query results.

For example, in an email composition screen, users may
want to promote email addresses related to an account
selected as a "from" field. This change allows the
client to let the contacts provider know the account.

Must be with I2a22be56822226e3ea6b6f2ef23bb77816d0345a

Bug: 3510087
Change-Id: Ibce363d336cb3e3a1fca10bddbd912ec96e4b059
Don't create E164 numbers during update (country detector not ready)

Bug:4174796
Change-Id: I1e69253e6c9968f4d52b3213acc09395568a77c2
Rewrite subquery to make better use of indexes

Bug:4021462

Change-Id: If14d2c6b2e3a57c27bf16387295d45d23df52465
Move snippet logic from DB to a cursor wrapper.

This results in a huge performance boost when doing searches and filters across
large Contacts DBs, since the expensive snippet() function (and associated
joins necessary for its logic) no longer need to be run for each record
returned; instead, the snippetization is only done as each entry is retrieved
from the cursor.

If the query string entered by the user consists of multiple tokens, the DB
snippet() function will still be used.

Bug: 4021462

Change-Id: I60ce69b4506bc7f770f139c127f859689b05f2d3
Handle zero-query case for global search.

When a request for no query is received, return recently contacted
contects. This is used to show recently contacted contacts in QSB
when it is first launched.

Bug: 4306122
Change-Id: Ic7b492c400d80be9661afc32a539c9317d7f73ef
Fix issues with Contacts sync.

We were wrapping cursors on Contacts queries too aggressively - the only cases
we should be wrapping with a snippetizing cursor are when the query actually
contains a snippet column.

Bug: 4382294
Bug: 4378350
Change-Id: I0bd007afde0bb850e88f5953f5efcfddbda0e2e4
Merge "Fix issues with Contacts sync."
Fix wrong handling in getQueryParameter()

ContactsProvider2#getQueryParameter() wrongly
interprets long parameter name as shorter one which is
substring of the original.
(e.g. "longer_param=value" is also treated as "param=value")

Bug: 4260119
Change-Id: Ide096589106984a5d99e70f754830d7943a7ac5c
Fix search support tests.

Bug: 4382711

Change-Id: I48faaadeafa4e265fc8d72382a0e91b071b9215e
Reconcile with honeycomb-release

Change-Id: Ie2453cf52a38c62495ba6e40226a406e40ebdc4a
Import revised translations.

Change-Id: I0192447888f86e036ffeef5105c3dcf981c44424
Enable selection strict mode and sql injection tests

Bug:4368912
Change-Id: I3f854a54e402f366be9bc6712a6188b4537b990b