Database Develop

[PRJ] The Manhattan Project - 1.6GHz - Shelved/Succeeded by Core

http://board.teamwhiskey.com/viewtopic.php?f=3&t=53&start=0
Project is simple in design and is a work in progress, overclock as far as we can go with ample supplied voltage for maximum stability. These are the screenshots taken last night from the last few builds of the evening, were up to something like 40 builds so far trying to get everything just the way we want it to run, look, and feel.
Currently we are overclocking both the GPU and CPU using both base frequency modifiers and multipliers. This is allowing us to directly push the GPU to its stable limit while adjusting out the CPU accordingly.
Project Developers
Morfic and Viralblack of Team Whiskey. This is and will continue to be Morfic's baby until the phone prints money and/or can transform into a jet.
The Short and Long term goals are the following:
-To optimize the kernel with the best toolchains available to us
-Inject vital code enhancements for stability and to extend the feature set of the SGS Vibrant line
-To determine Min/Max Voltage, Bus Clock, and Multiplier values for Maximum Overclock and Maximum Effecient Overclock
-Continue to push the GPU to its theoretical maximum independant of CPU clock values.
Target Numbers and Current Results.
CPU Target 2.0GHz, Current Maximum Overclock 1.6 Stable (Time limitation only, havent rebuilt to try more)
GPU Target 85 FPS Stable Bench, Current 78 FPS
At current this is a JFD Stable build thats more than fairly bulletproof on battery life. To use with JI6 builds just flash Eugene's JFD/JI6 support package.
{
"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 is NOT a hoax or scam, these are real DDMS screenshots from the build currently in progress, as it has not yet been released we do not have code or kernels available until we know its running smoothly. The following zImage is a prerelease alpha. Its strictly for proof of concept. This kernel is mildly optimized and includes the CPU and GPU overclocks. In three of three test phones the CPU was stable, in two of three phones the GPU was stable. One test phone was not able to complete neocore under this coding.
Battery life has proven about the same as traditional OC/UV kernels. This is NOT our finished product, this is an Alpha for proof of concept for other developers. Run at your own risk. There is no failsafe, this does not require SetCPU to engage. It comes out of the box at 1.6GHz with steppings of 1,2,4,8,16
Currently, tested incorporations with the zMod have shown that overclocking renders the zMod unstable and bricks the device. I personally preferred to use RyanZAs OCLF v2.2 APK.
I had one out of 20 quadrant runs fail because I switched scheduler away from deadline. CFQ proved to be less stable for one reason or another when running quadrant.
This thread will be updated as work progresses, Do not flash this if you do not know what youre doing. Suggestions are welcome for integrated features you would like to see in this kernel, we will not however be fielding bug reports as this right now is staged as a Prerelease Alpha or RC0.
If when this is flashed your phone crashes and is unable to work, my suggestion is odin the stock kernel back in place and wait for a lighter overclock version to be released.
Download -
Removed while core is being rewritten
EDIT 10/28:
To update the project and to iterate why the download link was removed, the kernel seems to be misbehaving and we havent yet nailed down the correction as of yet.
As many people pointed out once it was released, the kernel seems to slow down 3D graphics. With this information and taking a day to go through all the options and data available to me, we discovered this issue isnt limited to just 3D graphics.
Imagine if you were running at 10MPH, and while you were running time slowed down but the slowdown didnt effect you. So youre still running at 10MPH but to the rest of the slowed down world, now youre running at 15MPH, even though your speed and direction havent changed.
The changes in the code for one reason or another arent playing nice with the Android system. Instead of pushing the clock up, in most cases, what its doing is simply slowing the internal clock down to the tune of about 30%. This is what is actually providing the benchmark gains that were being recorded, not an actual gain. This doesnt mean that the project is dead, we are recompiling to get a stable overclock with the new configurations. This doesnt mean the project was a failure, it just means we need to rewrite the alpha.
Edit 10/30 -
So, we are having distinct issues removing the timing error from the kernel while maintaining the integrity of the time system. So, being that the timing is much more important, we began rewriting it all from scratch. This is currently marked as Project Core in the same forums. Core is taking the best of the overclocking and fine tuning that this kernel has and combining it with energy effeciency and stability a daily driver phone needs.
So, we will be balencing the high end power thats desired and the low power use that is needed in this new project. With that being said, I dont believe that 1.6GHz (in my own humble opinion) is even remotely necessary for 99 percent of phone, let alone for daily use. This project is being succeeded by Core to make a power friendly daily driver kernel.
The kernel will still be available from the forums Alpha/Beta Download Section, but will not be supported as its being replaced by Core.
We found the redline Now we need to find the happy medium. If you enjoyed this release, youll love Core and Core with zMod.
Thread Locked until release, OP PM me when you want to release it

Good work TW
You guys should start working on a 2.2 version (Once you get this one smooth)

Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....

n2ishun said:
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
Click to expand...
Click to collapse
My phone never gets hot?
But they did put a warning, and you are the one modding your device.

Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?

Eazail70x7 said:
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Click to expand...
Click to collapse
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.

Master™ said:
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Click to expand...
Click to collapse
Yeah, mine will get warm, but I've never seen it get real hot.

testing now . just flash with clockwork? this is super cool guys. props

blackerwater said:
testing now . just flash with clockwork?
Click to expand...
Click to collapse
Yes, its CWM flashable, but be careful with it. There is no failsafe, if your phone cant handle the overclock itll just crash as its set automatically to 1.6GHz topend

So far so good. Just got a linpack of 12.062. Outstanding job guys!

doesn't work yet. just sits on vibrant screen. its cool ill just flash back ji6 zimage then it should boot. im on stock ji6..... I have a vibrant that can handle 1.3mhz for sure and voodo so ill keep playing with it.

Will this run with stock ji6?

Thank you so much for uploading! I reread about it in phandroid and was about to ask around for it
Sent from my SGH-T959 using XDA App

I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?

blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
Right now ive only tested it on Fusion personally

Viralblack said:
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Click to expand...
Click to collapse
Excellent. I hope you guys can get an Epic soon and work some magic. Also good to hear thatyou'll be working with other devs. Good luck

blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.

Have you tried flashing the back kernel support file for JI6 then flash this kernel?

Whitehawkx said:
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Click to expand...
Click to collapse
ok ill give that a shot. thanks

Will this work with voodoo?
Bionix Fusion 1.0 Jacs Xmod Oc/Uv Kernel Color fix Voodoo

[Kernel][AOSP] Tiamat 4.1.0 | 2.6.38.8 | 10/12/2011

​
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

[JB]Result of Benchmark Comparison with different ROM&Kernels

this is my first thread in xda. sorry if i break any rules. and plz tell me if i did.
============================================================
Hello committee! I just registered here a few days ago and find it a really nice place. i found a lot of useful infos and learned skills here. enjoyed every second reading the posts.
i just spend the afternoon testing with some different kernels and ROMs. trying to figure out which one should i choose for daily use. i know it would be a long term testing to get a conclusion but this is a start anyway.
i'm posting my result here hoping could do a little contribution to this committee. and PLEASE share your ideas with me too!
============================================================
I used the app AnTuTu Benchmark on my Nexus S. dunno if it's the best benchmarking app but i think as long as i keep all the other settings the same. the result still tells some truth.
The results below ONLY show the performance of roms and kernels at BENCHMARKING. it does NOT say anything about battery life, usability or stability.
View attachment 1265857
=======================UPDATE===============================
AOKP seems not working properly with AirKernel. trying to figure out why. anyone can help?
*Air186B65f = AirKernel #186 BlueColor with 65fps
*Air186V = AirKernel #186 VoodooColor without 65fps
(both the above are High-BigMem versions.)
*marOTA4.2= marmiteKernel v4.2 for stockOTA ROM
*mar4.2 = marmiteKernel v4.2 for Custom ROMs
*bfq is not currently available on marmiteKernel v4.2 so i only tested deadline. dunno if it's a proper choice.
*Adroxd = Androxide 3.1.0
*NotPass = benchmarking was interrupted by force close of the app.
some conclusions:
1. ROOT does NOT affect the performance on stock ROMs.
2. performance does NOT do better at benchmarking, as it's supposed to, than some other governers.
3. NotPass does NOT happen every time with the same settings. i.e. i tested 2 times at 1.4GHz with smartassV2 and bfq on stock ROM. the first time it gave an result of 4090. but the 2nd time it force closed.
4. schedulers seem to be not affecting benchmarks on a big scale.
5. The result shows stock ROM with custom kernels DOES better performance than custom ROMs. (I like things to be stock. it makes me feel safe. But at the same time i prefer those mods in custom ROMs like the volume rocker wake-up and advanced power menus.)
6. I love xda-developers.com :laugh:

New benchmark expert arrived!
Welcome!
Edit: aha...not in-progress like bedalus:/
Sent from my Nexus S using xda app-developers app

Since you are new to this let me say something that most users are unaware of: the governor is absolutely irrelephant. The CPU will always be at 100%, otherwise it's not a true benchmark, thus rendering the delay to reach such % (basically what a governor does) a parasite variable.
The I/O scheduler performance is also tricky to measure as some are better in sequential operations, some are not.
So if you want to test ROMs & kernels (which makes much more sense, not I/O schedulers and governors), then here are a few tips:
More ROMs (make sure to include CM as it has many small code optimizations).
More kernels.
Drop the governor column and do everything in performance (this will force the max CPU frequency and eliminate the aforementioned parasite variable).
Choose one I/O scheduler and use it for every kernel (homogeneity).
Don't do OC.
Use more benchmarks (CF-Bench, Sunspider, GLBenchmark).
Run at least 3 times and note down the average result.

ioplkj13 said:
New benchmark expert arrived!
Welcome!
Edit: aha...not in-progress like bedalus:/
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
LOL no i'm not a benchmark expert, yet. ;D but thanks for the advise. i think in-progress makes ppl excited and helps me to do the work better. just like knzo's post!
knzo said:
Since you are new to this let me say something that most users are unaware of: the governor is absolutely irrelephant. The CPU will always be at 100%, otherwise it's not a true benchmark, thus rendering the delay to reach such % (basically what a governor does) a parasite variable.
The I/O scheduler performance is also tricky to measure as some are better in sequential operations, some are not.
So if you want to test ROMs & kernels (which makes much more sense, not I/O schedulers and governors), then here are a few tips:
More ROMs (make sure to include CM as it has many small code optimizations).
More kernels.
Drop the governor column and do everything in performance (this will force the max CPU frequency and eliminate the aforementioned parasite variable).
Choose one I/O scheduler and use it for every kernel (homogeneity).
Don't do OC.
Use more benchmarks (CF-Bench, Sunspider, GLBenchmark).
Run at least 3 times and note down the average result.
Click to expand...
Click to collapse
these are very helpful! i'll take the advise and make my test better.
but i don't think i'll do A LOT ROMs and kernels. since i'm just testing those ROMs and kernels which i might be using for daily. but i WELCOME all other guys here to post their results! :fingers-crossed:
again, many thanks to your help!

So the best rom+kernel is the stock+air kernel?

We need more numbers. A benchmark thread with nearly only conclusions is just asking people to believe you without any proof. Not gonna happen in a place full of skeptics.
Knzo suggestions are very good too. You need more homogeneity in your benchmarks. Being all over the place only adds variables in the equation that favor one kernel or the other. And more tests. Pretty much just follow all what he said.
knzo said:
Since you are new to this let me say something that most users are unaware of: the governor is absolutely irrelephant
Click to expand...
Click to collapse
{
"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"
}
Irrelevant*

polobunny said:
Irrelevant*
Click to expand...
Click to collapse
You don't really think I'd write irrelephant unintentionally right? I'm meme-aware! ;p

knzo said:
You don't really think I'd write irrelephant unintentionally right? I'm meme-aware! ;p
Click to expand...
Click to collapse
Haha! You got me there. I kinda knew of your meme ways, but that was some good trolling right there.

•Run at least 3 times and note down the average result.
Click to expand...
Click to collapse
Try to make the conditions the same for each run. For example, restart the phone and leave idle for 3 minutes, etc.

Andrew1998 said:
So the best rom+kernel is the stock+air kernel?
Click to expand...
Click to collapse
remember there's nothing called "best". as i said above the result only shows performance at benchmarking. as we know good benchmark score may result in poor battery life so it's not recommended for daily use.
if you could help this work it's much appreciated!
maybe you just do a benchmark (takes only 3 mintes) and post your rom and kernel with the score.
best wishes.

vikingsail said:
this is my first thread in xda. sorry if i break any rules. and plz tell me if i did.
Click to expand...
Click to collapse
Well since you asked nicely, you did post in the wrong section.
Thank you for the data, and there have been some good suggestions about tweaking the method.

Stock Rom.. air kernel #186..
Sent from my Nexus S

siddhesh.raikar said:
View attachment 1267462
Stock Rom.. air kernel #186..
Sent from my Nexus S
Click to expand...
Click to collapse
that is very impressive! any tweaks?

polobunny said:
We need more numbers. A benchmark thread with nearly only conclusions is just asking people to believe you without any proof. Not gonna happen in a place full of skeptics.
Knzo suggestions are very good too. You need more homogeneity in your benchmarks. Being all over the place only adds variables in the equation that favor one kernel or the other. And more tests. Pretty much just follow all what he said.
yes that's indeed what we need. i wish more ppl could take part in this.
and i'm trying to take more homogeneity into my testing. thanks for the advise!
Irrelevant*
Click to expand...
Click to collapse
sysadmn said:
Try to make the conditions the same for each run. For example, restart the phone and leave idle for 3 minutes, etc.
Click to expand...
Click to collapse
very funny...

siddhesh.raikar said:
View attachment 1267462
Stock Rom.. air kernel #186..
Sent from my Nexus S
Click to expand...
Click to collapse
Haha you over clocked to 1.4ghz. Here is mine.
Sent from my Nexus S using xda app-developers app

Good luck!

..

[APP][ROOT][BB][Bricked]KControl - Kernel control app for msm/tegra3

KControl for msm/tegra3 devices​
Requirements?
Root.
Busybox. (For doing stuff faster on the shell than in java, zcat for example and module ops)​
Playstore Link, Screenshots, Features, etc...
​
Supported devices?
Tested, by myself, on:
Nexus 5 (hammerhead)
Nexus 4 (mako)
Nexus 7 (grouper/tilapia)
Nexus 7 (flo/deb)
HTC One X (endeavoru)
HTC One S (ville)
Theoretically this app should work fully on any msm/tegra3 device using my kernels features. Tegra3 will lack thermal configuration though.
Functionality on stock kernels or custom kernels without Bricked features will be quite limited. (Everything with *1 or *2 in the feature list won't work then)​
How can I make my kernel compatible?
http://bricked.de/kcontrol_compat.php​
Where to complain about errors/bugs? (I have no doubt there will be some)
Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://github.com/showp1984/KControl/issues​
Changelogs:
http://bricked.de/kcontrol_changelogs.php​

{
"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 is a really great app. I can absolutely recommend it.
Sent from my Nexus 7 using Tapatalk 4

any mirror?
i can not use play store

mesarabi said:
any mirror?
i can not use play store
Click to expand...
Click to collapse
Nope.
Currently the only way to get it is through Google Play.

Will this app support ART? On Nexus 7 2013 Wifi it doesn't work with ART, only works with Dalvik

Steyux said:
Will this app support ART? On Nexus 7 2013 Wifi it doesn't work with ART, only works with Dalvik
Click to expand...
Click to collapse
4.4.2 I presume?
Hadn't tested with that yet, but probably only requires a rebuild with the 4.4.2 sdk. Will look into that, thank you for the report.

@show-p1984
Is it the normal behavior of the apk to be able to change frequencies of your mp decision?
I was able to mess your kernel, ak, faux... In fact all kernel running customs decision or touch boost..
My habit was from other soft like faux or trickster...
Hope I'm understandable...

sgs505 said:
@show-p1984
Is it the normal behavior of the apk to be able to change frequencies of your mp decision?
I was able to mess your kernel, ak, faux... In fact all kernel running customs decision or touch boost..
My habit was from other soft like faux or trickster...
Hope I'm understandable...
Click to expand...
Click to collapse
Not entirely. If you meant: "Is it normal that one can change the boost frequencies of bricked's mpdecision with KControl?" - yes.
I am unsure though what you mean about ak and faux.
KControl will offer you modification options for everything it detects, regardless of the kernel used. This means that KControl still features some options on 3rd party kernels other than bricked, or even on stock kernel. (on stock roughly ~50%, on any other custom kernel than bricked it's highly dependent on the features merged into it, but it won't be less than stock )

show-p1984 said:
Not entirely. If you meant: "Is it normal that one can change the boost frequencies of bricked's mpdecision with KControl?" - yes.
I am unsure though what you mean about ak and faux.
KControl will offer you modification options for everything it detects, regardless of the kernel used. This means that KControl still features some options on 3rd party kernels other than bricked, or even on stock kernel. (on stock roughly ~50%, on any other custom kernel than bricked it's highly dependent on the features merged into it, but it won't be less than stock )
Click to expand...
Click to collapse
Here is the man...
I will try being more understandable
I was able to change the normal mpdecision behavior
I mean the noob I am was looking in the frequencies tab...
There I saw was I thought were strange value... Now I know that it was the normal behavior for the frequencies not to be always in the range I select
So when I was thinking I correct them in fact I was modifying the normal behavior
For example on the screen shot
The dummy me was trying to fix touch boost... Causing bad working
Also sometimes the frequencies tab can be populated with not only touch boost but thermal decision which I was thinking them to be artifacts and needed to be set"properly" again...
I was (still but won't) able to edit intelliplug behavior... Faux mpdecision ..
Am I clear ?! Hope so

sgs505 said:
Here is the man...
I will try being more understandable
I was able to change the normal mpdecision behavior
I mean the noob I am was looking in the frequencies tab...
There I saw was I thought were strange value... Now I know that it was the normal behavior for the frequencies not to be always in the range I select
So when I was thinking I correct them in fact I was modifying the normal behavior
For example on the screen shot
The dummy me was trying to fix touch boost... Causing bad working
Also sometimes the frequencies tab can be populated with not only touch boost but thermal decision which I was thinking them to be artifacts and needed to be set"properly" again...
I was (still but won't) able to edit intelliplug behavior... Faux mpdecision ..
Am I clear ?! Hope soView attachment 2526286
Click to expand...
Click to collapse
Ah now I got you. So you wanted to know if it's normal behavior that the app shows you the real frequencies currently in effect and not the one you set. Yes, that is normal. The app always shows you the frequency range your soc is currently running on with those 8 text labels. They are meant as a monitoring option. Touchboost and thermal decisions will ofc interfere with your min/max freq for their respective durations.

show-p1984 said:
Ah now I got you. So you wanted to know if it's normal behavior that the app shows you the real frequencies currently in effect and not the one you set. Yes, that is normal. The app always shows you the frequency range your soc is currently running on with those 8 text labels. They are meant as a monitoring option. Touchboost and thermal decisions will ofc interfere with your min/max freq for their respective durations.
Click to expand...
Click to collapse
Yes... U say it more clearly
Perhaps an advice in your apk could be nice for user coming from faux clock or trickster mod...
Cause in those apk... This messing action isn't possible

Does this app have the ability to check for the latest version of the bricked kernel for the device its installed on and download it?
Sent from my Nexus 7 2013 using Tapatalk

lmulli said:
Does this app have the ability to check for the latest version of the bricked kernel for the device its installed on and download it?
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
Like faux or Franco apk...?
Nope it's up to you to take a look at bricked.de ....

sgs505 said:
Like faux or Franco apk...?
Nope it's up to you to take a look at bricked.de ....
Click to expand...
Click to collapse
For the moment. I am working on a big version 2.0 update which will make that feature list explode.

show-p1984 said:
For the moment. I am working on a big version 2.0 update which will make that feature list explode.
Click to expand...
Click to collapse
Can we tell you wishes for the new version ?

sgs505 said:
Can we tell you wishes for the new version ?
Click to expand...
Click to collapse
Sure: https://github.com/showp1984/KControl/issues?state=open
Tag it as "enhancement"

show-p1984 said:
Sure: https://github.com/showp1984/KControl/issues?state=open
Tag it as "enhancement"
Click to expand...
Click to collapse
lol now i had to understand how github works ...:silly:
hope i did it well ( not so sure ) ...

Any recomendations for a battery saving configuration?
Would like to improve battery life, undervolted allready and im not seeing any improvments...
THX

oliverano said:
Any recomendations for a battery saving configuration?
Would like to improve battery life, undervolted allready and im not seeing any improvments...
THX
Click to expand...
Click to collapse
These are the more 'simple' settings:
Mpdecision->Simple Settings: Hotplug slow / unplug fast
Mpdecision->Simple Settings: Disable input event boost
Governor: Powersave or interactive
KControl provides you with way more "in depth" options, but those values will depend highly on your usage and are best left at defaults for the average user. If you are experiment happy, try fiddling with them (and set apply on boot off). If you don't like them you can just reset them through KControl or reboot and the kernel will be back to defaults

[KERNEL] moob v43

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!!