Android Emulator 31.3.10 thinks target architecture is ARM on x86 [247843000]

Fixed

Bug

Status Update

No update yet.

Description

ws...@gmail.com

created issue #1

Sep 20, 2022 08:49PM

We're running the emulator CLI, using the latest API 30 AOSP ATD x86 image, 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-kvm

On emulator 31.2.10:

INFO    | Android emulator version 31.2.10.0 (build_id 8420304) (CL:N/A)
INFO    | Found AVD name 'emulator-avd'
INFO    | Found AVD target architecture: x86
INFO    | argv[0]: '/android-emulator-sdk/emulator/emulator'; program directory: '/android-emulator-sdk/emulator'
INFO    | emuDirName: '/android-emulator-sdk/emulator'
INFO    | Probing for ./system/x86/kernel-ranchu-64: file exists
INFO    | try dir /android-emulator-sdk/emulator
INFO    | Trying emulator path '/android-emulator-sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64'
INFO    | Found target-specific 64-bit emulator binary: /android-emulator-sdk/emulator/qemu/linux-x86_64/qemu-system-x86_64
...

and the emulator starts successfully.

On emulator 31.3.10:

INFO    | Android emulator version 31.3.10.0 (build_id 8807927) (CL:N/A)
INFO    | Found AVD name 'emulator-avd'
WARNING | Failed to process .ini file /home/coder/.android/./config.ini for reading.
WARNING | Found AVD target architecture: arm
INFO    | Found AVD target architecture: arm
INFO    | argv[0]: '/android-emulator-sdk/emulator/emulator'; program directory: '/android-emulator-sdk/emulator'
emulator: INFO: Use user provided system path ./system/x86
INFO    | emuDirName: '/android-emulator-sdk/emulator'
emulator: INFO: Use user provided system path ./system/x86
INFO    | Probing for ./system/x86/kernel-ranchu-64: file exists
INFO    | try dir /android-emulator-sdk/emulator
INFO    | Trying emulator path '/android-emulator-sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64-headless'
INFO    | Found target-specific 64-bit emulator binary: /android-emulator-sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64-headless

Eventually failing with this:

ERROR   | This AVD's configuration is missing a kernel file! Please ensure the file "kernel-ranchu" is in the same location as your system image.
ERROR   | ANDROID_SDK_ROOT is defined (/android-emulator-sdk) but cannot find kernel file in /android-emulator-sdk/system-images/ sub directories

(Note: we pass the -sysdir arg 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?

Comments

am...@google.com <am...@google.com> Sep 21, 2022 01:07PM

Assigned to an...@google.com.

ya...@google.com <ya...@google.com> Sep 21, 2022 06:43PM

Reassigned to bo...@google.com.

bo...@google.com <bo...@google.com> #2Sep 21, 2022 07:23PM

Accepted by bo...@google.com.

These changes would be really nice! Being able to change the text colour is really important as it now doesn't match the rest of our app either.

Stack overflow posting -

http://stackoverflow.com/questions/32533069/how-to-change-a-title-color-in-chrome-custom-tabs

ws...@gmail.com <ws...@gmail.com> #3Sep 21, 2022 07:47PM

Changing text color and the overflow icon color is important to us too! Awesome work on the feature though.

bo...@google.com <bo...@google.com> #4Sep 22, 2022 05:28PM

The ability of customize the status bar color is very important!

ws...@gmail.com <ws...@gmail.com> #5Sep 22, 2022 07:02PM

It is in the essence of a "custom" UI component to have a custom color. Please add this feature!

ws...@gmail.com <ws...@gmail.com> #6Sep 22, 2022 07:03PM

I have noted that the status bar automatically generated from the toolbar color is a bit darker than needed. The status bar color of the chrome activity is different to the one of the rest of my app. It doesn't strictly follow Material guidelines.

bo...@google.com <bo...@google.com> #7Sep 23, 2022 05:37PM

The same issue I met. And is there a way to customize the title? using my own title rather than the url's. Thanks

bo...@google.com <bo...@google.com> #8Sep 23, 2022 05:39PM

Would very appreciate this enhancement!

ws...@gmail.com <ws...@gmail.com> #9Sep 26, 2022 08:35PM

I'd love to have the possibility to change title text color, I'll be a very important graphic consistency inside my app

bo...@google.com <bo...@google.com> #10Sep 27, 2022 10:30PM

Voting +1 for this feature.

ws...@gmail.com <ws...@gmail.com> #11Sep 27, 2022 10:32PM

It has been more than a year. Please add this!

bo...@google.com <bo...@google.com> #12Sep 28, 2022 04:23AM

[Comment deleted]

ws...@gmail.com <ws...@gmail.com> #13Sep 28, 2022 04:47PM

It will certainly be a nice feature and have a nice title for the chrome tab. Please fix this.

bo...@google.com <bo...@google.com> #14Sep 28, 2022 06:17PM

Customize the status bar color is a real need. Voting +1

ws...@gmail.com <ws...@gmail.com> #15Sep 28, 2022 06:31PM

Yes, it's needed definitely. Please!! Voting+1.

bo...@google.com <bo...@google.com> #16Sep 28, 2022 11:20PM

Any date to the release of this feature? Working with VectorDrawables is awesome and let us have an IconKit but this little impediment make it not perfect

Message last modified on Sep 28, 2022 11:21PM

ws...@gmail.com <ws...@gmail.com> #17Sep 29, 2022 12:59AM

Voting +1 for this feature.

bo...@google.com <bo...@google.com> #18Sep 29, 2022 03:34AM

Assigned to de...@google.com.

Voting +1 for this feature.

de...@google.com <de...@google.com> #19Oct 17, 2022 04:38PM

Marked as fixed.

voting +1 for this feature

to...@gmail.com <to...@gmail.com> #20Oct 19, 2022 08:50AM

Voting +1 for this feature.

IMG_20221005_235528.jpg

3 MB

View

Download

Screenshot_20220909-184414.png

127 KB

View

Download

IMG_20220912_102411.jpg

4.3 MB

View

Download

IMG_20221005_235538.jpg

3 MB

View

Download

route.print.txt

2.6 KB

View

Download

Issue 247843000

Description

Issue summary

Comments

am...@google.com <am...@google.com> Sep 21, 2022 01:07PM

ya...@google.com <ya...@google.com> Sep 21, 2022 06:43PM

bo...@google.com <bo...@google.com> #2Sep 21, 2022 07:23PM

ws...@gmail.com <ws...@gmail.com> #3Sep 21, 2022 07:47PM

bo...@google.com <bo...@google.com> #4Sep 22, 2022 05:28PM

ws...@gmail.com <ws...@gmail.com> #5Sep 22, 2022 07:02PM

ws...@gmail.com <ws...@gmail.com> #6Sep 22, 2022 07:03PM

bo...@google.com <bo...@google.com> #7Sep 23, 2022 05:37PM

bo...@google.com <bo...@google.com> #8Sep 23, 2022 05:39PM

ws...@gmail.com <ws...@gmail.com> #9Sep 26, 2022 08:35PM

bo...@google.com <bo...@google.com> #10Sep 27, 2022 10:30PM

ws...@gmail.com <ws...@gmail.com> #11Sep 27, 2022 10:32PM

bo...@google.com <bo...@google.com> #12Sep 28, 2022 04:23AM

ws...@gmail.com <ws...@gmail.com> #13Sep 28, 2022 04:47PM

bo...@google.com <bo...@google.com> #14Sep 28, 2022 06:17PM

ws...@gmail.com <ws...@gmail.com> #15Sep 28, 2022 06:31PM

bo...@google.com <bo...@google.com> #16Sep 28, 2022 11:20PM

ws...@gmail.com <ws...@gmail.com> #17Sep 29, 2022 12:59AM

bo...@google.com <bo...@google.com> #18Sep 29, 2022 03:34AM

de...@google.com <de...@google.com> #19Oct 17, 2022 04:38PM

to...@gmail.com <to...@gmail.com> #20Oct 19, 2022 08:50AM

Add comment

Issue metadata