IssueTracker

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. Reference

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);
}

CL is merged. We plan to release it to the next canary and stable.

Still seeing this issue with Emulator 31.3.14 Stable. Refer to the screenshot.

@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?

RE#9 Thanks Devki. Actually the fix is included in aosp-emu-31-release branch. https://android-build.googleplex.com/builds/branch-dashboard/aosp-emu-31-release?build_id=9296499 There is probably still something missing in the stable release and I will take another look.

Upload a new CL which will enforce time update when QT application state changes, which happens when emulator sleeps and wakes up.

Please use the build from go/ab/9413197 https://android-build.googleplex.com/builds/branch-dashboard/aosp-emu-31-release?build_id=9413197

Hi Weilun, Devki,
Still seeing this issue on Emulator 31.3.15 Stable build.
Can you check if the changes are in 31.3.15 or not?

RE#12 31.3.15 uses build 9456632 so it should have included the fix. Let's sync up in chat.

Retried as per offline discussion with Weilun, sometimes the time adjusts automatically but sometimes it gets adjusted after interacting with AVD.

I think we can close the bug as verified.