Status Update
Comments
ya...@google.com <ya...@google.com>
bo...@google.com <bo...@google.com>
ke...@netflix.com <ke...@netflix.com> #2
Thank you for the report. We will try to fix this soon. In the meantime, could you please start the emulator from the console (see the commands below), open the camera app to crash it and attach the output, it might help to figure out what the problem is:
cd /Users/YOUR_USERNAME/Library/Android/sdk/emulator
./emulator -list-avds
./emulator -verbose -avd YOUR_AVD_FROM_PREVIOUS_STEP
if there is a crash report to send, please send it and attach the report id.
bo...@google.com <bo...@google.com> #3
We got a crash report (thanks JP): 872e3b20bc34905b. It says EXC_BAD_INSTRUCTION / 0x00000001
and the console also says "Illegal hardware instruction". I suspect the new MacOS brought a new hypervizor which causes this behavior. Haitao, could you please take a look?
zh...@google.com <zh...@google.com> #4
We have quite some crashes like this:
product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"
sy...@syntezzz.ru <sy...@syntezzz.ru> #5
The most of crashes happen here:
vVertical_Scale_ARGB_8888_Accelerate
vImageVerticalShear_ARGB8888
vImageVerticalShear_ARGB8888
vImageScale_ARGB8888
vRotateClockwise270Degree_ARGB8888_Accelerate2
vRotate_90_ARGB_8888_270Degree_Accelerate2
bo...@google.com <bo...@google.com> #6
I suspect EXC_BAD_INSTRUCTION
happens in vImageRotate90_ARGB8888
and vImageScale_ARGB8888
which are used by webcam on MacOS.
bo...@google.com <bo...@google.com> #7
ja...@google.com <ja...@google.com> #8
ki...@gmail.com <ki...@gmail.com> #9
ki...@gmail.com <ki...@gmail.com> #10
We confirmed vImageRotate90...
and vImageScale...
and use what I could find (which is not as efficient as vImage...
ones, we will try to figure out why these functions crash), it does not handle all aspect ratios and resolutions so far (it might crash for different reasons, I will be working on this tomorrow). If anyone wants to try my local build, I can share it.
wh...@gmail.com <wh...@gmail.com> #11
ch...@gmail.com <ch...@gmail.com> #12
ch...@gmail.com <ch...@gmail.com> #13
ch...@gmail.com <ch...@gmail.com> #14
rforzani22 and treblew2017, I shared a Google Drive link with you, see your email.
Description
Android Studio Version: Giraffe | 2022.3.1
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.14-10330179
HAXM / KVM Version: HVF 13.5.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.5
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint:
AVD Details: Name: Pixel_C_Tablet_API_33
CPU/ABI: arm64
Path: /Users/tomas/.android/avd/Pixel_C_API_33.avd
Target: google_apis [Google APIs] (API level 33)
Skin: 2560x1800
SD Card: 512 MB
AvdId: Pixel_C_Tablet_API_33
PlayStore.enabled: false
avd.ini.displayname: Pixel C Tablet API 33
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6G
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:b6f369a5174fab4bbf46015b0d842ec6
hw.device.manufacturer: Google
hw.gps: no
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: landscape
hw.keyboard: yes
hw.lcd.density: 320
hw.lcd.height: 1800
hw.lcd.width: 2560
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-33/google_apis/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: no
skin.dynamic: yes
skin.path.backup: /Users/tomas/Library/Android/sdk/skins/pixel_c
tag.display: Google APIs
vm.heapSize: 192
Steps to Reproduce Bug:Call PackageManager.hasSystemFeature(PackageManager.FEATURE_SENSOR_HINGE_ANGLE) and this method returns true on Pixel C tablet.
Expected Behavior:
Returns false on Pixel C tablet.
Observed Behavior: