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

Hi, some users reported that installing "Vulkan SDK" helps with this issue. What is your GPU and its driver versions?

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

WARN - Emulator: Pixel 9 Pro XL API 35 - Vanguard anti-cheat software is detected on your system. It is known to have compatibility issues with Android emulator. It is recommended to uninstall or deactivate Vanguard anti-cheat software while running Android emulator.
2024-12-03 13:34:02,503 [ 53041] INFO - #com.android.adblib.impl.SessionDeviceTracker - trackDevices() failed, will retry in 2000 millis, connection id=32
java.lang.IllegalStateException: ADB location has not been initialized

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

Hi, I have installed the Vulkan SDK on my PC, and my GPU is an NVIDIA GeForce RTX 3060 Laptop GPU with driver version 30.0.15.1274. I also tried deactivating the Vanguard anti-cheat, but the AVD still terminated. I’ve attached the log file after deactivating Vanguard.

Regarding the ADB issue ("ADB location has not been initialized"), I ran the adb version command in Command Prompt and successfully retrieved the version. Could you help me check this again?

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

Could you please try stating the Emulator from the command line this way

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
emulator.exe -avd Pixel_9_Pro_XL_API_33 -wipe-data -no-snapshot -verbose -feature -Vulkan

and attach its output? If you notice any popups about missing dlls please include them here.

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

Hi this is the output txt flle

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

Thank you, please try adding -gpu swangle (this is a software GPU, it will be slow), I think for whatever reason we can't talk to your GPU.

Please consider trying the latest version we have here:

https://developer.android.com/studio/emulator_archive

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

The attached TXT file contains the output after adding -gpu swangle. Following that, I manually updated the emulator from Android Emulator (35.2.10) Stable to Android Emulator (35.4.3) Canary. I also deleted the old AVD and created a new one, but it still terminated. I’ve attached the report generated after updating the emulator version.

Could you please check this for me?

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

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

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

Please check if you have crashreports and if you do consider uploading them (please attach crash ids here):

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
crashreport.exe -l
crashreport.exe -u

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

Hi this is the output crash id :

Microsoft Windows [Version 10.0.19045.5131]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -l
C:\Users\crazy\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.4.3.db\reports\fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a.dmp

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -u
Report fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a is available remotely as: 9a9150ec7b65047e

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>