Emulator with API above API 30 not working in Intel 12th gen processor. [215231636]

Verified

Bug

Status Update

No update yet.

Description

ad...@gmail.com

created issue #1

Jan 19, 2022 05:38AM

Build: AI-203.7717.56.2031.7935034, 202111210535,

AI-203.7717.56.2031.7935034, JRE 11.0.10+0-b96-7249189x64 JetBrains s.r.o., OS Linux(amd64) v5.15.0-051500-generic, screens 1366.0x768.0

Emulator version:31.1.4
Android SDK platform tools version:31.0.3
Host cpu:12th Gen Intel(R) Core(TM) i5-12600K
Device name:Pixel 5

Emulator with system image android 11 is working properly but Android 12(31) and 12L(32) is not even loading in my PC.
It was working perfectly in my previous PC with Ryzen 3200G processor,So I believe that the issue is with intel 12th gen processor.FYI I'm not using any external GPU.running emulator in cpu.

idea.log

35 KB

View

Download

Comments

ku...@google.com <ku...@google.com> Jan 19, 2022 08:05PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> #2Jan 19, 2022 11:24PM

Reassigned to wd...@google.com.

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.

bo...@google.com <bo...@google.com> #3Jan 19, 2022 11:25PM

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.

ad...@gmail.com <ad...@gmail.com> #4Jan 20, 2022 05:56AM

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.

avd-log-without-modem.txt

219 KB

View

Download

tr...@gmail.com <tr...@gmail.com> #5Feb 12, 2022 04:22PM

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> #6Mar 2, 2022 08:47PM

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.

tr...@gmail.com <tr...@gmail.com> #7Mar 3, 2022 02:08PM

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

wd...@google.com <wd...@google.com> #8Mar 3, 2022 06:27PM

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

Message last modified on Mar 3, 2022 06:28PM

bo...@google.com <bo...@google.com> #9Mar 3, 2022 06:53PM

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!

bo...@google.com <bo...@google.com> #10Mar 3, 2022 07:23PM

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

Gemini

tr...@gmail.com <tr...@gmail.com> #11Mar 4, 2022 01:07AM

Gracias

bo...@google.com <bo...@google.com> #12Mar 4, 2022 02:02AM

Thanks #11
that is very helpful information.

I was surprised that emulator does not even try ipv4 when ipv6 failed;

error_setg should be just a warning instead of quitting.

ad...@gmail.com <ad...@gmail.com> #13Mar 19, 2022 04:25AM

"I tried enabling it and viola, the emulator is starting for me again (without needing the ModemSimulator flag)".

Yes,turning IPv6 on worked for me too.

wd...@google.com <wd...@google.com> #14Mar 23, 2022 06:10PM

bohu@, shall we close this bug?

wd...@google.com <wd...@google.com> Jun 10, 2022 06:23PM

Status: Won't Fix (Obsolete)

jo...@gmail.com <jo...@gmail.com> #15Apr 23, 2023 07:20PM

is this bug closed? I have followed steps in this issue tracker. Only way I can start my emulator is via the command terminal.

wd...@google.com <wd...@google.com> #16Apr 24, 2023 03:06PM

Status: Assigned (reopened)

@bohu It is probably a good idea to make sure that emulator keeps going when the name service resolution fails in ipv6 for at line

if ((rc = getaddrinfo(addr, port, &ai, &local)) != 0) {
        error_setg(errp, "address resolution failed for %s:%s: %s", addr, port,
                   gai_strerror(rc));
        goto err;
    }

wd...@google.com <wd...@google.com> Apr 28, 2023 05:00PM

Accepted by wd...@google.com.

bo...@google.com <bo...@google.com> #17Apr 28, 2023 05:51PM

agreed,

there should ahve been more attempts before erroing out

wd...@google.com <wd...@google.com> #18May 2, 2023 10:48PM

Hi, would it be possible to test this bug with the new build on Linux? Thanks! It works on my Linux machine.

wd...@google.com <wd...@google.com> #19May 8, 2023 02:59PM

Marked as fixed.

The bug is fixed by CL. I will also make sure this CL is cherry-picked to stable release.

ra...@google.com <ra...@google.com> #20May 15, 2023 10:37PM

Verified by ra...@google.com.

This bug has been verified as fixed with the latest Emulator Stable 32.1.13-10086546 on my Linux workstation. Following steps are followed to reproduce and verify the issue

Disabled Network connectivity on my machine
Launch API 30/31/32 AVDs using older Emulator[API 30 worked and 31/32 failed]
Installed Latest Emulator 32.1.13-10086546
Launch API 30/31/32 AVDs using new Emulator[API 30/31/32 works]