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

Hi, sorry for the trouble. I am working on improving our radio HAL. Unfortunately, it will take a while because it is very large. Please do not send non-ASCII characters in SMS.

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

Hi, I don't know if it may be implemented as quick fix on the actual code, but looks like Ñ is the only alphabet letter having the issue (at least between ones widely used within GSM 03.38 GSM 7-bit).

I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.

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

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

I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.

I see, maybe we missed that one Unicode somewhere then. Could be easier to fix then. I will take a look this week. Thank you for pointing this.

pixel2_33.txt

22 KB

View

Download

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

Just to get the full picture, I've tested with all characters included here

https://en.wikipedia.org/wiki/GSM_03.38 both in Basic Character Set (they should take 1 char of the 160) and Basic Character Set Extension (they should take 2 char, first is ESC prefix) and the only one causing the issue is Ñ

Sending a character outside that set, like á, message it's correctly split into 2 parts, first one of 70 chars as expected.

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

So, we have this:

https://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/android/emu/telephony/src/android/telephony/gsm.c#551

'Z', 0xc4, 0xd6,0x147, 0xdc, 0xa7,

I think 0x147 is wrong and it must be 0xd1 instead.

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

Yes, I agree. 0x147 is something similar, but correct one is 0xd1

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

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

Feel free to try this build (pick a gfxstream one):

https://ci.android.com/builds/branches/aosp-emu-master-dev/grid?head=12910395&tail=12910395&legacy=1

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

Accepted by wd...@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.4.6 Canary

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!

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

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

https://issuetracker.google.com/389330750#attachment62124209

Gemini

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

Gracias

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

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

RE#11 Ok, let me see what has been changed from build 9456632 to build 9536276. Thanks again for the information.

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

RE#11 I found the culprit. It's this CL which basically makes sure that the DNS servers discovered via /etc/resolve.conf are passed into slirp instances. In Android Emulator 32.1.11-9536276, the aforementioned CL was not cherry-picked while in emulator 31.3.15-9456632, the CL was merged. Therefore, the "problematic" link local DNS is passed into emulator 31 release but not emulator 32 release.

Solution: make sure the CL that ignores ipv6 link local DNS goes into in both 31 and 32 release and also make sure CL goes into emulator 32 release.

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

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

Marked as fixed.

We mark this bug as fixed since the issue is fixed by CL.

For those users who have experienced similar issues, please try emulator 32 stable release.

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

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

i want to install simulators android but i cant install in my laptop.

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

RE#15 It seems like this is a different topic if you cannot install android studio on your laptop. Would you like to file a different bug?