[KERNEL] [N4] [6.0][3.4.0][AOSP/CM] [10/26] [M2] - AK
- Thread starter CallMeAldy
- Start date
[CM10.2] STABLE KERNELS
changelog:
+ 2 patches for interactive from 3.10 android
+ some patches for lib routine
+ a lot of fixes here and here
+ low cpu freqs steps: +162 Mhz, +270 Mhz, +378 Mhz
+ auto hotplug tuned for battery life
+ rwsem patches
+ binder patches
NB:
no lag with last cm nighlty for me!
NB:
seems users want speed ..... and speed will be!
Last edited:
Is this updated from today's previous release?
Sent from my Nexus 4 using XDA Premium 4 mobile app
That means lights out for me, time to give my glasses a break and go contacts tomorrow.
See you in the morning man, thanks for all of your work!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Is this compatible with stock 4.3 JWRYY?
I had flashed the latest version just now but my display become such a total mess. I've also tried flashing the screen tearing fix I found on purified kernel thread but its still the same.
Any help?
I had flashed the latest version just now but my display become such a total mess. I've also tried flashing the screen tearing fix I found on purified kernel thread but its still the same.
Any help?
No compatible my friend ... only CM10.2 roms and derivate ... CAF godness is inside. :highfive:
Last edited:
mpd is dropped = only auto hotplug
I have uploaded a new version super optimized:
http://forum.xda-developers.com/devdb/project/?id=1023#downloads
Changelog:
https://github.com/anarkia1976/AK-xCrossing/commits/ak-cm10.2-015-prima
... you can try this version and report if lags are gone.
Thanks a lot.
Did anyone notice that in 0.41 some strange default color gamma? It's too blue. Is it related to commit "Switch to cm10.2 colors " ?
EDIT: Forget about this, it's my bad gamma settings, after resetting it colors become fine
Last edited:
Doesn't use halfbreed by default. But there are preset options, that can be chosen, present in trickstermod.
Sent from my Nexus 4 using Tapatalk
Nope... My CPU tends to stay @162Mhz; it takes some times to raise, so when I scroll the homepages, i have lag... It takes around 1 second, but I need to use the touchscreen a lot, if I make a single press, frequency stays at 162...
I'm sorry if this is silly or redundant, but has anyone tried this on Slim ROM? I know cm kernels used to work on slim, but they made some changes that forced use of a JWR kernel that seriously reduced compatibility with most kernels for a while. Since then supposedly things have improved. I'm currently using AK JWR 0.23+ and would love to try out your latest work.
Sent from my Nexus 4 using Tapatalk
Sent from my Nexus 4 using Tapatalk
yeah, I wish there was a JSS/JWR version of this great ROM.
That's how intelliplug works
And that's the reason I'm back to the official cm kernel while waiting for a faux kernel with CAF support: I love the smoothness provided by mpdecision and can't appreciate my phone without it :-\
What governor are you guys with lag using? I'm using intellidemand and I don't suffer any responsiveness issues. Default hot plug & governor settings.
Sent from my Nexus 4 using Tapatalk
Sent from my Nexus 4 using Tapatalk
Shouldn't take that long to ramp up... Do ypou mean intellidemand? The hotplug here is generic hotplug by thalamus. Faux kernel primarily uses intelliplug on the main cores, not mpdecisionThat's how intelliplug works
And that's the reason I'm back to the official cm kernel while waiting for a faux kernel with CAF support: I love the smoothness provided by mpdecision and can't appreciate my phone without it :-\
Try another governor, like interactive because it should not take a whole second to ramp up unless its a super power saving governor.
There is no intellitplug in the kernel. It uses auto_hotplug. If you want a raised frequenzy by touch, you need a touch boost. There are more theories about it. I'm thinking it's a way to improve smoothness, and i'ts a way to save battery. It doesn't need to scale up and down when you are scrolling, or interact with the UI. 1ghz for example can handle a lot of backgroundload and UI Interactions. Fix it by touch for 1 second after touch, but let it scale above, if needed.That's how intelliplug works
And that's the reason I'm back to the official cm kernel while waiting for a faux kernel with CAF support: I love the smoothness provided by mpdecision and can't appreciate my phone without it :-\
Every frequency-calculation needs power. If you reduce them in form of less frequencies avaiable to scale (by touch it scales only from 1ghz to max) you will have some sort of battery saving. mpd does something similar. By touch min_freq = 1026000 for 3 seconds and 2 Cores.
Look at @anarkia1976 git, you will find there something
hells
---------- Post added at 02:29 AM ---------- Previous post was at 02:13 AM ----------
intellidemand is a good example. It uses a dynamic samplerate. If you touch your screen, the samplingrate will be lower for 2.5 sec, so you will have much less latency in UI interactions. If you use that lesser latency together with touch boost, like I do... Yes, it's smooth as butter
hells
Strange is that I use kernels without MPdecision from a long time, but I never had issues of CPU not ramping up...
This looks more like a touch boost issue, not a governor one.
This looks more like a touch boost issue, not a governor one.
Last edited:
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