Adding ARC folks. Sorry for using two ARC components - pls tell me which is preferred.

Thank you for looking into this.
One correction to my initial report, I believe the last ChromeOS version this was working fine was V64. It started with V65 if my memory serves me right.
I also checked Dev channel V68 and the issue is also happening on the dev channel.

Please also note that this is only happening with sending audio, the receiving audio channel always works fine and this only happens in Android apps.

Paul maybe you could take a look?

I'll try to reproduce the issue first and log something down from both 
adb logcat and cras_test_client.

I can't reproduce the issue by the following settings with phone call on android hangout app more than 1+hr.

1. ChromeOS call to my workstation using hangout app.
2. Using internal speaker and microphone on ChromeOs.
3. The microphone on my workstation is muted.

Can you give one more specific settings that will trigger the problem?
Is there any other app running beside (web or android app)?

Thanks!

Here is the test environment I used:
DEVICETYPE=CHROMEBOOK
CHROMEOS_ARC_VERSION=4794359
CHROMEOS_ARC_ANDROID_SDK_VERSION=25
GOOGLE_RELEASE=10575.47.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BUILDER_PATH=eve-release/R67-10575.47.0
CHROMEOS_RELEASE_BUILD_NUMBER=10575
CHROMEOS_RELEASE_BRANCH_NUMBER=47
CHROMEOS_RELEASE_CHROME_MILESTONE=67
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=10575.47.0 (Official Build) dev-channel eve test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_BOARD=eve
CHROMEOS_RELEASE_VERSION=10575.47.0

I just made two calls, both had this issue within 5 minutes into the call. I did however capture the logcat for both calls (attached). It shows the error and failure towards the end. I hope it helps.

This was done using Bria VOIP app, but it is also happening when using Vonage business, hangouts and the new Google Voice WiFi calling beta (android app).
I was using the built in speaker and mic.

I am not using any other android app while on the call, but i am using the browser with two gmail tabs open, google docs tab another tab for our business ticketing system. I also have a slack tab open.
The Pixelbook is connected to an external monitor, keyboard and mouse.
This is also happening on my Asus flip C101 so am ruling out this is hardware issue.

I hope the logs will help see what's happening here.

Thank you!

Deleted: audio_failure.txt 202 KB

audio_failure.txt 202 KB View Download

Deleted: audio_failure2.txt 312 KB

audio_failure2.txt 312 KB View Download

here is another crash log. This time i was using the Vonage business app, 21 minutes into the call it happened. You can see the failure at the end of the log.
I did open a google doc spreadsheet (in the browser) when it happened, not sure it it's related or not.

Deleted: audio_failure3.txt 140 KB

audio_failure3.txt 140 KB View Download

Today i received the HP X2 and the issue is also happening in this device.
I am able to easily reproduce the error "AudioFlinger: read failed: framesRead=-2147483631" on this device than on the Pixelbook.
Simply start a VOIP call from an android app, open a a few browser tabs (i used two gmail and one google drive tab) and you can see the AudioFlinger error in 90% of the time.
As soon as this error appears, audio input from the VOIP apps stops.
I am attaching another adb logcat from the HP X2, this was using google hangouts to make the VOIP call.

Deleted: audio_failure_HP.txt 216 KB

audio_failure_HP.txt 216 KB View Download

I was wondering if anyone from ChromeOS team was able to look at the logs i sent over the weekend? There is clearly an issue with AudioFlinger here and it's happening on multiple Chromebooks.
This makes android VOIP apps unusable and not what i would expect from my $1700 i7 pixelbook. I hope this can be addressed promptly.

Hi Jonathan,

Sorry for the late reply and thanks for your report.
We received your logs, we'll try to fixed the issue ASAP.

Best,

@paulhsia thank you.
If you need me to grab logs of this issue happening from the ChromeOS side, please let me know how to do this and i'll be happy to provide some.
If you would like to replicate the issue yourself simply open any android app that uses the microphone (VOIP apps, sound recorders etc), then open chrome and open multiple gmail and google drive tabs and watch the Android AudioFlinger error happening (which results in audio input stops working).
That would be the fastest way to reproduce the issue.

Hi Jonathan,

Thanks for your helpful information.
I just got a HP X2 deice and I can reproduce the bug by it easily now, so I can setup a debug environment by this and start to look into the issue.
We will let you know if the issue is fixed.

Best

Thank you Paul.
I hope this can be fixed quickly as it really makes all android VOIP apps unreliable for calling as it happens across the Pixelbook, HP X2, Samsung Chromebook Pro and Asus C101.

Thanks again.

Hi Jonathan,

I found the bug and know how to fix it.
The bug is inside android audio framework.
We just initiated a discussion with android team and the problem will be fixed soon (b/110129265).

We'll let you know when the fix land.

Best

Thank you Paul.
Until this is fixed with the Android Team, is there any workaround you can recommend (maybe an ADB command I can run?)?

Hi ChromeOS team,

Is there any update on fix for this? Any update from the Android team?
This is still happening as of the latest beta version 68.0.3440.25 and it's making using any Android VOIP apps on ChromeOS unusable.
I have not checked the latest Dev channel.

Thank you.

Hi Jonathan,

I landed the change to android last week and it will be in the image with Chrome OS Version >= 10718.31.0

Best

Great! thank you so much. I will check as soon as the beta channel updates to 10718.31.0.

just confirming this is indeed fixed in the latest V68 beta.
Thank you so much!