Fixed
Status Update
No update yet.
Comments
am...@google.com
ya...@google.com
bo...@google.com
ws...@gmail.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.
bo...@google.com
@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.
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.
ws...@gmail.com
Another similar issue that's related
ws...@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.
bo...@google.com
@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) ...
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...
bo...@google.com
@6 Also please check on all versions of the emulator, to see when this issue started, and fix from there.
ws...@gmail.com
I reproduced this bug on Windows with emulator version 31.2.10-8420304
bo...@google.com
@9 Please test on more API versions.
ws...@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
bo...@google.com
@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
?
@11 So it could be the same reason that this bug occurs:
?
ws...@gmail.com
RE#12 I have uploaded a
bo...@google.com
@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?
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?
ws...@gmail.com
RE#14 This issue is for API 31+, I will check for API 32 and API 33. Thanks for reminding me.
bo...@google.com
@15 Please check before too, to make sure it doesn't cause new issues
ws...@gmail.com
Please fix it for all Android emulator versions.
When will the fix be available?
When will the fix be available?
bo...@google.com
The fix has been merged in both 31 release and 32 release for since 05/2022.
de...@google.com
@18 Merged, but is it available for all using the normal updates?
On which version ?
On which version ?
to...@gmail.com
I certainly don't know what to do at this point, I have had 3 cell phones and 3 computers and a Chromebook all reconfigured and they were not even open out of the box in the case of the Chromebook and the hp All in one, 3 cell phones bootlocked and the deffrent types of platforms of each component of the vertual box in which e have to call it for what it is. The activity surrounding my devices in this instance is also the same as the activity surrounding my devices and cyber security breaches and identity theft and cyber exploits I recall in December 31,201. To August of 2021. The use of X86, System 32,64, Android9 pie and below, Windows NT, iOS, sequel, XML, Emulators and Ghosting, casting, broadcast and interaction with my actions in real time in visual and text, and auto correct of a click or choice of words with certain systems in the accounts for the same platforms as of today. Google, Chromium is is a component of the ratio so is chrome OS, firebase as a identifyer but not a component, Windows is affected, Android, Apple, Amazon flypads are very operational in this environment and they are used for the activity monitoring in some occasionally. In this hybrid Linx. Is the major part of the ratio of the different codes. Meta data was very operational in the activity of my windows 11 HP All inn One, my program files were of the meta data type and python was also used. I don't want to ramble on this subject for the reason that I have lost the majority of the data back ups, and the researching I had to take on when I was first exposed to the vertual Box. I probably would have a very detailed and technically correct of terms for the activity of the ratio so much so is that the same in astute use of a tunnel to deliver to intubation and the details of the IP address and the Protocol for the activity of the Modems and ro the gateways identity the value of the:,.,0,= f,E this instance it was the use of a dummy and the ipv4, Asus WRT-CMd-Exe , for the Network and the Windows, and the Androids it was a file to the chrome in the download and I had to delete it, but it was not a update I had down loaded. It was a guesture of interaction with my actions and my intrests as the activity is very disturbing the Tayloring of the individual is very befriending and the isolation of the exhausting tasking and the persistent,. It occupies and I have been trying to take on an old friend with a very interesting infatuation of the Devices and the details of what I utilize them for or any subsequent to reprogram a operate to the very befriending of my rights in some of the activity of the data that I have I think to myself and have to be aware that this is very disturbing and I have to allow it or any other case there's no way to stop it.
tonyvg2013@gmail.com
Tony if you want to contact me for some questions or related topic it would be great.
I have been a whitness for the activity of my friends and others over 35 individual cases of the same MO.
tonyvg2013@gmail.com
Tony if you want to contact me for some questions or related topic it would be great.
I have been a whitness for the activity of my friends and others over 35 individual cases of the same MO.
Description
We're running the
emulatorCLI, using the latestAPI 30 AOSP ATD x86image, on an x86_64 host, like this:/android-emulator-sdk/emulator/emulator -avd emulator-avd -no-boot-anim -read-only -verbose -no-window -sysdir ./system/x86 -system ./system/x86/system.img -ramdisk ./system/x86/ramdisk.img -qemu -enable-kvmOn emulator 31.2.10:
and the emulator starts successfully.
On emulator 31.3.10:
Eventually failing with this:
(Note: we pass the
-sysdirarg explicitly, since our system images are not stored in the SDK directory.)Found AVD target architecture: arm, thus trying to run qemu-system-aarch64-headless, seems likely to be the root cause?