| 778df2417da0c0186862b25519ce65ed633a9b6d |
|
01-Jul-2014 |
Tyler Gunn <tgunn@google.com> |
Changing call log adapter to normalize phone number where possible.
Bug: 15616526
Change-Id: Id8fe981a622bdea786a48cbadf9ff08289ae3987
/packages/providers/ContactsProvider/src/com/android/providers/contacts/DefaultCallLogInsertionHelper.java
|
| a16c2509fa398159988861a3fc8408b493fa445b |
|
01-Oct-2013 |
Christine Chen <christinech@google.com> |
Filtes out legacy number in call logs
Bug: 10966248
Change-Id: I297925f336114d98c1109158e19546e81f03fe90
/packages/providers/ContactsProvider/src/com/android/providers/contacts/DefaultCallLogInsertionHelper.java
|
| 38210445730ee04c351c7cc1b3800cfe23e34325 |
|
27-Jun-2012 |
Makoto Onuki <omakoto@google.com> |
Reorganize import in contacts provider
Change-Id: If3afb134ea36bd93859efcd114885526e1592b91
/packages/providers/ContactsProvider/src/com/android/providers/contacts/DefaultCallLogInsertionHelper.java
|
| c4144727cd740079f47e74ae5078d1613874f72a |
|
29-Aug-2011 |
Makoto Onuki <omakoto@google.com> |
Lazily-initialize PhoneNumberOfflineGeocoder/PhoneNumberUtil
- They were indirectly created in VoicemailContentProvider.onCreate and
CallLogProvider.onCreate, and were slow. It was taking ~300ms on my
measurement on a nexus-s. Also it touched the filesystem, so it can
be much slower on worn-out flash or when flash is busy.
- Doing it in a provider's onCreate means it affects auto-complete
performance if acore is not started. Also it'll affect app-startup
when we merge processes.
- But they were actually only used when inserting a call log, so we don't
have to initialize them at startup.
- Inserting a call-log should be done in a worker thread, so lazy-
initialization shouldn't cause laggy UI.
(Alternatively, we could initialize them in a worker thread at startup,
but I don't think it's worth it.)
- Also, now CallLogProvider and VoicemailContentProvider share the
same instance of DefaultCallLogInsertionHelper.
(They used to have their own)
same instance of DefaultCallLogInsertionHelper doesn't have any
instance specific state, so this should be safe.
Bug 5220669
Change-Id: Ibcd664ed683507c5dcac88bec736e4903a4a7032
/packages/providers/ContactsProvider/src/com/android/providers/contacts/DefaultCallLogInsertionHelper.java
|
| 32f5e00ffc769059731056a47aadf183ec948d1a |
|
12-Aug-2011 |
Shaopeng Jia <shaopengjia@google.com> |
Renaming com.google.i18n.phonenumbers to com.android.i18n.phonenumbers
to avoid name collision.
Bug: 5157607
Change-Id: If7db52ae5eba1696d20e9897860d757021477002
/packages/providers/ContactsProvider/src/com/android/providers/contacts/DefaultCallLogInsertionHelper.java
|
| aeaba441ddb05dede8bd86291ca78f42d670d54c |
|
09-Aug-2011 |
Flavio Lerda <flerda@google.com> |
Automatically add a geocoded location to entries in the call log.
This change adds a geocoded location value to entries added to the call
log.
One limitation is that this is unaware of changes to the locale. We
needed to decide whether this is fine or if we should update the stored
geocode on locale changes.
Bug: 5129581
Change-Id: I2ad1b3fbd24491df2febf3e1fd615c16dd74398f
/packages/providers/ContactsProvider/src/com/android/providers/contacts/DefaultCallLogInsertionHelper.java
|