Tutorial: Android 4.0 x86 ICS in VirtualBox with ethernet support and Google Play (Part 1 of 2)
April 18, 2012 · by by314 · in Android-x86, Tutorials
This manual is for people who want to develop for android on the x86 platform or in general, and those who simply want to try before getting android more fully into the matter installing android on your netbook, laptop, or pileup compatible, although we also have the ability to use Android x86 in live mode and with a virtual sdcard, but we’ll see on another occasion .
The purpose of this manual is to set up a system Android 4.0 ICS in our virtual machine, in this case vbox, with access to the network, and with the google apps (we will see later what is that of the google apps ..), so here we go.
1- The first thing we will go to the website and download vbox case you had not already installed, What you can download from here.. https://www.virtualbox.org/wiki/Downloads or by clicking on the image below, I am using Linux, but the tutorial will serve the same for any operating system, win7, linux and mac, we selected our downloaded and installed.
2- With VirtualBox installed and the next thing we need is the file OVA, and can be found in the web of people who are continuing to develop the vbox target for google android on x86 which abandoned the site in question is http://www.buildroid.org there you can find all the info of the project, and the last OVA file as of today 18/04/2012 the can download by clicking on the image below.
UPDATE: to get the latest images visit this post in the blog : http://android-x86.sceners.org/en/?p=523
--- Android-4.0.3_bd2 Release Notes ---
AOSP source version : android-4.0.3_r1
Kernel : android-goldfish-2.6.29
** Known issues
- OpenGL is software
- Cannot play video
- No Audio IN
- The status bar says "No Internet Connection" whereas Internet connection is working
- No static IP configuration for Ethernet (only DHCP)
** Changes from Android-4.0.3_bd1 to Android-4.0.3_bd2
- RTC driver integrated -> Clock and Alarm are now OK
- Power management OK : Battery level and charging status are updated (via a polling mechanism, as it seems VirualBox doesn't issue ACPI events on battery level changes), the only non-working thing is the "screen off" feature which has been disabled via a new Development setting ("Always stay awake")
- USB is now enabled
- USB mass-storage devices are now automatically mounted on /mnt/USB/
- Astro File Manager application included
The OVA file according to the nautilus (the file browser in linux) sees it as a TAR file, so here rename it to .TAR if you are in windows, we can use winrar to decompress and get these two files…
Fortunately or unfortunately, going to load the OVF file gave me an error that said that the imported image was 2 IDE devices, and to load it could only have an IDE device, so here we need to edit the OVF in case we show this error, and later fine tune the settings at the moment we open the VirtualBox menu and go to file> Import Service Virtualized> and look for the Android-4.0.3_bd2a.ovf file, we should see something like..
But in my case I get this crash when clicking next ..
And it says that we have many IDE devices, then remove one by editing the Android-4.0.3_bd2a.ovf, open it with the text editor that we like, and look this paragraph of text that you see in the image selected below ..
We erase it to make it in this way ..
Now when you load the file-4.0.3_bd2a.ovf Android instead of displaying TWO IDE devices, show just ONE, but no longer fails when importing .. now we do a hack, to run this after editing the OVF file , and that we will in the following manner, selecting our new virtual system imported into the VirtualBox menu, and clicking on SETTINGS as shown in the picture below..
Below we will see a menu like the one pictured below, and we change the value displayed on our VirtualBox by default will be “Primary IDE Master” and should look like in the picture below ..
You can click to accept, and we will have our android .. ready to start, press START and see the screen with GRUB, which will select the line below as we shall see in the image below ..
With this we have our android running, on the login screen maybe tells you that we do not have internet connection as I show below ..
But you see that the internet works there is a screenshot more: D
And one more screenshot of the desktop in Castilian and such … (currently without Google apps, we’ll see in the second part: D)
And that’s it for now, continue with part two showing how to install the google apps (Google play, Google Maps, Google Mail, etc. .. :D) I hope you liked it, and forgive my spelling mistakes, it is important it being understood as the successful end to our mission is to launch the emu.
If you copy this article does not forget cite the source, thanks for reading.
Read more: http://android-x86.sceners.org/en/?p=105#ixzz3qKu3YSlG
April 21, 2012 · by by314 · in Android-x86, Tutorials
Well here we are with the second part of the tutorial: D I did not want to publish it until you’ve tried everything.
As stated by the people of buildroid.org virtualbox image to ICS, has some bugs at the moment but is quite usable in my point of view, I’ve used Android-x86 4.0.3rc2 on my netbook and was quite thin, but hopefully them to compile a current source code is 4.0.4 as of today (for x86), and that gradually debug drivers for the emulator and some failures.
The point is that we will have an emu Android-x86 version 4.0.3 to test your own apps without extra hardware, the Android-x86 emulator INTEL official is still in version 2.3 so here we can develop for a far superior version and to test our emu lol, in order to update their code quickly people buildroid.org and will fine the emu, the subject is, by then we will know how to make it work;) can also use it with AppInventor or anything else that use adb hehe.
Come on to the mess … in the web of buildroid offer a pack with google apps, but according to them had many crashes with many apps .. well, I have done many tests with google apps for my builds to the netbook, and I saw that to the pack was not very carefully and had things to ARM, so here I deleted many things that were not necessary, some of which were duplicates (when installed applications check that natives do not have different names they install and do not duplicate gallery.apk google.gallery.apk example we would have 2 gallerys imagine what happens with duplicate calendar using a service would be two services .. calendar = problems, and was doubled, so now will better .)
Also I have allowed myself the luxury of adding some additional apps like 0xbenchmark by if you want to do some performance tests, also the Android terminal, Superuser, and the Open FileManager, I’ve also updated the youtube player but it seems that even failure (I imagine that will be the version of the ICS had one of the releases that failed that or maybe because 3D acceleration) in any case the new package attached here:
Well before we get to work, need the Android SDK and you’ll use one tool called adb to upload files to your virtual android, you can find it here the Android SDK http://developer.android.com/sdk/index.html
After installing the SDK adb look for the application, and in our case on Linux and create a symbolic link to / bin to run when we want with:
sudo ln -s /home/pi/android-sdks/platform-tools/adb /bin/adb
Substituting my home directory for your.
Once done, adb should work from where we launch it, so let’s unpack the downloaded file ..
tar -zxvf gapps_buildroid_modby314.tar.gz
and we stand inside such that so..
next I need to know the ip of the virtualbox, start the vbox, and to see the ip I do is monitor the network card that uses virtualbox in my case eth1 with iftop, I do:
Open the android browser, once opened go to command prompt and type:
iftop -pPB -i eth1
Substituting eth1 for your network device.
Once this is done we can write any website in the Android browser, and the iftop see an IP that begins to consume bandwidth, this will be the ip of our virtualbox, now we only activate the USB debugger (picture below ) and upload the files.
If we continue in the folder above “gapps_buildroid_modby314” , only have to do the following:
adb connect 192.168.1.137
that will be tell us something like “connected to 192.168.1.137:5555” below we will remount the system as R/W with..
adb remount
it should respond “remount succeeded” and then you can upload the folder /system complete with..
adb push system /system/
Below I put a screenshot of the entire process..
Once uploaded the files only have to restart the virtualbox and we are ready, when we rebooted, and we launch the market, go to market settings and enable automatic updates, play google will update without any problem, in terms of market failure buildroid those who commented about the apps does not show, I tell you that only shows an app by category, but that does not happen when you do your own search for apps, so here be able to put a keyword and you will come out all compatible apps x86, I’ve also added some modifications to the file build.prop for google android emulator see us as a eeepc and not as a vbox, so you can see in the picture below :).
Final results :
And that’s it, hope it works, if I missed some step or something wrong tell me I hope, especially hope you find it useful.
Cheers. (if you copy that article please cite the autor, than you)
Tags: Android Emu, Android Emulator, Android-x86, appinventor, gapps, google play, ICS, VirtualBox
1.
Read more: http://android-x86.sceners.org/en/?p=176#ixzz3qKv0rHEp
wendy6