Right? It's probably because the op hasn't updated the title to make it day it's for CM10.1
lol thanks, I just changed it
Right? It's probably because the op hasn't updated the title to make it day it's for CM10.1
One more happy user running 4.2.2 aokp with this kernel. Thanks!
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.
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.
Sorry, my question was very unspecific. I mean the stock CM kernel, not this one.
Have a feeling we will have s2w soon
Sent from my One X using xda premium
Sorry, my question was very unspecific. I mean the stock CM kernel, not this one.
It seems that after flashing this kernel and then flashing the 2/24 nightly (and running the stock boot.img from CM zip) there is a bootloop. Once this kernel, or an older CM boot.img is flashed, the device can boot.
h8 said bootlooping was caused by a recent commit that should be fixed in the next nightly. As far as I know this kernel wasn't the issue.
D/WifiService( 464): setWifiEnabled: true pid=1181, uid=1000
D/BluetoothAdapter( 675): 1090326768: getState() : mService = null. Returning STATE_OFF
D/BluetoothAdapter( 1181): 1089374768: getState() : mService = null. Returning STATE_OFF
E/WifiStateMachine( 464): Failed to load driver!
D/BluetoothAdapter( 675): 1090326768: getState() : mService = null. Returning STATE_OFF
E/WifiStateMachine( 464): DriverFailedState
D/BluetoothAdapter( 1181): 1089374768: getState() : mService = null. Returning STATE_OFF
Running 2.22 with the linaro 2 (last file in the list). Everything except wifi seems to work fine.
Edit: useful information time. Instead of just saying "it's not working", I'll provide some description.
I toggle the wifi setting to on, and it says "turning wifi on..." but it never comes on.
Logcat say:
Code:D/WifiService( 464): setWifiEnabled: true pid=1181, uid=1000 D/BluetoothAdapter( 675): 1090326768: getState() : mService = null. Returning STATE_OFF D/BluetoothAdapter( 1181): 1089374768: getState() : mService = null. Returning STATE_OFF E/WifiStateMachine( 464): Failed to load driver! D/BluetoothAdapter( 675): 1090326768: getState() : mService = null. Returning STATE_OFF E/WifiStateMachine( 464): DriverFailedState D/BluetoothAdapter( 1181): 1089374768: getState() : mService = null. Returning STATE_OFF
I am really glad that people are enjoying this kernel but I would like to urge you guys to NOT report any issues in the CM10.1 thread or anywhere other than in this thread unless you are using the stock kernel for that ROM.
Also, just to reiterate, cm10.1_vz-oc(linaro).2.zip kernels are ONLY properly compatible with cm-10.1-20130219-NIGHTLY-evita.zip
ps. I will look at Rohans helpful suggestion soon but probably not for the next build.
CPU: 1782 MHz 1.25 V
L2: 1350 MHz 1.15 V
BUS: 532 MHz
fastboot flash boot boot.img
system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
git clone https://github.com/vanja-zecevic/android_kernel_htc_msm8960.git
git checkout jellybean-oc
export CCOMPILER=$PATH_TO_TOOLCHAIN/bin/arm-eabi-
cp ./config-oc ./.config
make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER -j12
./split_bootimg_pl ./boot.img
./mkbootimg --base 0x80400000 --ramdiskaddr 0x81800000 \
--cmdline 'console=ttyHSL0,115200,n8' \
--kernel arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz \
-o boot_vz-oc.img
--cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom'
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.