[XP][KERNEL][3.0.101][Kitkat] AJ Kernel [v4][Dual Recovery][PhilZ touch|TWRP] - Sony Xperia P, U, Sola, Go

Before anything I'd like to sincerely thank DooMLoRD. He was the first dev ever to bring multiple recoveries to Xperias since Xperia X10 days and he has done a lot to make this work. So if you like this, please consider donating him for his great work.
Click to expand...
Click to collapse
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* You may have voided your device's warranty.
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications on your device
* I absolutely disclaim any responsibility.
*/
Downloads
LINKS REMOVED. DISCONTINUED.
Instructions
-Installation
1. Download zip.
2. Flash via recovery
3. Reboot
Click to expand...
Click to collapse
-Booting into recovery
For philZ recovery 6.41.6 :
+ Press vol. up when phone vibrates
For twrp 2.7 :
- Press vol. down when phone vibrates
Click to expand...
Click to collapse
Changelog/Feature list
v4
- Flashable zip for kernel
- Kernel compressed with LZO for better compression/decompression speeds
- Doubled the VM readaheads
- Optimized CPU performace
- Boost networks speed by locking the initial TCP window size to 64K
- Entropy tweaks
- Enabled ARCH_POWER
- BFQ and SIOplus now working properly
- Properly fixed dynamic management of dirty page writebacks
- Enabled ARM_THUMBEE
- Disabled gentle fair sleepers
v3
- Cross-compiled with arm-cortex_a9-linux-gnueabihf-linaro_4.9.1-2014.04 toolchain with arm-gnueabi binaries.
- New logo
- Add sioplus i/o scheduler and bfq i/o scheduler
- Fixed n_tty_write crash when echoing in raw mode(thanks to peterhurley)
- O3 optimizations
- Dynamic management of dirty page writebacks
- Enabled 5 GHz band and cleancache
- Lots of optimizations and good speed boost.
v2
- PhilZ touch recovery instead of CWM
- Changes for LZO compression/decompression(thanks to Gava97)
- Frandom modules added(thanks to Gava97)
- Code optimized
- Used 4.7 toolchain instead of 4.4.3 GCC
v1
-Initial release
-Dual recovery
-AOSX kernel compiled from source
-One kernel compatible with all kitkat ROMs(Both CM and AOSP based)
Click to expand...
Click to collapse
CPU Governors and I/O schedulers
CPU Governors
interactiveplus
fantasy
pegasusqplus
dyninteractive
intellidemand
nightmare
sakuractive
abyssplug
wheatley
pegasusq
ondemandAX
lulzactiveq
hotplug
minmax
smartassV2
interactive
conservative
ondemand
userspace
powersave
Lionheart
performance
I/O Schedulers
bfq
sioplus
noop
deadline
cfq
sio
vr
row
zen
Usage of some features
Dynamic management of dirty page writeback
What is does?
- Allows to dynamically manage the dirty page writebacks with two different intervals, one when the screen is on and another when the screen is off. By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
Thanks to Christopher83 and kingBABAsula.
Usage-
To enable it:
Code:
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
To disable it:
Code:
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
To customize intervals (in centisecs):
Code:
echo xxxx > /proc/sys/vm/dirty_writeback_active_centisecs
echo xxxx > /proc/sys/vm/dirty_writeback_suspend_centisecs
Commit list
5502c9d- LZO compression for kernel for better speed
3583d16- 2x(min,max VM READAHEAD)
85bc173- Change CPU performance
33eaf7c- Boost network speed
e4adc50- random: entropy tweaks are all the rage nowadays
b2f1fb2- Enable ARCH_POWER
58aa12b- IOsched update: Add BFQ and SIOPLUS in defconfig
982e2cc- Defconfig part for 96f9959
e07c683- Enable ARM_THUMBEE
ad5f538- Disable gentle fair sleepers
7ff3c51- Add new logo
eda4962- O3 optimizations
96f9959- mm: Dynamic management of dirty page writebacks
ab20cd6- block: Add BFQ I/O scheduler
cba2d5a- mutex: dynamically disable mutex spinning at high load
65581fa- n_tty: Fix n_tty_write crash when echoing in raw mode
2dcff35- Enable 5GHz band and clean cache
7a1805b- IOSCHED: Add SIOplus
231a11c- Add philZ touch recovery
713597e- lib/lzo: Optimize code for CPUs with inefficient unaligned access
a7e474f- lib/lzo: huge LZO decompression speedup on ARM by using unaligned access
548b108- lib/lzo: Update LZO compression to current upstream version
13cad97- drivers/char: add frandom modules
6096ed0- Dual recovery
Credits
linus(and other guys)- For linux kernel
ST-ericsson- For making the kernel compatible with montblanc board
Sony mobiles- For making the kernel compatible with riogrande
munjeni- For his great development and help
DooMLoRD- For dual recovery in other devices from which I could take reference and for helping me
AOSX team(Including me )- For development of 2012 xperia novathor devices
Phil3759- For PhilZ touch recovery
Dees Troy(and omnirom team)- For TWRP
cocafe- For work on u8500 samsung devices
KINGbabasula- Also for work on u8500 samsung devices
Christopher83- For modified linaro toolchains for cortex-a9
abcdjdj- For helping me in this
Gerald Carl- For testing it
Estape11- For testing it
#include<iForgotYou.h>
Sources
Kernel sources- https://github.com/Abhinav1997/AJ-Kernel
Ramdisk- https://github.com/Abhinav1997/AJ-ramdisk (other device devs/users can look into this to understand what changes were done)

---

Nice work bro

---

Great work bro

---

everything works fine !
tnx :good:

---

v2 released
Cheers,
AJ

---

been using triple recovery on xperia sp.
Will try this one on my xperia P :good:

---

Nice job ^^
But one question: is this 3.4 kernel, so yes can you make one for JB ?
Verstuurd vanaf mijn LT22i met Tapatalk

---

Dark Mist said:
been using triple recovery on xperia sp.
Will try this one on my xperia P :good:
Click to expand...
Click to collapse
Will soon bring triple recovery to this also
Pandemic said:
Nice job ^^
But one question: is this 3.4 kernel, so yes can you make one for JB ?
Verstuurd vanaf mijn LT22i met Tapatalk
Click to expand...
Click to collapse
Nope. This is 3.0.101 though I can bring dual recovery to stock JB kernel.
Cheers,
AJ

---

Abhinav2 said:
Will soon bring triple recovery to this also
Nope. This is 3.0.101 though I can bring dual recovery to stock JB kernel.
Cheers,
AJ
Click to expand...
Click to collapse
Wow bro, I would like to have that stock jb kernel with dual recovery...can you make one???
Sent from my LT22i using Tapatalk

---

Xperia_Fans said:
Wow bro, I would like to have that stock jb kernel with dual recovery...can you make one???
Sent from my LT22i using Tapatalk
Click to expand...
Click to collapse
Well yeah, I can but firstly I'll have to bring more features to this kernel
Cheers,
AJ

---

*mcdaonald theme song* tada tada dat da i am loving it :laugh:

---

cellabonez said:
*mcdaonald theme song* tada tada dat da i am loving it :laugh:
Click to expand...
Click to collapse
lol
BTW you can use it with carbon to get the netfilters working like you wanted
Cheers,
AJ

---

Abhinav2 said:
Well yeah, I can but firstly I'll have to bring more features to this kernel
Cheers,
AJ
Click to expand...
Click to collapse
ok bro no rush, take your time...I understand that

---

Abhinav2 said:
lol
BTW you can use it with carbon to get the netfilters working like you wanted
Cheers,
AJ
Click to expand...
Click to collapse
damn talk about side order :highfive:

---

Great work @Abhinav2! Just a quick suggestion. Maybe you could update the mali graphic driver and/or add OC feature to Cpu (and Gpu if you will)
Sent from my Xperia P using XDA Premium 4 mobile app

---

kopter3161 said:
Great work @Abhinav2! Just a quick suggestion. Maybe you could update the mali graphic driver and/or add OC feature to Cpu (and Gpu if you will)
Sent from my Xperia P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried update mali drivers and gralloc to 6 may update but unfortunately it didn't passed kernel logo. I'll try to debug it but it can take time. Also DevSwift1 tried GPU OC but it had no effect on device.
AJ

---

Abhinav2 said:
I tried update mali drivers and gralloc to 6 may update but unfortunately it didn't passed kernel logo. I'll try to debug it but it can take time. Also DevSwift1 tried GPU OC but it had no effect on device.
AJ
Click to expand...
Click to collapse
the first custom kernel for kitkat, thanks AJ!
1. dual recovery seems cool, but imo there is no real benefit when both of them do effectively the same. Again, great job that you managed to include both, but to me it becomes just "bloat". no offence.
2. I'm not a fan of overclocking but there are uses for better CPU/GPU controls. I would love to underclock and undervolt them to squeeze a little more battery out of my phone. God, it seems lots of those kids here care about their "gaming performance" and their "lagfree" "smoothness", but I use my phone as a phone and I don't give a sh... about that if I can get a couple more hours of use.
What's your opinion on this? Do you think we will ever get this working here like all the others (looking at those qualcomms and snapdragons in the other forums)? I mean we got more manufacturer sources than most of them, right? Or does it come down to sacrificing a phone to find those precious values for the right voltages, ...? Please shed some light on this for me, I never read a real answer from any dev out there.
3. On 4.1.2 we had this phantom kernel with a lot more CPU frequency steps. Some governors worked definitely better when they can scale over more frequencies. Maybe you can implement that?

---

stothegee said:
the first custom kernel for kitkat, thanks AJ!
1. dual recovery seems cool, but imo there is no real benefit when both of them do effectively the same. Again, great job that you managed to include both, but to me it becomes just "bloat". no offence.
2. I'm not a fan of overclocking but there are uses for better CPU/GPU controls. I would love to underclock and undervolt them to squeeze a little more battery out of my phone. God, it seems lots of those kids here care about their "gaming performance" and their "lagfree" "smoothness", but I use my phone as a phone and I don't give a sh... about that if I can get a couple more hours of use.
What's your opinion on this? Do you think we will ever get this working here like all the others (looking at those qualcomms and snapdragons in the other forums)? I mean we got more manufacturer sources than most of them, right? Or does it come down to sacrificing a phone to find those precious values for the right voltages, ...? Please shed some light on this for me, I never read a real answer from any dev out there.
3. On 4.1.2 we had this phantom kernel with a lot more CPU frequency steps. Some governors worked definitely better when they can scale over more frequencies. Maybe you can implement that?
Click to expand...
Click to collapse
1. Got many PMs asking for dual recovery so included it. And it won't slow down the boot process or make it laggy. Why?
If you extract the ramdisk you'll see that init.sh script controls the booting just like in CM(new builds)/AOSX. What the help of this script, ramdisk and recoveries are separately extracted so it doesn't extract and ramdisk or ramdisk-recovery until and unless the particular key assigned to it is pressed.
2,3. Honestly, I never looked at oc/uc, as I don't like playing with my CPU clock at all. Though I can try to integrate it and can only give a proper answer after trying
Cheers,
AJ

---

OK guys. I did read about OC CPU and various methods for our devices and basically all the kernels which say having OC aren't properly adding it. What they actually did was just adding CPU frequency names in the table in drivers/cpufreq/dbx500-cpufreq.c. Also it is quite hard(and maybe risky) to OC our kernel since I can't find the OC threshold anywhere. So it'd be better not to bring OC to it.
And about triple recovery, I won't be bringing it in this or kumquat kernel. DooMLoRD said that he wanted to keep it exclusive to DooMKernel and TBH I agree with him. He did put a lot of efforts in it and I respect his decision.
Cheers,
AJ

---

thanks for the amazing work