packages_providers_ContactsProvider.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Changing call log adapter to normalize phone number where possible.	Tyler Gunn	2014-06-30	1	-0/+11
\| \| \| \| \|	Bug: 15616526 Change-Id: Id8fe981a622bdea786a48cbadf9ff08289ae3987
*	Filtes out legacy number in call logs	Christine Chen	2013-10-01	1	-0/+12
\| \| \| \| \|	Bug: 10966248 Change-Id: I297925f336114d98c1109158e19546e81f03fe90
*	Reorganize import in contacts provider	Makoto Onuki	2012-06-27	1	-5/+4
\| \| \| \|	Change-Id: If3afb134ea36bd93859efcd114885526e1592b91
*	Lazily-initialize PhoneNumberOfflineGeocoder/PhoneNumberUtil	Makoto Onuki	2011-08-30	1	-7/+29
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	- 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
*	Renaming com.google.i18n.phonenumbers to com.android.i18n.phonenumbers	Shaopeng Jia	2011-08-12	1	-4/+4
\| \| \| \| \| \| \|	to avoid name collision. Bug: 5157607 Change-Id: If7db52ae5eba1696d20e9897860d757021477002
*	Automatically add a geocoded location to entries in the call log.	Flavio Lerda	2011-08-10	1	-0/+82
	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