| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
- PhotoPriorityResolverTest
Now the mock sync adapter needs an intent filter
- LegacyContactsProviderTest
The authority check in ContentProvider got tightened, which broke our test because
we didn't set up the multiple authorities correctly.
Change-Id: Iab1eed24434bd159a99f0b794a7756554dc02281
|
|
|
|
|
|
| |
Bug 5261517
Change-Id: I6c16bb1f9897589beec222fc63ad899cd478b923
|
|
|
|
|
| |
Bug:6202229
Change-Id: I88a9a9bb72921f7a3ed80aebe40935656a92eb3a
|
|
|
|
|
|
|
|
|
| |
This should help avoid running out of memory when running the test
suite.
Bug 5199245
Change-Id: Ibb2591c3f58777c680eba8f5a89a6cc01f09c198
|
|
|
|
|
|
|
|
|
|
|
| |
In the new logic, we'll pick the largest photo (in pixels, using file
size as a tiebreaker for display photos) to determine photo priority
if no super-primary is defined.
If this logic doesn't pick a winner, we fall back to the old photo
priority based on the account.
Change-Id: I9cf58b86a6c22bcf671a4852606a4534fa0fa7da
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change adds support for storing large photos for contacts in the
file system. Large photos passed to the provider will be downscaled
and re-encoded as JPEGs before being stored in the usual data BLOB
field (for the thumbnail) and in the photo store (for the display
photo).
See go/large-photo-design for details.
Change-Id: I26a69ac2ccba631962a3ac5c83edb3f45d7cfc7f
|
|
Discussed the solution with Tim Sullivan, got a Dr.No approval
for fixing the issue in FroYo and for the solution itself.
In two separate CLs we will set picture priorities for
Facebook (5) and Twitter (3)
Bug: 2535693
Change-Id: I3d90474d92b58db2845a43658845176260c24812
|