Status Update
No update yet.
Comments
km...@google.com
bo...@google.com
wd...@google.com
lblb636@ Thanks for reporting this bug. I just want to confirm that the issue is the call device button being not responsive according to the uploaded video. It seems like this issue only happened on Windows.
wd...@google.com
And why only from specific API of Android?
On API 28 for example, it doesn't occur...
Please fix this issue for all API versions of the emulator.
de...@google.com
Another similar issue that's related
ra...@google.com
RE#4 I need to try this on Windows laptop first and I couldn't repro on MacOS or Linux. But I think this is most likely related to the modem simulator we introduced for API 31. Will need to further investigate.
wd...@google.com
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...
de...@google.com
wd...@google.com
I reproduced this bug on Windows with emulator version 31.2.10-8420304
wd...@google.com
bo...@google.com
de...@google.com
wd...@google.com
Found the root cause when the "call device" button was unresponsive. It became unresponsive because the inbound call failed to initialize. Basically, the modem simulator's shared FD failed. When receive_inbound_call is invoked, it is supposed to make connection to the "host server" via a shared fd but it is flaky on Windows unfortunately.
modem-simulator: receive_inbound_call:101 inbound call from 6505551212
modem-simulator: process_msgs:296 waiting for new messages ...
modem-simulator: main_host_thread:501 got connection at host server at 65094
modem-simulator: start_calling_thread:254 making a connection to main host server 65094
modem-simulator: main_host_thread:507 Detected close from the other side
modem-simulator: start_calling_thread:262 nothing read quit
modem-simulator: main_host_thread:494 looping at main host server at 65094
modem-simulator: start_calling_thread:284 done with this thread
ra...@google.com
@11 So it could be the same reason that this bug occurs:
?
wd...@google.com
RE#12 I have uploaded a
ra...@google.com
Have you tested it on all API versions, to make sure that it doesn't cause new issues, and also fixes the issue on other places in case it's there too?
wd...@google.com
RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.
mi...@mercurydevelopment.com
wd...@google.com
When will the fix be available?
mi...@mercurydevelopment.com
The fix has been merged in both 31 release and 32 release for since 05/2022.
wd...@google.com
On which version ?
wd...@google.com
#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.
mi...@mercurydevelopment.com
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.
ne...@gmail.com
Em sex., 3 de fev. de 2023 15:08, <buganizer-system@google.com> escreveu:
wd...@google.com
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.
mi...@mercurydevelopment.com
I'm launching the emulator in a standalone window.
wd...@google.com
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?
mi...@mercurydevelopment.com
Sure, will try
ne...@gmail.com
mandaram aí por escrito
Em sex., 3 de fev. de 2023 15:59, <buganizer-system@google.com> escreveu:
mi...@mercurydevelopment.com
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.
wd...@google.com
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!
mi...@mercurydevelopment.com
Thank you!
wd...@google.com
wd...@google.com
de...@google.com
ranjitkumar@
mp...@gmail.com
pa...@marketrebellion.com
Host: Darwin Kernel Version 22.4.0 arm64
wd...@google.com
wd...@google.com
wd...@google.com
The fix is available in the next canary and stable release in June.
de...@google.com
de...@google.com
si...@gmail.com
Android emulator version 33.1.4-9936625
Host: macbook pro M1 Max, macOs: 13.5.1 (22G90)
Is there anything I need to do to fix this?
si...@meta.com
wd...@google.com
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.
ra...@google.com
wd...@google.com
ra...@gmail.com
I confirm 34.1.9 has no this issue anymore
Description
Please Read:https://developer.android.com/studio/report-bugs.html#emulator-bugs
Android Studio Version: 2021.3
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.13-9189900 HAXM / KVM Version: HVF 12.6.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 12.6
CPU Manufacturer: Apple CPU: Apple M1 Max
RAM: 65536 MB
GPU:
Build Fingerprint:
AVD Details: Name: Pixel_3a_API_33_arm64-v8a CPU/ABI: arm64 Path: /Users/ralfeus/.android/avd/Pixel_3a_API_33_arm64-v8a.avd Target: google_apis [Google APIs] (API level 33) Skin: 1080x2220 SD Card: 800 MB AvdId: Pixel_3a_API_33_arm64-v8a PlayStore.enabled: false avd.ini.displayname: Pixel_3a_API_33_arm64-v8a 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: emulated hw.camera.front: emulated hw.cpu.ncore: 1 hw.dPad: no hw.device.hash2: MD5:0e6953ebf01bdc6b33a2f54746629c50 hw.device.manufacturer: Google hw.device.name: pixel_3a hw.gps: yes hw.gpu.enabled: yes hw.gpu.mode: auto hw.initialOrientation: Portrait hw.keyboard: yes hw.lcd.density: 440 hw.lcd.height: 2220 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: no skin.dynamic: yes skin.path.backup: _no_skin tag.display: Google APIs tag.id: google_apis vm.heapSize: 256
Steps to Reproduce Bug:
Expected Behavior: Time matches one of host or real one from NTP server
Observed Behavior: Time is behind real one