This method only works for ext3 partition. The user data will be directly saved to that directory.
Install your favorite linux distribution, then copy android files and modify the grub menu.Boot from any rescue cd like systemrescuecd, and follow the instructions in the previous section.
People still ask, what if my hard disk is empty? How to install grub and copy files into it? There are several ways to do it. Just copy android files into an existing partition, install grub to the hard disk (if not done yet), and modify the menu.lst. Even you do not need to create a new partition. Install to a hard disk is just the same as install to a USB disk. If you hope to save data to disk, see the next section. Note all data are saved to the ramdisk, so all will lose after power off. Then you can boot from the USB disk and enjoy Android.
If you want to add new target for your x86 device, refer to the article. Target based on android_x86 for your device. Since jb-x86 we tried to use android_x86 as a universal It doesn't have some advanced features like hardware acceleration. But note generic_x86 is just a base for other targets. In short, if you don't know how to choose, use eeepc for donut-x86 branch, and use generic_x86 for eclair-x86 to ics-x86 branches. Do not use it if you are not using an EeePC. Since eclair-x86 branch, eeepc is changed to serve ASUS EeePC family only. motion_m1400 : for Motion M1400 (Intel Centrino M based with Intel PRO/Wireless)Īctually, for historical reason, you have to use eeepc for a generic x86 PC, notebook or netbook before (includes) donut-x86 branch.vm: for virtual machine (virtual box, qemu, vmware).sparta: for Dell Inspiron Mini Duo platform.tegav2: for Tegatech Tegav2 (may work with other Atom N45x based tablets).generic_x86: for generic x86 PC/notebook.nougat-x86 / marshmallow-x86 / lollipop-x86.We provides several targets for different branches:
You need to choose a target for the x86 device you want to use/test. Since gingerbread-x86, a 64-bit build environment Note: Before froyo-x86 (included), you can build on either aģ2-bit or 64-bit host. Since lollipop-x86, java 1.7 is required and OpenJDK is supported. You need Oracle java 1.6 ( OpenJDK may not work) to build branches before (includes) kitkat-x86.
Once the repo sync is complete, you can build a cdrom iso image. Do not bother us with any of the syncing problem. Repeatedly run ' repo sync' until it succeeds without any error. If you encounter problems of sync it, it's likely a network Note: The Android-x86 repository is very big (about >ġ0GB). See the below section for how to solve this situation. However, sometimes you may see conflicts during repo sync. If you hope to keep syncing your tree with Android-x86 repository, just do repo sync. Since AOSP evolves very quickly, we have created different branches corresponding to different releases of AOSP:īased on Android 6.0 release (Marshmallow).īased on Android 4.3 release (Jelly Bean).īased on Android 4.0 release (Ice Cream Sandwich).īased on Android 3.2 release (Honeycomb).īased on Android 2.3 release (Gingerbread).įirstly, follow the AOSP page " Establishing a Build Environment" to configure your build environment. Now it is very easy to compile Android for x86 platform from our git Real hardware as well as virtual machines (qemu or virtual box). This page has (hopefully) the latest information about how to buildĪndroid for x86 platforms like Eee PC.