There has been a lot of active development on the kernel for our device with new commits almost every day. For this reason, the kernels I put up have been becoming outdated pretty quickly. For example, the cm10.1-oc(-linaro).2 builds are only EXACTLY compatible with the 20130219-NIGHTLY. You may find the kernels also work with other builds however it is not guaranteed.

I will be putting up new builds roughly once per fortnight and I will attempt to keep the compatibility section up to date.

There has been a lot of active development on the kernel for our device with new commits almost every day. For this reason, the kernels I put up have been becoming outdated pretty quickly. For example, the cm10.1-oc(-linaro).2 builds are only EXACTLY compatible with the 20130219-NIGHTLY. You may find the kernels also work with other builds however it is not guaranteed.

I will be putting up new builds roughly once per fortnight and I will attempt to keep the compatibility section up to date.

If you set the kernel to install the modules the kernel build generates as well, you will almost completely rid your kernel of these compatibility problems. Unless a kernel commit is merged that also has parts in the device trees, your kernel will still function as it was intended, and nothing should break.

If you need help with an installer for the modules, feel free to grab one of my recent kernel release packages and see how the updater script i use does it.

For anyone who flashed this kernel, can you boot into the 2/24 CM nightly using the boot.img from that zip? Me and a few others are experiencing a boot loop on the latest nightly over in the CM10.1 thread after flashing this kernel.

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?