Test libs for new houdini

[Daniel Fages - android-x86]

Hi all,
I'm very sorry but I can hardly find time to integrate new houdini features in android-x86.
I've managed to port my changes to android-x86-ics but can hardly find time to test it.
So I've just rebuilt the two necessary libs (libdvm.so libandroid_runtime.so) so that some (advanced) users can test.
Please be careful I didn't even test it so it can break things.

If you want to test you have to replace your libdvm.so and libandroid_runtime.so libs by the following ones :
- http://androvm.org/Download/android-x86/libdvm.so
- http://androvm.org/Download/android-x86/libandroid_runtime.so

You also have to download the houdini libs from http://androvm.org/Download/houdini-libs-20121106.tgz and push them on your android host.

Once again, your system could be unstable and event not boot after pushing these libs - so be careful.

If this works for you, I'll happily push the changes to the android-x86 git.
If it not, I'll try to find some time to debug that.

Dan.

[gerhard smith]

Hi Dan,
I gave it a whirl, but sadly it seems to break the network access.
Opera Mini crashed but used to work without the new patch
Skype crashed - it used to load OK but did not manage to log in
Angry birds ran OK but I believe it has been ported to android-x86

\link below of what I did and dmesg output. Unfortunately logcat log is full of rubbish so useless. I will clean it up if it will help you.

https://rapidshare.com/files/595132885/postfile



Thanks for your efforts

[Chih-Wei Huang]

Hi Dan,
Would you please send the patches to the forum to review
so people can debug it easier? Thanks!

2012/11/29 gerhard smith <ger...@wearethevoters.com>:

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

[Daniel Fages - android-x86]

Hi,
you'll find attached my patch for Jelly Bean. Didn't have time to adapt and test it for ics-x86.
This is a "full patch" over unmodified Android source code so it may be easier to adapt over the initial AOSP dalvik source code.

Some differences with previous patch
- ARM native activity are now supported (modifications in the frameworks/base/core/jni/android_app_NativeActivity.cpp)
- ICS houdini libraries from a "xolo" smartphone are now used
- Android can now use a "ro.product.cpu.abi3" so that we can load x86, armeabi-v7a and armeabi libs

This should improve ARM support in android-x86.

Up-to-dated libs are here : http://androvm.org/Download/houdini-libs-20121106.tgz

[Daniel Fages - android-x86]

One thing I forgot : You can now have a look at the androvm source code at https://github.com/androvm in case I forgot something.

Dan.

> <patch_dalvik_houdini-20121204><patch_frameworks-base_houdini-20121204><patch_frameworks-base-2_houdini-20121204><patch_libnativehelper_houdini-20121204>
>
> Dan.

>> --
>> You received this message because you are subscribed to the Google Groups "Android-x86" group.
>> To post to this group, send email to andro...@googlegroups.com.
>> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>>
>

[Chih-Wei Huang]

Thanks a lot!

About arm native activity, could you suggest
what apps could be used to test it?

2012/12/4 Daniel Fages - android-x86 <dfa...@android-x86.org>:

[Daniel Fages - android-x86]

Hi,
the "Minecraft pocket edition demo" app uses an ARM native activity.

Dan.

[Chih-Wei Huang]

I've tested the patches on ics-x86.
It works fine.
Thanks a lot for the great work.

The following apps are tested on tegav2:

* Minecraft pocket edition demo
* Where's My Water
* Perry? Free
* Osmos Demo
* Angry Birds Rio (this seems to be the only angry birds game that
doesn't support x86 natively so far)

Besides, the Chrome browser (arm version) can start,
but unable to load webpages.

Fantashooting can start but then crashed.
Such an app seems has embedded arm libs in its asset.
Maybe that's a problem.

One issue is, many apps in Google Play still
say incompatible with my device.
But if I install the app directly (e.g., pull the apk
from an android phone and then install via adb install)
it works fine. (e.g., Where's My Water)

Any idea?

2012/12/5 Daniel Fages - android-x86 <dfa...@android-x86.org>:

> Hi,
> the "Minecraft pocket edition demo" app uses an ARM native activity.
>
> Dan.
>
> Le 5 déc. 2012 à 09:42, Chih-Wei Huang a écrit :
>
>> Thanks a lot!
>>
>> About arm native activity, could you suggest
>> what apps could be used to test it?
>>
>> 2012/12/4 Daniel Fages - android-x86 <dfa...@android-x86.org>:
>>> One thing I forgot : You can now have a look at the androvm source code at https://github.com/androvm in case I forgot something.


--

[Gerhard Smith]

OK. I feel stupid, but Angry Birds RIO doesn.t run.
It gives in logcat:
I/ActivityThread( 3581): Pub com.rovio.AB_RIO.AdContentProvider: com.greystripe.android.sdk.AdContentProvider
D/dalvikvm( 3581): Trying to load lib /data/data/com.rovio.angrybirdsrio/lib/libangrybirds.so 0xa0664ca0
E/dalvikvm( 3581): Unable to open libdvm_houdini lib: Cannot load library: reloc_library[1289]:  2347 cannot locate '_Z24jniRegisterSystemMethodsP7_JNIEnv'...
E/dalvikvm( 3581):
E/dalvikvm( 3581): dvm_dlopen: unable to open /data/data/com.rovio.angrybirdsrio/lib/libangrybirds.so
F/libc    ( 3581): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
D/wpa_supplicant( 2971): nl80211: survey data missing!
I/DEBUG   ( 2344): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

What I did: (ICS 4.0.4)
I copied the following 2 files to /system/lib
_http://androvm.org/Download/android-x86/libdvm.so
_http://androvm.org/Download/android-x86/libandroid_runtime.so
I downloaded
http://androvm.org/Download/houdini-libs-20121106.tgz
and extracted to /system/lib/arm
Rebooted.


What am I doing wrong? It looks like I have a qrong lib somewhere, but I have double checked.

[Daniel Fages]

Hi
You should also patch your source code tree with the provided patches.
If you don't compile your Android image you should wait for someone to release some.

Dan.

[Gerhard Smith]

Thanks for that Dan. I got to the bottom of the mystery. I use the
latest version of Firefox and new Google Groups and your post showed
the patches as plain text(no links).
When I reverted to the old google groups, they came up as downloadable
links. Before that I could not find the patches anywhere LOL!.

Some of the patch files failed for me as I think they apply to 4.0.2
and I have done a repo sync and I am now on 4.0.4.

I will try to apply by hand and post the patchfiles for 4.0.4 here -
the differences are not too major and should be able to work it out.

Thanks for your response and providing the code.

[Chih-Wei Huang]

2012/12/10 Gerhard Smith <ger...@android-x86.org>:

It's in our repository now.

[Gerhard Smith]

Hi  Chih-Wei,
Is the 4.0.4 ICS patched in the repository?
Or do the patches still have to be applied?
Or do we have a set of patches for 4.0.4 as the patches supplied by Dan does match on 4.0.4.
Gerhard

[Gerhard Smith]

To install libhoudini go to this link:
http://android-x86.sceners.org/en/?p=536
You don't have to do anyhting else.
Thanks to Chih-Wey and Damiel Fages.

[Chih-Wei Huang]

2012/12/21 Sreekanth Vietla <vie...@gmail.com>:
> Hi Dan,
> I was wondering if the patches that you posted missed
> frameworks/base/core/java/com/android/internal/content/NativeLibraryHelper.java?

Yes, it missed. But it's easy to find.

Check git.android-x86.org for full workable patches
for ics-x86.

[issor...@gmail.com]

Hello,

I've managed to push lib files with ADB tool (I'm working with a VirtualBox VM).

After installing a recent homemade jb-x86 build and the latest JB testbuild from tables-x86.org, I've tried to adb push library files and arm directory,

but when I edit build.prop to add the line ro.product.cpu.abi2=armeabi

and I reboot Android-x86 I can't boot, it stays stucked foverver with blackouts and reloading the ANDROID logo.

Is JellyBean porting at the same step of ICS regarding support for libhoudini?

Thanks for any info.
Mauro

PS: Regarding my previous question on how to include libhoudini in Android iso, could I workaround by doing a backup of the system image and then by copying system.img (or system.sfs) to USB boot installation drive?
I know It's a quite tricky procedure, but I would like to know if it could in principle work, because it would be a lot faster that rebuilding.

Thanks in advance for any help on this.

[Chih-Wei Huang]

No, libhoudini cannot work with jb-x86, since
old ics libhoudini is incompatible with the newer bionic.

2013/1/28 <issor...@gmail.com>:

[dscm]

PREVIEW build with MINIMAL GAPPS available.....

http://www.tabletsx86.org/android-x86-builds.htm

[George Endrulat]

Considering that this thread is lib houdini specific, am I to assume that the posted build has it working?

[issor...@gmail.com]

Hi, apparently something went wrong with my remount procedure before,

but now I've managed to upload libhoudini files and to edit build.prop to add the line ro.product.cpu.abi2=armeabi

Now from Chih-Wei H. statment it seems that anyway jb-x86 branch is not yet able to handle libhoudini or the latest ARM translator.

As a report for the community, with current jb-x86, after pushing GAPPS taken from http://goo.im/gapps/ latest jb signed

I've noticed Keyboard AOSP, Google TTS and Google Search are crashing (I had to disable them in the Settings/Apps)
while Google Play is working but no ARM apps are available (and this what to expect now, since actual ARM emulation requires some developments)

Can I ask to dscm I he could kindly explain to me how to build iso with integrated Gapps?
Thanks in advance

Mauro

[Ron M]

@Chih-Wei

I thought @dfages mentioned he has integrated it with JB, and AFAIK
the latest version of AndroVM relies on a JB4.1 codebase.
If I am not mistaken, there have been some changes in bionic from
JB4.1.* and JB4.2.1.

Is this the problematic part, and we are not expected to see supported
houdini libs till Intel comes out with a 4.2 device, or am I missing
something?

-Ron

> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

> To post to this group, send email to andro...@googlegroups.com.

> Visit this group at http://groups.google.com/group/android-x86?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Chih-Wei Huang]

2013/2/5 Ron M <ron...@gmail.com>:

> @Chih-Wei
>
> I thought @dfages mentioned he has integrated it with JB, and AFAIK
> the latest version of AndroVM relies on a JB4.1 codebase.
> If I am not mistaken, there have been some changes in bionic from
> JB4.1.* and JB4.2.1.

Yes. Check the dlmalloc part if you're interesting.

> Is this the problematic part, and we are not expected to see supported
> houdini libs till Intel comes out with a 4.2 device, or am I missing
> something?

Probably.
Or it may be overcome by the LD_PRELOAD trick.
But I have no time to try it yet.

[amawt]

Is there something missing with 4.0.4 rc2 ARM emulator patches? Cause as advised I have pushed libhoudini and libdvm_houdini to system/lib. Also arm libs to /system/lib/arm/

But still i get LoadLibrary errors for tested apps (Mincraft Demo) . Is there something that I'm missing? 

Seems like Josue is also facing the same issue. 

Chih-Wei Huang, it would be great if you could put some light onto this. Thanks!

On Thursday, December 6, 2012 1:28:59 AM UTC+5:30, Josue Aquino wrote:

Hi all, i'm new on this, and yesterday I've installed the android-x86 4.0 rc2 on my hp mini, works great, but, when I "Install" (copy the libhoudini.so and the other things) nothing changes and it doesn't work, could you please help me? 

[amawt]

I got it working. I was using Dan's older libs. The correct ARM libs to be used with 4.0.4 rc2 are: http://androvm.org/Download/houdini-libs-20121106.tgz

Thanks.

[Verachten Bruno]

Hi all,

what is the status of houdini with the 4.3 branch?
I discovered yesterday there was a enable_houdini command in /system/bin, but it seems it's not enough to get some arm code to execute (under VirtualBox).
Any hint?

Thanks.

Bruno Verachten

[Chih-Wei Huang]

2014/1/15 Verachten Bruno <goun...@gmail.com>:

> Hi all,
> what is the status of houdini with the 4.3 branch?

Works fine without problem.

> I discovered yesterday there was a enable_houdini command in /system/bin,
> but it seems it's not enough to get some arm code to execute (under
> VirtualBox).

As usual, you need to put the Intel libraries
to the built image yourself.

[Verachten Bruno]

Sorry to post dumb questions, but I just don't know what I did wrong.

I didn't know where to copy the files in the source tree, so I copied them in the out directory, after removing the iso file.

$ ls out/target/product/x86/system/lib/*houdini*
out/target/product/x86/system/lib/libdvm_houdini.so  out/target/product/x86/system/lib/libhoudini.so
$ ls out/target/product/x86/system/lib/arm
check.xml              libcrypto.so  libexpat.so            libicui18n.so      libnativehelper.so  libsonivox.so   libvoicesearch.so
cpuinfo                libc.so       libgcomm_jni.so        libicuuc.so        libnetutils.so      libsqlite.so    libwpa_client.so
libandroid_runtime.so  libcutils.so  libGLESv1_CM.so        libjnigraphics.so  libnfc_ndef.so      libssl.so       libz.so
libandroid.so          libdl.so      libGLESv2.so           libjpeg.so         libOpenSLES.so      libstdc++.so    linker
libbinder.so           libEGL.so     libgui.so              liblog.so          libpixelflinger.so  libtalk_jni.so
libcamera_client.so    libemoji.so   libhardware_legacy.so  libmedia.so        libskiagl.so        libui.so
libc_orig.so           libETC1.so    libhardware.so         libm.so            libskia.so          libutils.so

I then build the iso with make -j4 iso_img TARGET_PRODUCT=android_x86, install the iso in virtual box, connected with adb, then launched a shell, and then:
root@x86:/ # ls /system/lib/libhoudini.so
ls /system/lib/libhoudini.so
/system/lib/libhoudini.so: No such file or directory
1|root@x86:/ # ls /system/lib/arm
ls /system/lib/arm
check.xml
cpuinfo

I can't find my files anymore.

I then copied the files directly through adb, moved them in the right place, but the arm app tried (AngryBirds) only displays a black screen, as without the houdini files (even if I launch enable_houdini).

I know I'm wrong, but I don't know where.

Thanks a lot.

Bruno Verachten

[Chih-Wei Huang]

2014/1/17 Verachten Bruno <goun...@gmail.com>:

>
> I then build the iso with make -j4 iso_img TARGET_PRODUCT=android_x86,
> install the iso in virtual box, connected with adb, then launched a shell,
> and then:
> root@x86:/ # ls /system/lib/libhoudini.so
> ls /system/lib/libhoudini.so
> /system/lib/libhoudini.so: No such file or directory
> 1|root@x86:/ # ls /system/lib/arm
> ls /system/lib/arm
> check.xml
> cpuinfo
>
> I can't find my files anymore.

The easiest way to put the libs into the iso is just copy
them to the vendor/intel/lib dir:

vendor/intel/lib/libhoudini.so
vendor/intel/lib/arm/libwpa_client.so
vendor/intel/lib/arm/libskia.so
vendor/intel/lib/arm/libgui.so
...

The build system will add them automatically.

> I then copied the files directly through adb, moved them in the right place,
> but the arm app tried (AngryBirds) only displays a black screen, as without
> the houdini files (even if I launch enable_houdini).
>
> I know I'm wrong, but I don't know where.

AngryBirds is not a good app to test arm translator anymore.
It already has x86 libs in the apk (unless you used a very old version).
It just can't run on a virtualbox.
You need a real machine with hardware acceleration to run it.
Actually most game apps (with arm libs) need hardware acceleration.

The app I suggest to test arm translator is Where's the Water?

[Verachten Bruno]

Thanks for your reply. The libs are now in the installed version of android-x86 under VirtualBox.

I installed Where's the water (e68b30c47920185baf920712eeaba142  com.disney.WMWLite-1.apk) but it crashes.

I'll see what logcat tells me.

Best wishes,

Bruno Verachten

[Verachten Bruno]

The problem seems to be related to another library, not houdini:
01-17 14:30:13.699: E/dalvikvm(1713): dlopen("/data/app-lib/com.disney.WMWLite-1/libfmodex.so") failed: dlopen failed: "/data/app-lib/com.disney.WMWLite-1/libfmodex.so" has unexpected e_machine: 40

I'll try to find another way to test for arm compatibility.

Thanks.

--
Bruno Verachten

[Chih-Wei Huang]

2014/1/17 Verachten Bruno <goun...@gmail.com>:

> The problem seems to be related to another library, not houdini:
> 01-17 14:30:13.699: E/dalvikvm(1713):
> dlopen("/data/app-lib/com.disney.WMWLite-1/libfmodex.so") failed: dlopen
> failed: "/data/app-lib/com.disney.WMWLite-1/libfmodex.so" has unexpected
> e_machine: 40

This error means your arm translator doesn't work.
(It cannot recognized the arm library)

Are you sure you have these libs in your image?
/system/lib/libhoudini.so
/system/lib/libdvm_houdini.so

[Verachten Bruno]

I have the files at the right place:
adb shell
root@x86:/ # ls /system/lib/*houdini*
ls /system/lib/*houdini*
/system/lib/libdvm_houdini.so
/system/lib/libhoudini.so
root@x86:/ #

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.

Visit this group at http://groups.google.com/group/android-x86.

For more options, visit https://groups.google.com/groups/opt_out.

--
Bruno Verachten

[Verachten Bruno]

Hi,

I downloaded in another place houdini libs (http://forum.xda-developers.com/showthread.php?t=2528952) and rebuilt the iso.

Where's the water is now functional thanks to your help. Thanks a bunch!

Kind regards,
Bruno Verachten

[Stefan Svensson]

The download links are broken / forbidden :-(

[Verachten Bruno]

Not for me: http://www14.zippyshare.com/v/44278764/file.html .

[Stefan Svensson]

Do I have to rename any files or just copy files into system/lib and arm folder to system/lib/arm ?

Do I have to edit build.prop as well?

[Edmond Wong]

Hey guys,

Were you guys able to get them files and have the ARM working? And will this method work for genymotion?

[John Maier]

I'm  resurecting this thread, I have this very *important* (extreme sarcasm) issue.

I recently got a renewed interested in Android x86, I while playing around with the lastest stable release of Android x86_64 8.1.0 and for fun wanted to see if Pokemon Go would work.  Yes, one of the most important (time wasting) mobile apps of our time.

I enable Native Bridge, and upon launching, it instantly crashed.  Looking at the System Log, there is an error:

Failed to load 'libmain.so' ... 
java.lang.UnsatisfiedLinkError: dlopen failed: "data/app"

...==/lib/arm/libmain.so has unexpected e_machine: 40 (EM_ARM).

I'm gathering this is a long time issue with libhoudini(?)
Reading around, I found this to be a relatively, common emulation issue for some apps with native ARM compiled in, under x86.  

What I'm curious about, are 8.1 and 9.x using libhoudini for running ARM native apps?
I initially tried 9.0, and my Lenovo Thinkpad Helix had some issues, so I went back to 8.1, which seems reasonably stable.

I was reading that Android 11 now has native ARM emulation support.  Any attempts at porting Android 11 yet?

I'm preping a new new dev machine, and though I might play a bit with building images, so I look forward to seeing how much things have moved forward.

[Michael Goffioul]

On Sun, Sep 6, 2020 at 6:55 PM John Maier <devo...@gmail.com> wrote:

I'm  resurecting this thread, I have this very *important* (extreme sarcasm) issue.

I recently got a renewed interested in Android x86, I while playing around with the lastest stable release of Android x86_64 8.1.0 and for fun wanted to see if Pokemon Go would work.  Yes, one of the most important (time wasting) mobile apps of our time.

I enable Native Bridge, and upon launching, it instantly crashed.  Looking at the System Log, there is an error:

Failed to load 'libmain.so' ... 
java.lang.UnsatisfiedLinkError: dlopen failed: "data/app"

...==/lib/arm/libmain.so has unexpected e_machine: 40 (EM_ARM).

I'm gathering this is a long time issue with libhoudini(?)
Reading around, I found this to be a relatively, common emulation issue for some apps with native ARM compiled in, under x86.  

What I'm curious about, are 8.1 and 9.x using libhoudini for running ARM native apps?

Yes. Houdini libraries are downloaded at runtime when you enable the native bridge in the Android settings app. However there was a DNS issues a couple of weeks ago that prevented the binary blobs to be downloaded properly. I'm not sure whether the issue has been resolved.

 

I initially tried 9.0, and my Lenovo Thinkpad Helix had some issues, so I went back to 8.1, which seems reasonably stable.

I was reading that Android 11 now has native ARM emulation support.  Any attempts at porting Android 11 yet?

I did a very experimental build a couple of months ago. The various android-x86 patches could be ported without too much problems, much of the issues came from the fact that the Android R code base is not supposed to be buildable (that's the standard response you get when you report a build error or compilation problem for Android R on their mailing list) and the preview tags that are put on the various git repos do not form a coherent ensemble. Regarding ARM translation (and Widevine, for that matter), the preview images for x86 do contain the necessary binary blobs, but they're unusable in android-x86, because those binaries depend on code that hasn't been released, and it's unclear whether it will be (e.g. Widevine depends on DRM-1.3 HIDL, but that is nowhere to be found). All this was a couple of months ago, maybe things have changed since then.

Michael.

[fguy]

On Sun, Sep 6, 2020 at 6:55 PM John Maier <devo...@gmail.com> wrote:

I did a very experimental build a couple of months ago. The various android-x86 patches could be ported without too much problems, much of the issues came from the fact that the Android R code base is not supposed to be buildable (that's the standard response you get when you report a build error or compilation problem for Android R on their mailing list) and the preview tags that are put on the various git repos do not form a coherent ensemble. Regarding ARM translation (and Widevine, for that matter), the preview images for x86 do contain the necessary binary blobs, but they're unusable in android-x86, because those binaries depend on code that hasn't been released, and it's unclear whether it will be (e.g. Widevine depends on DRM-1.3 HIDL, but that is nowhere to be found). All this was a couple of months ago, maybe things have changed since then.

Google has released the release of android 11. Hopes for getting houdini files for android 10 tend to zero. Hopefully, it will be possible to integrate the ndk_translation files from the android 11 SDK image for the emulator. Then we will finally have another version of android with arm64 code translation besides android 7.1. 

[Mauro Rossi]

Google has released the release of android 11. Hopes for getting houdini files for android 10 tend to zero. Hopefully, it will be possible to integrate the ndk_translation files from the android 11 SDK image for the emulator. Then we will finally have another version of android with arm64 code translation besides android 7.1. 

Looking here: https://developer.android.com/studio/releases/emulator#support_for_arm_binaries_on_android_9_and_11_system_images

it is mentioned that Android 9 x86 system images support the ARM emulation too. 

...

These Android 9 and Android 11 system images support ARM by default and provide dramatically improved performance when compared to those with full ARM emulation.

...

but are these Android 9 x86 system images provided with NDK translator?

[Mauro Rossi]

Android 10 ARM emulation seems also in the plans

https://www.reddit.com/r/androiddev/comments/frsgwl/run_arm_apps_on_the_x86_android_11_emulator/ 

[fguy]

On Wednesday, September 9, 2020 at 6:54:54 PM UTC+2, Mauro Rossi wrote:

Looking here: https://developer.android.com/studio/releases/emulator#support_for_arm_binaries_on_android_9_and_11_system_images

it is mentioned that Android 9 x86 system images support the ARM emulation too. 

IMHO the appearance of ndk_translation in android 11 is due to the transition of ChromeOS to this service instead of intel houdini. Android 10 has never arrived on ChromeOS over the past year. Most likely before the end of the year, ChromeOS will appear with built-in android 11 and ndk_translation. Ndk_translation has been referenced for 2 years in the ChromeOS ARC compiler repository. In the SDK emulator, the latest versions of r11 for android 9 and 10 images still do not contain the translation of the arm code and I strongly doubt it will appear there.

It looks like Intel Celadon is already preparing to transfer the master branch to android 11.