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
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
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?
Howdy,
I've been using the CM7 nightly builds for a while now and figured it'd be nice to have a kernel that's based on CM7 with overclocking, RAM hack and couple of other tweaks. This kernel is pretty similar to the volkKernel but I wanted to have my own
Changes:
* Overclocking up to 1500 mhz (only through pimp my cpu at the moment)
* Default I/O scheduler of NOOP
I'll try to keep it up to date with the latest CM7 kernel sources.
[Releases]
Third release based on nightly #114
http://www.mediafire.com/?r57gqyuvhujwk6g
Second release based on nightly #101
* Removed RAM hack
* Balanced out the CPU clock values a little bit
http://www.mediafire.com/?1waipap3c71hat3
Initial release based on nightly #79
http://www.mediafire.com/file/w3e0s3vxwtznclz/cm7_79.zip
very nice welcome on board ^^
fallout0 said:
Howdy,
* Overclocking up to 1500 mhz (only through pimp my cpu at the moment)
Click to expand...
Click to collapse
Can't use setcpu?
i would like to use OC via CMParts ^^
Hmmm pardon me for asking, but why is it a 32mb RAM hack now instead of 64mb? Is it to resolve the gallery bugs?
I am using the original cpujauste o/c code that's why it only works with pimp my CPU. ill look into the others tomorrow to get that working
The 64mb hack caused issues for people with 1080p recording and the gallery. ill try it again and see how it works
ok, i found some bugs.
1. Reboot doesn't work. I guess thats because of the 32MB Ram Hack (for the vorkkernal, reboot doesn't work either)
2. After running a couple of hours, you only get around 50% of your CPU performance. Maybe the scheduler isn't optimized well. I recognized it by playing n64oid and it has lagged. Also I only get 3900 points at Antutu instead of ~5000 points.
ranrick said:
ok, i found some bugs.
1. Reboot doesn't work. I guess thats because of the 32MB Ram Hack (for the vorkkernal, reboot doesn't work either)
2. After running a couple of hours, you only get around 50% of your CPU performance. Maybe the scheduler isn't optimized well. I recognized it by playing n64oid and it has lagged. Also I only get 3900 points at Antutu instead of ~5000 points.
Click to expand...
Click to collapse
I think it's actually booting at ~700mhz by default so unless you set it up in pimp my cpu it'll stay at ~700 mhz. Probably why it's lagging.
We need more people working on kernels, thanks for doing so. Any improvements on battery life? Personally I find CM7 battery life to be pretty bad.
fallout0 said:
I think it's actually booting at ~700mhz by default so unless you set it up in pimp my cpu it'll stay at ~700 mhz. Probably why it's lagging.
Click to expand...
Click to collapse
Yep, now running with 1ghz again ^^
Can i request Voodoo Sound support?
Hey fallout0,
Nice work mate.
I think the general consensus is to not have the 64mb hack in kernels judging from a couple of poles about only 20% wanting the hack, probably less now.
I prefer to not have the hack at all imho, far too many instabilities for zero gain that being said I have yet to find a completely stable o/c kernel to use - stock seems to be the only completely stable kernel.
Be trying yours later on today so keep up the good work!
-smc
somemadcaaant said:
Hey fallout0,
Nice work mate.
I think the general consensus is to not have the 64mb hack in kernels judging from a couple of poles about only 20% wanting the hack, probably less now.
I prefer to not have the hack at all imho, far too many instabilities for zero gain that being said I have yet to find a completely stable o/c kernel to use - stock seems to be the only completely stable kernel.
Be trying yours later on today so keep up the good work!
-smc
Click to expand...
Click to collapse
Hey
Cheers
The ram hack and even overclocking support are pretty nasty hacks. Having said that I like the ability of adjusting voltages/maximum frequencies and until there is a better solution I think it's worth having this one
I agree about the RAM hack. I tried volkKernel and besides the reboot issue I didn't have any problems with the 32mb RAM hack. However the extra 32mb of RAM might not even be that useful.
I'll see how things pan out with this one then remove/add things as people complain
fallout0 said:
Hey
Cheers
The ram hack and even overclocking support are pretty nasty hacks. Having said that I like the ability of adjusting voltages/maximum frequencies and until there is a better solution I think it's worth having this one
I agree about the RAM hack. I tried volkKernel and besides the reboot issue I didn't have any problems with the 32mb RAM hack. However the extra 32mb of RAM might not even be that useful.
I'll see how things pan out with this one then remove/add things as people complain
Click to expand...
Click to collapse
Can't the reboot issue be easily resolved? According to RC, the bootloader expects the reboot-information to be at 128MB + 11 bytes, while the system writes it to [MB Reserved for Graphics]+11 bytes. As long as no ram-hack is applied, it'll of course be in the right place. Shouldn't it be easy for a kernel to just copy what is at [MB RESERVED]+11 to [128MB]+11 before shutdown?
Just talking by the seat of my pants here, haven't looked at any of the sourcecode, but it certainly feels feasible.
::Trym
I wish for that kernal:
- option on 32mb hack
- AVP/SD ram OC
- CMPart OC settings
thats it ^^
He-hey!))) This kernel is almost burnt my phone off.... Came upstairs after the dinner and found the phone off and very-very hooot... So, now I'm waiting for it to cool down a bit... Hope it'll turn on again)))
Update: Thank God that it didn't turn into BRICK))) Came on again and I've flashed it back to vorkkernel.
I am using MIUI ROM.
Very good works!! I have now tested with CM7 ROM "nightly full-77" version.
Fantastic Quadrant Score!!!
{
"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"
}
TrymHansen said:
Can't the reboot issue be easily resolved? According to RC, the bootloader expects the reboot-information to be at 128MB + 11 bytes, while the system writes it to [MB Reserved for Graphics]+11 bytes. As long as no ram-hack is applied, it'll of course be in the right place. Shouldn't it be easy for a kernel to just copy what is at [MB RESERVED]+11 to [128MB]+11 before shutdown?
Just talking by the seat of my pants here, haven't looked at any of the sourcecode, but it certainly feels feasible.
::Trym
Click to expand...
Click to collapse
I thought about it, and decided against it. Writing random information into active RAM is never a good idea.
so far so good with this kernel on RC1...
we want more OC !!!
moooooooore!
FEATURE LIST
------------------------
Voodoo Lagfix
Voodoo Sound
ThumbEE
BLN
TinyRCU //Lower memory footprint,not going with preempt cause I noticed some funkiness when rendering 3D
Add New Freqs
FPS UnCap
Ext4 Patch
348mb RAM
Simple I/O
SLUB
Compiler Optimized
LowMemoryKiller Patch
optimized govners
tweaked gov values
--------------------------
{
"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"
}
---------------------------------------------------------
1. What about SETCPU?
What about it? You can use w/e cpu OC tool you want
3.Why dont I get #### in Quadrant?
who gaf about quadrant scores anymore?
4.Can I use this is XYZ ROM?
OF COURSE! =} just credit me
Screen off Profiles are not needed or recommended on this kernel (its got it handled =P)
---------------------------------------
Morfic for Help and answering questions
laststufo for posting his sources (very helpful even though not for vibrant, just for ref.)
cmenard for TONS of question answering (I havent done much kernel work =3)
Supercurio for Voodoo (and great Documentation)
hardcore (his tweaks)
and anyone else I forgot
this in itself is a community effort because I couldnt have done this without
all the great Devs that support linux and android
so credit to EVERY dev out there, thank every dev you come across for this is you like it
-------------------------------------------
--------------------------------------------------
https://github.com/ECOTOX
-------------------------------------------------------------------------------------------------------------------------------------
changelog
Beta2 [6/27/2012]
--------------------------
added smartassv2 and lulzactive govs
--------------------------
Beta3 [7/18/2012]
--------------------------
removed lulzactive and smartass2 for now, readding next update
tweaked govs to ramp up more aggressively but also ramp down agressive when not in use
removed 100mhz steps, now steps as 100,200,400,600,800,1000,1100,1200,etc.
stabalized gpu clock @ or around 200mhz to prevent issues with phones not being able to do higher gpu clock
added 1.4ghz freq (use at own risk and may not work for all)
--------------------------
Few things to know
1.Will glitch at power on due to kernel size and some tweaks i made, its no big deal
2.for the first 10min after boot the clocks tweak out and wont go under 1000mhz, so let it sit and it'll settle down
3.With no tweaks just stock KB5 I get great performance, so idk how well it does witha tweaked rom
Great Froyo Support!
A 2.2 Kernel, Great work!
Thanks for your contributions!
Say ECOTOX, you work has been added to the Vibrant Kernel Bible thread, please stop by to post updates and I will update the thread, Cheers!
Yes it is for Froyo 2.2.
And so far it rocks....
Testing - SIO / Scary now!!
Thanks ECOTOX
NS4g_DMz.zip ???
Is this for the Verizon Nexus S 4g?
Inside the zip doesn't look like it for the Vibrant.
Don't want anyone flashing this and bricking phones.
fishman0919 said:
NS4g_DMz.zip ???
Is this for the Verizon Nexus S 4g?
Inside the zip doesn't look like it for the Vibrant.
Don't want anyone flashing this and bricking phones.
Click to expand...
Click to collapse
oops wrong link
fixed, ty for telling me
ECOTOX said:
oops wrong link
fixed, ty for telling me
Click to expand...
Click to collapse
NP... Thanks for the kernel... nice to see you around here again.
fishman0919 said:
NP... Thanks for the kernel... nice to see you around here again.
Click to expand...
Click to collapse
thanks =] nice to be back for a bit, I got a few things I wanna get workin on vibrant 2.2 anyway before i move on to 2.3/4.0 vibrant kernels. I'm gonna try and be a bit more active but i cant make promises, but i will fix bugs and update as i can
ECOTOX said:
thanks =] nice to be back for a bit, I got a few things I wanna get workin on vibrant 2.2 anyway before i move on to 2.3/4.0 vibrant kernels. I'm gonna try and be a bit more active but i cant make promises, but i will fix bugs and update as i can
Click to expand...
Click to collapse
Good to here... glad you got your compiling issue worked out... Lubutu rocks
Wow 100mhz stepping from 100-1300mhz rocks!
So far very smooth kernel.
Very smooth, haven't encountered any problems so far. Thanks!
Sent from my SGH-T959 using Tapatalk 2
Moped_Ryder said:
Wow 100mhz stepping from 100-1300mhz rocks!
So far very smooth kernel.
Click to expand...
Click to collapse
Good =) was built on an already well tested kernel (my previous one) mostly I had to tweak clocks and voltages to maximize stability. Now I just gotta work on some method for voodoo color on 2.2, that's my immediate task now.
Sent from my Galaxy Nexus using Tapatalk 2
So far no issues, thanks a lot for the kernel. Very smooth indeed..
Eco that would be badass if you could get adjustable Voodoo Color to work on a 2.2 kernel because it has never been done. I can't wait until you build a current Touchwiz GB based kernel with working GPS and adjustable Voodoo Color since there is no supported Vibrant kernel at this time, and Talon was the last to do it but never had GPS and Voodoo Color working at the same time. An updated CM 7.2 VC kernel would also be badass. I remember running your older kernels and they were quick and stable.
ECOTOX said:
Good =) was built on an already well tested kernel (my previous one) mostly I had to tweak clocks and voltages to maximize stability. Now I just gotta work on some method for voodoo color on 2.2, that's my immediate task now.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just what I want. I have been using your previous kernel along with Toxic Crazy 8 ROM since quite some time.
But, I would love to see some other features borrowed from Semaphore like:
Touchscreen sensitivity changes provided by Chainfire and automatic brightness handling(as the default one is not very intelligent).
I have tried, 2.3.x & 4.x kernel(&rom) , but all in vain, some or other thing stops me from making it my daily driver. I will try this out along with D9RC3 Fishman Mod1 Rom, today.
Lastly, what do you recommend for GPU & CPU tweaking,as I couldn't get 3 games working on DMZ kernel, but there could be other issues, sending you pm for the same.
Any chance to include voodoo colour with adjustable colors?
ECOTOX said:
Good =) was built on an already well tested kernel (my previous one) mostly I had to tweak clocks and voltages to maximize stability. Now I just gotta work on some method for voodoo color on 2.2, that's my immediate task now.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Stevethegreat said:
Any chance to include voodoo colour with adjustable colors?
Click to expand...
Click to collapse
Really, and only 4 post up. But I guess you did ask for adjustable colors... lol
fishman0919 said:
Really, and only 4 post up. But I guess you did ask for adjustable colors... lol
Click to expand...
Click to collapse
Yes I had read it, my request was the adjustable colors which to me is of greater importance than mere voodoo color... Then again I'm not sure if it is possible...