android x86 virtualbox no bootable medium found

#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND HOW TO#
#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND FOR ANDROID#
#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND ANDROID#
#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND PC#
#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND ISO#

Unfortunately I haven't a slate for further tests (a WeTab tablet I borrowed for tests was retuned to vendor 4tiitoo a week ago).

#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND ANDROID#

In my view the current release of Android x86 is a big step forward. 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. My conclusion: Android x86 3.2 RC2 isn't perfect, but it teased my appetite for more. That was amazing, because I haven't mounted an SD card on my live system. But I managed it to enter my credentials and then I downloaded and installed Astro file manger. Also invoking the market login screen turns the display to 'portrait mode' causes me some trouble. Although it was a bit fuzzy, because of the english keyboard layout on my German keypad. What was hot? I was able to access my Google market account. Also mounting a SD-Flash card wasn't possible (I haven't invested much time investigating this issue in detail). What won't work? I was not able to use a German keyboard layout. Sound was working now (only the web cam app continues to crash). Then I bootet the 2nd USB thumb drive created from the Android.

Only my web cam wasn't working, and also sound was not available. The image below shows the Android apps page. A WLAN access was set up after a few seconds (this runs now out of the box, what was not true for RC 1). Using the touchpad was no problem and handling was really smooth. 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. After selecting my USB thumb drive as boot device, I was able to launch Android Live system from the Grub menu. Just pushed the on button, then pushed the F11 function key to invoke the BIOS boot device menu.

#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND PC#

Therefore I used my USB thumb drive with Eee PC live android. But I have used this machine also for several Android and Linux test drives.

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 guess, owners of a Eee PC 1000 or successors will have fun, using the new Android x86 implementation.įor a 2nd test I used my MSI Wind U 100 (which was branded here in Germany as Medion Akoya 1210). Only my web cam doesn't works and I was not able to chance some settings (for an external TFT display for instance). But WLAN and audio output works out of the box, and I was able to use Apps.

Therefore the lower desktop part, containing the 3 Android Buttons for Home, Back e.g. Using Android on my Eee PC 701G is fast, although the screen resulution isn't the best. But the image obove proves that Android-x86 will do on such a small machine. 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. … and after a few seconds more, I was greeted by this image on my Eee PC 701G display. After a few seconds the Android boot logo was visible …

Then a Android boot menu was shown and I was able to select the Android Live system entry from boot menu. 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.

#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND FOR ANDROID#

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.īecause I'm a 'guy born stupid and never learned a lot', I decided to give it a try. 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 Android x86 3.2 fit for an old Eee PC 701G? For my testdrive I created two USB thumb drives, one with an Eee PC version and on with a ASUS version of Android x86.

#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND ISO#

iso file and unetbootin are discussed here (German). The steps to create a bootable live version of Android x86 on a USB thumb drive using an Android. But a more interesting question is: how would the live version of Android x86 fits for Netbooks.

#ANDROID X86 VIRTUALBOX NO BOOTABLE MEDIUM FOUND HOW TO#

Here I have blogged (in German) how to use Virtualbox as a device emulator for Android using Android x86.

Android x86 virtualbox no bootable medium found