| 76821d02351701b3829aa5754dd9a86e417f635f |
|
10-Oct-2011 |
Flavio Lerda <flerda@google.com> |
Only show recent items in the new section.
This commit limits the set of items in the new section to items that
have been receiving within the last 7 days.
In order to make the unread items more visible even when they are not in
the new section, use highlighting on them, both in the text and the play
icon.
Bug: 5403047
Change-Id: I577c58bfcb9ef2031839092d50f41c357c7decba
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|
| 74628686391735dac1b13409e7f61e9f1514ea20 |
|
06-Oct-2011 |
Flavio Lerda <flerda@google.com> |
Remove strict mode violation with number formatting.
The call log is currently performing formatting on phone numbers in the
main thread (during bind view).
At the same time, however, we are always doing a background request to
look-up the contacts. Move the formatting call to the background thread.
In order for the right information to be shown as soon as the call log
is opened, we also need to store this information in our cached values
in the database. This means that the number will show unformatted the
very first time, and then updated once the background require is
completed.
Bug: 5316982
Change-Id: I20d1971948afa33c7825f0bd38a9520021f75378
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|
| 55e30c7a0feb8fe533b489c6c053454bfb2eb155 |
|
05-Oct-2011 |
Flavio Lerda <flerda@google.com> |
Revert "Remove strict mode violation with number formatting."
This reverts commit bbe62216b5163ec53eb990218bdbe608631dd8e7
Broke the build.
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|
| bbe62216b5163ec53eb990218bdbe608631dd8e7 |
|
28-Sep-2011 |
Flavio Lerda <flerda@google.com> |
Remove strict mode violation with number formatting.
The call log is currently performing formatting on phone numbers in the
main thread (during bind view).
At the same time, however, we are always doing a background request to
look-up the contacts. Move the formatting call to the background thread.
In order for the right information to be shown as soon as the call log
is opened, we also need to store this information in our cached values
in the database. This means that the number will show unformatted the
very first time, and then updated once the background require is
completed.
Bug: 5316982
Change-Id: If1e4990243e73af6c9519fbf5e76a5d234e99e15
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|
| 4813c270af2b5d904437757807541f1f5e19bb93 |
|
19-Aug-2011 |
Flavio Lerda <flerda@google.com> |
Use the call log to cache additional contact information.
The new version of the call log needs a bit more information about the
matching contact (if any) to render its entries.
This change both uses the newly added columns in the call log to lookup
this values and stores the updated values back into the call log.
These values are used for setting up the quick contact badge and
formatting the phone number.
This also fixes a few smaller issues:
- the phone number shown used to change format between the initially set
value to the one obtained from the contact: this value is now cached.
- we were using -1 as the id of a non-existing contact, but 0 is
actually the value used elsewhere for this, so stick to that.
- make sure we use the cached value from the call log for formatting.
- update the call log if there was no previous value.
- introduce a UriUtils with a couple of useful functions for handling
URIs.
Bug: 5101753
Change-Id: I22f2b03b234da91e02dbeebe11a94c2f56295a3d
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|
| b5f6432139f887e6f65e1206e927f57cfb670cc6 |
|
13-Aug-2011 |
Flavio Lerda <flerda@google.com> |
Use the content of the call log to predict the contact info.
This change re-instroduces the cache stored in the call log table for
the contact info associated with a call.
This is the first part of the necessary changes. In this change, I also
use the stored information, I do not update it when the contact is
actually looked up in the call log.
Bug: 5101753
Change-Id: Ib906e9af06410c2cc295192cd4623b011fa0ad09
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|
| 568ad27e706d7c75dd7412e34c2236c772704a04 |
|
13-Aug-2011 |
Flavio Lerda <flerda@google.com> |
Extract nested classes from CallLogFragment.
This should help making the changes to the CallLogFragment easier to
make as there is less code around.
This has been done entired using Eclipse's refactoring with no manual
changes.
In the process, a couple of fields have been expanded from private to
package, because, while their were private, they were being used by
the parent/nested class anyway. I will fix those in a follow-up.
Bug: 5101753
Change-Id: Id46e18cfa86939100342daa020430063959dfcfc
/packages/apps/Contacts/src/com/android/contacts/calllog/CallLogQuery.java
|