Android Studio Emulator Network [267647323]

Fixed

Bug

Status Update

No update yet.

Description

do...@gmail.com

created issue #1

Feb 3, 2023 11:38AM

Description has been deleted.

Comments

do...@gmail.com <do...@gmail.com> #2Feb 3, 2023 01:48PM

ml...@google.com <ml...@google.com> Feb 3, 2023 02:50PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Feb 8, 2023 07:22PM

Reassigned to wd...@google.com.

wd...@google.com <wd...@google.com> #3Feb 8, 2023 07:52PM

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.

Message last modified on Feb 8, 2023 07:58PM

do...@gmail.com <do...@gmail.com> #4Feb 9, 2023 09:20AM

@3 Why does it occur?
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.

pixel2_33.txt

22 KB

View

Download

wd...@google.com <wd...@google.com> #5Feb 9, 2023 03:51PM

Another similar issue that's related https://b.corp.google.com/issues/226426377

wd...@google.com <wd...@google.com> #6Feb 9, 2023 04:07PM

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.

ma...@google.com <ma...@google.com> #7Feb 9, 2023 04:33PM

@6 There are plenty of issues on emulator API 31 (and on Android 13 emulator). Many glitches. Spend 5 minutes on it and you will notice.
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...

Message last modified on Feb 9, 2023 04:35PM

ma...@google.com <ma...@google.com> #8Feb 9, 2023 04:36PM

@6 Also please check on all versions of the emulator, to see when this issue started, and fix from there.

wd...@google.com <wd...@google.com> #9Feb 9, 2023 08:26PM

Accepted by wd...@google.com.

I reproduced this bug on Windows with emulator version 31.2.10-8420304

Message last modified on Feb 9, 2023 08:26PM

wd...@google.com <wd...@google.com> #10Feb 10, 2023 12:16AM

@9 Please test on more API versions.

do...@gmail.com <do...@gmail.com> #11Feb 10, 2023 10:45AM

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

Message last modified on Feb 10, 2023 10:50AM

wd...@google.com <wd...@google.com> #12Feb 10, 2023 02:12PM

@5 I can't reach the link you've provided.

@11 So it could be the same reason that this bug occurs:

https://issuetracker.google.com/issues/233123301
?

wd...@google.com <wd...@google.com> #13Mar 13, 2023 09:48PM

RE#12 I have uploaded a patch to fix this issue. I don't think it's the same reason for https://issuetracker.google.com/issues/233123301

Message last modified on Mar 13, 2023 09:49PM

wd...@google.com <wd...@google.com> #14Mar 14, 2023 02:56PM

Marked as fixed.

@13 OK thanks.
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?

Message last modified on Mar 14, 2023 03:41PM

go...@gmail.com <go...@gmail.com> #15Jul 19, 2023 10:45AM

RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.

wd...@google.com <wd...@google.com> #16Aug 28, 2023 02:58PM

@15 Please check before too, to make sure it doesn't cause new issues