Run Android on your PC

Customize Kernel

The Android build system doesn't compile kernel on-fly. It just contains a prebuilt kernel binary which will be added to the target image. This approach may be good enough for the arm emulator target, but not suitable for x86 platforms. The x86 platforms have various hardware. The kernel binary and its modules may need to be adjusted at compile time or runtime.

This article explains an extra feature of the android-x86 build system. That is, the ability to build kernel and modules by a predefined or customized config during the building process.

Prepare the source tree

We have modified the Android build system to compile a kernel image on-fly. You need to use our repository to get this feature. Read the article for details.

Build the target default kernel

We put default configs of supported targets of android-x86 in kernel/arch/x86/configs/. The corresponding defconfig of a selected target will be used automatically. For example,

make iso_img TARGET_PRODUCT=android_x86_64

By specifying the TARGET_PRODUCT to android_x86_64, the build system automatically selects the config android-x86_64_defconfig to compile the kernel binary and its modules. The binary will be generated in out/target/product/x86_64/kernel, and the modules is put under out/target/product/x86_64/system/lib/modules/. The final target out/target/product/x86_64/android_x86_64.iso will contain the kernel binary and its modules.

Build and update kernel solely

To build the kernel and its modules solely, change the goal iso_img to kernel:

. build/; lunch android_x86_64-userdebug
make kernel

Then you can copy $OUT/kernel and $OUT/system/lib/modules/ to the target device. Put the former to the android-x86 installation directory, and the latter to /system/lib/modules. Note the /system must be installed as read-write mode.

Specify kernel architecture

Since Android 5.0 it supports both 32-bit and 64-bit images. Usually 32-bit userspace works with 32-bit kernel, while 64-bit userspace must work with 64-bit kernel. Android-x86 build system supports both since lollipop-x86.

Sometimes you may want to run 32-bit userspace with 64-bit kernel. In this case, you may specify kernel architecture by TARGET_KERNEL_ARCH:

. build/; lunch android_x86-userdebug
m -j8 iso_img TARGET_KERNEL_ARCH=x86_64
This builds a 32-bit userspace image with 64-bit kernel.

Force recompilation of the kernel

Android and kernel use entirely different build systems. Though we combine them together, the integration doesn't work very well. An example is if you modify the kernel tree, Android build system won't notice the change. That means, the kernel won't be rebuilt automatically if you rebuild the image.

There are several ways to overcome that. One is to touch the defconfig like:

touch kernel/arch/x86/configs/android-x86_*

Or remove the kernel config in the out/ directory:

rm $OUT/obj/kernel/.config

Or remove the kernel image:

rm $OUT/obj/kernel/arch/x86/boot/bzImage
Then rebuild the image as usual.

Replace the kernel

Since we build kernel with modules support, to replace the kernel of an installed system, you have to replace the corresponding modules as well. To do that, copy the kernel image to the android-x86 installation directory, and copy modules to /system/lib/modules. You can do that by booting to debug mode like:

Detecting Android-x86... found at /dev/sda1

Type 'exit' to continue booting...

Running MirBSD Korn Shell...

Use Alt-F1/F2/F3 to switch between virtual consoles
Type 'exit' to enter Android...

Running MirBSD Korn Shell...
mount /dev/sdb1 /hd
cp /hd/kernel /src
rm -rf /system/lib/modules/*
cp -a /hd/modules/* /system/lib/modules
sync; umount /hd; reboot -f
The example assumes the new kernel image and the corresponding modules are in a USB disk /dev/sdb1, and the /system/ was installed as read-write mode.

Build a customized kernel

Suppose you already have a workable kernel config for you hardware, it's easy to tell the build system to use your config to build the iso. Just put your config file to kernel/arch/x86/configs/, and run (suppose the name of your config is my_defconfig)

make iso_img TARGET_PRODUCT=android_x86 TARGET_KERNEL_CONFIG=my_defconfig
Note you cannot use a kernel config from a normal linux distribution (e.g, ubuntu) for android-x86. You need to enable android kernel features to make it work. See android/configs/android-base.cfg for a list of required configuration options for a kernel to support an Android system. (but removes arm specific options for android-x86, e.g., PMEM)

Customize the kernel configuration

It is never advisable to edit the kernel config file directly, as it may generate faulty configuration (dependencies not met etc.). The correct way to customize the kernel config is (on the top of android-x86 tree)

. build/; lunch android_x86_64-userdebug
make -C kernel O=$OUT/obj/kernel ARCH=x86 menuconfig

If you get an error message Unknown option: -C, change make to /usr/bin/make. That's because since Android 8 the build system overrides the default make command of the system by its own make function (to invoke soong rules) which doesn't recognize the -C option. To overcome that, just use the make command of the system.

The generated config is $OUT/obj/kernel/.config. Copy it to where you want it to be.

DO NOT issue make menuconfig in the kernel/ directory directly. If you do so, the build rules may be broken. In this case, try this way to recover it (on the top of android-x86 tree):

make -C kernel distclean
rm -rf $OUT/obj/kernel

Use a prebuilt kernel

If you have a workable prebuilt kernel binary for your hardware, you can generate the iso with it:

make iso_img TARGET_PRODUCT=android_x86 TARGET_PREBUILT_KERNEL=<path to the prebuilt kernel>

Compile kernel for ARM (deprecated)

The kernel build system can also be used to compile kernel for ARM. For example, to compile kernel 2.6.29 for the goldfish CPU of the arm emulator, run

cd kernel
git checkout x86/android-goldfish-2.6.29
cd ..
make kernel TARGET_KERNEL_CONFIG=goldfish_defconfig TARGET_NO_KERNEL=
The kernel binary will be generated in out/target/product/generic/kernel.
Set TARGET_NO_KERNEL to be empty is important, otherwise the kernel building steps will be skipped.