Status Update
Comments
sa...@google.com <sa...@google.com>
rk...@google.com <rk...@google.com>
si...@google.com <si...@google.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.
si...@google.com <si...@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?
si...@google.com <si...@google.com> #4
We have quite some crashes like this:
product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"
co...@accenture.com <co...@accenture.com> #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
si...@google.com <si...@google.com> #6
I suspect EXC_BAD_INSTRUCTION
happens in vImageRotate90_ARGB8888
and vImageScale_ARGB8888
which are used by webcam on MacOS.
Description
The Car Service API allows programmatic access to the AAOS VHAL. The problem is that thehttps://android.googlesource.com/platform/external/qemu/+/emu-master-dev/android/android-grpc/services/incubating/car/proto/car_service.proto has the type for CarEvent as string whereas its expected as a byte string by AAOS.
The fix is to change the type from string to bytes. I've rebuilt the emulator on Linux and the fix is working fine with both python and node.js gRPC clients.
The following example python script can be used for reproducing the problem using a Linux emulator running an AAOS image (for example system-images;android-32;android-automotive-playstore;x86_64)