Testdrive: Android x86 3.2 RC2 on Eee PC & MSI Wind U 100

[German Edition]Yesterday Google released Android 4.0 Ice Cream Sandwich source code for the public. Android-x86.org also presented release candiate 2 (RC2) of their Honeycomb x86-port. Time for another testdrive on my Eee PC 701G and on my Netbook MSI Wind U100.


Anzeige

I’ve blogged already several times about Android on x86 systems (see my link list at the end of this text). Yesterday I visited the Android-x86 projec site and found RC2 of Android 3.2. I downloaded the .iso files for a testdrive.

Here I have blogged (in German) how to use Virtualbox as a device emulator for Android using Android x86. But a more interesting question is: how would the live version of Android x86 fits for Netbooks. The steps to create a bootable live version of Android x86 on a USB thumb drive using an Android .iso file and unetbootin are discussed here (German). For my testdrive I created two USB thumb drives, one with an Eee PC version and on with a ASUS version of Android x86.

Will Android x86 3.2 fit for an old Eee PC 701G?

I still own a Eee PC 701G from my first Netbook project (the machine still has a place in my “hall of fame” of valuable tech gadgets). Will Honeycomb run on such a machine, although Google told us that a Tegra2 platform is mandatory for Android 3.x? Also, some people explained to me, Honeycomb won’t run on a machine with a desktop resolution of 800 x 480 pixel.

Because I’m a “guy born stupid and never learned a lot”, I decided to give it a try. Connecting the USB tumb drive to my Eee PC 701 4G, pressing the on button, pressing the ESC key to show the BIOS boot device menu and then select my USB thumb drive as boot device was all what I did.

Then a Android boot menu was shown and I was able to select the Android Live system entry from boot menu. After a few seconds the Android boot logo was visible …


Anzeige

… and after a few seconds more, I was greeted by this image on my Eee PC 701G display.

Wow, incredible – looks like Honeycomb, isn’t it? The thing that should not work, because my Eee PC 701G still has online 800 x 480 – hey, and also a 600 MHz Celeron processor along with a simple Intel graphic unit is far away from a Tegra2 platform. But the image obove proves that Android-x86 will do on such a small machine. Below is my apps page.

Using Android on my Eee PC 701G is fast, although the screen resulution isn’t the best. Therefore the lower desktop part, containing the 3 Android Buttons for Home, Back e.g. isn’t visible. But WLAN and audio output works out of the box, and I was able to use Apps. Only my web cam doesn’t works and I was not able to chance some settings (for an external TFT display for instance). But I guess, owners of a Eee PC 1000 or successors will have fun, using the new Android x86 implementation.

Using a MSI Wind U 100

For a 2nd test I used my MSI Wind U 100 (which was branded here in Germany as Medion Akoya 1210). It’s a 10,1 Inch Atom-Netbook with 1 GB RAM I’m using for Windows XP, Windows 7 and Windows 8. But I have used this machine also for several Android and Linux test drives. Therefore I used my USB thumb drive with Eee PC live android. Just pushed the on button, then pushed the F11 function key to invoke the BIOS boot device menu. After selecting my USB thumb drive as boot device, I was able to launch Android Live system from the Grub menu.

I’ve got a warning, that it isn’t an ASUS machine, but who cares? After a few seconds I found my Honeycomb desktop on the display.

Using the touchpad was no problem and handling was really smooth. A WLAN access was set up after a few seconds (this runs now out of the box, what was not true for RC 1). The image below shows the Android apps page.

Only my web cam wasn’t working, and also sound was not available. Then I bootet the 2nd USB thumb drive created from the Android .iso made for ASUS notebooks. Sound was working now (only the web cam app continues to crash). I was able to run a few Youtube clips. What won’t work? I was not able to use a German keyboard layout. Also mounting a SD-Flash card wasn’t possible (I haven’t invested much time investigating this issue in detail).

What was hot? I was able to access my Google market account. Although it was a bit fuzzy, because of the english keyboard layout on my German keypad. Also invoking the market login screen turns the display to “portrait mode” causes me some trouble. But I managed it to enter my credentials and then I downloaded and installed Astro file manger. That was amazing, because I haven’t mounted an SD card on my live system.

My conclusion: Android x86 3.2 RC2 isn’t perfect, but it teased my appetite for more. I’m really eager to get my hands on a Ice Cream Sandwich port for x86, because Android 4.0 will be supporting different screen resolutions. In my view the current release of Android x86 is a big step forward. Unfortunately I haven’t a slate for further tests (a WeTab tablet I borrowed for tests was retuned to vendor 4tiitoo a week ago). Otherwise I would have tested RC2 also on such a x86 slate.

Similar Articles (but in German):
1: Android x86 3.2 auf dem Medion Akoya 1210
2: Android x86 3.2 Honeycomb im Test
3: Android x86 in Virtualbox als Device Emulator I
4: Android x86 in Virtualbox als Device Emulator II
5: Android-Netbook im Eigenbau (Teil 1)
6: Android Live-System booten und installieren (Teil 2)
7: Tipps zum Eigenbau Android 2.2 (Teil 3)
8: Eigenbausystem: Update für Android 2.2 (x86)


Anzeige
Dieser Beitrag wurde unter Android, Tablet PC abgelegt und mit , , , verschlagwortet. Setze ein Lesezeichen auf den Permalink.

9 Antworten zu Testdrive: Android x86 3.2 RC2 on Eee PC & MSI Wind U 100


  1. Anzeige
  2. Andres Garcia sagt:

    Hi, thanks for showing us that you can install “honeycomb” in the asus eeepc 701. Testing found that installing the application “LCD Resolution” and changing “LCD Dencity” to 125, magically fix the problem of the resolution and the screen is OK!.

  3. Andres Garcia sagt:

    Here is a video of how it works http://www.youtube.com/watch?v=l1iDkCo-Ejk

  4. Anzeige

  5. Pingback: Running Honeycomb on a Eee PC 701G « Borns IT- und Windows-Blog

  6. Max sagt:

    Hi guys,
    I did a try with Honeycomb on my eee 701, but it seems that wifi and some other settings don’t work at all (all seems to work fine with gingerbread, except for And Appstore).

    Am I missing something ??

  7. Günter Born sagt:

    @Max: I guess, you catched the wrong build/iso. And you should have a look into my other article:

    https://www.borncity.com/blog/2011/12/13/running-honeycomb-on-a-eee-pc-701g/

    where I discuss all necessary modifications, to run Honeycomb Android 3.2 on Eee PC 701G. WiFi works, settings problem is fixed, and also market works.

    HTH

  8. Pingback: Android auf Laptop - Android-Hilfe.de

  9. Anzeige

  10. Swizzle sagt:

    I’ve followed all the steps to boot my MSI u100 with android x86 3.2 and it boots great however I can’t get the wifi to work and after hours of searching can’t find a solution. It seems like many are having the same problem. Any suggestions?

    • Günter Born sagt:

      @Swizzle: Unfortunately I haven’t any clue, why wifi isn’t supported on your machine (here I use a MSI Wind U100 branded as Medion Akoya 1210). Maybe MSI used in some models a modified Wifi adapter. Don’t know, here it works out of the box.

      After a quick search I can confirm, that other people adressed this issue. What you can try: Test different iso for Eee PC, Asus etc. as a live system. And follow this suggestion and test honeycomb 3.2 RC2. If that works, I guess you need to wait till the next build of ICS is released.

      If you like to investigate the issue – here are a few suggestions: First of all, we need to clarify, what “I can’t et wifi to work” really means. Is the Wifi functionality not available under Android 4.0.1 – or are you not able to establish a wifi connection to your wlan router? If the Wifi adapter isn’t detected in android, it will be strange – you can try to run a console and test with dmesg, whether wifi is recognized or not.

      If wifi functionality is available under settings – it must be testet step by step to establish a connection (open wifi, WEP, WPA”). Here I mostly failed during my first attempts to establish a wifi connection typing a wrong WPA key.

Schreibe einen Kommentar zu Andres Garcia Antworten abbrechen

Deine E-Mail-Adresse wird nicht veröffentlicht.