android-discuss is probably a better forum for this discussion. I would like to correct a misconception: Android is an application processor stack. It does not include a radio stack, nor is it likely to include one in the near future. The radio firmware is typically proprietary to the chip vendor and closely tied to the hardware architecture of the chip.
On Jan 4, 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 - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
