Status Update
No update yet.
Comments
vi...@google.com
bo...@google.com
wd...@google.com
wd...@google.com
bi...@gmail.com
se...@gmail.com
Here is what I found:
On API 31+, time was not updated after the host was waken up. While on API 30 and under, time was updated after host was waken up. The main difference is caused by switching the modem simulator. In API 30 and under, time will be updated whenever signal strength query is received.
Looking at the code in API 31+ for time update when signal strength query is received, I think it is possible that timeUpdate is not invoked
void NetworkService::HandleSignalStrength(const Client& client) {
std::vector<std::string> responses;
std::stringstream ss;
if (WakeupFromSleep()) {
misc_service_->TimeUpdate();
} else if (first_signal_strength_request_) {
first_signal_strength_request_ = false;
misc_service_->TimeUpdate();
}
android_last_signal_time_ = time(0);
auto response = BuildCSQCommandResponse(GetCurrentSignalStrength());
responses.push_back(response);
responses.push_back("OK");
client.SendCommandResponse(responses);
}
[Deleted User] <[Deleted User]>
ta...@gmail.com
Still seeing this issue with Emulator 31.3.14 Stable. Refer to the screenshot.
ta...@gmail.com
@devki How do I know if the fix is in 31.3.14 stable? Any tool for checking if a CL went into the specified version?
bu...@gmail.com
bu...@gmail.com
RE#9 Thanks Devki. Actually the fix is included in aosp-emu-31-release branch.
[Deleted User] <[Deleted User]>
Upload a new
Description
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.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
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.