image announce incorrect ABI support / tested with android-x86-8.1-rc2

[Румен Петров]

Hello,

Image android-x86-8.1-rc2 announce itself as suitable for 86 and arm(5 and 7) 32-bit processors. As result with IDE like Android studio could be uploaded application that support only arm processor (native binaries, build with "product flavors with dimension by 'abi'").

Image status could be verified with property check (unix command line):

$ adb shell getprop  | grep -i cpu

Result is:

[ro.product.cpu.abi]: [x86]
[ro.product.cpu.abilist]: [x86,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [x86,armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []

As is visible "abilist" is not correct.

Also logcat is full with warnings like:
... W/zygote: Unexpected CPU variant for X86 using defaults: x86

Regards,

Roumen Petrov

[Antony Stone]

On Wednesday 02 January 2019 at 19:25:17, Румен Петров wrote:

> Hello,
>
> Image android-x86-8.1-rc2 announce itself as suitable for 86 and arm(5 and
> 7) 32-bit processors.

I think the clue is in the name - "Android-x86" is designed to run on x86
CPUs; if you want to run Android on an ARM CPU, just use the standard Android
release, instread of Android-x86.

> As result with IDE like Android studio could be uploaded application that
> support only arm processor (native binaries, build with "product flavors with
> dimension by 'abi'").
>
> Image status could be verified with property check (unix command line):
> $ adb shell getprop | grep -i cpu
>
> Result is:
> [ro.product.cpu.abi]: [x86]
> [ro.product.cpu.abilist]: [x86,armeabi-v7a,armeabi]
> [ro.product.cpu.abilist32]: [x86,armeabi-v7a,armeabi]
> [ro.product.cpu.abilist64]: []
>
> As is visible "abilist" is not correct.

Are you sure this means that Android-x86 claims to be able to *run* on an ARM
CPU, or is it possible that it just means it will accept ARM-code apps and
support running those under it (with an emulator such as Houdini)?


Antony.

--
3 logicians walk into a bar. The bartender asks "Do you all want a drink?"
The first logician says "I don't know."
The second logician says "I don't know."
The third logician says "Yes!"

Please reply to the list;
please *don't* CC me.

[Chih-Wei Huang]

Румен Петров <rpetr...@gmail.com> 於 2019年1月3日 週四 上午2:25寫道：

>
> Image android-x86-8.1-rc2 announce itself as suitable for 86 and arm(5 and 7) 32-bit processors. As result with IDE like Android studio could be uploaded application that support only arm processor (native binaries, build with "product flavors with dimension by 'abi'").
>
> Image status could be verified with property check (unix command line):
> $ adb shell getprop | grep -i cpu
>
> Result is:
> [ro.product.cpu.abi]: [x86]
> [ro.product.cpu.abilist]: [x86,armeabi-v7a,armeabi]
> [ro.product.cpu.abilist32]: [x86,armeabi-v7a,armeabi]
> [ro.product.cpu.abilist64]: []
>
> As is visible "abilist" is not correct.

What's not correct?

It means we can run APK with x86, armeabi-v7a, or armeabi.
That's true. Of course, you need to enable ARM translator
(aka native bridge, houdini) to run a pure arm APK.

Unfortunately there is no known public houdini for 32k32u yet.
To use ARM translator you have to run the 64-bit version
and enable it via
Settings -> Android-x86 options -> Enable native bridge

> Also logcat is full with warnings like:
> ... W/zygote: Unexpected CPU variant for X86 using defaults: x86

I didn't check the exact reason.
But it's harmless.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org