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.

I'm still seeing this issue in Emulator 32.1.10.

RE#16 Hi minyushov@, would it be possible to provide more details with what kind of host OS and what are the repro steps I can follow? Thanks!

Hi

I'm using MacBook Pro with Apple Silicon and macOS Ventura 13.0.1.

Steps are pretty straightforward:

1. Power adapter is plugged in. Energy mode is set to Automatic for both 'On battery' and 'On power adapter' options.
2. Run emulator.
3. Keep it running until macbook automatically goes to sleep.
4. Wake it up after ~10 minutes and observe the time in the emulator. It shows not the actual time but the time when macbook fell asleep.

I'm not sure that this happens all the time but often enough.

#18

One more question: After step 4 Wake it up after ~10 minutes and observe the time in the emulator. It shows not the actual time but the time when macbook fell asleep., have you tried to move the emulator window? I think the time should be updated when you starting using the emulator.

I'm not sure that I've moved the emulator window but usually I install our app using Android Studio and see network errors due to time difference between the app and our servers. So it looks like the time isn't updated in this case.

RE#21 Another question, are you using the emulator in a tool window? I think it might be the specific scenario which still has bug.

I'm launching the emulator in a standalone window.

RE#24 Ok, I tried it myself and I could not reproduce unfortunately. With have you tried to move the emulator window? I think the time should be updated when you starting using the emulator. being said, would it be possible for you to try it again?

Sure, will try

Unfortunately, it happened again. Moving a window did not help.

Some additional info:

• I use a pair of external displays connected via Type-C, Bluetooth keyboard and mouse.
• Power adapter is plugged in. This way I can safely close a macbook lid and continue using it with the external displays. When macbook is sleeping I can wake it up by pressing a key on a keyboard or by clicking a mouse button.
• Today I left my workplace for 40-50 minutes. When I came back, external displays were in standby mode. After waking the macbook up, I've reproduced the issue.

RE#28 I realized what went wrong. My fix didn't merge into the 32 release. It's only available in the 31 release and the dev branch. Let me resolve that issue real quick and release a new version. Thanks for your input!

New CL merged. Will release a new version ASAP.

The fix is available in the next canary and stable release in June.

RE#36 To clarify, the bug is still reproducible for API 29 and API 30. Other APIs are working fine. We have an internal bug for tracking the API specific time update issue.

The new fix is merged

sivhuop@ Hi, the fix is not merge in (33.1.4-9936625). Would it be possible for you to upgrade your emulator the latest canary version or at least 33.3.14? Here is the link to the archived emualtor downloads.

RE#42 Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps as much as possible of the following information:

1, Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -wipe-data” and send the logs from terminal

2, Run adb bugreport and send the zip file.

I confirm 34.1.9 has no this issue anymore

https://developer.android.com/studio/releases/emulator#32-1-14

We are working on a better patch (the performance should be about as before and should also work on non-Max CPUs as we see here), the build should be available today-tomorrow.

I shared my local build with our next patch to fix this issue.

This is our second version:

https://ci.android.com/builds/submitted/10937044/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10937044.zip

Hi clerici.m89, thank you for the update. Could you please try (our first fix):

https://ci.android.com/builds/submitted/10914596/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-10914596.zip

Hi Andi, the Android Emulator is released independently from the Android Studio. The 32.x.x version is EOL, 33.x.x will be promoted to stable soon and the webcam fixes will be available there.

also the image has different size as before, at least with obs before sonoma i was seeing a cropped image out of the 1280x720 but now i can see it full size on the emulator screen.

In the first fix there is no scale function, I crop and put black everywhere I have no pixels for. When we have the scale function, we crop a smaller image and resize to fill all requested pixels.

Hi Andi, thank you for reporting this. I think this is a different problem here as 10914596 does not change anything related to opening the device and 10937044 probably missed even more around this case.

I am marking this as "fixed" for our internal release process. We are still looking into it. The changes should be available in 34.1.7 (canary) and 33.1.21 (stable).

The Emulator is release independently from the Android Studio. This fix is available in the Emulator 34.1.11 which is shipped with the Android Studio Iguana (2023.2.1 Canary 14).

If the Emulator is released independently, I would expect that it would also be updated in SDK Manager for prior versions of Android Studio, no?

We ship the emulator through several channels (stable, canary, beta), if you are on the stable channel, you will get the emulator updates later. Consider getting https://developer.android.com/studio/preview for faster updates.

The fix does work with the actual webcam but it BREAKS the virtual webcam. Here's the error message:

ERROR   | -[MacCamera captureOutput:didOutputSampleBuffer:fromConnection:]: error in allocate rotateInputBuffer_: -21602
ERROR   | -[MacCamera captureOutput:didOutputSampleBuffer:fromConnection:]: error in allocate rotateInputBuffer_: -21602
 (127x)
ERROR   | _camera_client_query_frame: Unable to obtain first video frame from the camera '7626645E-4425-469E-9D8B-97E0FA59AC75' in 2001 milliseconds: Undefined error: 0.

Please help take a look

Also got the same error as above comment. The 34.1.11 breaks emulator with virtual cam on Sonoma.

error in allocate rotateInputBuffer_: -21602

This one is fixed in https://ci.android.com/builds/submitted/11125189/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11125189.zip

This one is fixed in https://ci.android.com/builds/submitted/11125189/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11125189.zip

This one works, thank you! Will this new version be released anytime soon?

This one works, thank you! Will this new version be released anytime soon?

Please try our latest stable push (33.1.23).

Hi Timar, please file a new bug with repro steps and screenshots. Please specify the Android Studio version, the Emulator version and the system image you use.

Timar, file a new bug into the Android Studio component.

You can try the latest Emulator version from https://developer.android.com/studio/emulator_archive

If the performance is still bad, you could try fixing this yourself and send us your patch. The Emulator is open source, this is what we changed: https://android.googlesource.com/platform/external/qemu/+log/refs/heads/emu-master-dev/android/android-emu/android/camera/camera-capture-mac.m

still poor performance after opening camera.

Hi industrialstrengthdatasystems, if you can build Emulator yourself, please try this patch: https://android-review.googlesource.com/c/platform/external/qemu/+/3093185

luunguyen0811, this is tracked in https://issuetracker.google.com/issues/325814592

Hi folks, please try this build for improved webcam (while it is open) performance:

https://ci.android.com/builds/submitted/11871170/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11871170.zip

A newer build to try:

https://ci.android.com/builds/submitted/11887261/emulator-mac_aarch64_gfxstream/latest/sdk-repo-darwin_aarch64-emulator-11887261.zip

Hi bien2k4. Unfortunately, MacOS camera experts are in short supply here :) Thank you for reporting that the issue does not repro on Ventura.

BTW, the camera performance issue is tracked here: https://issuetracker.google.com/issues/325814592