Fixed
Status Update
Comments
ke...@gmail.com <ke...@gmail.com> #2
Could you attach a video of this happening ?
il...@google.com <il...@google.com> #3
I'll try to get more details, but wanted to bring it up at least.
Please specify your OS, CPU, GPU, the emulator version, the system image you use and how your start the emulator (standalone or embedded into AS).
il...@google.com <il...@google.com> #4
I'm experiencing same issue. It happened randomly, the most often it froze after I resized the emulator window.
I'm on Macbook Pro M2 Max, MacOS Sonoma 14.1.1, Android Studio Iguana 2023.2.1 Canary 14.
I opened the emulator through the Device Manager and use the floating window emulator (not docked).
Screen record attached. The easiest way to reproduce is by resizing or zooming in/out the emulator.
I'm on Macbook Pro M2 Max, MacOS Sonoma 14.1.1, Android Studio Iguana 2023.2.1 Canary 14.
I opened the emulator through the Device Manager and use the floating window emulator (not docked).
Screen record attached. The easiest way to reproduce is by resizing or zooming in/out the emulator.
pe...@gmail.com <pe...@gmail.com> #5
Hi okynk91, thank you for screen recording, we will investigate. I see you run the emulator in the AS window. Could you please try running it in its own window (see the attached screenshot)?
il...@google.com <il...@google.com> #6
#5 Hi, It seems working fine when it's running in its own window. It doesn't have the zoom in/out buttons, I couldn't reproduce the issue. Resizing the window seems working without issue.
ja...@gmail.com <ja...@gmail.com> #7
I'm facing the same problem. I can reproduce it in the own window too. How can you see in the video maybe the problem start when we minimize or resize the window(the integrated AS window too) for the first time.
Run emulator outside AS(standalone) work normally.
OS: Manjaro
Kernel: Linux 6.5.11-1-MANJARO
AS Version: Android Studio Canary 14
CPU: Ryzen 7 5800H
GPU: Vega 8 from my CPU and GTX 1650. I'm using Prime
Emulator version: 34.1.11
I already try disable my offboard graphics from bios but the bug persist independent of the GPU used.
My emulator device details:
Properties
avd.ini.displayname Pixel 3a API 31
avd.ini.encoding UTF-8
AvdId Pixel_3a_API_31
disk.dataPartition.size 6G
fastboot.chosenSnapshotFile
fastboot.forceChosenSnapshotBoot no
fastboot.forceColdBoot yes
fastboot.forceFastBoot no
hw.accelerometer yes
hw.arc false
hw.audioInput yes
hw.battery yes
hw.camera.back virtualscene
hw.camera.front emulated
hw.cpu.ncore 4
hw.device.hash2 MD5:0e6953ebf01bdc6b33a2f54746629c50
hw.device.manufacturer Google
hw.device.name pixel_3a
hw.dPad no
hw.gps yes
hw.gpu.enabled yes
hw.gpu.mode auto
hw.initialOrientation Portrait
hw.keyboard yes
hw.lcd.density 440
hw.lcd.height 2220
hw.lcd.width 1080
hw.mainKeys no
hw.ramSize 2048
hw.sdCard yes
hw.sensors.orientation yes
hw.sensors.proximity yes
hw.trackBall no
image.androidVersion.api 31
image.sysdir.1 system-images/android-31/google_apis_playstore/x86_64/
PlayStore.enabled true
runtime.network.latency none
runtime.network.speed full
showDeviceFrame no
skin.dynamic yes
skin.path.backup /home/gabriel/Android/Sdk/skins/pixel_3a
tag.display Google Play
tag.id google_apis_playstore
vm.heapSize 256
Run emulator outside AS(standalone) work normally.
OS: Manjaro
Kernel: Linux 6.5.11-1-MANJARO
AS Version: Android Studio Canary 14
CPU: Ryzen 7 5800H
GPU: Vega 8 from my CPU and GTX 1650. I'm using Prime
Emulator version: 34.1.11
I already try disable my offboard graphics from bios but the bug persist independent of the GPU used.
My emulator device details:
Properties
avd.ini.displayname Pixel 3a API 31
avd.ini.encoding UTF-8
AvdId Pixel_3a_API_31
disk.dataPartition.size 6G
fastboot.chosenSnapshotFile
fastboot.forceChosenSnapshotBoot no
fastboot.forceColdBoot yes
fastboot.forceFastBoot no
hw.accelerometer yes
hw.arc false
hw.audioInput yes
hw.battery yes
hw.camera.back virtualscene
hw.camera.front emulated
hw.cpu.ncore 4
hw.device.hash2 MD5:0e6953ebf01bdc6b33a2f54746629c50
hw.device.manufacturer Google
hw.dPad no
hw.gps yes
hw.gpu.enabled yes
hw.gpu.mode auto
hw.initialOrientation Portrait
hw.keyboard yes
hw.lcd.density 440
hw.lcd.height 2220
hw.lcd.width 1080
hw.mainKeys no
hw.ramSize 2048
hw.sdCard yes
hw.sensors.orientation yes
hw.sensors.proximity yes
hw.trackBall no
image.androidVersion.api 31
image.sysdir.1 system-images/android-31/google_apis_playstore/x86_64/
PlayStore.enabled true
runtime.network.latency none
runtime.network.speed full
showDeviceFrame no
skin.dynamic yes
skin.path.backup /home/gabriel/Android/Sdk/skins/pixel_3a
tag.display Google Play
vm.heapSize 256
ja...@gmail.com <ja...@gmail.com> #8
I see only canary reports above. For me, this also happens in stable; Giraffe patch 4. Started after updating to latest emulator and it happens every 20-30 minutes or so. Restarting the emulator fixes it for a while. Will try running in its own window.
Android Studio Giraffe | 2022.3.1 Patch 4
Build #AI-223.8836.35.2231.11090377, built on November 13, 2023
Runtime version: 17.0.6+0-b2043.56-10027231 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 12288M
Cores: 12
Registry:
ide.experimental.ui.inter.font=true
external.system.auto.import.disabled=true
debugger.new.tool.window.layout=true
ide.text.editor.with.preview.show.floating.toolbar=false
ide.instant.shutdown=false
ide.experimental.ui=true
Non-Bundled Plugins:
detekt (2.2.0)
manjaro.mpb (1.8)
com.intellij.lang.jsgraphql (4.0.1-222)
com.navigatetomodule (0.32)
com.developerphil.adbidea (1.6.12)
ou...@newaccess.ch <ou...@newaccess.ch> #9
So... Probably the problem was with the new emulator instead of the android studio
Description
Version used:1.0.0-alpha01
Devices/Android versions reproduced on:
Device agnostic
- Sample project to trigger the issue.