IssueTracker

lblb636@ Thanks for reporting this bug. I just want to confirm that the issue is the call device button being not responsive according to the uploaded video. It seems like this issue only happened on Windows.

Another similar issue that's related https://b.corp.google.com/issues/226426377

RE#4 I need to try this on Windows laptop first and I couldn't repro on MacOS or Linux. But I think this is most likely related to the modem simulator we introduced for API 31. Will need to further investigate.

I reproduced this bug on Windows with emulator version 31.2.10-8420304

Found the root cause when the "call device" button was unresponsive. It became unresponsive because the inbound call failed to initialize. Basically, the modem simulator's shared FD failed. When receive_inbound_call is invoked, it is supposed to make connection to the "host server" via a shared fd but it is flaky on Windows unfortunately.

modem-simulator: receive_inbound_call:101 inbound call from 6505551212
modem-simulator: process_msgs:296 waiting for new messages ...
modem-simulator: main_host_thread:501 got connection at host server at 65094
modem-simulator: start_calling_thread:254 making a connection to main host server 65094
modem-simulator: main_host_thread:507 Detected close from the other side
modem-simulator: start_calling_thread:262 nothing read quit
modem-simulator: main_host_thread:494 looping at main host server at 65094
modem-simulator: start_calling_thread:284 done with this thread

RE#12 I have uploaded a patch to fix this issue. I don't think it's the same reason for https://issuetracker.google.com/issues/233123301

RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.

The fix has been merged in both 31 release and 32 release for since 05/2022.

lechun.sk, unfortunately a bug report will not help here. It would useful to debug issues inside Android. This crash happens outside. There should be a popup window when you start the emulator asking to send a crash report. Maybe it is not available for local builds. The fix is in code review.

Do you mind trying API34? We have a new camera HAL there.

This is the emulator build on our build server:

https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip

But it lags

yes, it does, because our rotation is not as efficient as vImageRotate90_ARGB8888.

and then crashes

I can't repro it with a build-in camera in my laptop. What camera do you use? Do you see a crash upload dialog to upload it (please share the ID if you have one)?

I can't repro it with a build-in camera in my laptop. What camera do you use?

You can use OBS Studio or XSplit VCam to create a virtual webcam, or you can purchase any Logitech camera, both of which should cause a crash.

Do you see a crash upload dialog to upload it (please share the ID if you have one)?

The dialog doesn't appear at all.

You can use OBS Studio

No crash, see the emulator screen recording. What resolution do you use in OBS Studio?

What resolution do you use in OBS Studio?

1280 * 720. By the way, I'm using mac mini 2023(M2).

• simulator version: sdk-repo-darwin_aarch64-emulator-10914596
• log(only four lines)

VERBOSE | Timed out with running command |/Users/user/Library/Android/sdk/platform-tools/adb -s emulator-5554 shell am broadcast -a com.android.emulator.multidisplay.START -n com.android.emulator.multidisplay/.MultiDisplayServiceReceiver |
[54176:8959974:20231007,XXXXXX.766822:WARNING in_range_cast.h:38] value -634136515 out of range
[54176:8959974:20231007,XXXXXX.823661:WARNING crash_report_exception_handler.cc:235] UniversalExceptionRaise: (os/kern) failure (5)
[1]    54174 illegal hardware instruction  emulator -avd Test_Pixel_5_API_31 -verbose

1280 * 720

Still cannot reproduce, unfortunately. I put 60FPS to match your screenshot. I also tried 720*1280, it even crops correctly.

I'm using mac mini 2023(M2)

MacBook 2021 (M1 Max).

Unfortunately, I don't have an update as it works for me (somewhat slow, yes).

Hi

In case anybody is still experimenting a crash with https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip , please consider running just after the crash the command

• crashreport -l to see if a local crash has been created
• crashreport -u to upload the crash (if any). It will give a crash report-id, and please enter the crashid as a comment of this bug. It will help us if you can also say what you were doing during the crash, and if you were using a specific webcam

crashreport being part of the zipfile sdk-repo-darwin_aarch64-emulator-10914596.zip

We were able to reproduce the crashes on different MacOS running Sonoma before the fix in 10914596, but since the fix, the emulator is not crashing anymore in our tests on Sonoma.

Thanks

You want to download the file (sdk-repo-darwin_aarch64-emulator-10914596.zip) and

xattr -d com.apple.quarantine sdk-repo-darwin_aarch64-emulator-10914596.zip

then unzip it.

So how do I open it?

Start it from the console, e.g. ANDROID_SDK_ROOT=/Users/rforzani22/Library/Android/sdk ./emulator -avd YOUR_AVD -wipe-data -no-snapshot -camera-back webcam0

Hi skergx, thank you for the feedback. What CPU do you run on?

We are working on a better patch (the performance should be about as before and should also work on non-Max CPUs as we see here), the build should be available today-tomorrow.

I shared my local build with our next patch to fix this issue.

This is our second version:

https://ci.android.com/builds/submitted/10937044/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10937044.zip

Hi clerici.m89, thank you for the update. Could you please try (our first fix):

https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip

Hi Andi, the Android Emulator is released independently from the Android Studio. The 32.x.x version is EOL, 33.x.x will be promoted to stable soon and the webcam fixes will be available there.

also the image has different size as before, at least with obs before sonoma i was seeing a cropped image out of the 1280x720 but now i can see it full size on the emulator screen.

In the first fix there is no scale function, I crop and put black everywhere I have no pixels for. When we have the scale function, we crop a smaller image and resize to fill all requested pixels.

Hi Andi, thank you for reporting this. I think this is a different problem here as 10914596 does not change anything related to opening the device and 10937044 probably missed even more around this case.

I am marking this as "fixed" for our internal release process. We are still looking into it. The changes should be available in 34.1.7 (canary) and 33.1.21 (stable).

The Emulator is release independently from the Android Studio. This fix is available in the Emulator 34.1.11 which is shipped with the Android Studio Iguana (2023.2.1 Canary 14).

If the Emulator is released independently, I would expect that it would also be updated in SDK Manager for prior versions of Android Studio, no?

We ship the emulator through several channels (stable, canary, beta), if you are on the stable channel, you will get the emulator updates later. Consider getting https://developer.android.com/studio/preview for faster updates.

The fix does work with the actual webcam but it BREAKS the virtual webcam. Here's the error message:

ERROR   | -[MacCamera captureOutput:didOutputSampleBuffer:fromConnection:]: error in allocate rotateInputBuffer_: -21602
ERROR   | -[MacCamera captureOutput:didOutputSampleBuffer:fromConnection:]: error in allocate rotateInputBuffer_: -21602
 (127x)
ERROR   | _camera_client_query_frame: Unable to obtain first video frame from the camera '7626645E-4425-469E-9D8B-97E0FA59AC75' in 2001 milliseconds: Undefined error: 0.

Please help take a look

Also got the same error as above comment. The 34.1.11 breaks emulator with virtual cam on Sonoma.

error in allocate rotateInputBuffer_: -21602

This one is fixed in https://ci.android.com/builds/submitted/11125189/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11125189.zip

This one is fixed in https://ci.android.com/builds/submitted/11125189/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11125189.zip

This one works, thank you! Will this new version be released anytime soon?

This one works, thank you! Will this new version be released anytime soon?

Please try our latest stable push (33.1.23).

Hi Timar, please file a new bug with repro steps and screenshots. Please specify the Android Studio version, the Emulator version and the system image you use.

Timar, file a new bug into the Android Studio component.

You can try the latest Emulator version from https://developer.android.com/studio/emulator_archive

If the performance is still bad, you could try fixing this yourself and send us your patch. The Emulator is open source, this is what we changed: https://android.googlesource.com/platform/external/qemu/+log/refs/heads/emu-master-dev/android/android-emu/android/camera/camera-capture-mac.m

still poor performance after opening camera.

Hi industrialstrengthdatasystems, if you can build Emulator yourself, please try this patch: https://android-review.googlesource.com/c/platform/external/qemu/+/3093185

luunguyen0811, this is tracked in https://issuetracker.google.com/issues/325814592

Hi folks, please try this build for improved webcam (while it is open) performance:

https://ci.android.com/builds/submitted/11871170/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11871170.zip

A newer build to try:

https://ci.android.com/builds/submitted/11887261/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11887261.zip

Hi bien2k4. Unfortunately, MacOS camera experts are in short supply here :) Thank you for reporting that the issue does not repro on Ventura.

BTW, the camera performance issue is tracked here: https://issuetracker.google.com/issues/325814592