| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| | |
Bug: 6485489
Change-Id: I6ad819578d79e332594fc3deb4ec0995220d0697
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now it's launchable with:
adb shell am start \
-a com.android.contacts.action.QUICK_CONTACT \
-d content://com.android.contacts/contacts/lookup/...
Bug 6434853
Change-Id: I41868dcb61a602b02c4de9b6587ed265c975552d
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When selecting different contacts on a tablet, the
animation is to set the contact details pane to white
and fade in the new contact details.
From quick contacts view (from Group or Favorites tab
and launcher screen shortcut), if quickcontact is opened
up and user touches the image, then when transitioning
back to the contact details, the contact details shows all
white and then transitions in the new contact details without
showing the previously selected contact details.
Bug: 6194409
Bug: 6324730
Change-Id: I5f56d46aef338b5d7a22e548548c42054656f381
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apparently the framework first needs to starts the contacts provider just to
resolve the content-type for a shortcut, which is a heavy process involving
a lot of disk I/O.
Remove this by pre-setting the content type to shortcuts.
This will improve the shortcut launch performance from roughly 3.45 seconds to
2.35 seconds on a prime with a test contact in extreme cases, i.e. after:
adb shell kill `pid acore` `pid contacts` ; \
adb shell "sync; echo 3 > /proc/sys/vm/drop_caches"
Also pre-start the provider in Application.onCreate() in order to maximize
the overlap between the app initialization and the provider initialization.
This may or may not help the regular app launch performance too.
Bug 6434853
Bug 6476832
Change-Id: Ia8dcd877dcda2cac562bec18442d7fc019a08ad2
|
|\ \
| |/
|/|
| | |
jb-dev
|
| |
| |
| |
| |
| | |
Bug: 5288751
Change-Id: I8c2c56ca44b5bdca56b7b20a1dfe510ec08a76c3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The tabs in the action bar have been removed for the
tablet form factors and replaced with the action bar
drop down navigation list.
Also, this changes the list item padding in the browse
list on the 7" tablet to extend a little further on the
border to the contact detail panel in portrait mode, so
that more text of longer names can be seen.
Bug: 6426927
Change-Id: Ieced44f5241c3f4f71bdbd7818846e24076fb355
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
card yields in an empty details screen.
In the old code, we even copied the requested URI, which caused the issue
if the URIs for the first request and the second request are different
but still point at the same contact. If we do this, the second result
will have a different requested URI than the actual requeseted URI,
which makes ContactLoaderFragment ignore the result.
This really happens because the lookup URI has variations.
Also make sure not to cache error results.
Bug 6479405
Change-Id: I71254578f0513b391804ee27a21a810bdb6881ac
|
|\ \ \ \
| |_|/ /
|/| | |
| | | | |
jb-dev
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
No longer does SocialWidgetConfigureActivity launch a second
contact-picker when the picker result is returns in a different
device orientation.
Bug: 6478425
Change-Id: I51c6e91afb269f07bf45fb29aa017a0044baa237
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Created a new DialogFragment that shows a ProgressDialog
which will appropriate re-create itself after device
orientation changes. This dialog fragment also has a
parameter to ensure that the dialog is showing for at
least the minimum specified display time.
Bug: 5838580
Change-Id: Ida735c3bea22d1e95f4f4243e98e66c21119871e
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| | |
Bug:6449630
Change-Id: I5aec3ffdd3032bd3d037a053f5cb86fc9f0f16e0
|
|\ \
| | |
| | |
| | | |
jb-dev
|
| | |
| | |
| | |
| | |
| | | |
Bug: 5288751
Change-Id: Ic587ae67501fe43e3c0fbb1abe5be34bb32df076
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| | |
Bug: 6117164
Change-Id: I2ccae66a77031bd1a36a5997ad849af984379471
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Scrollbars in contact details no longer overlay
the contact detail content.
Bug: 6379258
Change-Id: I0f074d9cc74e09a0565b7f2cff2f35359b541a2a
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
When tapping a contact detail photo on any device, the
detail photo will attempt to expand as large as indicated
while still remaining fully on the screen and leaving some
space underneath to show the popup menu options.
If there is no photo, then there will be no expansion
although writable contacts will show a popup menu.
Bug: 6462711
Change-Id: I8f69a1c18dfa10ff0d02b9dbd3ba78043cc7eb4e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Contact details in 7" landscape uses the fragment
carousel to show details with updates. The layout
of the contact details fragment follows the 10"
landscape contact details fragment layout. Dimming
of the detail or updates panel in the fragment
carousel has been disabled, and to be consistent,
this dimming is also disabled on the phone landscape
layout.
Also, this changes fixes the bug with the overscroll
indicators in the contact details pane.
Bug: 6398940
Bug: 6378743
Change-Id: Ie93ab73a9ebad8b66f5bc7d75222f5550ed1b005
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 6399620
Change-Id: I8d6d7f4e75a18745d7127edde9ae3326220d4fcb
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Gave them clearer names and added javadoc.
And added a workaround for the fact that the view notification
service for the google account type is implemented in the sync
adapter, not in the authenticator.
This really needs further clean up.
Change-Id: I567656393fab30293c831fac802884dc84daf861
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In contact details, the name of a particular network
connection has been made to show in secondary text
color and unselectable.
Bug: 6000520
Change-Id: I89d84ad64ad827ce820c854715ca34175e3c7813
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Every time we choose a new contact photo (either an existing one from
the gallery or a new one from the camera), we write the cropped image
/sdcard/DCIM. As a result, the cropped image (eventually) appears in
the gallery, is uploaded to G+, etc.
The new behavior is to write the cropped photo to a temp directory,
and to clear it when we're done with it.
Revert some of the changes from Ib7037a66; we still need to persist
properties in onSaveInstanceState() in case ContactEditorFragment is
killed while the user interacts with the camera/gallery.
Bug: 6423139
Change-Id: Icf8cb5b4824e3d8757ff483ef128527ac9132e72
|
|\ \ \ \
| |_|_|/
|/| | |
| | | | |
into jb-dev
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We were setting a flag in onPause() to ensure that we re-initialize the UI
properly in onResume(). However, this was causing a side-effect when the
background PeopleActivity received loader-notifications that were triggered
by the foreground QuickContactsActivity, because the code triggered by the
loader-notification was looking at the flag set in onPause().
To fix this, showContactsUnavailableFragmentIfNecessary(), gains a boolean
"forceUpdate" argument, which more directly reflects the intended usage.
Also, rename sCUFIN() to updateViewConfiguration(). It's cleaner. And more
accurate.
Bug: 6117162
Change-Id: I35b9f06c0deeffe94d5cf80d4df58a9866387792
|
| | |
| | |
| | |
| | |
| | | |
Bug:6009385
Change-Id: If31cdfd50e9b7295bf8d5ae9c19c9f46172e2f6f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When viewing contact details from a quick contact card, the contact
details appear in a two-pane UI, forming a sort of implicit Up
navigation. As a result, viewing contact details from another task is
in effect a task jump since the user may choose to navigate to other
contacts using the other pane of the UI.
Use the new shouldUpRecreateTask API in JB to determine whether the
trampoline from ContactDetailActivity to the two-pane People activity
should also include a task jump.
Bug:6449430
Change-Id: I90b86873a3a21022d52bb387d9adc5391c8d23ac
|
|/ /
| |
| |
| |
| | |
Bug:6408369
Change-Id: I68c1330f81dbfd2d3eb60be8431f2460e185f2f5
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removed checkbox next to the last "Create new group" option
in popup and removed square brackets in string.
After creating a new group, the view shows the popup again
with the newly create group visible and checked. This is
accomplished via a listener interface to the
GroupCreationDialogFragment. The tricky part to this is if
the user changes device orientation while the
GroupCreationDialogFragment is open. The ContactEditorFragment
will save the resource id of the RawContactEditorView (since
there can be many via joins) and the view id of the
GroupMembershipView which is the listener.
Bug: 6013015
Change-Id: Ia50a68fb6f4631995ae913182765efb24ef227ec
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove unnecessary padding view, and adjust the section-header heights
directly. Now the height is what UX has wanted for a while.
Bug: 6427081
Change-Id: I83180ccd4ae7f27bcd504d93321a38523d8280c5
|
| | |
| | |
| | |
| | |
| | | |
Bug:6138459
Change-Id: I7c76e70d20bd483d3599d9e28f81e5ef7477477d
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This activity doesn't handle orientation changes right. Let's just close it
on any configuration changes. This activity is kinda like a popup, so it
should be okay.
Now this activity handles all config changes by itself, so we can remove a lot
of things, such as onSaveInstanceState and PendingPhotoResult.
Bug 6236774
Change-Id: Ib7037a66d092c8d9a285224ea4cf70e7da8ff1b5
|
|\ \ \
| |_|/
|/| | |
|