Status Update
No update yet.
Comments
rk...@google.com
rk...@google.com
ga...@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.
rk...@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.
ga...@gmail.com
Another similar issue that's related
rk...@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.
ga...@gmail.com
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...
rk...@google.com
rk...@google.com
an...@google.com
I reproduced this bug on Windows with emulator version 31.2.10-8420304
an...@gmail.com
le...@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
Description
This is the correct behaviour in case characters of UCS-2 Encoding are used, but not for standard characters included into GSM 03.38
Ñ character is included into GSM 03.38 GSM 7-bit default alphabet:
In fact with a real phone only one SMS with 97 characters is received.
Code is pretty easy, see attached screenshots, with $ everything is ok, while with Ñ smsMessages array is made of 2 items
For privacy and security reasons I cannot attach more than this and full log files, but I think it may be enough because it's quite simple to reproduce.
Tested with emulator API 31 and API 35, both have the issue.
Studio Build: Build #AI-242.23726.103.2422.12816248, built on December 18, 2024
Version of Gradle: 8.9
Version of Java: 11
OS: Windows 11 Professional