Why is the Android Telephony API so limited (closed)?

Post by loginx » Thu, Sep 10, 2009, 1:47 PM UTC

charltones wrote: post #10

thwarted wrote: post #3

Earlier quoted context omitted.

A little research reveals: http://developer.android.com/reference/android/media/AudioTr... -- supports both streaming and static playback modes, interfaced by writing bytes http://developer.android.com/reference/android/media/AudioRe... -- interfaced by reading bytes. Specifically for telephony, does one need something else? If you want to make a phone call, you can ask the device to dial a number. If it's possible t…

>Specifically for telephony, does one need something else? Often, yes. Device manufacturers and operators have traditionally been very cautious of allowing low level access to telephony APIs. For instance, getting access to the audio uplink and downlink of a GSM conversation is quite tricky (often impossible) on other platforms, so if it is possible on a real Android device as you indicate then that is a big win. If…

Post by thwarted » Thu, Sep 10, 2009, 3:41 PM UTC

loginx wrote: post #11

charltones wrote: post #10

Earlier quoted context omitted.

>Specifically for telephony, does one need something else? Often, yes. Device manufacturers and operators have traditionally been very cautious of allowing low level access to telephony APIs. For instance, getting access to the audio uplink and downlink of a GSM conversation is quite tricky (often impossible) on other platforms, so if it is possible on a real Android device as you indicate then that is a big win. If…

Pretty insightful. Regarding the last part of your comment, I don't agree with the idea of using a developer certificate. In the case of malicious software, this only pushes the malicious developer into having to have their piece of software create maximum damage at once, since they will only get one shot at it. I like the current Android approach better: when you install an app, the phone lists all the pieces of fun…