How do you modify the call log

by Seer » Sun, 12 Apr 2009 18:37:45 GMT


Sponsored Links
 Can anyone tell me how to modify the call log?  What permissions do i
need and is it possible to get some basic code to show how?  just a
few lines not whole classes or anything.

thanks

Chris
--~--~---------~--~----~------------~-------~--~----~



How do you modify the call log

by Mark Murphy » Sun, 12 Apr 2009 18:54:32 GMT


 


You don't, AFAIK. That is handled by the firmware.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

_The Busy Coder's Guide to Android Development_ Version 2.0 Available!

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


How do you modify the call log

by Seer » Sun, 12 Apr 2009 19:05:22 GMT


 You can at least read the call log right? Do you know how to do that?
maybe i can start from there to write code to modify it.  The issue i
have is that if my contact phone number is 555666 then i modify the
outgoing call to call 1122,555666.  Problem is i want the call log to
show i called 555666 not that i used a calling card like service.






--~--~---------~--~----~------------~-------~--~----~



How do you modify the call log

by Mark Murphy » Sun, 12 Apr 2009 19:15:31 GMT


 


Yes.


Use the CallLog.Calls content provider. You will need the READ_CONTACTS
permission.

It is possible that with the WRITE_CONTACTS permission, you will be able
to do insert/update/delete operations on that content provider. I seem
to recall trying that and it not working, but that was some time ago.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

Android App Developer Training:  http://commonsware.com/training.html 

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. How to notice deprecated fields/methods

Android 1.6 SDK has some deprecated fields and methods that are
annotated with @Deprecated. But they are not marked deprecated in the
api documentation (which supposedly happens automatically with
Javadoc).

This might be a bug with the way the api docs are generated.

Is there a way to notice deprecated fields and methods in the api
reference?

For example, android.util.Config has some deprecated fields that do
not show as deprecated in the online reference -

  36     /**
  37      * Always the inverse of DEBUG.
  38      */
  39     @Deprecated
  40     public static final boolean RELEASE = !DEBUG;


--~--~---------~--~----~------------~-------~--~----~

2. Make different instances of a widget behave different based on their appWidgetId

A solution (or rather a workaround) was found.
I am posting this for future reference:

It was simpler than I thought, but it didn't occur to me or my friend
with whom I am developing this widget, until he recently came up with
this simple solution.

It consists in having the different flags selected by the users in the
configuration activity appended as strings to the intent action.

That way, if you want some instances of your widget to behave by
outputting sound and others not, setup different action strings
accordingly.
(for example, "action_button1_sound" if the button should output
sound, and "action_button1_nosound" for the opposite behavior.

If you have more than one flag you can set in your configuration
activity, as it is in our case, you'll have to manifest all possible
combinations in your intent-filters. You don't have to parse the
intent action string, though, as that is only needed so the intents do
not overwrite each other.
Therefore, you can now read the arguments passed through the extras
and make the buttons behave accordingly.

If someone finds a nicer solution I will be happy to hear about it!

thanks!



--~--~---------~--~----~------------~-------~--~----~

3. application with root permssion

4. Maps API Add-Ons Device Support?

5. Webview with progress and url overriding

6. Unknown permission com.android.browser.permission.READ_HISTORY_BOOKMARKS

7. apikey for MapView