here are the results as of Android 4.1.2 - testing the calls

[sallespromanager]

telephonyService.answerRingingCall();
NOT allowed - throws SecurityException

telephonyService.endCall();
works, if you answer the call beforehand - it does not block incoming call

call that silences the ringer
NOT allowed - throws SecurityException

[teddscofield]

Hey, thank you very much for checking this out!

Very disappointing results, I'd hoped it might work, but appreciate the findings none the less. Guess that's that for the answering tools. Time to fork it off to a screen guard only app.

[sallespromanager]

oh, no. thank you Sir for starting this up.

i would indeed like to implement the screen guard for ti can be very usefull fetching some more user/contact data for quick reference as well as avoiding unwanted hang ups.

i would also like to promote some kind of movement pro freeing up Telephony functionality, even if it requires certifying one's application to make use of them.

Do you know if there's is any other situation like that you may be aware of ?

[tolland]

On 6 September 2013 04:32, salles notifications@github.com wrote:

i would also like to promote some kind of movement pro freeing up
Telephony functionality, even if it requires certifying one's application
to make use of them.

Do you know if there's is any other situation like that you may be aware
of ?

My contract is up, and I can get an upgrade. So I am going to write to
t-mobile UK to ask about the lack of functionality in their stock Android.

My understanding was that setting the MediaRecorder.AudioSource to "
VOICE_CALLhttp://developer.android.com/reference/android/media/MediaRecorder.AudioSource.html#VOICE_CALL"
fails because it was not implemented in the Android that was shipped by the
networks, in the firmware.

However I am not so sure about the cause of the failure from
"telephonyService.endCall();"

Are you aware of any analysis in depth?