ROM as been moved to this thread: http://forum.xda-developers.com/showthread.php?t=2134196
Re: [ROM] CM 10.1 with bionic patches (next version to be built with Linaro toolchain
Can i use trinity kernel for this rom?
Sent from my Nexus 4 using xda app-developers app
zarboga said:
Can i use trinity kernel for this rom?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Any kernel that works with CM 10.1 will work. I just posted the ones I've tested and had success with.
Re: [ROM] CM 10.1 with bionic patches (next version to be built with Linaro toolchain
What are bionic patches ?
Verstuurd van mijn Nexus 4 met Tapatalk
Ibsonic said:
What are bionic patches ?
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
They are patches that improve performance. A lot of ROMs include them. From what I understand, it has to do with code that is more optimized to our CPU than what is in AOSP.
Re: [ROM] CM 10.1 with bionic patches (next version to be built with Linaro toolchain
Is this updated to JOP40G?
How often do you plan to sync with latest CM sources and update this?
Michealtbh said:
Is this updated to JOP40G?
How often do you plan to sync with latest CM sources and update this?
Click to expand...
Click to collapse
Yes, I did a repo sync last night. Build number: cm_mako-userdebug 4.2.1 JPO40G eng.adam.20130203.024746 test-keys
I'd like to update at least once a week, maybe more, until if/when CM adds the bionic patches.
Ibsonic said:
What are bionic patches ?
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
Hi,
viking37 said:
It's a performance enhancement "built" in the ROM.
A little explanation from Morfic:
morfic said:
bionic is the "libc" of android, there are hardware optimized memcpy/memset and a few others for cortex-a9 and/or armv7-a, but also others specifically for krait, using those instead of stock bionic versions perform the same job a lot better than the more generic versions in aosp.
That affects memory throughput significantly and anything where you move data and need memory throughput using those functions will benefit from it.
there are other (math) functions that can be optimized more for the particular hardware
hope this helps
Click to expand...
Click to collapse
And an example from Simms22:
simms22 said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Thank you to them
Click to expand...
Click to collapse
EvoXOhio, you should do run Antutu at stock CPU freq for see (here you are at 1.18 Ghz...), normally you have over 20 000 at 1.51 Ghz. With a compilated Linaro ROM and (for example) Trinity kernel it will be rocking!!!
But you should test with the CM kernel at stock CPU freq...
Nice, I will give it a try , well done
As far as I know it's the first fully based CM ROM with bionic patches (nevermind, it seems there is another one...).
I thanked you and give 5 stars to the thread!
viking37 said:
EvoXOhio, you should do run Antutu at stock CPU freq for see (here you are at 1.18 Ghz...), normally you have over 20 000 at 1.51 Ghz. With a compilated Linaro ROM and (for example) Trinity kernel it will be rocking!!!
But you should test with the CM kernel at stock CPU freq...
Nice, I will give it a try , well done
As far as I know it's the first fully based CM ROM with bionic patches (nevermind, it seems there is another one...).
I thanked you and give 5 stars to the thread!
Click to expand...
Click to collapse
That's weird, I checked and it's set to 1.51 gHz and the interactive governor. Maybe I'll re-run them again but force it to performance governor. Or maybe my particular phone is slower for some reason. The important part to look at is the improvement, not just the raw numbers.
Where is the other CM based ROM with bionic patches? The whole reason I made this one is because I couldn't find one.
Thanks for the feedback!
Re: [ROM] CM 10.1 (JOP40G) with bionic patches (next version with Linaro toolchain)
Awesome job! I hope the next version with linaro will be soon
Sent from my Nexus 4
EvoXOhio said:
That's weird, I checked and it's set to 1.51 gHz and the interactive governor. Maybe I'll re-run them again but force it to performance governor. Or maybe my particular phone is slower for some reason. The important part to look at is the improvement, not just the raw numbers.
Where is the other CM based ROM with bionic patches? The whole reason I made this one is because I couldn't find one.
Thanks for the feedback!
Click to expand...
Click to collapse
Re,
Interactive is not bat but try with Ondemand governor, but it's weird that Antutu see 1.18 Ghz CPU freq... maybe a conflict between an app and the buit-in CPU settings ...
Also your Quadrant score does not reflect a score at 1.51 Ghz...
Maybe try another kernel for test (Trinity kernel).
If I have time I'll flash your ROM today and test.
EDIT: here for the another CM "bionic patched": http://forum.xda-developers.com/showthread.php?t=2131378 (compiled with Linaro it seems). Contact him and discuss with him about Linaro compiling...
0.0 said:
Awesome job! I hope the next version with linaro will be soon
Sent from my Nexus 4
Click to expand...
Click to collapse
Running a build now. If it works it will be up later today.
EvoXOhio said:
Running a build now. If it works it will be up later today.
Click to expand...
Click to collapse
that is awesome man! i saw some good merges too, like the privacy notification for the Messaging app and a fix that i liked for the call statistics :good:
Thank you. So much. I have wanted to go back to CM10.1 for a while, but didn't like not having the bionic patches. Can't wait for the Linaro patches to be sorted out.
:good:
Connor Baker
P.S. I have eight thanks good sir. You are going to receive every one of them.
viking37 said:
Hi,
EvoXOhio, you should do run Antutu at stock CPU freq for see (here you are at 1.18 Ghz...), normally you have over 20 000 at 1.51 Ghz. With a compilated Linaro ROM and (for example) Trinity kernel it will be rocking!!!
But you should test with the CM kernel at stock CPU freq...
Nice, I will give it a try , well done
As far as I know it's the first fully based CM ROM with bionic patches (nevermind, it seems there is another one...).
I thanked you and give 5 stars to the thread!
Click to expand...
Click to collapse
Firstly please downsize the images or link them, it's rather massive for anyone on a slower net connection or just plain annoying (no offense).
Secondly, you are misinformed about Linaro. Linaro is responsible for sets of patches to devices which can improve your performance. This very patch, the Bionic strings patch, comes from Linaro. They also make a toolchain. That toolchain is reputed to be slightly faster than others, maybe (and I'd say 5% at most), but it isn't what gives the gains shown in your presentation, that is the patches to the kernel/AOSP (like this one). These patches include handwritten assembly code that is written directly for the processor in our phones (Cortex-A9 Krait), and multiplies the speed of those functions. Compiler tweaks just make a bad assembly code generator very slightly better.
I seek only to stop misinformation, lots of people are confused about Linaro
Ranguvar said:
Firstly please downsize the images or link them, it's rather massive for anyone on a slower net connection or just plain annoying (no offense).
Secondly, you are misinformed about Linaro. Linaro is responsible for sets of patches to devices which can improve your performance. This very patch, the Bionic strings patch, comes from Linaro. They also make a toolchain. That toolchain is reputed to be slightly faster than others, maybe (and I'd say 5% at most), but it isn't what gives the gains shown in your presentation, that is the patches to the kernel/AOSP (like this one). These patches include handwritten assembly code that is written directly for the processor in our phones (Cortex-A9 Krait), and multiplies the speed of those functions. Compiler tweaks just make a bad assembly code generator very slightly better.
I seek only to stop misinformation, lots of people are confused about Linaro
Click to expand...
Click to collapse
And you have a little misinformation about "Krait" too:
Krait (CPU)
From Wikipedia, the free encyclopedia
Krait is an ARM-based central processing unit included in Snapdragon S4 System on chips. It is a successor to Qualcomm's Scorpion CPU and has architectural similarities to ARM Cortex-A15.
Click to expand...
Click to collapse
rskyline said:
And you have a little misinformation about "Krait" too:
Click to expand...
Click to collapse
Architectural similarities. It's halfway between the two.
I say Cortex-A9 because when you're a developer, you consider the lowest case.
If you try to write Cortex-A15 assembly for the Krait, it won't work (not specifically optimized code).
The Bionic strings patch was written for the Cortex-A9.
The CPU frequency seems to be wrong but it isnt. http://www.scottsroms.com/showthread.php?447-CPU1-governor-change-with-MPDECISION-file-script
Thank you Evo, thisis exactly what I was looking for for a long time, mostly CM but with those bionic optimizations
You already got all my thanks for today.
Keep it up while I'm going to flash it
EvoXOhio said:
That's weird, I checked and it's set to 1.51 gHz and the interactive governor. Maybe I'll re-run them again but force it to performance governor. Or maybe my particular phone is slower for some reason. The important part to look at is the improvement, not just the raw numbers.
Where is the other CM based ROM with bionic patches? The whole reason I made this one is because I couldn't find one.
Thanks for the feedback!
Click to expand...
Click to collapse
Looks like you're getting thermal throttled, which is very common. Performance governor probably won't do any better.
Related
Hello,
I'm the author of Voltage Control, an application for Galaxy S series to control OC/UV kernels. I don't personally own a Nexus S (and I cant say I will, unless someone want to Nexus S donate one for me ;p).
Voltage Control Lite 4.00 on Android Market!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know there are many apps to control OC, but I dont know any doing UV work.
If anybody is interested in making UV kernel for Nexus S there are some working kernels for SGS (given the hardware similarities some knowledge may be taken from current solutions).
Authors of most OC/UV code are raspdeep and Unhelpful, heres the topic: http://forum.xda-developers.com/showthread.php?t=822027 and second: http://forum.xda-developers.com/showthread.php?t=762171
If you are interested in creating UV kernel working with Voltage Control, I'll give brief explanation how VC works, and how are things done on SGS.
My application communicates with kernel via sysfs interfaces via cat and echo:
mandatory:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state // to read all states
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq // may be obsolete, didnt make a decision yet
Code:
/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
key in UV procedure, it represents undervolt for each frequency from highest to lowest; "25 25 50 50 100" means UV highest freq by 25, and lowest by 100
providing additional functionality:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table
Containing all frequencies and corresponding voltages, format:
FREQ STOCK CURRENT
Code:
1120000 1300 1300
1000000 1300 1300
This is useful for determining stock voltages used by the device, because they are needed in voltage calculation. Stock values are hardcoded, but If you want to change them I suggest to implement this table, to let user know at exactly what voltage his device is running.
Third column is obsolete, since VC calculates current (stock-uv) voltage itself might be removed in the future.
Code:
/sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
This is table where we store enabled ("1") and disabled ("0") state for each frequency;
"0 1 1 0 1" means we disabled highest frequency and second to lowest.
This is useful when kernel developer wants to produce ONE kernel for all OC lovers.
This means there could be one kernel supporting OC frequencies up to 1600Mhz (lets say 1600,1500,1400,1300,1200,1120), and user could choose which ones he wants to use (eg 1400 and 1120, disabling the rest).
I'm aware that Nexus S will receive tremendous attention from developers so I believe that someone might actually come with better implementation (single table consisting of all information needed by VC?)of this mess.
Best idea would be to make one table for all information, so it can be easily parsed.
Current version of app is 4.0 beta, which is a complete rewrite.
I'm open for ideas, suggestions regarding additional features.
Happy OCing.
Thanks xan for this invitation
Unhelpful also played a big part with the initial code to load dynamically frequencies and voltages using a sysfs interface.
BTW, your app source is welcome on project-voodoo github !
I know several people motivated to contribute, it would be a place to start.
Right, Unhelpful, adding topic to OP.
Yes, this needs to be open-sourced.
No date yet, because there are monsters inside.
The thing that struck me now, is why is all of that so complicated?
I think I like single-table idea more and more.
ill volunteer to help.
Very exciting to see some of the best dev names from the SGS community showing interest in the Nexus S. Many goog things to come for us if they remain interested...
So when are we gonna see a 1.2GHz Voodoo OC/UV kernel
My phone recieves a noticeable speed increase with the voodoo kernel for Nexus S with max and min set to 1000 with performance governor Can't wait for a super optimized kernel OC/UV!
looking forward to a UV kernel to extend battery life.
jroid said:
My phone recieves a noticeable speed increase with the voodoo kernel for Nexus S with max and min set to 1000 with performance governor Can't wait for a super optimized kernel OC/UV!
Click to expand...
Click to collapse
Anything on battery?
defysword said:
looking forward to a UV kernel to extend battery life.
Click to expand...
Click to collapse
+1
why is no one compiling a kernel supporting xans app? i really loved it on my galaxy s and when i saw this threat i was hoping for a supported kernel for my nexus s. it really can make oc more stable if u r patient enough to test the best setzings for ur phone
Sent from my Nexus S using Tapatalk
Can't wait for this too. Xan's app is really good on SGS.
shrooms90 said:
why is no one compiling a kernel supporting xans app? i really loved it on my galaxy s and when i saw this threat i was hoping for a supported kernel for my nexus s. it really can make oc more stable if u r patient enough to test the best setzings for ur phone
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
This died the 22nd of December, I got my Nexus S around that time, kept it stock while on vacation over the holidays, missed out there.
I *may* check this out, don't want to turn into Patches....
But I could continue to build Honity stable for Will, but others run lower than he does.
Instead of stock + UV build it would be only 1.
And Honity14 could be the UVOC some want.
Problem in that is that I take a risk of people not understanding the "use at your own risk" part involved.
Thanks for bumping this thread, didn't know xan had this.
Sent from my Nexus S
morfic said:
This died the 22nd of December, I got my Nexus S around that time, kept it stock while on vacation over the holidays, missed out there.
I *may* check this out, don't want to turn into Patches....
But I could continue to build Honity stable for Will, but others run lower than he does.
Instead of stock + UV build it would be only 1.
And Honity14 could be the UVOC some want.
Problem in that is that I take a risk of people not understanding the "use at your own risk" part involved.
Thanks for bumping this thread, didn't know xan had this.
Sent from my Nexus S
Click to expand...
Click to collapse
sounds good. i like honity kernel but for my phone it needs a little fine tuning.
i think people would understand "use at ur own risk" imo most people understood it on the sgs forum.
so i really would love to see honity14 with uv options
Sent from my Nexus S using Tapatalk
Is there any progress?
xan said:
I'm open for ideas, suggestions regarding additional features.
Happy OCing.
Click to expand...
Click to collapse
Hi. great stuff here. would this app work (or made to work) using snq-'s undervolting via sysfs here.
I use a kernel with the above patch enabled and my ROM users would love to be able to do this using an app like this.
Thanks!
pongster said:
Hi. great stuff here. would this app work (or made to work) using snq-'s undervolting via sysfs here.
I use a kernel with the above patch enabled and my ROM users would love to be able to do this using an app like this.
Thanks!
Click to expand...
Click to collapse
Im a noob when it comes to kernel developping, but i hope this will help u:
From what i understood this app undervolts using following command:
echo "0,0,50,100,0...." /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
Where the numbers stand for the amount of undervolting in mV for each freq. (I think it is from lowest to highest but im not sure. If u set the values at boot it just writes a startup script in /system/etc/init.d/
Sent from my Nexus S using Tapatalk
Fantastic,
The nexus s dev community is definitely growing now
JD
Sent from my Google Nexus Magic Wand S
JupiterDroid said:
Fantastic,
The nexus s dev community is definitely growing now
JD
Sent from my Google Nexus Magic Wand S
Click to expand...
Click to collapse
wtf? fancy seeing you here
Stea1thmode said:
wtf? fancy seeing you here
Click to expand...
Click to collapse
WTH young man, did you get lost
Just thought that I'd mention this.
I develop a kernel for the Captivate for CM7. Our cm kernel is based off Nexus S code, so anything that works under it will work under your kernels as well (probably). I've implemented this successfully under my kernel with no real problems.
Just add a sysfs interface to the cpufreq driver to store the uv amount, then subtract that amount * 1000 from arm_volt before feeding it into the regulator.
Sources are here --> https://github.com/TheEscapistxda/CM7-OCUV
PS I apologize for my terrible commenting.
AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.
Click to expand...
Click to collapse
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads
Click to expand...
Click to collapse
Quick Links
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code
Our site is up.
tiamat-aosp.com
Check it out and give us feedback guys.
Also, join us on irc!
irc.freenode.net
channel - #tiamat
Userbars: -- thanks to -viperboy-
Founder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Staff
Contributor
Tester
User
reserved for later
Downloading this now to try out; I assume that you included both Evervolv's and r2doesInc's GB ROMs in your statement of "all current GB ROMs"? That'd be great, because I swear that Invisiblek's kernel, fast and fluid as it is, is causing some majorly excessive overheating in my phone. I'd prefer that my phone break down...well, never, but if it did, closer to my contract upgrade date. lol hoping yours puts out less heat (and I'm only running the main profile at 1.1GHz, so it's not even that much over the stock).
Question: What exactly is HAVS and what is this undervolted to? And I don't know how to test USB tethering, sorry. Also I am running Cyanogen 6.1
I have installed this and ran a quadrant score and linpack test that I will post a screenshot of. I overclocked to 1.15 w/ smartass governor as default:
Going to look at this
Sent from my ADR6300 using XDA App
Cayniarb said:
This is the second iteration of my kernel, but it is the first time I'm posting it on XDA. You can find the post for the first version on the miui-dev forums here.
Click to expand...
Click to collapse
So far no problems with the kernel.
Does your kernel offer any built in screen off profiles when using the Smartass governor? Some kernels with smartass usually do a min-max screen off profile of 245.
Just checking, in case I have to make a screen off profile in setcpu.
dccoh said:
So far no problems with the kernel.
Does your kernel offer any built in screen off profiles when using the Smartass governor? Some kernels with smartass usually do a min-max screen off profile of 245.
Just checking, in case I have to make a screen off profile in setcpu.
Click to expand...
Click to collapse
Second this, i'd like to know about all of this too.
dccoh said:
So far no problems with the kernel.
Does your kernel offer any built in screen off profiles when using the Smartass governor? Some kernels with smartass usually do a min-max screen off profile of 245.
Just checking, in case I have to make a screen off profile in setcpu.
Click to expand...
Click to collapse
Screen off on smartass sets to 128/384 min/max.
morph3k said:
Question: What exactly is HAVS and what is this undervolted to? And I don't know how to test USB tethering, sorry. Also I am running Cyanogen 6.1
I have installed this and ran a quadrant score and linpack test that I will post a screenshot of. I overclocked to 1.15 w/ smartass governor as default:
Click to expand...
Click to collapse
I've seen quadrant scores in the mid 1500's with this kernel. The linpack app always gives kind of low scores since it was updated. With 0xBench, I've seen linpack scores in the 41's.
HAVS is hybrid active voltage scheduling. It allows the CPU to dynamically change the voltage at each frequency (speed) based on need. The ultimate result is better battery life.
This kernel will undervolt as far as 925 mV at lower frequencies. That is a fairly aggressive level and honestly, it may need to be raised a bit. On the other hand, I'm coming from the Evo which is a bit more power hungry (a lot of Evo's can't boot with that low of an undervolt, but my Incredible has not had any issues with it).
Thanks for the kernel. Great to see all the new options popping up from a growing pool of devs. Much appreciated.
Cayniarb said:
Screen off on smartass sets to 128/384 min/max.
Click to expand...
Click to collapse
Thank you for the quick response. Is there a specific reason for the 384 max?
My phone seems to handle the kernel fine, despite it being heavily undervolted. Having it undervolted, yet having a 384 max screen off probably balance out, so im not complaining. I'll continue to test it and see how battery life goes. Thanks again for the kernel.
Happy Holidays!
dc
I am liking the aosp explosion as of late.
Sent from my ADR6300 using XDA App
Cayniarb said:
I've seen quadrant scores in the mid 1500's with this kernel. The linpack app always gives kind of low scores since it was updated. With 0xBench, I've seen linpack scores in the 41's.
HAVS is hybrid active voltage scheduling. It allows the CPU to dynamically change the voltage at each frequency (speed) based on need. The ultimate result is better battery life.
This kernel will undervolt as far as 925 mV at lower frequencies. That is a fairly aggressive level and honestly, it may need to be raised a bit. On the other hand, I'm coming from the Evo which is a bit more power hungry (a lot of Evo's can't boot with that low of an undervolt, but my Incredible has not had any issues with it).
Click to expand...
Click to collapse
I was not trying to say your kernel was bad, in fact 1400's is great for me. I am enjoying your kernel a lot. I just thought you would like some feedback and those 2 things were some quick feedback i thought I could give ya.
DS36 said:
I am liking the aosp explosion as of late.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Me too. Very nice to see new AOSP ROM's and especially some AOSP Kernel's. Not long ago the choice for AOSP Kernels was very very limited, just kk's and ziggys I think.
dccoh said:
Thank you for the quick response. Is there a specific reason for the 384 max?
My phone seems to handle the kernel fine, despite it being heavily undervolted. Having it undervolted, yet having a 384 max screen off probably balance out, so im not complaining. I'll continue to test it and see how battery life goes. Thanks again for the kernel.
Happy Holidays!
dc
Click to expand...
Click to collapse
I don't like to drop the screen-off max to 245. Maybe this is another hang-up coming from the Evo, but when it is that low, there can be some issues on wake-up. That said, it's a max, so unless the phone needs to clock that high while the screen is off, it wont. Also, even at that level it will still undervolt at either 925 or 950 mV.
morph3k said:
I was not trying to say your kernel was bad, in fact 1400's is great for me. I am enjoying your kernel a lot. I just thought you would like some feedback and those 2 things were some quick feedback i thought I could give ya.
Me too. Very nice to see new AOSP ROM's and especially some AOSP Kernel's. Not long ago the choice for AOSP Kernels was very very limited, just kk's and ziggys I think.
Click to expand...
Click to collapse
I didn't think you were cutting on it, I was just saying that the numbers can go even higher. For my part, this kernel screams. It's not quite as fast as my Evo, but that can handle an OC to 1267, my Inc locks up at anything over 1113. Also, it's probably a bit easier to squeeze some extra performance out of it when cellular data is always turned off.
Only overclocked to 1075. I think I'm in love.
Sent from my ADR6300 using XDA App
I'll give this a try. invisiblek #21 broke my touch capabilities altogether, so we'll see if this one actually works with the 10 point touch.
Edit/Update: My phone does NOT like the 10 point patch, so this kernel is another no-go for me. It figures I can overclock to 1190 but I can't do this, which in the end is probably a lot more useful.
willhill said:
I'll give this a try. invisiblek #21 broke my touch capabilities altogether, so we'll see if this one actually works with the 10 point touch.
Edit/Update: My phone does NOT like the 10 point patch, so this kernel is another no-go for me. It figures I can overclock to 1190 but I can't do this, which in the end is probably a lot more useful.
Click to expand...
Click to collapse
Not every panel is capable of the 10-point multitouch. I can recompile a version that cuts it back down to 3 and that should work for you.
Sent from my PC36100 using Tapatalk
Cayniarb said:
Not every panel is capable of the 10-point multitouch. I can recompile a version that cuts it back down to 3 and that should work for you.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
thanks for the cayniarb... we miss you in the miui irc gonna load it up now... my panel doesnt like 10 either but why the hell do i need 10 neways... 2 is enough for me
thanks for the great work
Mod edit due to ignorance & immaturity. This thread is closed until it can be reviewed & further action can be taken. I know this affects users, and I am sorry for that, but you never see me bad mouthing anyone on the forum, but when you keep running your mouth & repeatedly have issues, you obviously are looking for a long term ban. BTW, if anyone has any evidence of me doing anything wrong, ANYTHING, forward it to MikeChannon or the Administrator. We have logs & I am confident & deliberate in all my actions. Not to mention, Synergye is the only person I can remember ever having to ban.
Are you ready to be KangBanged? The NEW git for the kernel is here: HERE
NOW *SHOULD* BE WORKING ON HOLIDAY BASES
S-ON? FOLLOW THIS GUIDE TO FLASH THE UPDATEZIP (THANKS TO DASPAZZ FOR WRITE UP)
Main Features:
MILD GPU OC (but powerstate scaling/VERY HIGH BUS FREQS)
2GHz Max OC
NO Bull**** and unnecessary governors (just tweaked OnDemand, Interactive, and InteractiveX for better battery life (sleep state))
TinyRCU
Compiled with daily built Yuxon toolchain and various optimizations
Cleaner CAF3.4 wakelock/power code
CAF Block and FS Drivers
CAF Scheduler Code (fairsched, etc)
Tweaked Voltages (WiFi voltages even)
Increased Potential Bus Throughput at higher clockstates
CodeAuroraForum GPU/Video drivers (opposed to HTC (the update for AOSP net most a 15-20% gain))
Larger PMEM allocations
CodeAuroraForum updated headers/drivers such as memcopy/kgsl/msm_rotator
CodeAuroraForum FS/Block/MMC/IO Scheduler Drivers/Headers
Other CodeAuroraForum Display Header Tweaks
CodeAuroraForum VMAlloc
CodeAuroraForum IRQ
CodeAuroraForum Thermal Drivers
CodeAuroraForum Genlock Tweaks
TONS MORE that you can see on git (if you can make sense of it...)
UNIVERSAL across AOSP/Sense!
DISCLAIMER: I AM NOT RESPONSIBLE FOR PHONES ON FIRE, BLACK EYES, FINDING YOUR PHONE IN ORIFICES SURPRISINGLY, FRIED PHONES, YOUR CAT DYING, OR YOUR KID DOING A LINE OF BATH SALTS AND EATING YOUR FACE
Thanks and Credits:
IOMonster
KozmikKick
Faux123
MDeejay
ShowP1984
Cayniarb
Kali-
CodeAuroraForum
Bhanvidia
DeamonFish
MrSchapps
Kraizk
ALL Team Codefire members
Google
KushDeck
Aus_azn
BananaCakes
Contactwajeeh
Rafyvitto
dumpsta
cruzin_cruzin
zacgoesrawr
78Cortina
daspazz
jenkem110
Guide/Troubleshooting:
IF you run into video/music issues, your ROM is using too old of libs. Bug your ROM dev to update to latest CodeAuroraForum libs.
Before any issue will be diagnosed, Please wipe dalvik cache, and disable any app that sets scheduler or cpu frequencies.
Run Ondemand up to 1.8ghz. Above 1.8ghz scaling may make it unstable
If your device is limited at a higher clock, then it cannot handle the voltage required and the regulator is reporting an unstable voltage. THIS IS GOOD.
TO RUN 2GHZ FOR BENCHES, RUN PERFORMANCE GOV FOR BENCHES
Changelog
Look on Git until I re-do changelogs (were accidentally lost, and I just started over but got it all back up to speed (and them some) quickly.
Like my work? Feel free to buy me a beer for early morning dev HERE
Download Here!
ChangeLog From SR2.0 Forward
I fell asleep last night my badd
Sent from my team codefire HTC Holiday using XDA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extremely nice!
ENvisiNKeD said:
View attachment 1113640
Extremely nice!
Click to expand...
Click to collapse
Nice! I will be maintaining the rootz thread mostly, but will try and get to this thread also (won't change OP or Title here at all). I'm slowly but surely switching to Qualcomm CodeAuroraForum drivers while maintaining sense compatibility for cleaner, faster code. The test kernels will also be posted in that thread. Thank you.
Edit: If you set 2.05ghz, but your phone doesn't run up to 2.05ghz, it means that your phone can't handle the voltages on one or both cores. The performance improvement is nominal nonetheless.
Updated to A11. HUGE changes. Basically quite close to a CM kernel...but functional on htc roms. Big IO increases, and a TON of driver/header changes also. Just look at git to check it out (anything that says update, means update to CodeAuroraForum AOSP variant): https://github.com/TeamCodefire/KangBanged-Kernel/commits/master
Do I have to reflash a rom after? Because I dont really want to do that. If I HAVE to i will. Thanks
VDubGli said:
Do I have to reflash a rom after? Because I dont really want to do that. If I HAVE to i will. Thanks
Click to expand...
Click to collapse
If you're s-off, just flaash the zip and reboot. If you're s-on, you can flash the zip by following the instructions I detail in this post: http://rootzwiki.com/topic/27167-kernel-3032-kangbang-kernel-a11-jun8-aospsense-universal-caf-drivers-uvoc/page__st__10#entry725337
great job!
bananacakes said:
great job!
Click to expand...
Click to collapse
Thanks man! Also, it should go without saying that in general the source is a huge Work In Progress. None of those commits are really ready to be cherry-picked yet. If nothing booting comes of it tonight, then I'll fix the voltage spam, and tinyrcu and just rebase/cherry-pick it into a new branch and have a WIP branch for the CAF rebasing.
You had me at spam.
Good work man.
Sent from an HTC Vivid via XDA Premium
Jirv311 said:
You had me at spam.
Good work man.
Sent from an HTC Vivid via XDA Premium
Click to expand...
Click to collapse
A11has some stability issues in sleep. Edit: A12 now up
Edit: A quick note: I will never include insane gpu OC, due to GPU OC doing very little in benchmarks. On a good kernel, there is no usability increase for our devices, and it barely helps in benches. Been asked a few times for insane gpu oc's, and for now the answer is no.
Sent from my Desire HD using XDA Premium HD app
bananacakes said:
great job!
Click to expand...
Click to collapse
Hey bro could you be awesome and update th libs that is talking about on the list of the new A12 "IF you run into video/music issues, your ROM is using too old of libs. Bug your ROM dev to update to latest CodeAuroraForum libs." so i can use this awesome kernel.. i just wanna test the 2Ghz for a while
chachin said:
Hey bro could you be awesome and update th libs that is talking about on the list of the new A12 "IF you run into video/music issues, your ROM is using too old of libs. Bug your ROM dev to update to latest CodeAuroraForum libs." so i can use this awesome kernel.. i just wanna test the 2Ghz for a while
Click to expand...
Click to collapse
I'll just have a separate zip soon. I could include in kernel zip, but I only want kernel to be flashed alone, and don't like the idea of a kernel modifying rom at all like another kernel on this forum does. Would prefer HTC rom cookers to just be diligent.
Sent from my Desire HD using XDA Premium HD app
I love the fact the vivid can reach theoretical speed of up to 2ghz now, but I don't know of what application besides a benchmark app, game emulator or a heavy 3d game that it would be useful for. Battery gets eaten horribly but I like the concept a lot. May come in handy soon....
Running a test using a fully charged 1800 mah battery, don't think shadowgun can get any smoother than this. Will be following.
Working on a potential backtrack linux port in its infancy, hey it had to be done, this kernel just might be for what I'm looking for.
Sent from my HTC PH39100 using xda premium
8125Omnimax said:
I love the fact the vivid can reach theoretical speed of up to 2ghz now, but I don't know of what application besides a benchmark app, game emulator or a heavy 3d game that it would be useful for. Battery gets eaten horribly but I like the concept a lot. May come in handy soon....
Running a test using a fully charged 1800 mah battery, don't think shadowgun can get any smoother than this. Will be following.
Working on a potential backtrack linux port in its infancy, hey it had to be done, this kernel just might be for what I'm looking for.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
PM me, I've been working on porting debian. There's better kernel source for it.
Edit: or join #htc-holiday on irc and ping me or my cloud accuont if I'm not on.
Edit2: it would seem the vivid should be capable of 2.5GHz theoretically.
synergye said:
PM me, I've been working on porting debian. There's better kernel source for it.
Edit: or join #htc-holiday on irc and ping me or my cloud accuont if I'm not on.
Edit2: it would seem the vivid should be capable of 2.5GHz theoretically.
Click to expand...
Click to collapse
Will do, don't think the vivids pipes can sustain 2.5 GHz without complete thermal meltdown. What I'm looking for is a governor that behaves like Intel's c1 CPU state, not a gradual declination of cpu speeds, something that works like on demand, but increases only between four to five different speeds at the most stable known voltages. Even a toaster can run linux, but the CPU doesn't have to be at 2ghz all the time, only for those "special" calculations.
Sent from my HTC PH39100 using xda premium
8125Omnimax said:
Will do, don't think the vivids pipes can sustain 2.5 GHz without complete thermal meltdown. What I'm looking for is a governor that behaves like Intel's c1 CPU state, not a gradual declination of cpu speeds, something that works like on demand, but increases only between four to five different speeds at the most stable known voltages. Even a toaster can run linux, but the CPU doesn't have to be at 2ghz all the time, only for those "special" calculations.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Believe me I understand that, and it's quite easy to set up something like that with interactive, or even by modifying ondemand. The issue is heat throttling with 2GHz stable.
In any case,
New Beta1-Test1 uploaded from totally re-doing kernel from closer to the beginning(rebased and cherry-picked from my own repo). There were just too many issues I'd run into on sense, and I knew what really affected performance positively I wanted to keep. Left a lot of the driver changes (not base changes) out for now until I can do proper testing. At this point I'm close to 50 hours no sleep, so just leaving the kernels up. I'll be doing a gitlog off the master branch, and separating for the build changelogs. Look at git (new default branch) if you really want to see what all's been done, or look at master to get a sense of what was done recently for A14
I was able to finally able to clean it up enough to use the linaro 4.7 o3 flag
AR15 uploaded (changed naming scheme from Alpha to Alpha Release). More stable than beta1-test1, lots of issues from A14 and earlier fixed in this re-tooling. Fast charge added back *properly* this time. PLEASE wipe dalvik cache after flash for good battery life. Battery usage should be the same as dumpsta's screenshot in this release.
Enjoy!
Edit: okay, this one only works on rom ports also. Goddammit HTC, learn to ****ing standardize your compilations a bit!
There as to be a way to get xz compression to work. EVO was stock gzip just like vivid I believe. Xz also works on sensation which is stock gzip. Ive been trying to wrap my head around it.
I can compile with -O3 but the zimage is to big :/ turning everything possible into modules first help on size either sadly.
Sent from my HTC One X using xda premium
kozmikkick said:
There as to be a way to get xz compression to work. EVO was stock gzip just like vivid I believe. Xz also works on sensation which is stock gzip. Ive been trying to wrap my head around it.
I can compile with -O3 but the zimage is to big :/ turning everything possible into modules first help on size either sadly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well, I decided to drop support for any holiday based rom. No reason not to use coredroid port, virtuous, or another rom base from another device. HTC ****ed us and we can't use new adreno libs, ksm, new video/media/gpu kernel drivers or xz compression on this base.
I don't want to let a ****ty rom base slow down kernel development.
KANGERANG
Click to expand...
Click to collapse
INTRO:
This kernel is a kernel based off of Franco's kernel with patches from various other sources, such as faux123, motley, Code Aurora Forums, Linaro, and others, to add features, stability, and optimization to the kernel.
Click to expand...
Click to collapse
FEATURES:
Hotplug control (franco)
fsync toggle (franco)
vibration control (franco)
headphone control (franco)
logging toggle (franco)
franco's gamma control options (franco)
per-app power modes (with franco's app) (franco)
dynamic kernel governor settings (franco)
cpu voltage control (franco)
sweep2wake (showp1984 + faux123)
"simple" GPU governor (faux123)
GPU overclock to 600mhz (exp version only) (faux123)
fauxSound compatability (faux123)
speaker amp control (faux123)
Android scheduler enhancements (faux123)
ZRAM enhancements/fixes (faux123)
USB fast charge support (motley)
Codel Net Scheduler (anarkia1976)
MSM OTG support with external power (exp version only) (ziddey)
few extra MB of RAM from logger (dorimanx)
wireless driver enhancements/fixes (CAF)
topolgy drivers updated to linaro (linaro)
various board updates (CAF)
max readahead pushed to 512
warning fixes (LaboDJ)
default TCP congestion algorithm is Westwood
default I/O scheduler is ROW
default CPU scheduler is interactive
numerous linaro patches (linaro)
GCC 4.8.2 (SaberMOD)
patched to Linux 3.4.51
numerous further optimizations from CAF/Linaro
Click to expand...
Click to collapse
DOWNLOADS HERE
Normal version contains the features above
Exp version contains features above + MSM OTG with external power and GPU OC to 600mhz support
Click to expand...
Click to collapse
Note: The majority of the code in this project is not by me, nor am I claiming to be by me. I'm just a high school kid who slapped this kernel together for myself and people have prodded for me to release it.
Click to expand...
Click to collapse
DONATIONS:
I will not be accepting donations of any kind for this kernel. Seriously, don't. I didn't write the majority of this kernel's features. All I did was compile it into one single, streamlined kernel. Instead, donate your money to the people given credit above. I don't need your money (I'm in high school) and I don't want it either
Show your appreciation by hitting the thanks button and/or following me on twitter @rohanXm
Click to expand...
Click to collapse
FAQ:
Will you add ___________ feature from ___________ kernel?
Ask nicely in the thread if it has not already been asked for and I'll determine what to do from there.
Kanging is bad, you butt!
Don't use this kernel if you don't want to. All credit both here and on github was given to their respective authors, and I don't claim to be making this kernel for my benefit.
OMG HALP my WiFi keeps dropping zomg why???
Attach a logcat of it entering deep sleep and dropping a connection.
My phone is bootlooping, WTF man?
Flash the reset kernel before flashing this kernel, because some kernels use non-standard ramdisks which are incompatible bigtime with this kernel.
How do I control this kernel?
Franco's kernel control application has 100% compatibility with this kernel, as this kernel is based off his kernel. Faux's kernel control application has approximately 70% compatibility or so, as things such as intellidemand-specific parameters (Snake Charmer, Eco Mode, etc) are not yet available. Also, although color control works, gamma control does not work in faux's app. I've heard that TricksterMOD provides a good balance of tweaks available and that most things can be controlled from that app, but I have not tried it myself.
Click to expand...
Click to collapse
THANKS:
-franciscofranco for the base
-faux123 for his numerous kernel features/patches
-LaboDJ for the supercharged base
-bhanvadia for his patches
-motely for his patches
-SaberMOD for their optimization-related commits
-showp1984 for his sweep2wake commits
-dorimanx for his patch
-CAF/Qualcomm for their dedication to the open source community
-Google for being awesome
Click to expand...
Click to collapse
SOURCE is available HERE
Click to expand...
Click to collapse
...
reserved for science! and for future information
For science son
---------- Post added at 04:06 PM ---------- Previous post was at 03:48 PM ----------
*jumps around in slow motion*
KANG A RANG
Hey just coming from the HTC One Xl... just wondering if this has aznrices mods.. I really liked how it sounded and honestly it's just better then other mods.. thanks pls
Thank you. Will flash.
Sent from my Nexus 4 using xda premium
Awesome! Do the WiFi fixes include delayed notifications fix?
Sent from my Nexus 4 using Tapatalk 4 Beta
I'm not sure but I can testify to getting all my notifications on time. Gmail is faster on my phone then my computer..
Sent from my Nexus 4 using Tapatalk 4 Beta
@rohan32 Thanks for the great kernel dude! It's got all of the features I look for
Do you know if this kernel includes Franco's version of the Simple GPU governor (I'm not even sure if he's released this yet), or the plain Faux version?
Thank you very much for taking the time to do this!
Connor Baker
Connor Baker said:
@rohan32 Thanks for the great kernel dude! It's got all of the features I look for
Do you know if this kernel includes Franco's version of the Simple GPU governor (I'm not even sure if he's released this yet), or the plain Faux version?
Thank you very much for taking the time to do this!
Connor Baker
Click to expand...
Click to collapse
Yeah it has Franco's changes to the governor in it as well
ooooh a new kernel, better flash fast!
You came all the way to the nexus 4 to be with me and chongo? How thoughtful!
Sent from my Nexus 4
Nice kernel. Running very good so far.
But a general question after having flashed hundreds of kernels in my life:
How can it be that different based kernels are running better or worse? To be precise, for me all kernels based on faux's are running bad. Choppy animations and lag...Based on franco they run so well for me...I don't get it!
Hello sir, can i ask what version of Franco's kernel this is based off?
..sent from space
Does this kernel work on miui roms?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thing screams
It's beautiful T_T ;D
The improvements are what franco's missing! Awesome work so far! Keep it up!
Are you pulling all commits from franco's kernel to keep yours up to date?
Stylez Ray. said:
How can it be that different based kernels are running better or worse? To be precise, for me all kernels based on faux's are running bad. Choppy animations and lag
Click to expand...
Click to collapse
I hardly think you should criticise someone's hard work. Frankly both are great developers and both make my phone fly. Its only a matter of personal opinion.
Will test and report this kernel soon. Seems pretty hardcore.
Sent from my Nexus 4 using xda app-developers app
running it on Atom...great kernel so far....missing some colour profiles but hey that i can input on my own..many thanks for this kernel...nice to have a choice
TheDarkLord1997 said:
I hardly think you should criticise someone's hard work. Frankly both are great developers and both make my phone fly. Its only a matter of personal opinion.
Will test and report this kernel soon. Seems pretty hardcore.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No no no, I dind't criticise! There's no best developer, I won't argue.
I just always wondered why the kernel mackes so much differene in terms of user experience. For me all I can say is faux just doesn't work right nd franco flies!
amarb70 said:
Hello sir, can i ask what version of Franco's kernel this is based off?
..sent from space
Click to expand...
Click to collapse
Its based on the latest commits from franco, and at the time of the post, that is Milestone 3.
mert2go said:
Does this kernel work on miui roms?
Click to expand...
Click to collapse
It should as the installer only injects the zImage of the kernel, but the ramdisk stays the same. I haven't tried it, however.
Limit8 said:
It's beautiful T_T ;D
The improvements are what franco's missing! Awesome work so far! Keep it up!
Are you pulling all commits from franco's kernel to keep yours up to date?
Click to expand...
Click to collapse
Yes, I am!
Stylez Ray. said:
No no no, I dind't criticise! There's no best developer, I won't argue.
I just always wondered why the kernel mackes so much differene in terms of user experience. For me all I can say is faux just doesn't work right nd franco flies!
Click to expand...
Click to collapse
Really can depend on any number of things, like each phone's hardware is different, and the fact that there are many different commits that constitute each kernel. Your phone may react differently to various commits than other people's devices.
Ate too much KitKat?
Download: here
Mirror: here (DontPushButtons tries to mirror as soon as new versions are released. Please remember to thank him)
F2FS help: this post/page
- features my own governor 'preservative' with 702MHz touch/GPU activity boost for responsive UI and smooth scrolling
- in kernel hotplugging (thanks to myfluxi)
- debug stuff disabled
- various safe optimisations
- built on the latest 4.4.3 source (no new source was released for 4.4.4)
- offers reduced heat and better better performance through my original bus speed mod: higher bus speeds at lower CPU speeds allows max FPS at lower CPU speeds, and keeping the CPU speed low is the best way to save power. UV is not the way! (Established 'wisdom' debunked here)
- includes kexec-hardboot patch for multiROM thanks Tasssadar
- includes Fast Charge, Gamma, and Audio-gain mods
- support for F2FS and multirom
User Reviews
- This is the only one you'll need: here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Objectives
- a high standard of performance
- as power saving as possible, but not compromising the first point
- keeping it simple
- remaining stock-like as much as possible for stability, but I'll add features if I personally want them!
Caveats - Flashing this will void your warranty, and may cause you to grow hairy man boobs, and this is the last thing anyone needs (ladies doubly so). I'm not a developer a such. I can just about program well enough in C to be able to understand what I'm doing. I've taken code from other sources and merged it in. Credit goes to mrg666, myfluxi, morfic, faux123, franciscofranco, hellsgod, ak, stratosk, and of course the hundreds of developers of the linux and android kernel source. I'm so lazy with git that often my commit history gets re-written and the original source of my cherry-picks gets lost. If this is an issue please pm me and I'll try to fix it, otherwise let me be lazy.
I think you should add... - Although I'm happy to hear suggestions, before you start you should be prepared to hear a 'no'. This is a personal project that I'm just sharing.
Source: https://github.com/bedalus/nexus4
Linaro Toolchain: [url="http://forum.xda-developers.com/showthread.php?t=2098133]click here[/url] thread by @Christopher83 (a15 4.9.x version) Thanks for the awesome work!
bedalus said:
A simple OP for simple KitKat kernel featuring nearly nothing.
http://d-h.st/LAP
- intellidemand governor with 192MHz min freq and 702MHz optimal freq
- useless frequencies disabled
- 2 core minimum when screen is on
- in kernel hotplugging
- debug stuff disabled
- various safe optimisations (take a look at the rather short commit history on github)
The Goal - to make the minimum changes to the stock source required to make a smooth experience that doesn't bake your hands.
Caveats - Flashing this will void your warranty, and may cause you to grow hairy man boobs. I'm not a developer a such. I can just about program well enough in C to be able to understand what I'm doing. I've taken code from other sources and merged it in. Credit goes to morfic, faux123, franciscofranco, hellsgod, stratosk, and of course the hundreds of developers of the linux and android kernel source. I'm so lazy with git that often my commit history gets re-written and the original source of my cherry-picks gets lost. If this is an issue please pm me and I'll try to fix it, otherwise let me be lazy.
Why's this in general? - because I'm not really developing anything. This kernel is more like my personal preference for how a kernel should be configured. I reserve the right to change my mind about what I want. I also reserve the right not to change anything for months on end.
I think you should add... - Although I'm happy to hear suggestions, before you start you should be prepared to hear a 'no'. This is a personal project that I'm just sharing.
There are lots of other fast moving and exciting kernels out there. I want this one to be more like a Daiquiri at the beach. Lazy, slow and probably asleep.
Source: https://github.com/bedalus/nexus4
Linaro Toolchain: [url="http://forum.xda-developers.com/showthread.php?t=2098133]click here[/url] thread by @Christopher83 (I always grab the latest 4.7.x arm-unknown version) Thanks for the awesome work!
Click to expand...
Click to collapse
Wow you're here too? I will try this kernel now!!
TO DO: 2 core minimum
Subscribed. Glad to see a thread for your kernel, its always nice to see a development growing good luck with furthure goals too bad you didnt left marmite as a name, it was so popular in nexus s days.
Sent from Pure Nexus⁴
Yes, a new joke name for a new era of ineptitude! Good to see you as always
Omg bedalus you are here too! Missing the Nexus S days man hahah
Sent from my Nexus 4 using Tapatalk
There's no way I'm running all those benchmarks and power drain tests again! My nexus s is still going strong in the hands of my wife
bedalus said:
There's no way I'm running all those benchmarks and power drain tests again! My nexus s is still going strong in the hands of my wife
Click to expand...
Click to collapse
Haha, nowdays its not all about numbers, its about user experience. just a two questions, do you plan to add min 1 core online and abillity to UV?
Sent from Pure Nexus⁴
Glad to see you here dude
Sent from my Nexus⁴
Wow, someone was quick off the mark. I see a download before I even finished updating the OP.
Anyway....
OP UPDATED!
- two core minimum fixed.
alen1901 said:
Haha, nowdays its not all about numbers, its about user experience. just a two questions, do you plan to add min 1 core online and abillity to UV?
Sent from Pure Nexus⁴
Click to expand...
Click to collapse
Nope to one core. See the updated op for more info.
UV is a big no-no in my eyes. Remember in the nexus s section I did those battery drain measurements? I didn't find any benefit to it, and it can make your device unstable. It's just not worth it
Nice to see you
always loved your marmite kernel on my nexus s... will try this out as soon as i can
one question: is custom colors included in this kernel?
thanks
@bedalus glad to see you here man! Loved your work on my Nexus S and now on the Nexus 4 too
qaz2453 said:
Nice to see you
always loved your marmite kernel on my nexus s... will try this out as soon as i can
one question: is custom colors included in this kernel?
thanks
Click to expand...
Click to collapse
I may have a little mess around with the colours. They look okay to me since kitkat dropped. But while I'm on the subject I think that stratosk had decent colours as default... unless I'm imagining it? Can anyone confirm?
bedalus said:
I may have a little mess around with the colours. They look okay to me since kitkat dropped. But while I'm on the subject I think that stratosk had decent colours as default... unless I'm imagining it? Can anyone confirm?
Click to expand...
Click to collapse
Yeah stock colors (which I believe is what stratosk uses) is decent enough. It's definitely way better than when the Nexus 4 was first released.
In that case I think I'll leave it for now. I'm not looking to blaze through commits like the old days
kernel update, see OP
I've begun the process of merging in the mainline commits, but I'm only merging in patches that apply cleanly, and only if they affect code that's actually being built. There's no point cluttering my git repo with commits for code that isn't going to be built in my kernel! I automated the process a little with a fun script. If you're interested take a look at the head commit in my github/maKKo_02
It took me most of the day today to get from v3.4.0 to v3.4.14 so it'll be quite a long time before I get to v3.4.70 but I'll upload a new version every 10 sets or so...
Here's another one: http://d-h.st/6Kp
I can't stick it in the OP right now because I'm using tapatalk and editing is a pain.
I've merged up to 3.4.16 and taken the hellscore zip as a base to ensure the low fq of 192 is available on first boot.
Edit: I forgot to mention that I switched to xz compression so it's reduced the zip size somewhat
Also, does anyone play sword & sorcery? Is it normal for the back to get so hot on this game?
bedalus said:
Here's another one: http://d-h.st/6Kp
I can't stick it in the OP right now because I'm using tapatalk and editing is a pain.
I've merged up to 3.4.16 and taken the hellscore zip as a base to ensure the low fq of 192 is available on first boot.
Edit: I forgot to mention that I switched to xz compression so it's reduced the zip size somewhat
Also, does anyone play sword & sorcery? Is it normal for the back to get so hot on this game?
Click to expand...
Click to collapse
Im glad u are here! A couple months ago i asked if u would do a n4 kernel, the awnser was negative... But u finally did it!
Anyway, most games heat up quite a lot the back of the phone, mainly those who require internet connection and/or GPS at the same time
(Doubletaptowake? U think its usefull enough to be added?)
sent from my NEXUS 4 tasting KitKat for the first time
So... could we say this should be the best kernel for battery life for 4.4?
Thanks a lot!! This is what I was waiting for!!