| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ListView used in call log will execute lot of SQL queries and
load lots of data, as a result, getView function will cost lots
of time to load data and draw views. This will reduce the FPS.
When list view is flinging, we try to avoid to load data and bind
views. We will reload the data for visible items in list view when
list view's scroll state is not flinging.
Change-Id: I1149f90d8ecb3723598a60ca66105214b3731b27
CRs-Fixed: 755408
|
| |\ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Dialer set add participant extra with the call intent
irrespective of call exist. This leads to no Call UI
display if dial a number immediately after add a
participant and end the conf call to use same dialpad
which launch earlier when the participant added.
Add code to set add participant extra if user clicks
on add participant and there is a call exist.
Change-Id: Ifa18b26ed9ccd368afb930382d5e8aeaf8e9511a
CRs-Fixed: 817666
|
| |\ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By MAT tool, we find there exists several PopupMenu
objects after repeating operation "dial 10086 -> hangup"
several times. It's not right, there should exist only
one object of PopupMenu for DialpadFragment. This PopupMenu
object occupies 40 byte but indeed causes memory leak.
The root cause is that we will call onResume() after hangup
every time, onResume will new PopupMenu every time and set its
mDragListener to overflow image button's mOnAttachStateChangeListeners,
this listener references PopupMenu object and causes PopupMenu can not
be released by GC.
We create PopupMenu in onCreate instead of onResume to avoid
this leak.
Change-Id: Id787bc5e23f9d5f86a9fa03536e9ae901e12cb13
|
| |\
| | |
| | |
| | | |
incomplete"
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Widget.Material.ActionBar has 16dp to the right as the parent of
DialtactsActionBarStyle, and it will cause no enough room to show the text
"Type a name of phone number".
Override ActionBar title offset to keep search box aligned right.
Change-Id: I1a8878932f4517593cbfd628c27aba1228339e75
CRs-Fixed: 809652
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The phone account icon is covered by the tint
which is set in app side.
No need to set the tint in app side, when create
the icon, it has been already set in framework.
Change-Id: I91fba4e760fe3bfb52e4554041b0093f4de18e5e
CRs-Fixed: 809501
|
| |\ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The view that invoked the options menu, it's layout direction is "ltr".
So we change the view's layout direction to "rtl" in RTL mode.
Change-Id: I1586fd283312d3d1b997167d8d8d8486f1660f32
CRs-Fixed: 816280
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The string "call_log_blacklist_header" did not have Chinese string.
Add Chinese string for "call_log_blacklist_header".
Change-Id: I57c0d0290dab86219305bec767b8c320e51fddcb
CRs-Fixed: 813626
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
App does't change the popupmenu to right side in RTL mode.
When create the PopupMenu, set PopupMenu with Gravity.START in Dialer.
Change-Id: Ic1536f867c67e7ebb522fbba78b4ad26f2357fec
CRs-Fixed: 813015
|
| |\ \ \
| | |/ /
| |/| | |
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When reenter the DialtactsActivity, because phone state is offhook,
it should show dialpad chooser, but immediately due to sub2's call
state is idle, then the dialpad chooser is hidden.
Only when the phone state is idle, we hide the dialpad chooser.
Change-Id: I9eeecff316a6e658ceb278473550865f249980e1
CRs-Fixed: 809521
|
| |\ \
| | |/
| |/| |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- The smart dial search normalizes the dial string and removes
anything other than digits
- Pass original dialed string instead of normalized dial string
to fix this issue.
- Original dial string contains the number which is actully entered
by user. Pass this number as it is as dialed number validation is
already taken care by APIs defined in PhoneNumberUtils.
Change-Id: Ib85750abef765ace127ebde3a13397b4dfad48fa
CRs-Fixed: 806046
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are some compilation errors when upgrade
with some selective google L_mr1 patches.
Change-Id: I252078ab115d28184fd03c4f63024e671c59be88
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make sure that we check for the index to exist in the list before
we query for it. The problem is that the index is grabbed from the
listview but then applied to the contact entry arraylist. It is
possible that these two are out of temporarily out of sync. This check
will make sure that we do not throw an exception in those cases.
Bug: 19103509
Change-Id: Iba620ec859866b9f8bfc2614a17b1b1a11037230
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit c1ae1c6e7b2805726701d03dfa57d8e0c98a3036
Change-Id: I2290d832e1105d540dc9398a6d3f27a07d139ed2
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18933278
Change-Id: I1b351de91c54b7273d9af6f8ea425b4837cc4d8e
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the shortcut card was hidden due to the call log being cleared, the
offset for the overlapping pane needed to be recalculated based on the
new height of the top portion of the dialtacts activity.
Bug: 18849546
Change-Id: Ib5953a2a537e9a7520d4f022e43fa974f67eb410
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This CL fixes a bug that could result in the progress dialog
that appears when clearing call logs to never be dismissed.
The cause of this bug is a race condition that causes
the original dialog fragment to be detached from the parent activity
before the progress dialog is dismissed.
If that happens, the progress dialog is never dismissed and stays
on screen forever. This CL fixes this by assigning the activity to
the dialog explicitly and retrieving it when trying to dismiss it.
Bug: 18836384
Change-Id: I5f8941e13dc7eb962b23e828cf47bc64f2b1a2aa
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18796407
Change-Id: Ib3001ac08e64b4efa04a2d9915abe2177475bbe1
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't crash if unable to update the call log contact info cache because
the disk is full.
Bug:18770948
Change-Id: I4156581df0742d58ed28eeb0c767923e0bc78507
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use listview instead of root view as parent when inflating
footer view so that it is always inflated with AbsListView.LayoutParams
Bug: 18762303
Change-Id: If9f5a38017d07d35962881750e2b403aa95287cb
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's possible that it may no longer be necessary to dismiss this
specific dialog. For example, there may have been a rotation; in
those cases, we expect the DialogFragment to cleanup/dismiss its
own dialog.
Bug: 18728214
Change-Id: I307c299b1f0a6dabebaf4ac6af1d126bf548b190
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18738114
Change-Id: I3148d6c78561bf369d4ddbab09bf2fb9c7a7966b
|
| |\| |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18678952
Change-Id: I2f15cad4b71ba780e6ed860b5dd67c745a3b4823
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Traced through the original bug report; the problem is that a call to
TextUtils.expandTemplate was being made with a null 2nd parameter.
I traced through the callers to find out where a null could be introduced
and I was unable to identify a potential source. This change introduces
a last-ditch null check to protect against problems upstream.
Bug: 18684529
Change-Id: I7b608dfedf052d6933e94d1f23a658763b66059a
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1. For recent call entries with a name and phone number, the name will
now also be added.
2. For recent call entries which have complete address information provided
by nearby places, all information except the contact photo will be added. The contact photo is
excluded, as the ContactsLoader would attempt to load the contact photo
while parsing the contact information. On a slow connection this could
cause a noticeable pause while adding the contact.
Bug: 17308163
Change-Id: If2e78bd1257096b344ff2dd266dcdbaeed4f1471
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Add CircularRevealActivity to Dialer manifest
Bug: 18373617
Change-Id: I76e89fe1be628746dfa96c877aedd24abeec7350
|