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
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
http://goo.gl/EnELm
v5.2 Updates
-----------------
Fix video playback
Minor tweaks to ram reservations to try to help with stability
v5.1 Updates
-----------------
Voodoo Sound v6 (Thanks Supercurio!)
Ramdisk cleanup
v5.0 Updates
-----------------
Voodoo Sound v5 (Thanks Supercurio!)
Kernel version in Settings (Thanks S0niqu3!)
It includes Settings.apk in the ZIP file. It's the one S0niqu3 modified from Bionix V 1.3.1. It should be compatible with most ROMs, but it might cause problems. Make sure you back up your existing Settings.apk if you are on a different ROM. You can also just remove it from the ZIP file if you are concerned about it. I also removed the BLN settings app as there is now a version in the market.
Older Changelog
----------------------
Test 4 includes NFS/CIFS drivers, Tunneling driver, and some scheduler tweaks.
Test 3 includes voodoo color..
---- TEST2 Updates ----
OK... Think I've got the sound issue solved... at least via the speaker it sounds good without the pops. I appear to have misplaced my headphones, so I'll test that again tomorrow.
Set the voltages at 100-800 frequencies to stock. 1Ghz+ is at 1500 default, use voltage control to lower them down. As Alienz mentioned, keep the spacing reasonable. I set 1Ghz to 1350 and the OC voltages to 1400 on my phone. There is kernel code in there that is supposed to take the size of the jump into account and wait for it, but it doesn't seem to work at OC speeds... The jump from 800-1000mhz seems to work fine, even though the default is a big jump now. The reason for that is you can only specify 4 default voltages, and this seemed like the best distribution for now.
I've also backed off the scaling settings to try to help stability in general and so you can set your voltages in a nice linear pattern, not worrying about the kernel skipping some of them. I re-enabled the states drawer so you can disable some of them if you wish. I haven't noticed a lot of lag from leaving them in though. It will still scale faster than stock, but not as fast as TEST1.
---- TEST2 Updates ----
With SetCPU, don't set the max lower than 800, including under any profiles. It will likely crash.
Okay..... Same feature list as 3.6...
Based on real Vibrant source
BLN (BLN control installed in ZIP, updated version is available in the market)
OC to 1.4 available (limited to 1ghz at boot, enable with voltage control (installed) or setCPU)
Adjustable UV (Voltage control app)
Voodoo Sound v4 (requires the voodoo control app from the Market)
Voodoo Lagfix
Various speed tweaks based on the "speedmod" kernel patch
RAM hack to increase available RAM
TinyRCU
BFQ
Increased GPU cap (The screen must be turned off after boot once. Max is 65fps.)
Reduced speed stepping lag
CIFS/NFS support included in kernel (no modules needed)
Due to the way the frequency scaling works, I recommend setting voltage at 1Ghz and up to your set max to the same voltage. This helps stabilize the voltage before you start pushing the CPU too hard.
As people will ask, Samsung stock voltages:
1000000, 1275
800000, 1200
400000, 1050
200000, 950
100000, 950
Credits:
Morfic - Help with OC and GPU cap
Supercurio - Voodoo everything
Hardcore - speedmod patch for i9k kernels
Raspdeep - Configurable OC/UV
Xan - Voltage Control app
Known Issues:
1400 Mhz doesn't perform like one would think it should in benchmarks... 1360 and 1280 seem to be the sweet spots for most users.
Thank you
running Trigger 2.6
W/ dragon kernel uv/oc to 1.28
and Adw launcher ex
I'm assuming this is based off of vibrant source?
I R dumb and fail at life for not reading more carefully.
STiGLOGiC said:
I'm assuming this is based off of vibrant source?
Click to expand...
Click to collapse
Yes its in the op
It says its based off real vibrant source.
running Trigger 2.6
W/ dragon kernel uv/oc to 1.28
and Adw launcher ex
YaY ttabbal To The Rescue!!!!
Okay..... Same feature list as 3.6...
Based on real Vibrant source...in op.
Trying out now. Your awsome!!
STiGLOGiC said:
I'm assuming this is based off of vibrant source?
Click to expand...
Click to collapse
OMG...
Just like scrizz said before....
Read.. REad... REAd.... READ THE OP!!
And yes... It is based of the source!
All XDA App Users Rock Tapatalkie!!
Can anyone report whether HD video recording and playback are working? Also, does it have voodoo color?
so same feature as 3.6, is this just a stability test?
Ehh imma flash it anyway lol
running Trigger 2.6
W/ dragon kernel uv/oc to 1.28
and Adw launcher ex
I'll own that reading fail. My apologies for cluttering the thread. Again lol
Can I ask what type of boot up logo is used in this kernel? I used to be a regular user of your Dargon kernels Ttabbal, but I had to reboot my phone at the office the other day and my boss looked over and asked why, and I quote, I'm "playing dungeons and dragons at a place of business".
If its not too much trouble could you make an office friendly version of your kernel with a stock boot screen that says "Vibrant".
blinksilver said:
Can I ask about what type of boot up screen is used in this kernel? I used to a super regular user of your Dargon kernels Ttabbal, but I had to reboot my phone at the office the other day and my boss looked over and asked why and I quote I'm "playing dungeon and dragons at a place of business"
If its not too much trouble could you make an office friendly version of the your kernels with a stock boot screen that say "Vibrant".
Click to expand...
Click to collapse
Same as 3.6, dragon boot up screen
Hey the screen is bright again lol.
Running Trigger 2.6
W/ dragon kernel uv/oc to 1.28
and Adw launcher ex
Mannymal said:
Can anyone report whether HD video recording and playback are working? Also, does it have voodoo color?
Click to expand...
Click to collapse
I can confirmed that HD video and HD camcorder is working.
hmm is this suppose to be more stable when uv/oc?
I usually get instant freeze when I uv too much. And I uv 25more than usual and it havent froze yet. Will leave it till tomorrow and some more testing
this is my setting if anyone wants to try it
{
"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"
}
Edit: I lowered by 25. Will see how it holds up.
running Trigger 2.6
W/ dragon kernel uv/oc to 1.28
and Adw launcher ex
Awesome...was just going to bed when...bam
-big, huge, enormous, gigantic (you get the drift) thanks for all you do. Looking forward to seeing it move out of "test" - which means it has your full blessing and can party all night long. For now, I'll make sure I bring her back before the sun rises...
keep up the great work.
3.6 -> 5.0?
What's the difference? 3.6 seemed really good.
uurrnn said:
3.6 -> 5.0?
What's the difference? 3.6 seemed really good.
Click to expand...
Click to collapse
This is based off official kernel source.
Sent from my SGH-T959 using XDA App
uurrnn said:
3.6 -> 5.0?
What's the difference? 3.6 seemed really good.
Click to expand...
Click to collapse
there was 4.0 test1-4
hitman818 said:
This is based off official kernel source.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Oh LOL. I must've missed that. Nice. Very nice.
It's DoW if you owned a Vibrant before, Trinity is the name in its passport though.
-------------------------------------------------------------------------------------------
Files and source:
www . Der Kernel . com
-------------------------------------------------------------------------------------------
ICS:
Voodoo Sound V10 (Thanks supercurio)
Trinity Spice (based on voodoo color V1 by supercurio)
BLN (Backlight notification) (Big Thanks Neldar)
Backlight dimmer by Ezekeel
Based on Samsung git source.
Safeboot to lower clock, higher need a tool like setcpu or no-frills CPU control
New Trinity bootanimation by @rascarlo
TUN module (Tunneling/VPN support)
CIFS module (Samba support)
EXT4 tweaks
Most lean build achievable.
Not a rebooter.
JB: WIP
For CM, to use this kernel flash the CM Black Screen Fix (Thanks JackpotClavin and lurtis)
Thanks to @RyanMacG for euroskank hosting
When "Just Flash It" didn't work:
Flash rom.
Flash kernel.
Power off.
Pull battery for 2 minutes.
Put battery back
Now boot phone.
---------------------------------------------------------------------------------------
GPS woes? Try this .apk, worked wonders on GB.
Endursa shared this GL fixing link. Follow it, see 65fps on Quadrant planet like it was meant to be.
T for Trinity
UV for undervolt (you would want to uninstall setcpu like apps and just run it)
EUV represents a 880MHz top speed power savings kernel, snappy still? You Bet'cha!
144 for 1.44GHz (I will rethink this when the 10GHz phones hit the market)
-Any means it uses Koush's anykernel scripting to install trinity using the original ramdisk, making it possible to use it on m(any) roms w/o needing a special version.
(X)A new kernel just born by my slacker hands, feel free to use it, we think it's good even if it was eXperimental just moments ago. (X) comes off when we feel it's a daily driver.
maybe i need this later
Hmmm, interesting :3
I'll test it right now
edit: Freeze after playing games or using the 3d drawer
dario3040 said:
Hmmm, interesting :3
I'll test it right now
edit: Freeze after playing games or using the 3d drawer
Click to expand...
Click to collapse
Launcher Pro? Or do you mean adw's 4D?
Sent from my Nexus S
morfic said:
Launcher Pro? Or do you mean adw's 4D?
Sent from my Nexus S
Click to expand...
Click to collapse
Google's stock android 2.2/2.3 launcher.
{
"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"
}
Yea I will say this is the fastest kernel I have ever used, scored averaging 3700, best being almost 4000...Solid work morfic.
adewey234 said:
Yea I will say this is the fastest kernel I have ever used, scored averaging 3700, best being almost 4000...Solid work morfic.
Click to expand...
Click to collapse
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Sent from my Nexus S
morfic said:
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Sent from my Nexus S
Click to expand...
Click to collapse
Unfortunately not stable on my device. Ran a couple of quadrants (4015) but froze during smartbench.
morfic said:
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Sent from my Nexus S
Click to expand...
Click to collapse
Naw it runs 100% on full OC 1440. I only have issues with radio occassionally, but thats because i cant make up my mind which is better, KB1 or KB3. But yea, mos def a daily driver. Ive drained my battery in 1/3 of the time i usually do, playing with my phone so much. Much appreciated sir, if you need more experienced feedback, let me know, I've done some work with android, just dont have the time as of late, but logcats etc are easy and not that taxing on my time
morfic said:
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Click to expand...
Click to collapse
except for that damned 1.7ghz kernel. one of these days..
jlevy73 said:
Unfortunately not stable on my device. Ran a couple of quadrants (4015) but froze during smartbench.
Click to expand...
Click to collapse
the phone commited murphacide
adewey234 said:
Naw it runs 100% on full OC 1440. I only have issues with radio occassionally, but thats because i cant make up my mind which is better, KB1 or KB3. But yea, mos def a daily driver. Ive drained my battery in 1/3 of the time i usually do, playing with my phone so much. Much appreciated sir, if you need more experienced feedback, let me know, I've done some work with android, just dont have the time as of late, but logcats etc are easy and not that taxing on my time
Click to expand...
Click to collapse
i used(on uv now, will use again) this kernel, as a daily driver, longer than any other. it definitely deserves respect. btw, i use KB1, and also had a hard time decided which radio i liked best
Hey Morfic, I have a question, when you were applying the patches for the kernels with BFS, were you using this file or a different one? 2.6.37-sched-bfs-363.patch
adewey234 said:
Hey Morfic, I have a question, when you were applying the patches for the kernels with BFS, were you using this file or a different one? 2.6.37-sched-bfs-363.patch
Click to expand...
Click to collapse
359 and later 363, but been a while.
Curious to see if superuser still hangs in "VM_WAIT" with 363 now or not.
Sent from my Nexus S
Mine was stable at 1.4ghz, but crashing constantly at 1.44ghz.
terryhau said:
Mine was stable at 1.4ghz, but crashing constantly at 1.44ghz.
Click to expand...
Click to collapse
Exactly the same issue I had.
How can you guys get almost 4000 in quadrant scores.
The maximum I got w/ this kernel was 3100, for me the phone is reallly fast but if you have more I want this more that I don't have.
Thanks,
liquelt said:
How can you guys get almost 4000 in quadrant scores.
The maximum I got w/ this kernel was 3100, for me the phone is reallly fast but if you have more I want this more that I don't have.
Thanks,
Click to expand...
Click to collapse
set your cpu to 1440/1440, then test 4 times in a row. the 1st is always much lower then the rest. the 3rd or 4th test should be more accurate.
First - 3091
Second - 3247
Third - 3770
Forth - 3813
Fifth - 3591
So here is my results, thanks for this FANTASTIC KERNEL.
liquelt said:
First - 3091
Second - 3247
Third - 3770
Forth - 3813
Fifth - 3591
So here is my results, thanks for this FANTASTIC KERNEL.
Click to expand...
Click to collapse
there you go, good ole #4
@800MHZ is the voltage the same or lower than 1GZ?
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.