Status Update
Comments
xi...@google.com <xi...@google.com>
rk...@google.com <rk...@google.com> #2
Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.
rk...@google.com <rk...@google.com> #3
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
rk...@google.com <rk...@google.com> #4
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.
rk...@google.com <rk...@google.com> #5
That's good to hear. I think that the fix (which for reference was
For the record I am also arranging for
Thanks for the confirmation!
rk...@google.com <rk...@google.com> #6
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!
rf...@gmail.com <rf...@gmail.com> #7
Ucfucuccj
rk...@google.com <rk...@google.com> #8
Hyxucyccchccjch
be...@scandit.com <be...@scandit.com> #9
Ycucuccjcn
rk...@google.com <rk...@google.com> #10
Hola mundo
sa...@gmail.com <sa...@gmail.com> #11
rf...@gmail.com <rf...@gmail.com> #12
tr...@gmail.com <tr...@gmail.com> #13
rk...@google.com <rk...@google.com> #14
rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.
le...@gmail.com <le...@gmail.com> #15
rk...@google.com <rk...@google.com> #16
lechun.sk, I shared with you.
le...@gmail.com <le...@gmail.com> #17
rk...@google.com <rk...@google.com> #18
lechun.sk, this is unexpected. Do you mind uploading a crash report and sharing its id?
le...@gmail.com <le...@gmail.com> #19 Restricted
rk...@google.com <rk...@google.com> #20
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.
le...@gmail.com <le...@gmail.com> #21
rk...@google.com <rk...@google.com> #22
Do you mind trying API34? We have a new camera HAL there.
sa...@gmail.com <sa...@gmail.com> #23
le...@gmail.com <le...@gmail.com> #24
le...@gmail.com <le...@gmail.com> #25
le...@gmail.com <le...@gmail.com> #27
rk...@google.com <rk...@google.com> #28
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)?
ru...@gmail.com <ru...@gmail.com> #29
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.
ru...@gmail.com <ru...@gmail.com> #30 Restricted
rk...@google.com <rk...@google.com> #31
You can use OBS Studio
No crash, see the emulator screen recording. What resolution do you use in OBS Studio?
ru...@gmail.com <ru...@gmail.com> #32
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
rk...@google.com <rk...@google.com> #33
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).
rf...@gmail.com <rf...@gmail.com> #34
tr...@gmail.com <tr...@gmail.com> #35
The emulator camera is very slow
rk...@google.com <rk...@google.com> #36
Unfortunately, I don't have an update as it works for me (somewhat slow, yes).
jp...@google.com <jp...@google.com> #37
Hi
In case anybody is still experimenting a crash with
crashreport -l
to see if a local crash has been createdcrashreport -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
rf...@gmail.com <rf...@gmail.com> #38
rk...@google.com <rk...@google.com> #39
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.
rf...@gmail.com <rf...@gmail.com> #40
rk...@google.com <rk...@google.com> #41
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
sk...@gmail.com <sk...@gmail.com> #42
rk...@google.com <rk...@google.com> #43
Hi skergx, thank you for the feedback. What CPU do you run on?
sk...@gmail.com <sk...@gmail.com> #44
rf...@gmail.com <rf...@gmail.com> #45
rk...@google.com <rk...@google.com> #46
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.
rk...@google.com <rk...@google.com> #47
I shared my local build with our next patch to fix this issue.
an...@biomatrixci.com <an...@biomatrixci.com> #49
cl...@gmail.com <cl...@gmail.com> #50
Report 7d004e0f-9c06-49d8-b57e-30cd0fe4f033 is available remotely as d6281b959cb2c138
Report 149d7151-6381-46a2-83f8-1d77ab7280f3 is available remotely as 96a1cd1205509b81
rk...@google.com <rk...@google.com> #52
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.
an...@biomatrixci.com <an...@biomatrixci.com> #53
cl...@gmail.com <cl...@gmail.com> #54
- seems the performance is not the same as before (as already reported)
- 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.
- it crash after some time (as already reported) see here: Report 5f27bfa1-d033-4b91-9dcf-53c0fcb2a09c is available remotely as 62b6433b9dd77685
rk...@google.com <rk...@google.com> #55
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.
an...@biomatrixci.com <an...@biomatrixci.com> #56
Tested on M1 Pro 10914596 emulator build and it just hang when launching default camera app with verbose printout
"
DEBUG | getMultiDisplay 0 x 0 y 0 w 1440 h 3120 dpi 560 flag 0 enable 1
DEBUG | getMultiDisplay 0 x 0 y 0 w 1440 h 3120 dpi 560 flag 0 enable 1 (3x)
ERROR | -[MacCamera init:]: cannot add camera capture input device
ERROR | camera_device_open: Unable to initialize camera device.
ERROR | _camera_client_query_connect: Unable to open camera device
"
rk...@google.com <rk...@google.com> #57
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.
rk...@google.com <rk...@google.com> #58
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).
in...@gmail.com <in...@gmail.com> #59
For anyone wondering how to do implement this fix, follow the instructions in post #39 above. Download the file and follow the instructions in post #39 (do not just unzip the file!). Go into the unzipped folder and copy the 'emulator' folder to Users/<user>/Library/Android/sdk overwriting the existing 'emulator' folder.
When you launch Android Studio and start a new emulator it will be using the fixed version. However, if you check under Tools > SDK Manger you will not see the emulator installed (this is due to using the version provided above), ignore this.
I can confirm that I had the original issue before overwriting the 'emulator' folder, and now, I do not have the original issue any longer. Camera now works.
an...@biomatrixci.com <an...@biomatrixci.com> #60
#56 is due to running emulator as standalone as described in #41 and it may not have the necessary camera permission.
Thank you for the prompt response.
fu...@gmail.com <fu...@gmail.com> #61
kr...@gmail.com <kr...@gmail.com> #62
But the emulator is crashing again when using Webcam0 on 34.1.8 (Canary)
This is one report ID for it:
4b297feadfa6737b
ch...@vanoijen.eu <ch...@vanoijen.eu> #63
in...@gmail.com <in...@gmail.com> #64
vi...@gmail.com <vi...@gmail.com> #65
I use macbook pro m2 sonoma.
pa...@gmail.com <pa...@gmail.com> #66
rk...@google.com <rk...@google.com> #67
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).
in...@gmail.com <in...@gmail.com> #68
Perhaps this can be considered, as otherwise it is confusing how it is independent for those of us that wish to stay on our current version of Android Studio for various other reasons.
rk...@google.com <rk...@google.com> #69
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
ta...@honestbank.com <ta...@honestbank.com> #70
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
do...@gmail.com <do...@gmail.com> #71
Also got the same error as above comment. The 34.1.11 breaks emulator with virtual cam on Sonoma.
ve...@google.com <ve...@google.com> #74
OS: Mac M1(Sonoma 14.1.2).
Emulator Version: 34.1.13-11169323
API: API 33, 34
rk...@google.com <rk...@google.com> #75
This one works, thank you! Will this new version be released anytime soon?
Please try our latest stable push (33.1.23).
ti...@gmail.com <ti...@gmail.com> #76
All of a sudden, with the 33.1.23 version, I cannot record the screen anymore in Android Studio in mp4 format. It produces a 11 KB file whatever I do. Does anyone else experience this problem? Thanks!
rk...@google.com <rk...@google.com> #77
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.
li...@getstream.io <li...@getstream.io> #78
ti...@gmail.com <ti...@gmail.com> #79
rk...@google.com <rk...@google.com> #80
Timar, file a new bug into the Android Studio component.
in...@gmail.com <in...@gmail.com> #81
I am forced to use other devices as the performance is so poor after the camera opens. Unfortunately it is not possible to use just macOS any longer to work on Android/Flutter projects because of this.
It's been a couple months so I am very hopeful I am just missing the fix?
Thank you for the hard work.
ar...@rexel.com <ar...@rexel.com> #82
rk...@google.com <rk...@google.com> #83
You can try the latest Emulator version from
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:
in...@gmail.com <in...@gmail.com> #84
I wish this was my area of expertise. Hopefully someone with the capability will work on this, it's extremely significant for Android Studio on macOS obviously.
in...@gmail.com <in...@gmail.com> #85
Unfortunate.
lu...@gmail.com <lu...@gmail.com> #86
rk...@google.com <rk...@google.com> #87
still poor performance after opening camera.
Hi industrialstrengthdatasystems, if you can build Emulator yourself, please try this patch:
rk...@google.com <rk...@google.com> #88
luunguyen0811, this is tracked in
bi...@gmail.com <bi...@gmail.com> #91
Downgrading to Ventura solves this problem, but it's not an ideal solution.
rk...@google.com <rk...@google.com> #92
Hi bien2k4. Unfortunately, MacOS camera experts are in short supply here :) Thank you for reporting that the issue does not repro on Ventura.
rk...@google.com <rk...@google.com> #93
BTW, the camera performance issue is tracked here:
Description
Android studio emulator crashes when i open camera app when webcam0 is enabled iam using macOS Sonoma part of my catalog below device VINTF manifest. "09-28 17:36:47.910 354 354 I RefreshRateSelector: Display 4619827259835644672 policy changed 09-28 17:36:47.910 354 354 I RefreshRateSelector: Previous: {defaultModeId=0, allowGroupSwitching=false, primaryRanges={physical=[0.00 Hz, inf Hz], render=[0.00 Hz, 60.00 Hz]}, appRequestRanges={physical=[0.00 Hz, inf Hz], render=[0.00 Hz, inf Hz]}} 09-28 17:36:47.910 354 354 I RefreshRateSelector: Current: DisplayManagerPolicy{defaultModeId=0, allowGroupSwitching=false, primaryRanges={physical=[60.00 Hz, inf Hz], render=[60.00 Hz, 60.00 Hz]}, appRequestRanges={physical=[60.00 Hz, inf Hz], render=[60.00 Hz, 60.00 Hz]}} 09-28 17:36:47.910 354 354 I RefreshRateSelector: 0 mode changes were performed under the previous policy 09-28 17:36:47.911 316 375 I Gralloc4: mapper 4.x is not supported"
I tried to reinstall nothing worked iam using lates android studio Android Studio Giraffe | 2022.3.1 Patch 1 Build #AI-223.8836.35.2231.10671973, built on August 17, 2023 Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 14.0 GC: G1 Young Generation, G1 Old Generation Memory: 1280M Cores: 8 Metal Rendering is ON Registry: external.system.auto.import.disabled=true ide.text.editor.with.preview.show.floating.toolbar=false