I can only tell you that the feature is done. The timing of when you see a device in the field that supports it is up to the deployment manager.
It's important to remember that Android is a platform, and just because the platform advances doesn't necessarily mean that all devices are advancing in lockstep. Each deployment manager will make choices based on their own business case. For example, the G1 has different deployments based on region. On Dec 8, 6:49 am, "Dorn Hetzel" <[EMAIL PROTECTED]> wrote: > While I am sure any "forward looking statement" will need to be taken > with a grain of salt, perhaps you could alleviate many of our concerns > with some clue as to the timeframe in which we might expect relief on > this front. If we knew that in a month or two we could look forward > to at least rudimentary real-time audio we could quit expending energy > on trying to scheme a workaround and just delay our application plans. > If it's going to be a lot longer than that, we can make appropriate > decisions as well. Leaving us knowing nothing doesn't really engender > confidence. Some sort of roadmap with approximate dates would help a > lot! > > Regards, > > Dorn Hetzel > > On Fri, Dec 5, 2008 at 12:12 AM, Dave Sparks <[EMAIL PROTECTED]> wrote: > > > The reason this isn't in 1.0 is because we didn't want to ship a half- > > baked API. We have a solution coming soon in the form of a flexible > > base layer that supports push and pull models. For example, we have > > built an InputStream object on top of it that we will offer as sample > > code. > > > In the future, this development will be taking place in the open > > source repo so we can have a real-time dialog about the code as it is > > developed. In the meantime, we are working hard to get the code that > > has been in development since we forked the 1.0 branch moved into the > > open source repo as soon as possible. > > > On Dec 4, 6:40 pm, MichaelEGR <[EMAIL PROTECTED]> wrote: > >> On Dec 2, 5:22 am, "Dorn Hetzel" <[EMAIL PROTECTED]> wrote: > > >> > Maybe we need to start another mailing list for unrequited android > >> > realtimeaudio:) > > >> I'm all for focused discussion on this topic as it crosses between > >> native concerns and public APIs via the SDK. In my longer original > >> post I mentioned that it would be appropriate to evaluate how to not > >> only getting something workable on the G1, but keep in mind that > >> Android can/will be used in the future conceivably beyond smart phones > >> in devices/hardware that may support expanded audio I/O options. I > >> favor PortAudio (www.portaudio.com) for the task as it can provide a > >> workable real time audio API for desktop Java and Android audio > >> development/porting to other hardware configurations. It is also low > >> level enough to say even implement javax.sound on top of it for those > >> interested in that particular API. More discussion is welcome > >> especially in understanding unspecified work being done for the next > >> SDK release. > > >> Best, > >> --Mike --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
