Denis Souza wrote: > Ok, bad choice of words... still, I can generate requests to a the > call log's content provider. Does that mean that HTC likely replaced > the content provider with a buggy/restrictive version?
I have always considered CallLog to be read-only. It is only a matter of time before somebody realizes the problems inherent in it being read-write (e.g., forging outbound phone call records) and locks it down. I am rather surprised the core Android team hasn't locked this down yet. However, given your apparent symptoms, it is likely that HTC replaced it, and equally likely that the CTS doesn't test a read-write CallLog very much. > If that's the > case would there be another way to change that data without root > access? Probably not. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
