Status Update
No update yet.
Comments
xo...@google.com
ya...@google.com
mu...@gmail.com
Hi,
would you try to boot emulator with this command line flag:
-feature -Vulkan
and let us know if it fixes the issue for you? Also would you tell us what graphics card you are using and what is the graphics driver version?
would you try to boot emulator with this command line flag:
-feature -Vulkan
and let us know if it fixes the issue for you? Also would you tell us what graphics card you are using and what is the graphics driver version?
wd...@google.com
The feature flag did solve the issue for me. Thank you very much. I don't use a dedicated graphics card. Only the internal one from the CPU.
wd...@google.com
Your integrated GPU is supposed to support Vulkan 1.2. I would need more work to figure out why it crashes without that flag.
mu...@gmail.com
If there is more information that I can provide please let me know.
wd...@google.com
Thanks. Would you help me to try some more runs to isolate the root cause? Please try to run the emulator with this flag:
-feature -GLDirectMem,-GLDMA,-GLDMA2
I am suspecting the Vulkan direct memory access and coherent mapping is causing the issue.
-feature -GLDirectMem,-GLDMA,-GLDMA2
I am suspecting the Vulkan direct memory access and coherent mapping is causing the issue.
Description
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.2.9-8316981
HAXM / KVM Version: HVF 12.3.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 12.3.1
CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU
RAM: 16384 MB
GPU: GPU #1
Make: 1002
Model: 7340
Device ID: 7340
Build Fingerprint: google/sdk_google_phone_x86/generic_x86:7.0/NYC/4409132:user/release-keys
AVD Details: Name: 4base_makine_rooted
CPU/ABI: x86
Path: /Users/mustafa/.android/avd/4base_makine_rooted.avd
Target: google_apis_playstore [Google Play] (API level 24)
Skin: 1080x1920
SD Card: 512 MB
AvdId: 4base_makine_rooted
PlayStore.enabled: true
avd.ini.displayname: 4base_makine_rooted
avd.ini.encoding: UTF-8
disk.dataPartition.size: 2G
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
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.dPad: no
hw.device.hash2: MD5:55acbc835978f326788ed66a5cd4c9a7
hw.device.manufacturer: Google
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 420
hw.lcd.height: 1920
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSize: 1536
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-24/google_apis_playstore/x86/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: no
skin.dynamic: yes
skin.path.backup: _no_skin
tag.display: Google Play
vm.heapSize: 256
Steps to Reproduce Bug:
Expected Behavior:
Observed Behavior: Sometimes, the avd feels sticky touch. It doesnt release touch even if I dont touch trackpad. I m using macbook pro.and tap to click is enabled. I think avd cant handle mis-touches or cant differentiate between navigating and tap on trackpad. As a result, UI behaves oddly sometimes gets unresponsive