Status Update
No update yet.
Comments
aa...@google.com
bo...@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.
ma...@gmail.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.
rk...@google.com
Another similar issue that's related
ma...@gmail.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.
rk...@google.com
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...
ma...@gmail.com
rk...@google.com
I reproduced this bug on Windows with emulator version 31.2.10-8420304
rk...@google.com
ma...@gmail.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
rk...@google.com
@11 So it could be the same reason that this bug occurs:
?
rk...@google.com
RE#12 I have uploaded a
ma...@gmail.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?
rk...@google.com
RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.
ma...@gmail.com
rk...@google.com
When will the fix be available?
ma...@gmail.com
The fix has been merged in both 31 release and 32 release for since 05/2022.
ko...@google.com
On which version ?
an...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Emulator 35.3.11 Stable
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!
an...@google.com
Further fixes for this issue are now available in:
- Android Emulator 35.4.5 Canary
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
Hi, my name is Max, and I’m currently experiencing an issue with my Android Virtual Device (AVD). After creating the AVD, I’m unable to open it. The system keeps displaying a pop-up error stating that the AVD has terminated.
I checked the log file, and it shows the following error:
" 2024-12-04 19:07:57,970 [ 676451] INFO - Emulator: Pixel 9 Pro XL API 30 - [4504:2088:20241204,190757.970:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\crazy\AppData\Local\Temp\AndroidEmulator\emu-crash-35.2.10.db\attachments\4adcdf86-281b-417e-b896-b530668bbdcf: The system cannot find the file specified. (2) "
When I checked the file location, the folder was empty. Can u help solve about this ? Thank you!
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
3. If you know what they are, write the steps to reproduce:
3A. Unable to open the AVD
3B. Cannot file the attactments file
3C.
In addition to logs, please attach a screenshot or recording that illustrates the problem.
For more information on how to get your bug routed quickly, see
Build: AI-242.23339.11.2421.12700392, 202411230116
AS: Ladybug | 2024.2.1 Patch 3
AI-242.23339.11.2421.12700392, JRE 21.0.3+-12282718-b509.11x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 1920x1080 (100%), 1920x1080 (125%)
Android Gradle Plugin: 8.7.3
Gradle: 8.9
Gradle JDK: JetBrains Runtime 21.0.3
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
Source: send_feedback_icon```