-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"processAudioBuffer(666): Error -61 obtaining an audio buffer, giving up." from AudioRecord, in Android 13 #2124
Comments
Supplements:
After forcing Android 13 to using OpenSLES, the behaviour resume the same as Android 8 works smoothly, why? But the code document said this is deprecated in Android 13 and above, so I bet it's not the best solution, anyone encountered the similar thing would give some tips? Thanks in advance! |
Are the two streams related? In other words is the output a processed version of the input?
That error messages comes from frameworks/av/media/libaudioclient/AudioRecord.cpp
Yes, OpenSL ES is deprecated. It is OK to use it on older devices. But it is no longer actively supported. We would need more information to help diagnose the problem. Also what devices is this on? |
Thanks @philburk for your reply, here are some supplements:
Nope they're unrelated, this is a communication mobile app, one stream for recording voice, another one for playing incoming voice.
For playing:
For recording:
This is realme note 50, Android 13 |
@amos-yau - Thanks for the additional info. Does this happen on Android 14 or 15? Can you capture some of the logcat right before the processAudioBuffer() error? Maybe 100 lines?
Are the two callbacks with "this" using different objects? |
Do you have the same error on different phones or just the Realme Note 50? https://www.gsmarena.com/realme_note_50-12799.php It is runnng a UniSOC Tiger T612 Is the failure intermittent or does it always happen? |
Sorry for the late reply in the year end holiday season, currently I'm using the OpenSLES as a quick fix interim solution, will get back and dig into this issue after the current feature released, kindly keep this thread open, thanks! |
Sorry I may have missing something, so this would be a question rather than a bug:
requestStart()
, the title error message is shownThe text was updated successfully, but these errors were encountered: