On the nexus one, my app goes into Audio Record Stanby randomly after 0-40 seconds. I'm using the AudioRecord class, and while the standby is reported in the terminal, the AudioRecord instance reports the same states of RECORDSTATE_RECORDING and STATE_INITIALIZED throughout the entire sequence.
The bottom line is that when this anomaly occurs, audio is not captured. and this is what im working to prevent was only able to reproduce on nexus one android2.1 not g1 android1.6 I have looked extensively through the Android C/C++ libraries such as at this file: http://android.git.kernel.org/?p=platform/hardware/msm7k.git;a=blob_plain;f=libaudio/AudioHardware.cpp;hb=HEAD and http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=libs/audioflinger/AudioFlinger.cpp Most interesting to me, is this line in AudioFlinger: http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=libs/audioflinger/AudioFlinger.cpp#l3101 Specifically the bool AudioFlinger::RecordThread::threadLoop() As you can see, minput->standby() occurs in 4 different places in the code. I believe that one of these is entering an undesirable state. Now, I'm looking for a solution. Maybe I've missed something really obvious. Another person's perspective on the issue would be highly appreciated. Thank you. -- 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
