I hope to find some time in the next days...
K^Kernel 3.0.95 v2.8 for JB 4.1.2 and JB 4.2.2
Hi guys,
I released the new v2.8 builds of the kernel:
Note:
The kernel builds for CM 10.1 can be used only on new CM 10.1 rom releases that include the updated sensor libs.
Hi guys,
I released the new v2.8 builds of the kernel:
Code:
- Kernel 3.0.95
- Sources synched with jb-3.0 repo of Arco68 and ADC Team for JB-4.1.2 (CM 10) kernel builds
- Sources synched with cm-10.1_3.0 repo of Arco68 and ADC Team for JB 4.2.2 (CM 10.1) kernel builds
- Built with my latest custom Linaro 4.7.4-2013.08 toolchain optimized for Cortex-A8
- Bluetooth: Fix for the l2cap layer crashes while turning OFF BT (credits to Nitin Shivpure)
- Enable setting security contexts on rootfs inodes (credits to Stephen Smalley)
- ariesve_sensors: updated all sensors to match with the new opensource libsensors for CM 10.1 kernel (credits to CastagnaIT)
- board_ariesve: cleanup mdp_pdata and added missing mem_hid (credits to CastagnaIT)
- net: ipv6: add missing lock in ping_v6_sendmsg (credits to Lorenzo Colitti)
- net: ipv6: fix wrong ping_v6_sendmsg return value (credits to Lorenzo Colitti)
- msm_fb: Correct R and G offsets for correct mapping (credits to Jeevan Shriram, thanks to Arco68)
- USB: gadget: Cleanup boot-up message with default usb composition (credits to Mayank Rana, thanks to Arco68)
- cpufreq: interactive: fix show_target_loads and show_above_hispeed_delay (credits to Minsung Kim, thanks to Arco68)
- CIFS support on bootThe kernel builds for CM 10.1 can be used only on new CM 10.1 rom releases that include the updated sensor libs.
Damn! It gets close to be a full number..Will it continue as 3.0.1XX or 3.1?
I think 3.0.1.xx because there already is a 3.1.xx kernel
Sent from my GT-I9001 using xda app-developers app
Hmm, you're right. After looking at wikipedia i see it now, but the Kernel 3.1 wont get maintained anymore as it seems. But yeah, you said it already. Should be 3.0.1XXI think 3.0.1.xx because there already is a 3.1.xx kernel
Sent from my GT-I9001 using xda app-developers app
(Its the first one since Linux 1.3.100 to reach a 3rd digit after the decimal point)
Last edited:
Yep. 3.1 doesn't have long-time-support. But my nexus 7 uses it.
Sent from my GT-I9001 using xda app-developers app
Does this mean 2.8 should work on ADC's ROM?
Yes. And only this rom, because of the new sensor drivers.
Sent from my GT-I9001 using xda app-developers app
Yes, but only Release 6 (and up).
Do you will release the kernel for android 4.3 or cm10.2 rom by adc team ?
I think 3.4.X is stable enough at this time, we dont have to go back anymore.
Gesendet von meinem GT-I9001 mit Tapatalk 4
Yes maybe
but 3.0.X is better in battery life
Same with me. Makes a difference of 1-2h in favour of 3.0.x in my case...
Sent by i9001 0x07 board running CM10.1rc6 ADC on K^Kernel2.1exUV370MB with i9001XXKPO baseband
Sent by i9001 0x07 board running CM10.1rc6 ADC on K^Kernel2.1exUV370MB with i9001XXKPO baseband
I have an issue here while trying to install 2.8 exUV 370 MB.
Coming from cm10.1r6 ADC I installed 2.1 exUV 370 MB. This combination worked fine with some glitches at the beginning. In order to have longer battery life I downloaded 2.8. It seems everything is ok with the file, however could not check md5.
Tried to flash 2.8:
wiped dalvic + cache
fix permissions
flashed 2.8 with TWRP 2.4.1
wiped dalvic + cache
fix permissions
boot to system within TWRP 2.4.1
boot works fine until system appears but now I immediately get the message
Process com.android.phone closed (In German)
I can not access the phone.
went back (took battery off and then reboot with function keys) to Nandroid backup with 2.8 works fine.
Downloaded 2.8 again, in case the file is corrupt. - Same behaviour.
Downloaded 2.8 exUV 390MB, in case the problem is in 370MB only
Same behaviour with the 390MB version
Any idea how to solve it?
Coming from cm10.1r6 ADC I installed 2.1 exUV 370 MB. This combination worked fine with some glitches at the beginning. In order to have longer battery life I downloaded 2.8. It seems everything is ok with the file, however could not check md5.
Tried to flash 2.8:
wiped dalvic + cache
fix permissions
flashed 2.8 with TWRP 2.4.1
wiped dalvic + cache
fix permissions
boot to system within TWRP 2.4.1
boot works fine until system appears but now I immediately get the message
Process com.android.phone closed (In German)
I can not access the phone.
went back (took battery off and then reboot with function keys) to Nandroid backup with 2.8 works fine.
Downloaded 2.8 again, in case the file is corrupt. - Same behaviour.
Downloaded 2.8 exUV 390MB, in case the problem is in 370MB only
Same behaviour with the 390MB version
Any idea how to solve it?
Have you downloaded the correct file for 4.2.2??? Last time I accidentally flashed 4.1 kernel into 4.2 rom and it did boot successful but the process com.android.phone FC...I have an issue here while trying to install 2.8 exUV 370 MB.
Coming from cm10.1r6 ADC I installed 2.1 exUV 370 MB. This combination worked fine with some glitches at the beginning. In order to have longer battery life I downloaded 2.8. It seems everything is ok with the file, however could not check md5.
Tried to flash 2.8:
wiped dalvic + cache
fix permissions
flashed 2.8 with TWRP 2.4.1
wiped dalvic + cache
fix permissions
boot to system within TWRP 2.4.1
boot works fine until system appears but now I immediately get the message
Process com.android.phone closed (In German)
I can not access the phone.
went back (took battery off and then reboot with function keys) to Nandroid backup with 2.8 works fine.
Downloaded 2.8 again, in case the file is corrupt. - Same behaviour.
Downloaded 2.8 exUV 390MB, in case the problem is in 370MB only
Same behaviour with the 390MB version
Any idea how to solve it?
Oops, need to check. Would be a stupid mistake...
Yes, it is
K^Kernel_JB-4.2.2_3.0_v2.8_Linaro-4.7.4_OC_EXUV_370MB_Signed
Any other idea? Tried the process in my previous post again with the same result...FC
Last edited:
Mhh. No idea, but why do your way of flashing is a bit weird. Just flash the zip, and wipe cache/dalvik. Then you can reboot. No permission fix is needed, because the rom remains ubtouched after flashing a kernel and fixing permission is only active in /system/ and /data . The Kernel has its own partition.I have an issue here while trying to install 2.8 exUV 370 MB.
Coming from cm10.1r6 ADC I installed 2.1 exUV 370 MB. This combination worked fine with some glitches at the beginning. In order to have longer battery life I downloaded 2.8. It seems everything is ok with the file, however could not check md5.
Tried to flash 2.8:
wiped dalvic + cache
fix permissions
flashed 2.8 with TWRP 2.4.1
wiped dalvic + cache
fix permissions
boot to system within TWRP 2.4.1
boot works fine until system appears but now I immediately get the message
Process com.android.phone closed (In German)
I can not access the phone.
went back (took battery off and then reboot with function keys) to Nandroid backup with 2.8 works fine.
Downloaded 2.8 again, in case the file is corrupt. - Same behaviour.
Downloaded 2.8 exUV 390MB, in case the problem is in 370MB only
Same behaviour with the 390MB version
Any idea how to solve it?
But wait...can you try to switch to flightmode after FC, then reboot, and then turn off flightmode and test again?
Gz
X
Sent from my Nexus 4 using Tapatalk 4
No chance to get there. The error message com.android.phone appears immediately on the home screen. I hardly can get into recovery with a lot of trying as the message immediately reappears as soon as I push the ok button.
Tried the following procedure now:
1. I took my Nandroid backup of r5 kk 2.7 and restored it
2. Activating Trebouchet launcher as standard (Had lightning as standard).
3. Back to TWRP 2.4.1
4. Reflashing Rom r6 and kk 2.8 and gapps
5. wipe cache and dalvic
6. reboot to system
resulted in com.android.phone FC
Same procedure as above, but
5. wipe cache and dalvic and fix permission
resulted in com.android.phone FC
Unfortunaltely I can not create a syslog after flashing KK2.8, as I do not get beyond home screen.
Restore of r5 kk2.7 again
In TWRP
- flashing r6 + kk2.1 + gapps
- wipe cache and dalvic
- reboot to system
system hangs in boot logo > switched the device off > switched the device on
boot procedure is fine with kk2.1
Hence I guess there is a glitch in 3.0.x kernel KK2.8 which prevents my com.android.phone process to start.
3.0.x kernel until now was less battery consuming than 3.4.x and I did rated the battery life higher than the newer kernel version. Consequently I am still eager to have the 3.0.x kernel running on my device
No chance to get there. The error message com.android.phone appears immediately on the home screen. I hardly can get into recovery with a lot of trying as the message immediately reappears as soon as I push the ok button.
Tried the following procedure now:
1. I took my Nandroid backup of r5 kk 2.7 and restored it
2. Activating Trebouchet launcher as standard (Had lightning as standard).
3. Back to TWRP 2.4.1
4. Reflashing Rom r6 and kk 2.8 and gapps
5. wipe cache and dalvic
6. reboot to system
resulted in com.android.phone FC
Same procedure as above, but
5. wipe cache and dalvic and fix permission
resulted in com.android.phone FC
Unfortunaltely I can not create a syslog after flashing KK2.8, as I do not get beyond home screen.
Restore of r5 kk2.7 again
In TWRP
- flashing r6 + kk2.1 + gapps
- wipe cache and dalvic
- reboot to system
system hangs in boot logo > switched the device off > switched the device on
boot procedure is fine with kk2.1
Hence I guess there is a glitch in 3.0.x kernel KK2.8 which prevents my com.android.phone process to start.
3.0.x kernel until now was less battery consuming than 3.4.x and I did rated the battery life higher than the newer kernel version. Consequently I am still eager to have the 3.0.x kernel running on my device
i would advice you to make a backup all of you content and format internal and external sd
New posts
-
[VENDOR][GAMING][ARM64][A10][A11] - All variants
- Latest: Albino_Namekian
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone