Android x86

Forums › Android › Android x86

jbard

1377 posts

Uber Geek

#96512 29-Jan-2012 13:57

I discovered this project a while ago: http://www.android-x86.org

but i hadn't check it out in for about a year. Anyway i had another look today and they have come along way.

They now have working versions of android 2.2, 2.3, 3.2 and a dev build of 4.01.

I just downloaded 3.2 and installed it in virtualbox no problem at all.

Worked well for me. Tempted to try it out on my laptop as a live disk.

for anyone interested i followed these instructions to install it: http://androidspin.com/2011/01/24/howto-install-android-x86-2-2-in-virtualbox/

And you can download the latest releases from here: http://www.android-x86.org/download

1 | 2

368 posts

Ultimate Geek

#575047 30-Jan-2012 18:41

I take it you have the required hardware to match the v3.2 Android OS on one of the four distro.

Asus Laptop
eee Netbook
Tegra 2
AMD

I tried Asus and Tegra 2 and both said they were not compatible with VirtualBox (Win7) running on a Dell Dimension desktop.

I had a look at Android 2.2 'generic' in VirtualBox a while ago and it was borderline scary, as even though it could be installed and run within VirtualBox it'd take a brave man/woman a while to get it setup and usable.. and then it'd still be Android 2.2
Besides that version has been discontinued.

I looked to see if there was an updated Generic version, but can't find anything.

http://code.google.com/p/android-x86/downloads/list

Any thoughts?

jbard

1377 posts

Uber Geek

#575048 30-Jan-2012 18:43

I just used the Asus laptop version, i have a Dell XPS 15.

Maybe i got lucky with the hardware as i got no errors giving it a try?

Predated

177 posts

Master Geek

#575050 30-Jan-2012 18:50

Hi

I also gave it a try but couldn't get the asus laptop or any other version to boot in virtualbox, and couldn't find a generic version either.

I'm assuming the host system wouldn't matter as virtualbox as android would only detect the virtualbox virtual hardware.

Would love to try and play with this if someone can find either a generic .iso or an updated guide for 2.3 and 4.0

Cheers

jbard

1377 posts

Uber Geek

#575051 30-Jan-2012 18:50

Did you select Linux > Other linux as the operating system?

Predated

177 posts

Master Geek

#575056 30-Jan-2012 18:58

Yep, I've used Virtualbox to setup Ubunatu as well and that worked fine, however the android .isos wouldn't load using linux / other

DrStrangelove

368 posts

Ultimate Geek

#575057 30-Jan-2012 19:01

Interesting... maybe I'm not holding my tongue rite. ...write....right. Doh!!

I have a 3.2Ghz Pentium IV with no virtualisation running Win7 home. So maybe somewhere in that mix a wheel has fallen off.

I just get something like... No ASUS hardware found.

I reinstated my old Android 2.2 VirtualBox VHD and had another look at it.... then shut it down again.

This same Dell 'Box' wont let me install Windows 8 either. Had to do it via a partitioned boot drive.

So probably the desktop.... but wait... I'll try the Alienware jobbie as that has Win7 Pro, virtualisation and VirtualBox and does have Windows 8 running in a vbox so maybee..

Dude... you're quick with the replies.

DrStrangelove

368 posts

Ultimate Geek

#575061 30-Jan-2012 19:22

Awh, that power of off world technology.

My Alienware notebook still gives the warning "Not an Asus product" during the boot, but just keeps going and boots up Android anyway.

Have to see if I can install the official Google Market AND then see if the device is recognised, have played around with build.prop in the past, never really been able to make a bad thing better though, fingers crossed.

I'm now thinking...Android 4.0

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

jbard

1377 posts

Uber Geek

#575064 30-Jan-2012 19:26

Yeah i might try one of the 4.0 versions tonight as i haven't seen it yet.

Just a point i couldn't get my mouse to show up, is this is how it is meant to be?

DrStrangelove

368 posts

Ultimate Geek

#575134 31-Jan-2012 00:02

jbard: Yeah i might try one of the 4.0 versions tonight as i haven't seen it yet.

Just a point i couldn't get my mouse to show up, is this is how it is meant to be?

Android 4.0 x86 Asus gave me a Wizard error which blocked further progress.

Click “Mouse pointer integration” on the virtualBox panel in the machine dropdown.

There may be another issue in that there doesn't appear to be a 'simple' way to bind an IP address to the WiFi which for me shows a WiFi error.

Plus there _does_ appear to be a Market App that looks ball park ..... but'll need to work on the IP thing first.

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#575216 31-Jan-2012 11:25

DrStrangelove:
jbard: Yeah i might try one of the 4.0 versions tonight as i haven't seen it yet.

Just a point i couldn't get my mouse to show up, is this is how it is meant to be?

Android 4.0 x86 Asus gave me a Wizard error which blocked further progress.

Click “Mouse pointer integration” on the virtualBox panel in the machine dropdown.

There may be another issue in that there doesn't appear to be a 'simple' way to bind an IP address to the WiFi which for me shows a WiFi error.

Plus there _does_ appear to be a Market App that looks ball park ..... but'll need to work on the IP thing first.

I had ethernet working on my Acer laptop with Android x86 v1.6. Wifi didn't work.

I'll have to try some of these new ones. :-)

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

DrStrangelove

368 posts

Ultimate Geek

#575318 31-Jan-2012 14:04

Yerp, same here. I can get Ethernet working on Android v2.2 generic iso and was able to watch Youtube video.
However I've had no luck with WiFi and some of the later (2.3+) more bespoke x86 Android distro seem to create network problems too.

I read that the eeepc version it the most 'generically' friendly version, but don't know how true that is.

I'm going to install a 'generic' 2.3 x86 test version I found as that may work on my desktop which has in the past enabled network connections.

My laptop using WiFi with an Android x86 WiFi only distro hasn't (At this time) been able to establish a network connection.

The reason I'm so hell bent on get a higher version Android OS up and running is to then use Android Market to load apps my lesser Android systems can't. Then use app extractors to transfer them to other 'boxes' . However I fair Google will not see Android x86 as a 'real' system/device and reduce it's access and compatibility too. I haven't even looked at the build.prop yet.

I'd like to get a tablet Android OS up and running as that may give me Google Earth as my olde lack luster FV-1 Android TV and other devices can only load 'mobile' versions.

Now all we need is VirtualBox for Android so we can run Windows 7/8 and Unix with Android :-)

DrStrangelove

368 posts

Ultimate Geek

#575525 31-Jan-2012 19:33

I'm able to install all the eeepc versions of Android x86 in VirtualBox on both my olde Dell desktop and my notebook.

I suggest that the eeepc version is compatible with a wider range of hardware than the other versions are.

Still not able to get a WiFi connection working within VirtualBox.

The 'Generic' Android versions (v2.2, v2.3) which includes both Ethernet and WiFi seem to work OK when Ethernet is configured.
However the generic versions need their account names bound to an Exchange server, and I'm not installing one just for Android. I couldn't find the standard create/sign-in to Google account which is then bound to the Google Market app.

The tablet versions appear to have wider account configuration range for sync'ing and using with Google Market App and etc.
However the tablet versions with WiFi only are a problem (for me) in that I can not get a TCP/IP binding within VirtualBox.

So unless someone can find an cunning IP solution to get Android x86 WiFi running in VirtualBox on a Windows 7 PC .... I've got nothing.

I have numerous other VirtualBox clients (WinXP, Win8, Ubuntu and Debian) running network connections OK and even the Win7 Pro VM virtualised clients connect just fine....damn you Android!!!!

From within the Android GUI, Alt-F1 drops the interface into terminal mode, if someone knows of a configuration to get WiFi going that way.
I had no joy with the information I could glean from the web. Mostly didn't work or for different configurations.

Update - Oh and the sdcard (any old USB thumbdrive) works fine so one can use the virtualised Android OS with external data and or load additional apps with 'Unknown apps' ticked in setup.
However I found a lot just 'crashed' due to forced errors on Android v2.2 and v2.3 at least.

EStrong File explorer worked fine which is peachy for me and my NAS connection on the lower Android versions which did run Ethernet.

DrStrangelove

368 posts

Ultimate Geek

#586986 26-Feb-2012 16:41

Installed an Android x86 v2.3.7 OS in virtualBox on Windows 7.

Got it all up and running(sort of), but it's very hit and miss.

You'll generally need an Android x86 with Ethernet enabled if you're using VirtualBox as the WiFi interface has 'issues' and doesn't provide any connectivity(my findings).

Tried to install the latest version of some popular apps and some do install and work.
ES File Explorer does work which is good cause it gives access to my NAS and all the android apk files.
Gmail and Google Market install OK, but give forced errors on activation.
Tried a few older version of the market.com and they also failed.

Even if it did work, I'm guessing the access would be very restrictive, given the OS base build.

Given I already have mobile and 'desktop' Android systems that already work... it's hard to know what Android in virtualBox provides.

Maybe good for a quick look around the UI but that's probably about it.

Current versions of Android x86 4.0 that I've checked fail with a start-up error. Pity.

DrStrangelove

368 posts

Ultimate Geek

#591347 6-Mar-2012 16:53

Have Android 4.0 RC1 x86 up and running in VirtualBox.

Still no Ethernet and no way I know of to 'fox' WiFi access to work.

It does seem to have Market, Gmail and Maps pre-install, or at least listed in the 'All Applications'

So if one could get Network access up and running in VirtualBox, one may have a good little "Look and Feel" Android OS.

In the past I've found that a lot of applications crash even though they can be installed, however this was on Android 2.3 OS and lower.

So more twiddling of thumbs and a bit of waiting and we'll see what comes of it all.

Be nice if an Ethernet interface was provided.

alexx

867 posts

Ultimate Geek

#601647 29-Mar-2012 00:56

I've got android-x86 4.0 running in virtualbox.

I took a look at this a few weeks ago and used the instructions here:
http://www.android-x86.org/documents/virtualboxhowto

I was able to install a vm in VirtualBox 4.1.10 running on Win7 64-bit host, using a 4GB virtual disk. No networking or audio on that one.

Then tonight I decided to have another go using the image and info from the link here:
http://www.buildroid.org/blog/?p=86

Update: There is a newer image file here (and perhaps an even newer one before you read this):
http://www.buildroid.org/Download/android-x86-vm-20120307.iso.gz

More info here:
http://www.android-dev.ro/2012/02/22/android-x86-virtualbox-support/
http://www.android-dev.ro/2012/03/17/android-x86-4-0-rc1-for-virtualbox-is-released/

First download and gunzip the image.
Start VirtualBox and create a new virtual machine.

Operating System: Linux
OS Type: Linux 2.6
Base Memory: 512MB
Video Memory: 8MB

Once installed, reboot and open the terminal app and confirm Ethernet is supported and networking is up...

$ ifconfig eth0
eth0 : ip 10.0.2.15 mask 255.255.255.0 flags [up broadcast running multicast]

Start the browser and you should be able to confirm internet access. Sound appears to be working... quick check is to open the Voice Dialer app, but haven't tried music or anything else yet.

#include <standard.disclaimer>

1 | 2