1462934 - "mach android-emulator" for x86 shows dialog "Running an x86 based android virtual device (AVD) is 10x faster.

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Testing, defect, P2)

Description

[Rob Wu [:robwu]]

I installed the x86 Android emulators as follows:
mach android-emulator --version=x86
mach android-emulator --version=x86-6.0
mach android-emulator --version=x86-7.0

The emulators were installed to:
~/.mozbuild/android-device/avd/mozemulator-x86-6.0.avd
~/.mozbuild/android-device/avd/mozemulator-x86-7.0.avd
~/.mozbuild/android-device/avd/mozemulator-x86.avd

(file sizes 3547 MB, 4766 MB, 1417 MB respectively; total is 9729 MB)

In all cases I get the following dialog when the emulator is launched:
"Running an x86 based android virtual device (AVD) is 10x faster."

I looked in ~/.mozbuild/android-device/emulator.log and found:

<emulator: No build.prop property file found.>
<emulator: No boot.prop property file found.>
<emulator: Cannot find target CPU architecture, defaulting to 'arm'>
<emulator: Cannot find target CPU ABI, defaulting to 'armeabi'>

I looked up these messages in the source of the QEMU fork for Android, in android/avd/util.c and android/avd/info.c,
e.g. at https://android.googlesource.com/platform/external/qemu/+/65e628f590e3bbc9d8ac6810ceaa460f59111344/android/avd/
or https://github.com/android-ia/platform_external_qemu/tree/006a174244e336c578f45bf78a9dbdbd890c217d/android/avd


I got rid of the dialog by creating build.prop,
e.g. ~/.mozbuild/android-device/avd/mozemulator-x86-6.0.avd/build.prop ,
and setting the target via "ro.product.cpu.abi = x86" (or x86_64 - both work fine here).

This bug could be fixed by uploading the missing build.prop to tooltool.
If that is too much work/risky, then an alternative is to generate the file at one of the lines that I marked at https://searchfox.org/mozilla-central/rev/0e80033a10ca4f9940c083a33d175c99ab3568e5/testing/mozbase/mozrunner/mozrunner/devices/android_device.py#474,498,626

Comment 1

[Geoff Brown [:gbrown]]

Thanks so much for figuring this out Rob. I have created new avds just like the old ones but with the addition of build.prop files, copied from the appropriate sdk system-images. I included arm avds for completeness.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=b10ee8a91b5be7e4cb3a166af70cea9d198ea883

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/68fd5d83cc07
Update Android AVD configs to use archives with build.prop included; r=me,a=test-only

Comment 3

[Bogdan Tara[:bogdan_tara | bogdant]]

https://hg.mozilla.org/mozilla-central/rev/68fd5d83cc07