Emulator -timezone parameter is not working [249948338]

Fixed

Bug

Status Update

No update yet.

Description

me...@booking.com

created issue #1

Sep 30, 2022 09:54AM

Please Read:

https://developer.android.com/studio/report-bugs.html#emulator-bugs

Android Studio Version: 2021.3.1

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.11-9058569
HAXM / KVM Version: HVF 12.6.0

Android SDK Tools: 26.1.1

Host Operating System: macOS 12.6

CPU Manufacturer: Other CPU:
64-bit CPU

RAM: 65536 MB

GPU:

Build Fingerprint:

AVD Details: Name: Pixel_5_API_33
CPU/ABI: arm64
Path: /Users/marikan/.android/avd/Pixel_5_API_33.avd
Target: google_apis [Google APIs] (API level 33)
Skin: 1080x2340
SD Card: 2G
AvdId: Pixel_5_API_33
PlayStore.enabled: false
avd.ini.displayname: Pixel 5 API 33
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:3274126e0242a0d86339850416b0ce34
hw.device.manufacturer: Google

hw.device.name: pixel_5
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 440
hw.lcd.height: 2340
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-33/google_apis/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google APIs

tag.id: google_apis
vm.heapSize: 512

Steps to Reproduce Bug:
Start emulator with "-timezone" parameter(e.g emulator -avd Pixel_5_API_33 -timezone Asia/Shanghai)
Issue is reproducible when API level of the emulator is set to 31+. When API level is 30 emulator works as expected

Expected Behavior:
Emulator starts with timezone set to provided parameter value

Observed Behavior:
Emulator ignores the parameter and starts with host devices timezone.

Comments

vi...@google.com <vi...@google.com> Sep 30, 2022 09:59AM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Oct 5, 2022 06:43PM

Reassigned to wd...@google.com.

wd...@google.com <wd...@google.com> Oct 13, 2022 05:34PM

Accepted by wd...@google.com.

wd...@google.com <wd...@google.com> Oct 13, 2022 07:38PM

Marked as fixed.

bi...@gmail.com <bi...@gmail.com> #2Nov 10, 2022 04:16AM

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.

se...@gmail.com <se...@gmail.com> #3Nov 27, 2022 09:29PM

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?

dt...@gmail.com <dt...@gmail.com> #4Nov 30, 2022 09:00AM

We have quite some crashes like this:

product_name="AndroidEmulator" AND crash.Reason="EXC_BAD_INSTRUCTION / 0x00000001" AND cpu.Architecture="arm64"

[Deleted User] <[Deleted User]> #5Dec 2, 2022 12:53PM

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

ta...@gmail.com <ta...@gmail.com> #6Jan 23, 2023 01:51AM

I suspect EXC_BAD_INSTRUCTION happens in vImageRotate90_ARGB8888 and vImageScale_ARGB8888 which are used by webcam on MacOS.

ta...@gmail.com <ta...@gmail.com> #7Jan 23, 2023 01:51AM

With complete honesty, I have to say that I’m extremely disappointed by the handling of this issue by google and by the fact that it came out in the first place. I need to use android studio for work purposes and I am forced to switch to a different machine. Mac OS Sonoma has been in beta testing for months and google has had plenty of time to ensure the application would be properly running. I expect this issue to have the maximum priority and to be solved very soon.

bu...@gmail.com <bu...@gmail.com> #8Feb 20, 2023 05:15PM

Hi rforzani22, I am sorry for this experience. This bug is my top priority. We expect a fix to be merged within a week. You should be able to download a build directly from our build server (https://ci.android.com/builds/branches/aosp-emu-master-dev/grid) once the fix is merged. The release process will take some additional time.

bu...@gmail.com <bu...@gmail.com> #9Feb 20, 2023 05:23PM

Thanks for making it a top priority, looking forward for the fix, good luck!

[Deleted User] <[Deleted User]> #10May 15, 2024 12:30AM

We confirmed #comment6. I removed 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.

[Deleted User] <[Deleted User]> #11May 15, 2024 12:30AM

I had to downgrade my Mac to Ventura and I realized on Mac Ventura android studio emulator ask for webcam permission which I allowed and worked but on Sonoma it doesn't ask for permission when I open camera app on webcam0