IssueTracker

Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.

Thanks for the report. I believe that this is fixed in our development branch, and also in the branch that will become Ladybug Feature Drop Beta. If you could verify that this doesn't happen in a nightly build (from https://developer.android.com/studio/nightly) that would be helpful -- and of course if you can trigger this in a recent nightly build, that's would be very important information.

Sorry, I have not tried it on the nightly build, but since then I updated to Meerkat and I have not seen the freeze afterwards.

That's good to hear. I think that the fix (which for reference was https://github.com/JetBrains/intellij-community/commit/fe621544dd61a9af34d97958d3d823a7c3454a87) is effective for both beta and canary branches.

For the record I am also arranging for https://github.com/JetBrains/intellij-community/commit/a444c8a500883669fc05c7177f93b5b794fdd13b (same fix, different implementation class) to be included; it's probably inactive code in our configurations, but it might be possible to trigger nevertheless.

Thanks for the confirmation!

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 RC 1
• Android Gradle Plugin 8.8.0-rc01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Ucfucuccj

Hyxucyccchccjch

Ycucuccjcn

Hola mundo

The problem still exists.

Tech info: Android Studio 4.1.3 Build #AI-201.8743.12.41.7199119, built on March 11, 2021 Runtime version: 1.8.0_242-release-1644-b3-6915495 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.15.7

Android Emulator version 30.5.3

Can confirm a workaround for this situation when bluetooth devices used - disconnect and connect headphones again when the emulator is already running. For some reasons after reconnecting the sound is fine. Based on that I believe it is something that happens only when AVD is starting.

P.S. Please stop sending +1, since it is not helpful and spams every other person following this issue. Just star the issue at the top of the page.

This is not fixed! And noise created by emulator now is even harder to get rid sometimes even disconnect/reconnect of earphones doesn't help :(

This is still occurring, but given this issue is marked as fixed I'd recommend starring/commenting on an open one e.g. https://issuetracker.google.com/u/0/issues/183139207

This problem just got worse. I have been able to work around this by setting hw.audioInput=no in my emulator config.ini. However, this recently stopped working.

This is enormously disruptive:

1. If I open or restart an emulator while on a Zoom call, I'm stuck with terrible audio for the remainder of the meeting.
2. Changing the mic back to the internal mic from my WH-1000XM3 doesn't change BT back to a2dp. I have to toggle Bluetooth
3. I can't toggle Bluetooth because I'm using a Bluetooth keyboard and mouse so if I turn it off, I have to go to my laptop, open the lid, and turn it back on.

M1 Pro MacBook + Emulator 31.2.8

Hey, I've been using -noaudio flag when launching an emulator and it's working fine.

Here's my example alias command:

alias androidsim="cd ~/Library/Android/sdk/emulator && ./emulator -avd Nexus_5X_API_28 -noaudio"

It's appalling that this is still a problem 8 years later. During a meeting trying to show case a feature using the Android 10 emulator and suddenly my audio gets killed, my microphone muted, and all I can hear is sounds from the emulator. No one in the meeting can hear me too. Checking the emulator settings shows the mic input is already off, but makes no difference. Solution was the same as #56 . It's deplorable that this is a well known bug and they still pretend to be fixed.

Hi particlecore, please try an API33 or API34 AVD. This is the sound card we use there. If you still observe the audio issues, they are caused by the QEMU audio stack. We are currently upgrading our QEMU (from the very old 2.12 to the most recent one, 8 or 9). We don't have resources to fix this in our copy of 2.12, but this could be fixed in the latest version.

Hi mtrakal, feel free to send us patches (for the new QEMU), we are open source: https://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-dev