How to Use Libhybris and Android GPU Libraries with Mer (Linux) on the Cubieboard

You may have heard about libhybris, a library that cleverly loads Android HW adaptations and convert calls from bionic to glibc. One of the greatest achievement of this library is to allow Android GPU drivers to be used with Linux, and is notably used by Canonical, although they did not write it, for Ubuntu 14.04 which will be compatible with any recent Android smartphones or tablets.

One way to get started with libhybris is to port a device to Ubuntu Touch, but this may take a while. However, I’ve found a faster and easier way to play with libhybris thanks to Martin Brook (vgrade) who wrote a tutorial on how to use libhybris with Mer on the Cubieboard. Mer is an open source mobile Linux distribution powered by Qt/QML and HTML5, that’s born from the ashes of Meego, and is now used in the upcoming Sailfish OS.

Qt5 Cinematic Experienced Rendered at 25 fps in Cubieboard via Android GPU Drivers in Linux Thanks to libhybris
Qt5 Cinematic Experienced Rendered at 25 fps in Cubieboard via Android GPU Drivers in Linux Thanks to libhybris

You’ll need to follow 4 main steps:

  • Build Android
  • Build a minimal Mer image
  • Install Libhybris
  • Run demos

I’ll skip the Mer image build since Martin has provided a binary image. I’ll use a build machine running Ubuntu 12.04.2 LTS. You should make sure the build environment is setup correctly, you’ve installed repo, and that it’s in your path. I’ll use the Cubieboard (1GB RAM), but you may want to try other hardware platform, or Linux distribution as the instructions should be similar.

Build Android for the Cubieboard

This is basically following the instructions provided here. First let’s code Android Jelly Bean (CyanogenMod) source code:

repo sync may take quite a while depending on your Internet connection. It took 10 hours, after several attempts over three days… Once this is done, we’ll need to configure the build for the Cubieboard:

Select Cubieboard (#4), and start the build:

The build initially failed with this error:

So I shamelessly typed “make update-api” to automatically update current.txt, and continued the build with “make -j10”. The build may also take quite a while depending on your computer performance and available RAM. This step was much faster than repo sync in my case, as it just took about 45 minutes in total.

The Android build is now completed, but we need still to patch Bionic library, and rebuild:

Now let’s tar Android’s system directory as we’ll need to copy the will have the patched bionic library plus all the android libs (EGL, GLESv2, RIL etc):

Installing and Running Mer

Since we don’t build the image ourself, this step is rather easy, as we just need to download the image, and dump it to a micro SD card.

bzip2 -d nemo-cubieboard-tablet-cubieboard-mer-testing-armv7hl-weekly-20130511-1516-mmcblk0p.raw.bz2

Burn the image to a microSD card (4GB or greater):

Where you need to replace <sd_device> by your actual SD card device such as “sdc”.

My 4GB microSD is slightly smaller than the image provided, so dd failed at the very end. But you can usually run the following 2 commands on the last partition (in this case ext4) in order to resize the partition, and fix any potential boot problems:

Interestingly, this time those commands failed, but I still inserted the microSD in my Cubieboard, and I was able to login successfully into Mer via the serial console as root (password: mer). You should also have access a terminal on the HDMI monitor.

We don’t want X to start anymore, so let’s disable it and restart the Cubieboard:

If you’re using HDMI console, switch to VT2 (Ctrl+Alt+F2) before running the command.

Installing libhybris and Android system folder

Let’s log-in again via the serial console, or via VT2 on the HDMI monitor if this works for you, and install libhybris:

zypper ar
zypper in libhybris
zypper in libhybris-tests

You may want to enlarge your terminal for the steps above, as the text goes over the window, and you have to answer some questions for the installation. The next step is to install Android’s system files to /system in the Cubieboard. Copy the files from the Linux PC to the Cubieboard:

and complete the install in the board:

The installation is now complete and it’s time to try it out.

Graphics Demos

To test whether libhybris is correctly installed run the following:

The only problem is that it did not work exactly as expected:

After a reboot, Cubieboard decided to boot Android from flash, so I tried to remove and re-insert the micro SD, and noooooooooo! The micro SD socket let me down and refuses to lock the card in place, so I’ll have to replace the slot which will take me few weeks since I have to order the thing.

So I count on you to let me know what has gone wrong. Thanks 🙂

Let’s carry on as if everything worked just fine, and run the next demo:

This should display a white diamond shape filled with an animated Catherine wheel.

Martin also has instructions for several other demos, but the most interesting one (we have a video), is Qt5 Cinematic Experience that you can install in the board as follows:

Now edit content/Mainview.qml with vim, and comment out the PathAnimation part.

Finally run the demo:

Et voila!

18 Replies to “How to Use Libhybris and Android GPU Libraries with Mer (Linux) on the Cubieboard”

  1. This is really interesting and I think I’m going to try it out sometime. I’m even more excited about LIMA though.

  2. I don’t understand one think Android is always build as softfp (drivers same)
    and rest of os run as armv7hl (hard fp)
    it looks like libhybrids solve this part too right?

    there is some hack for NOKIA N9 (all hardfp libs) that is able to run softfp software for example angly birds star wars

  3. @misko
    In this setup he’s using a standard Linux kernel and drivers with the Android libraries.
    I’ve checked, and confirmed, the rootfs is armhf, and the Android libs are armel, I’m not sure what kind of magic happens with libhybris.

  4. Doh. I was hoping that all that would be needed would be to copy a few files from and Android release for the target device over to Linux and et voila, the library do its work. Life’s never that simple though. 🙁

  5. @PV
    It’s still not working for me (I haven’t fixed my Cubie), as per the error message in this blog. I haven’t seen your error before. Have you tried to follow the advice from the log?:

    Try: zypper install -C “debuginfo(build-id)=4b82b0a4d8b1e617453c92539129e9ea245f4124”

  6. @cnxsoft

    Aah sorry for late reply. I was expecting a email notification :).

    Yes I did try that. In fact with some further test I realise that error is same no matter I patch or not.

    I have also ensure that it’s patched properly but still situation same.

  7. @PV
    I’ve tried (and failed) to remove the microSD card slot from my Cubieboard with a soldering iron and desoldering wire, but it seems quite challenging for me.

    You’d better check the original article, and ask Martin Brook directly. I’ve probably done a small mistake in this tutorial.

  8. “Installing and Running Mer

    Since we don’t build the image ourself, this step is rather easy, as we just need to download the image, and dump it to a micro SD card.

    wget nemo-cubieboard-tablet-cubieboard-mer-testing-armv7hl-weekly-20130413-1612-mmcblk0p.raw.bz2

    Proper URL please, thanks

  9. @cnxsoft

    Hi, many thanks for the guide. I have a cubieboard, think I’ll have a look at Mer before anything else, and then move on to your guide!

    Thank you once again.

  10. I’ve managed to play the Qt5_CinematicExperience_rpi_1.0 example using qmlscene but something curious is happening:

    – I have no text being displayed, only graphical elements and images
    – near the top left corner of the screen I’m getting an intermittent cursor blinking
    – qmlscene crashes after a while and won’t allow me to re-run the example – only works after reboot

    I also tried the minimer example, with that I get the rotating/scaling wallpaper.

  11. Hi, there!

    Thanks for the guide. I struggled for a while with compiling the android image (I had to downgrade jdk, python and gnu make and still have some errors building it) and now decided to ask for help. If someone who manged to build the android image could provide the tar-archive of the /system folder (e. g. via ubuntu one, dropbox, …) you would save me hours of work. (And maybe others are interested in this, too?)

    Thanks in advance!


  12. Hi, again!

    It looks like I got it working. Here is my /system folder of the output: I don’t have my Cubieboard at hands, so I haven’t tested it right now.

    Another interesting thing you can do with libhybris is using the android CedarX driver, which is said to work better than the native glibc version. Have a look here:

    I also like to provide the extracted headers (using lutils/ from from the android Cubieboard source:


Leave a Reply

Your email address will not be published. Required fields are marked *