I'd never claim that all of the software on android can be replaced by third party developers. Most system application components can be re-used and replaced by third party apps, but that is a very different statement.
Also, just being able to replace the phone app (which is not really any app, but more a core system process) means nothing about being able to do IVR-like features -- all the phone app does is talk with the radio module (running on a different processor) using very high-level commands. If you want to add new features to the platform, you can get the source code and look/work on it, and talk about that work on android-platform. Though again, I doubt you would get very far adding IVR features even directly modifying the platform code. On Sun, Jan 4, 2009 at 5:30 PM, StevenS <shearer_ste...@hotmail.com> wrote: > > Thanks for the replies David ! > > I totally understand that the hardware manufacturer needs to implement > the appropriate links - like a couple of extra traces of copper - what > I don't understand is WHY they wouldn't ! Or WHY it wouldn't be seen > as a basic requirement for the product. > > I also question WHY there's concern about a lack of CPU power - I've > been doing IVR development since early 1997, where an Intel 386 CPU > was supporting multiple simulatenous phone calls. Well, actually, in > hindsight, the CPU was supported by a telephony board ... so maybe > this concern is valid ... > > In any event, what happened to the statement that ALL software on the > Android platform could be replaced - including the phone > (interface) ? It's my interpretation that if the phone app can handle > incoming & outgoing calls, then it should be possible to extend it to > include IVR-like features. > > Is there a more-appropriate forum to discuss this 'issue' / > requirement / feature request ? > > Thanks, > Steven. > > > On Jan 3, 8:36 am, Dave Sparks <davidspa...@android.com> wrote: > > It may be a compelling feature, but it's outside the control of the > > apps processor. It is up to the hardware manufacturer to implement > > this, not Android. > > > > My understanding is that there are strict latency requirements on GSM > > audio that makes it difficult to loop call audio through the apps > > processor. > > > > On Jan 2, 4:06 pm, "mashpl...@gmail.com" <mashpl...@gmail.com> wrote: > > > > > > > > > This is a mistake. There are many reasons why exposing in-call audio > > > to the apps process is a good idea. Please reconsider your position > > > on this. > > > > > Kind Regards, > > > > > Vince > > > > > On Jan 3, 1:27 am, Dave Sparks <davidspa...@android.com> wrote: > > > > > > There are no plans for exposing in-call audio to the apps processor. > > > > In-call audio is controlled by the radio and typically not accessible > > > > to the apps processor. > > > > > > On Dec 26 2008, 10:00 pm,StevenS<shearer_ste...@hotmail.com> wrote: > > > > > > > If I'm reading the API documentation correctly, neither the > > > > > MediaRecorder.AudioSource nor the MediaPlayer.AudioSource can > connect > > > > > to the telephone conversation audio channels - eg. the TELEPHONE > > > > > CONVERSATION microphone & speaker 'lines'. > > > > > > > Both of these would be required to support advanced call handling > > > > > applications ON THE DEVICE. > > > > > > > Are there any plans to support this type of functionality ? > > > > > > > When might it be available ? > > > > > > > Thanks, > > > > > Steven.- Hide quoted text - > > > > - Show quoted text - > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
