Fixed
Status Update
No update yet.
Comments
dy...@google.com
wi...@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);
}
ar...@google.com
bo...@google.com
bo...@google.com
ca...@google.com
Ranjit, can you please help verify this on 32.1.8 Canary and 31.3.14 Stable?
de...@google.com
Still seeing this issue with Emulator 31.3.14 Stable. Refer to the screenshot.
Description
The bug is showed in the video. This happens only in the android emulator window.
Please Read:
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.11-9536276
HAXM / KVM Version: HVF 13.2.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.2.1
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint:
AVD Details: Name: A22_API_31
CPU/ABI: arm64
Path: /Users/projecthouse/.android/avd/A22_API_31.avd
Target: google_apis_playstore [Google Play] (API level 31)
Skin: 720x1510
SD Card: 512M
AvdId: A22_API_31
PlayStore.enabled: true
avd.ini.displayname: A22 API 31
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: yes
fastboot.forceFastBoot: no
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:9847239f65ec7ef3089a6320357fa7a4
hw.device.manufacturer: User
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 240
hw.lcd.height: 1510
hw.lcd.width: 720
hw.mainKeys: no
hw.ramSize: 6144
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-31/google_apis_playstore/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: lte
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google Play
vm.heapSize: 80
Steps to Reproduce Bug:
The bug is showed in the video. This happens only in the android emulator window.
Expected Behavior:
Observed Behavior: