Ps.
1. content://call_log/calls starts
07-28 17:58:35.930: INFO/ActivityManager(498): Starting activity:
Intent { action=android.intent.action.MAIN flags=0x10200000 comp=
{com.android.phone/com.android.phone.DialtactsActivity} }
2. content://call_log/calls/XXX suppose to start
07-28 17:59:23.549: INFO/ActivityManager(498): Starting activity:
Intent { action=com.android.phone.action.RECENT_CALLS_DETAIL_VIEW comp=
{com.android.phone/com.android.phone.RecentCallsDetailViewActivity}
(has extras) }
On 7月28日, 下午5时42分, Wang He <[email protected]> wrote:
> Dear all
>
> Here in my activity I set a call_log Uri as:
> uri = Uri.parse("content://call_log/calls/4");
>
> I wrote code as:
> Intent intent = new Intent(Intent.ACTION_VIEW);
> intent.setDataAndType(uri, getContentResolver().getType
> (uri));
> intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
> startActivity(intent);
>
> I hope I could read this call_log by auto starting activity "Dialer",
> but got "stopped unexpectedly!"
>
> BUT, uri string "content://call_log/calls" could work!
> So, my question is: Is call log content provider/Resolver cannnot
> support content://call_log/calls/XXX?
>
> Thanks!
> He
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
