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.
Related
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?
OK, i know what you're thinking, "Another kernel for the Vibrant?" But this is my very first kernel development project so bear with me. This is just a project i've been working on since summer started, just to see if i can do it, learning experience. If you don't like it, you don't have to use it so please no flaming....and as always:
I (NOR TEAM WHISKEY) WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR PHONE BEFORE, DURING, OR AFTER FLASHING THIS. PLEASE READ ALL NOTES AND WARNINGS, FOLLOW DIRECTIONS, MAKE A NANDROID, HAVE ODIN READY, AND FLASH AT YOUR OWN RISK!!!
Features: (NEW IN V2.2)
-FPS cap completely removed (should help with you 3D gamers)
-More EXT4 patches
-Removed unnecessary code in patches
-Some debugging removed (should help with battery life & speed)
-Went back to stock voltages from v1, but still user configurable (to bring back stability)
-Now available in Kernel Manager app in the market.
------------------------v2.1----------------------------------------
-Retweaked HZ values, should now be as smooth and responsive as v1 was
-Added Juwe's RAM optimization script into flash package
-Added pieces of SpeedMOD
-Fixed a few bugs in Makefiles
--------------------------v2-----------------------------------------
-Voodoo Sound v10
-New Skull splash screen
-Compiled with optimized compiler flags (thanks drhonk)
-Added "Interactive" governor
-Added "Smartass" governor from DragonMODz (thanks ECOTOX)
-Screen Off profiles working on 400/100 with and/or without setCPU using Smartass
-Retweaked voltages table, -25UV across the board
----------------------------v1--------------------------------------------
Voodoo lagfix
Voodoo sound v9
Voodoo color
BLN = Back Light Notifications
LowMemoryKiller patch
Modified Kernel HZ value from 260 to 500....for smoothness and responsivness
TinyRCU
BFQ I/O scheduler (set to default)
CFQ removed
Battery polling values modified (an attempt at saving batt life)
JHash3 patch
EXT4 patches
Modified FPS (Increased, not removed)
333MB Ram Hack
User configurable OC/UV
Safe booting to 1ghz
Overclockable to 1.2 ghz
Avatar confirmed working with this and Bionix NextGen V2
{
"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"
}
Notes:
1. After flashing this and rebooting, let the phone sit for a few minutes, before doing stuff. It will be alot smoother,
trust me.
2. This safely boots to 1ghz, but use an app like Voltage Control or setCPU to UV/OC to meet your needs.
3. If using Smartass as the main gov, DO NOT USE A SCREEN OFF PROFILE. After extensive testing, Screen Off profile is NOT needed if using Smartass as main gov (Smartass can handle it, if your phone can handle Smartass)
4. Not all phones can handle the Smartass gov, if this is the case, just switch the the Conservative gov again.
My downloads will be hosted from Google Code now, so i can track number of downloads and issues, so:
Download Immortality v2.2 here: Download
Kernel Source Now Available here: Source
Wanna donate to my FFC fund for my services? Hit this donate button!!
Credits:
drhonk - For having patience and answering all the dumbass questions i had
ttabbal- also For having patience and answering all the dumbass questions i had
My beautiful fiance - for believing in me, and letting me do this
ECOTOX - For his sources from DragonMODz
supercurio - For all his work on Voodoo
coolbho3k - For SetCPU
xan - For his Voltage Control app (get the free version in the Market, buy his Extreme Version for more features)
neldar - for BLN
Paul McKenney - for TinyRCU
hardcore - for reference on Ram hack and battery tweaks \ SpeedMOD
cmenard - for having a baddazz kernel and references in sources
grendel905 - for having a baddazz kernel and references in sources
Juwe - RAM optimization script
s0niqu3 - Kernel version MOD
Skitz - Torture testing beta versions
Anyone else i forgot, let me know
Nice job! Trying it out now
Edit: seems to work flawlessly...very quick and responsive
Project-V vrs1
Are you going to make a GB kernel because right now there is only one, it is a great kernel but there is only one.
ali1276 said:
Are you going to make a GB kernel because right now there is only one, it is a great kernel but there is only one.
Click to expand...
Click to collapse
I'll think about it, i'm still learning
Next on the list is a 1.4ghz overclock kernel, but i'll see how you guys like this one.
Mr. Apocalypse said:
I'll think about it, i'm still learning
Next on the list is a 1.4ghz overclock kernel, but i'll see how you guys like this one.
Click to expand...
Click to collapse
Like it one.... after about 10 min, very, very very smooth and responsive
Thank You
Great job on this.extremely responsive and im loving it.great job for an artist. Lol..going to play around with set cpu at work and let you know how it works out.keep up the great work.you should rewrite that post because it sounds to negative for this bad ass kernel
ali1276 said:
Are you going to make a GB kernel because right now there is only one, it is a great kernel but there is only one.
Click to expand...
Click to collapse
A good gb kernel is talon kernel over in the cappy thread nice job!
Sent from my SGH-T959
Good job, man! I'm coming from Bali and I have to say that this is really responsive and snappy! Bali would freeze up every so often, but I'm not having any issues with this so far. It'll be interesting to see how much battery life it'll get.
I'll post later with my experience with it. I'm liking it so far though
Sent from my SGH-T959 using XDA Premium App
Came from Bali kernel and running Nextgen V2. This kernel is BAD!! So smooth and very responsive. Awesome job on this project.
Sent from my SGH-T959 using XDA App
I prefer SetCPU for its user-friendly interface and settings, but if I have to, I'll download Voltage Control for this.
Will this work with ETD Project V rom?
sumasage said:
Will this work with ETD Project V rom?
Click to expand...
Click to collapse
it SHOULD work on all 2.2 and 2.2.1 ROMs, but i havent tested it yet
I can confirm its running on trigger 3.3. Seems pretty good so far. Nice work!!
Trigger 3.3
Running great so far, but using voltage control...the kernel seems to never fall below 800 mhz and 1200 voltage comes up as undetected. I'm running it on conservative, noop, slider on 1200. Saved settings and rebooted a few times...crunching battery right now because of it.
Am I missing something or just had too many beers? Lol
<('.'<) ^( '.' )^ (>'.')>
draychi said:
Running great so far, but using voltage control...the kernel seems to never fall below 800 mhz and 1200 voltage comes up as undetected. I'm running it on conservative, noop, slider on 1200. Saved settings and rebooted a few times...crunching battery right now because of it.
Am I missing something or just had too many beers? Lol
<('.'<) ^( '.' )^ (>'.')>
Click to expand...
Click to collapse
try switching to the BFQ scheduler, and give the batt a good cycle before judging the battery, OCing can do that, thats why it boots to 1ghz by default
Yea, I always let new flashes run a few cycles...but the cpu is still running high and I'm not sure why...
<('.'<) ^( '.' )^ (>'.')>
sumasage said:
Will this work with ETD Project V rom?
Click to expand...
Click to collapse
^beep beep your bus is here^
Project-V vrs1
draychi said:
Yea, I always let new flashes run a few cycles...but the cpu is still running high and I'm not sure why...
<('.'<) ^( '.' )^ (>'.')>
Click to expand...
Click to collapse
the cpu is gonna run high a bit, especially if its OC'ed, my phone is dropping down to 400mhz, but i'll look into it if it becomes a major problem for people
I love the kernel but the the bootimage is kinda "Ehh"
philliple97 said:
I love the kernel but the the bootimage is kinda "Ehh"
Click to expand...
Click to collapse
It had a skull, but I changed it at the last minute, too many people would've complained
Sent from my XDA app cuz I'm stalking your mom....
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!
Hi, a friend came by and asked me to optimize his tegra. Thanks for faux123, we have an OC kernel. Made the following changes
1. Added JRCU with lazy to optimize RCU implementation of dual cores
2. Made INTERACTIVE (not powersave) default by making changes in cpufreq drivers
3. Made noop default (can be changed in ROM)
4. Overclocked settings from 216mhz - 1400000 mhz with voltage from 750mv - 1350 mv
5. AVP/VDE overclocked to 300000 mhz
6. GPU overclocked to 400000 mhz
7. Memory speed set at 333000mhz
8. Optimized utilization of dual-cores (cpu0 and cpu1) by making changes in how cpu1 is called.
9. Reverted a few changes in the overclocking code
Again, thanks to faux123 he saved me a lot of time and made things a lot easier.
WARNING:
These timings are pretty aggressive and might not work for your atrix that is why I called it elite (fortunately my friend's Atrix handled the timings pretty well) so please backup.
-----------------------------------------------------------------
-----------------------------------------------------------------
Update: 2/6/2012
1. Increased cyanogen overclocked speed to 1.6ghz!!!
Link:
www.tunerspotter.com/clemsyn/Ultimate1.6eliteCyano.zip
-----------------------------------------------------------------
-----------------------------------------------------------------
Update: 1/30/2012
1. Updated to 2.6.32.55 (Thanks faux123)
2. Build for ATT and Cyano at 1.5 GHZ
ATT 1.5 ghz kernel
www.tunerspotter.com/clemsyn/ClemsynATT1.5elite.zip
Cyanogen 1.5 ghz kernel
www.tunerspotter.com/clemsyn/ClemsynCyno1.5elite.zip
BTW, if you like my work, please
and help me buy some diapers. Thanks.
-----------------------------------
-----------------------------------
UPDATE: 1/28/2012
1. Increased overclocked to 1.5 ghz
2. Only for Cyanogenmod ROMs at the moment
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.5kernel.zip
-----------------------------------------------------------------
-----------------------------------------------------------------
UPDATE:
1. Updated to 2.6.32.48 with faux123 optimizations and changes
2. Added 1.0 ghz kernel for both att and cyanogenmod
3. Added a few optimizations in interactive governor to improve CPU sleep and wake
4. Added 1.4 ghz for att
5. Added 1.4 with aggressive memory timings for Cyanogen
ATT VERSION 11/22/2011
1.0 ghz ELITE version
www.tunerspotter.com/clemsyn/ClemsynATT1.0elite.zip
1.4 ghz ELITE version
www.tunerspotter.com/clemsyn/ClemsynATT1.4elite.zip
Source
www.tunerspotter.com/clemsyn/kernel2.tar.gz
--------------------------------------------------------------------------
CYANOGEN VERSION 11/22/2011
1.0 ghz ELITE version Cyanogen
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.0.zip
1.4 ghz ELITE version Cyanogen
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.4.zip
1.4 GHZ Elite version with a more aggressive memory timings Cyanogen
www.tunerspotter.com/clemsyn/ClemsynCyanoElite1.4memorytimings.zip
BTW, if you like my work, please don't hesitate to click on the donation button under my sig and help me buy some diapers It will be appreciated. Thanks.
------------------------------------------------------------------------
------------------------------------------------------------------------
Older version
www.tunerspotter.com/clemsyn/ClemsynCyanogenElite.zip
I suggest you use system tuner in the market to tweak voltages/governor/io scheduler and SD cachesize
SOURCE : www.tunerspotter.com/clemsyn/kernel.tar.gz
BTW, if you want 1ghz or 1.2 ghz max overclock here are the steps.
Install system tuner ==>Tweaks===> CPU and bring the top slider down to your desired speed (1ghz or 1.2 ghz) and that will prevent the phone from going higher your desired speed
BTW, if you like my work, pls dont hesitate to click on the donate button under my sig. Thanks.
It says "elite", but do you know how many people are going to flash this (that shouldnt be flashing this) and flood this thread with "noob questions"?
God speed my friend, God speed...
andrew.cambridge said:
It says "elite", but do you know how many people are going to flash this (that shouldnt be flashing this) and flood this thread with "noob questions"?
God speed my friend, God speed...
Click to expand...
Click to collapse
I have no issue with noob questions, BTW, I am a kernel dev for Gtablet, Adam and Asus Transformer so this is not my first release and I am familiar with the kernel code for the tegras
Any wifi issues?
Sent from my MB860 using XDA App
Took it for a spin just now. -100mv on all levels undervolt. Quadrant completed 3x with no issues. Best score was 5024
On nightly 19
*edit* 150 and 200mv under lock my phone instantly but -100 on all levels seems rock solid and the phone feels snappy. Ill report back tomorrow night after a day of normal use (unless something else to flash comes out)
Sent from my MB860 using Tapatalk
Whoever tries this kernel out, please post back results of what its currently doing and a few days after. I would personally try it but, my phone needs to be stable for my job and college.
Sent from my Atrix XDA Premium App
Voelker45 said:
Whoever tries this kernel out, please post back results of what its currently doing and a few days after. I would personally try it but, my phone needs to be stable for my job and college.
Sent from my Atrix XDA Premium App
Click to expand...
Click to collapse
Flashed this on nightly build #20 ended up not booting so I cleared the caches again and next restart put me in an endless bootloop. Restored my backup gonna try a different cyanogen build with this. Anybody who has success please let everyone know what cyanogen build you are on? Gonna try this with the weekly build next.
flashing now. will update back.
Sweet Welcome!
Awesome. UVed -170 on all for now. -175 randomly rebooted after a couple minutes. Gonna work myself down until it's stable. Knowing that every step is going to be UVed to the max 100 mV limit makes UVing a LOT easier. You only have to worry about the top step.
d11dog11 said:
Took it for a spin just now. -100mv on all levels undervolt. Quadrant completed 3x with no issues. Best score was 5024
*edit* 150 and 200mv under lock my phone instantly but -100 on all levels seems rock solid and the phone feels snappy. Ill report back tomorrow night after a day of normal use (unless something else to flash comes out)
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I couldn't go past -100 either but it was stable at that level. Pretty solid Antutu ratings: 6539, 6767, 6774
I'm sure if I pushed it I could do better, however that hammered stability pretty well. We'll see how it goes battery-wise as well. Thanks for the upload!
Is there any chance you can make a 1.5ghz version? Not for all use but it would be fun to have. I know Kholk has one so isn't it possible?
Successfully flashed. I notice smoother screen transitions and scrolling. Not placebo, as the previous at 1.45 ghz had a very slight lag time when swiping to a different home screen. Also nice bench score on cf-bench (7800s) Thank you very much!
Just it UV'd -150 on all, hammering CF-bench. Looking pretty stable so far, and I like how it handled Quadrant earlier, I saw some positive spikes in FPS and it was smoother overall. I don't put much stock in Quadrant tests but nonetheless. Will throw up some Nenamark test as soon as I'm done hammering CF-bench.
faux123 said:
Sweet Welcome!
Click to expand...
Click to collapse
Big Thanks to you I won't be developing much for the atrix since I just developed it for my friend but I just wanted to share what I made. Currently uploading the source (Ive got a really slow internet)
clemsyn said:
Big Thanks to you I won't be developing much for the atrix since I just developed it for my friend but I just wanted to share what I made. Currently uploading the source (Ive got a really slow internet)
Click to expand...
Click to collapse
It gives us something to play with. I'm more of a 1.0GHz Blur-oriented ROM user but I like new toys, and thank you for uploading it for us junkies.
BravoMotorola said:
Is there any chance you can make a 1.5ghz version? Not for all use but it would be fun to have. I know Kholk has one so isn't it possible?
Click to expand...
Click to collapse
I actually though about pushing it to 1.6 ghz but was very hesitant since I didn't own the device and it didn't have enough room in there the disipate the heat. I just played safe with 1.4 but 1.5 should be no issue. If I get the chance to get the atrix again, I'll try to push it to 1.6 and make one for att gingerbread.
Nenamark 1: 57.2fps
Nenamark 2: 27.5fps
Great scores for an Atrix!
clemsyn said:
I actually though about pushing it to 1.6 ghz but was very hesitant since I didn't own the device and it didn't have enough room in there the disipate the heat. I just played safe with 1.4 but 1.5 should be no issue. If I get the chance to get the atrix again, I'll try to push it to 1.6 and make one for att gingerbread.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashed... running fine so far, will report back. THANKS TO THE OP & FAUX!
Sent from my Atrix awaiting CM9....
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...