Fixed
Status Update
No update yet.
Comments
dy...@google.com
Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information:
1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.
For more information on what’s needed and how to obtain this information please read the guide athttps://developer.android.com/studio/report-bugs#emulator-bugs .
1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.
For more information on what’s needed and how to obtain this information please read the guide at
wi...@gmail.com
Looks like this is fixed in master, presumably as part of the synchronization with the chromeos gcc. Won't make r11, but will be in the next update.
ar...@google.com
bo...@google.com
bo...@google.com
Is this fixed? I am seeing linker error on log2 while using ndk-r13b.
bo...@google.com
ca...@google.com
log2 wasn't available in android until jb-mr2 (android-18).
Also possible that the problem you're seeing is just more ofhttps://github.com/android-ndk/ndk/issues/82 . Essentially, we have to build gnustl against the minimum supported version (currently android-14), so it can't make use of anything that was present in that version. We're working on fixing this for libc++ with a better libandroid_support, but that's still WIP.
Also possible that the problem you're seeing is just more of
de...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Emulator 33.1.19
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!
Description
The bug is showed in the video. This happens only in the android emulator window.
Please Read:
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.11-9536276
HAXM / KVM Version: HVF 13.2.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.2.1
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint:
AVD Details: Name: A22_API_31
CPU/ABI: arm64
Path: /Users/projecthouse/.android/avd/A22_API_31.avd
Target: google_apis_playstore [Google Play] (API level 31)
Skin: 720x1510
SD Card: 512M
AvdId: A22_API_31
PlayStore.enabled: true
avd.ini.displayname: A22 API 31
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
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.dPad: no
hw.device.hash2: MD5:9847239f65ec7ef3089a6320357fa7a4
hw.device.manufacturer: User
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 240
hw.lcd.height: 1510
hw.lcd.width: 720
hw.mainKeys: no
hw.ramSize: 6144
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-31/google_apis_playstore/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: lte
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google Play
vm.heapSize: 80
Steps to Reproduce Bug:
The bug is showed in the video. This happens only in the android emulator window.
Expected Behavior:
Observed Behavior: