IssueTracker

Adding 2 more thread dumps from another freeze. Again after switching branches and updating from git.

Thanks for the report. I believe that this is fixed in our development branch, and also in the branch that will become Ladybug Feature Drop Beta. If you could verify that this doesn't happen in a nightly build (from https://developer.android.com/studio/nightly) that would be helpful -- and of course if you can trigger this in a recent nightly build, that's would be very important information.

Sorry, I have not tried it on the nightly build, but since then I updated to Meerkat and I have not seen the freeze afterwards.

That's good to hear. I think that the fix (which for reference was https://github.com/JetBrains/intellij-community/commit/fe621544dd61a9af34d97958d3d823a7c3454a87) is effective for both beta and canary branches.

For the record I am also arranging for https://github.com/JetBrains/intellij-community/commit/a444c8a500883669fc05c7177f93b5b794fdd13b (same fix, different implementation class) to be included; it's probably inactive code in our configurations, but it might be possible to trigger nevertheless.

Thanks for the confirmation!

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 RC 1
• Android Gradle Plugin 8.8.0-rc01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Ucfucuccj

Hyxucyccchccjch

Ycucuccjcn

Hola mundo

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.

RE#18 Really appreciate it. I will start testing it.

#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!

Thank you!

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