Age | Commit message (Collapse) | Author |
|
contact is added to the favorites.
To conserve resources synced contacts only have the low-res icon by default, and the hi-res photo is only synced when the contact is viewed.
When a contact is "viewed" in dialer, dialer should send a ACTION_VIEW with the contact URI to the sync adapter service.
TEST=TAP
Test: TAP
PiperOrigin-RevId: 202373390
Change-Id: Ie3a173b7c3f442dc806a719910aea9b3a6c5cf4f
|
|
Moving it outside contacts.commons reduces dependency to legacy code. Also removed redundant implementations such as caching SharedPreferences (it is already cached), custom ListPreferences (standard ListPreferences already have what we want), and corrected preference storage location (allow standard ListPreferences to work)
TEST=TAP
Test: TAP
PiperOrigin-RevId: 202000393
Change-Id: I45374e610b3510784b5a4da92e5d8462cbfc92bb
|
|
Test: manual
PiperOrigin-RevId: 201745094
Change-Id: I7ba7b0d8063f056f0c5edb44c7649a1c807f6549
|
|
X. Pinned contacts are now saved onPause
4. Large display size no longer crops images
14. If ViLTE is disabled, IMS_VIDEO channels won't be added.
Bug: 78491298,79876391,79876661
Test: manual
PiperOrigin-RevId: 197068627
Change-Id: I642a11d684c648b7f6579792313b09eabb09a9fa
|
|
Bug: 78922118
Test: tap + manual
PiperOrigin-RevId: 194971448
Change-Id: I906250cb83c17198fac87f5ad6d3014cc8a34db2
|
|
App would crash when users attempted to remove a starred contact because we try
to update Phone.CONTENT_URI, which is not allowed. Test assumed that
we could update PHone.CONTENT_URI, which is why this wasn't caught.
Updated the test to verify the contact in Contacts.CONTENT_URI get updated to
starred = 0. Unforunately, since fakeContentProvider doesn't work exactly like
cp2, the update won't propogate to Phone.CONTENT_URI, so out test is less than
ideal, but it should cover our bases.
Also updated the image and text for starring a suggestion.
Bug: 78923466
Test: tap
PiperOrigin-RevId: 194962080
Change-Id: I9f8f71d70ba83510682890917081380a3c51cd7a
|
|
This is triggered by long pressing a SpeedDialUiItem and selecting remove in
the resulting menu. This will remove it's assocaited entry from the
SpeedDialEntry database and if the contact associated with the SpeedDialUiItem
being removed only has one speed dial entry, additionally we will unstar the
contact as well.
Bug: 77761023
Test: WIP
PiperOrigin-RevId: 194606709
Change-Id: I4d6fb104a388c39c77796f7626cd63e991303a51
|
|
Bug: 78491298
Test: WIP
PiperOrigin-RevId: 194323952
Change-Id: I6883ce1506684c93cb5538ebbc0e14aecc300a00
|