Database Info

[KERNEL][GPL][ACS]Xtreme Kernel v1.2.0-Lucy-1.3GHz OC,Battery,Tweaked Voodoo(options)

ANDROID CREATIVE SYNDICATE​presents​XTREME KERNEL V1.2.0​
First of all, I want to put my thank yous up here at the top, so, here they are:
-geniusdog254 - My primary teammate, been helping me every step of way.
-nullghost - One really cool dude. Always on when I ask for help. Git would still be a scary thing if not for him.
-rjmjr69 - Funny, funny dude. Keeps me motivated to keep going
-The Voodoo Team - Your work is awesome!
-My beta testers - You were/are all great. Thanks for helping me with this!
-All the devs across the board - Seriously, you're all a bunch of absolutely awesome people.
-Anyone I forgot - You're all great!
Now, here we go:
THE STANDARD DISCLAIMER
I, DevinXtreme, AM NOT responsible for what happens to your phone, your cat, your house, or anything relating to you! If your phone bricks, OH WELL. Have a nice day.
This kernel has a MixUp kernel base. DI18, blah blah. I deviated once Interactive got working. I also removed the Voodoo color modification. So, there's that.
It is built and designed for Syndicate ROM, which will be out later tonight. Sickest ROM you've ever seen. The version released with the ROM is slightly different, but only for fun's sake
Changelog:
v1.2.0
-Removed the 1.6GHz step. The time machine is gone. Plus, was causing more problems than it was helping.
-Added 1.3GHz step courtesy Herver
-Switched from MPLL to APLL. Smoothness and speed increase. Thanks to nullghost for help on this.
-Added Voodoo color mod, tweaked version, courtesy Herver. I will be maintaining a no-voodoo version. I just haven't yet.
-Tweaked the light sensor, adding a new step and made it not jump to the brightest setting as much. Should save battery and transition smoother. Also pols a little more often.
-Tweaked scaling rules for 1.3GHz. Should scale there less, thus saving battery.
ADDITION: The file ending in 'nv.zip' is a no-voodoo version. The file ending in 'ov.zip' is the version for the original voodoo mod, not the tweaked one.
v1.0.1
-Fixed scaling. Linpack scores and tests work fine now.
-Disabled Carrier IQ in init.rc. Carrier IQ is essentially Sprint spyware. Kernel devs: This is really easy to do. Just comment out the iqmsd lines at the end.
v1.0
-Overclock to 1.6GHz!! Requires SetCPU which is, for some reason, defaulting to performance. Make sure you change it to conservative.
-Default governor without SetCPU is conservative with 200MHz-1GHz steps.
-Removed Voodoo
-Framerate unlocked (78-80fps)
-Built for ROMs with a custom boot. Makes stock boot look like garbage. We're working (still) to fix this.
-Undervolted
KNOWN BUGS:
-In spare parts, if you set the WiFi policy to never sleep, it still sleeps with the screen off. -skandranon314
-Some weird vibration thing going on when 1.6GHz is hit.
NOTES:
Linpack is being strange with this. I'm getting between 9.2 and 9.8 with some REALLY strange numbers. I'll have this fixed this weekend.
SetCPU sets the default governor to performance. If you use it, be sure to change it immediately for battery life.
FOR 1.2
-I recommend 200MHz-1200MHz. Some phones can't reach 1.3GHz safely.
-200MHz - 800/1000MHz is a great setting for battery and you should still have a very smooth experience.
For those who care, I get 1135+ in quadrant.
You can read my source here.
Thanks, guys. I hope you enjoy!

How stable is this??

When is the rom out?
Sent from my SPH-D700 using XDA App

Looking forward to trying this out!

1.6 GHz???????
That's awesome, though I don't think I'll crank it that high.
Is there any advantage to this vs MixUp running at 1.0 Ghz?

spitefulrain said:
How stable is this??
Click to expand...
Click to collapse
I've hit no bumps, neither have my testers.
joshottley said:
When is the rom out?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Give it a couple of hours.
SORRY, HAD TO TAKE IT DOWN FOR JUST A LITTLE BIT. EXPECT AT ~12:45AM MST.

Why take it down? I already downloaded and flashed, was that a bad idea??

I'm running it. Smooth so far.
Sent from my SPH-D700 using XDA App

Dusting the epic off now.

[email protected] said:
Dusting the epic off now.
Click to expand...
Click to collapse
Should have never abandoned dude lol.
Sent from my SPH-D700 using XDA App

Very smooth so far. got 1194 on quad, and 9.2 average on linpack. Wonder how the battery life will fare.

spitefulrain said:
Why take it down? I already downloaded and flashed, was that a bad idea??
Click to expand...
Click to collapse
Nope, just a tweak. Your phone is fine! XD
And I'll be in a movie, so I won't be able to get it up until then. Sorry guys!

DevinXtreme said:
Nope, just a tweak. Your phone is fine! XD
And I'll be in a movie, so I won't be able to get it up until then. Sorry guys!
Click to expand...
Click to collapse
Ok, good. I was worried for a sec
So would you recommend flashing the new one when it's up since you're tweaking it?

Hmm.. something's not right here. I just got 22 fps in Neocore with the removed kernel. What could I be doing wrong?
Edit: Switching from performance to conservative upped my results to 62 fps which is quite respectable.

spitefulrain said:
Ok, good. I was worried for a sec
So would you recommend flashing the new one when it's up since you're tweaking it?
Click to expand...
Click to collapse
Yeah, it'll be a good idea.

what kind of voltage are you giving it to get 1.6 stable? based on what im reading, anything above 1.3/1.4 is pretty much unachievable on these devices and is not really the speed that the device is running thus the unscaled rise in benchmark scores. iv been following hero_over and he couldnt get a stable 1.4 OC although he did get 1.3ghz on stock volts stable..which keeps me wondering if we really can hit 1.6 stable

illogic6 said:
Hmm.. something's not right here. I just got 22 fps in Neocore with the removed kernel. What could I be doing wrong?
Edit: Switching from performance to conservative upped my results to 62 fps which is quite respectable.
Click to expand...
Click to collapse
lol I was gonna say. I'm going good with Neocore as well.
d94 said:
what kind of voltage are you giving it to get 1.6 stable? based on what im reading, anything above 1.3/1.4 is pretty much unachievable on these devices and is not really the speed that the device is running thus the unscaled rise in benchmark scores. iv been following hero_over and he couldnt get a stable 1.4 OC although he did get 1.3ghz on stock volts stable..which keeps me wondering if we really can hit 1.6 stable
Click to expand...
Click to collapse
All of it is on my git. I release my source, as devs should with GPL. The problem is that the fsb isn't scaled properly, affecting the floating point processor, causing low Linpack scores. I'll have it worked out this weekend,

Bummer.... I missed the link the first go around..... Will be waiting
Sent from my SPH-D700 using XDA App

If this was a hero_over post, he'd be in trouble for a teaser post lol... just trolling lol. Had to have a smart ass comment

Quick. And stable so far
Sent from my SPH-D700 using XDA App

[KERNEL][AOSP][2.6.35.10] - Savage-Kernel v1.6! [HAVS+CFS/BFS!!] UPDATED 1/12!

ALL SOURCE CAN BE FOUND HERE
I am proud to announce Savage-Kernel to the xda forms. This kernel is worked from the latest cm unified kernel; undervolted, HAVS with the SBC mod.
SENSE BASED ROMS NOT SUPPORTED THIS IS FOR AOSP ROM'S ONLY
According to ms79723 we are the first AOSP kernel to have the latest SBC mod with the new voltage and A/C AND USB trickle charging
So far the Kernel works great in conservative governor. which all the devs prefer.
Devs:
luisrcastillo (co-creator)
jsseidel1 (co-creator)
Credits:
toastcfh/cyanogen/cyanogen dev's --> the cm base kernel!!
ms79723 --> the SBC mod.
netarchy --> smartass gov
intersectRaven --> HAVS
lithid-cm (contributer. Updater-script guru)
ms79723 (SBC mod updates)
(credits are given to the dev's where we got some code from, may no be original designer)
CFS Builds:
v1.6 noSBC : Click here to download
BFS Builds:
v1.6 : Click here to download
Follow the github on twitter @evokernelsrc
If you like our kernel and want to support us... donate (goes to a group pay pal for Luis and I)

CHANGELOG
Code:
[B]Beta 1[/B]
Undervolted to 925
HAVS implemented configured for conservative
smartass added for fans
SBC Mod added (trickle Charging)
Enabled OC to 1.19 and stable
[B]Beta 2[/B]
SBC v5 (USB trickle added as well as modified voltage)
HAVS tweaks
smartass governor tweaks
conservative governor tweaks
[B]Beta 2.5[/B]
conservative governor tweaks
HAVS tweaks
[B]Stable v1[/B]
conservative governor tweaks
smartass governor tweaks (now recommended)
reverted back to SBC v4 due to USB trickle bug..(causes usb connection to disco) (i.e USB trickle doesnt work in this build)
HAVS tweaks
voltage tweaks
BFS360 (latest version) and CFS VERSION!!!
[B]Stable v1.1[/B]
SBC v7 -mA fix... still no USB trickle yet
merged latest cm-kernel commits, to include new wifi drivers
[B]Stable v1.2[/B]
Added SBC v7 USB charging and got rid of bugs
BFS tweaks to ondemand gov
tweaks to interactive gov
bad ass CFS tweaks!!!!!
[B]Stable v1.3.4[/B]
Core Kernel tweaks
CM7 wifi drivers added
aggressive swap drop
misc tweaks
[B]Stable v1.5.2[/B]
voltage tweaks
better memory handling
New BFS version
Fixed all Wifi issues
Put new Cam drivers and other new drivers in there
[B]Stable v1.6[/B]
Upgraded to CM .10 commits (CM7 Kernel)
Added Wimax (you still need a wimax enabled ROM)

FAQ's
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!

I fixed up my USB/AC charging tweak. I'll pm you as soon as I update my github in a bit

ms79723 said:
I fixed up my USB/AC charging tweak. I'll pm you as soon as I update my github in a bit
Click to expand...
Click to collapse
Sounds good. I'm working hard this morning on HAVS and governors... Luis was up all night getting the first private beta. Looking for about 5 testers that run AOSP roms to test. Barnacles is going to already, once Luis gets up we need to review the apps that came in... we should release a public by Thursday. Maybe tomorrow depending on the feedback from the private testers.

jsseidel1 said:
Sounds good. I'm working hard this morning on HAVS and governors... Luis was up all night getting the first private beta. Looking for about 5 testers that run AOSP roms to test. Barnacles is going to already, once Luis gets up we need to review the apps that came in... we should release a public by Thursday. Maybe tomorrow depending on the feedback from the private testers.
Click to expand...
Click to collapse
I would like to test the new kernel.

I can test for you guys.
Sent from my Liquid using XDA App

I'd be willing to test as well.

Hopefully others will come along and do the same thing you guys are doing but make it open to the full community and not do private selections. This does look like it has promise but until it gets made public and not private invites I will stay away from it

EJerVJerO said:
Hopefully others will come along and do the same thing you guys are doing but make it open to the full community and not do private selections. This does look like it has promise but until it gets made public and not private invites I will stay away from it
Click to expand...
Click to collapse
it will be, we just want to make a good first beta, future betas will be released right away. if our testers today give us good feedback and are very responsive... we will release the 1st public beta tomorrow, and then it will be norm... We dont get a picky about testing as snap. Zendroid doesnt release betas until he's done private testing, just we announced before the 1st public release.

All: Private beta testing is closed... we got enough guys already, got bombarded with requests this morning. Appreciate all the intrest, hopefully the users we selected will get us feedback asap so we can get out the public beta

BTW beta 1 so far getting 1435 on quadrant in gingerbread.
52fps
and 42 in linpack.
We will have a public release tomorrow

Sent from my PC36100 using XDA App

Beta 1 released
please look at the OP... BETA 1 has been released!!

Just downloaded. Gonna give it a shot. Thanks guys!

blackroseMD1 said:
Just downloaded. Gonna give it a shot. Thanks guys!
Click to expand...
Click to collapse
great please post your thoughts

Do I have to use SetCPU w/ this and modify my min/max? If I don't use SetCPU, will I achieve the trickle charge effect w/ the prolonged battery AND how will this affect my EVO's speed?

typeadam said:
Do I have to use SetCPU w/ this and modify my min/max?
Click to expand...
Click to collapse
No, you dont it defaults to conservative. you have to use SetCPU to change your min.max
typeadam said:
If I don't use SetCPU, will I achieve the trickle charge effect w/ the prolonged battery
Click to expand...
Click to collapse
Yes the trickle charge (SBC) has nothing to do with SetCPU. the BETA 1 only have a/c trickle so the USB charge will be normal. the next release will have the USB trickle as well. Make sure you charge it at least 30min after it says fully charged the first time.
typeadam said:
AND how will this affect my EVO's speed?
Click to expand...
Click to collapse
off the bat your battery life will be great, and speed will be alot snappier. Overclock for a safe speed boost, but its not required.
enjoy

I'm going to test it with CM 6.1.1

jsseidel1 said:
great please post your thoughts
Click to expand...
Click to collapse
Well, the first thing I noticed is I got my USB icon back, but it says that "There was a problem turning off USB...". Whenever I click on it, it kills the status bar.
That may be a problem with the ROM itself though, as everytime I reboot, I get "SD Card unexpectedly removed" error. The Kernel seems smooth as silk though after initial boot, and I will report back on battery life later.

[Kernel] [Updated 22OCT] HeroC - 2.6.35.14

This can now be considered stable, after significant testing and use by the community. As always, the hero you save could be your own, so be safe.
This would not have been possible without the efforts of everyone in the community that played a part in moving the ball forward. In particular s0be and riemer for their initial efforts to get a working 2.6.35 build as a baseline, and the continuing efforts of riemer, erasmux, arco, et al; also thanks to toast, darch, decadence, pershoot, and cyanogen, as well as the Linux, CM, AOSP, and CAF teams that have provided the broad shoulders for tinkerers like myself to stand on. My sincere gratitude to all of these and the legion of others who I have not listed, who have contributed to making the open source community strong and productive.
This kernel is based on a combination of updated board files for HeroC, and efforts by arco, riemer, erasmux on new sources originally from the HTC marvel code release. After several weeks on the new base, everything appears to be working well. Initial sources have been posted to github.
New version (2.6.35.14) is at:
https://github.com/TeamHeroC/heroc-kernel-2.6.35
The sources for this Kernel and the AOSP flavored 2.3.5 ROM sources are posted to the TeamHeroC github. This organization github was created instead of using a personal github so that others could join in team development efforts if they are interested, and the organization could be more easily maintained after people move on to other devices. I am probably looking at somewhere between 2-5 months myself.
Flash from recovery, and remember nandroid is your friend.
UPDATE - KERN-2.6.35.14-10SEP-V1.0.zip
10SEP version has been updated with changes from various sources. Github has also been updated to be in sync with this update.
UPDATE - KERN-2.6.35.14-22OCT-V1.1.zip
22OCT version has been updated with changes from various sources. Github has also been updated to be in sync with this update.

Old version - No Longer in Development
This is very much a work in progress, so be safe.
This would not have been possible without the efforts of everyone in the community that played a part in moving the ball forward. In particular s0be and riemer for their efforts to get a working 2.6.35 build as a baseline; also thanks to toast, darch, decadence, pershoot, and cyanogen, as well as the Linux, CM, AOSP, and CAF teams that have provided the broad shoulders for tinkerers like myself to stand on. My sincere gratitude to all of these and the legion of others who I have not listed, who have contributed to making the open source community strong and productive.
This kernel is based on a combination of the s0be/riemer board files and other mods applied to the CyanogenMod cm-kernel android-msm-2.6.35-unified branch. It does not have smartass (not working yet), but the camera seems to work consistently for me on both interactive and ondemand (Note: setting min cpufreq to 352 is recommended to minimize camera problems). This is still very much an early effort, but thought I would post for anyone interested. Initial sources have been posted to github.
https://github.com/TeamHeroC/cm-kernel-heroc
New version (2.6.35.14) is at:
https://github.com/TeamHeroC/heroc-kernel-2.6.35
The approach to building this kernel was to go back to a build based on the last CM 2.6.35 source from the repo and add files from the s0be/riemer source tree to get a working kernel. My goal is to get this as close to standard source as possible, so the changes will just be the device specific board files, drivers, etc. The reason for this approach is to (hopefully) get a well defined set of files and updates that can be applied to other kernel releases (.37, .38, ...) with minimal conflicts and dependencies.
Lots of things that I will be working on as time permits. In no particular order this includes things like:
complete headset updates
update qdsp5_comp to align with latest sources
update smd files to align with latest sources
rework board files to current standards
check and complete i2c updates
complete USB updates
compare and update MSM frame buffer files
cpufreq updates and smartass governor
check and update device specific drivers
The sources for this Kernel and the AOSP flavored 2.3.4 ROM sources are posted to the TeamHeroC github. This organization github was created instead of using a personal github so that others could join in team development efforts if they are interested, and the organization could be more easily maintained after people move on to other devices. I am probably looking at somewhere between 2-5 months myself.
Flash from recovery, and remember nandroid is your friend.
Added No Headset version as suggested by s0be. This version has no headset drivers built in. In theory, this should improve the stability of your USB functions. This has had very little in the way of testing. YMMV.

Thank You,
Flashing now!

painter_ said:
Thank You,
Flashing now!
Click to expand...
Click to collapse
Thank you this great news!!!!!
Sent from my HERO200 using XDA Premium App

Awesome news.
Thanks JB for picking this up.

jaybob413 said:
Flash from recovery, and remember nandroid is your friend.
Click to expand...
Click to collapse
Thanks again Jaybob,
One question, Ive been running the kernel that you posted on s0be's thread a few days back, is this one updated or is it basically the same? So far no Camera bug for me (which is why I flashed to begin with).

chalan30 said:
Thanks again Jaybob,
One question, Ive been running the kernel that you posted on s0be's thread a few days back, is this one updated or is it basically the same? So far no Camera bug for me (which is why I flashed to begin with).
Click to expand...
Click to collapse
A few changes since then, but nothing major. I can't really say whether it is better or worse than the previous. Seems about the same to me. I will add the previous version to the OP later as well.

jaybob413 said:
A few changes since then, but nothing major. I can't really say whether it is better or worse than the previous. Seems about the same to me. I will add the previous version to the OP later as well.
Click to expand...
Click to collapse
Radical.
Thanks for your efforts. The previous version has been working well for me on your May 30th rom with FR 118_15 with some autokiller tweaks. Battery life seems a little worse but still very decent. All very smooth with ADW eX and LPPro . Had a couple of issues with the phone locking up (black screen) for about 20 30 seconds, then coming back on its own. Not sure if it was because my min was too low on setcpu (on demand). Not that it matters but my linpack scores have been consistently lower. but real world performance is great.
Lets see how this does.

so totally didnt see this thread until just now.. thanks a ton jaybob.. this kernel has some loyal followers, and i know i can say for most of them that i am glad to see someone who is capable pick this up.. i was trying my hand at it, but i dont have the time right now, and my knowledge base just isnt as broad as it needs to be for this.. so thanks man, you are the best..

3 Hours now and it seams stable. It took a little while after the first boot before my phone became stable. The ROM I am running the 5/25 version of Evervolv.

painter_ said:
3 Hours now and it seams stable. It took a little while after the first boot before my phone became stable. The ROM I am running the 5/25 version of Evervolv.
Click to expand...
Click to collapse
Yeah these .35 kernels usually take a few minutes to warm up. but they tend to get tremendously better with time..
sent from my... wait.. what..

This thing is running too smooth on the latest nightly. Someone pinch me!!

pstevep said:
Yeah these .35 kernels usually take a few minutes to warm up. but they tend to get tremendously better with time..
sent from my... wait.. what..
Click to expand...
Click to collapse
Its kinda weird how they do that... but they do go nice after a little while!

and jaybob this build is running a lot smoother than the last one.. on a whole, its smooth a silk, camera is working great.. kudos so far man..

jaybob413 said:
(Note: setting min cpufreq to 352 is recommended to minimize camera problems)
Click to expand...
Click to collapse
Isn't camera supposed to engage perflock?

jasonmaloney said:
Isn't camera supposed to engage perflock?
Click to expand...
Click to collapse
No perflock in this kernel (or s0be's or deca's). My recommendation is just based on an observation that when the min cpu freq was set to a very low value (19), I would see a lot of camera freezes. It may work fine at lower settings, I normally have mine set to 352 and don't have camera problems with ondemand or interactive, so this is just what has worked for me. It may also be fine at 264 or 176, but I haven't tried them.

Running this kernel with the latest CM7 nightly and I've never seen my Heroc run so smooth nor get this crazy good battery life.
Thanks JB.
Haven't checked to see if I get my regular reboot after 10 minutes of Google navigation.

I was using sobe's .35 kernel and the camera worked at first but lately wouldn't work at all and I saw that the camera was supposed to be working well with this. Flashed it a little while ago and haven't been able to take a single picture. My cpu is ondemand with a min/max 518/768.

braczkowski said:
I was using sobe's .35 kernel and the camera worked at first but lately wouldn't work at all and I saw that the camera was supposed to be working well with this. Flashed it a little while ago and haven't been able to take a single picture. My cpu is ondemand with a min/max 518/768.
Click to expand...
Click to collapse
i honestly think that right now some of the camera stuff is phone specific.. because i know some people have no issues, asome people have intermittent issues (me), and some people lose it all together.. but thats how it was with s0be's version as well, i think until most of the camera bugs are squashed we will continue to see random issues for random people..
BTW since you already cant use the camera, try switching to interactive for the governor, and try it then.. jaybob said that his works fine with interactive, so maybe your phone will respond better with it.. just a thought, no promises..

352 min cpu fixed my camera issue.

[Kernel] Dragon-G2x v1.5.2 (CM7/Trigger) <Fix Boot on 173+> [10/19/2011]

APN Fix: The work here was done by cm_acree, I provided testing and reporting, nothing more. Thank him. I have noticed one issue testing this build, which could be my fault. Rebooting from the menu to recovery (I have clockwork installed) then rebooting from clockwork back to CM7.1 breaks data. Reboot from the power long-press menu, and it comes right up. But how often do we hit recovery?
FOR OTHER DEVS: To fix APN, grab the boot.img and use it's ramdisk in your build. That was the only thing I did to my kernel build to get this result. See the bug report here: http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
First off, big thanks to Faux123. This is based on his repo with a few tweaks of my own. I'll be adding more as we go on. And of course, he's welcome to pull any patches he likes from my github. Morfic also deserves top billing as of v1.3. I added a lot of tweaks from his code in the latest version.
Changes:
Added zram compressed swap support. I'll attach a script to turn it on and one to see what its status is. It's not like the older ramzswap that requires a special tool, everything is done through sysfs now. Very nice.
Added zcache compressed cache. This is a bigger win IMO, it compresses any compressible data in the cache. This means you can keep much more data in cache, which means you have to read it in from slow flash much less often.
Tweaked the low memory killer to take swap space into account, but only some of it.... This prevents swap thrashing while the system tries to kill processes and free up ram/swap. I also suggest using something like AutoKiller to set the levels to the best performance for your workload. We all run different apps and such, and that can affect how these things work for each user. There is no setup that is going to be perfect for 100% of users. Speaking of AutoKiller, I have found the advanced tweaks to help a fair bit as well. Don't use the memory management one, it overides your settings for things like swappyness. And the IO Scheduler doesn't do anything as we aren't using cfq. Unless you turn on cfq...
On Swap and compression:
While badly configured swap can slow things down, it's far more complex than people think. It also frees up RAM that's not being used frequently for apps that are. So your system can more efficiently use the resources it has. While compression does use some CPU time, our dual core 1Ghz+ CPUs can compress/decompress REALLY fast. Far faster than reading from the flash storage. In theory, this can affect battery life, though I haven't seen any significant issues from it.
Q: But we have 512M, that's a LOT!
A: Well, kind of... Not all of it is accessible to the kernel for running apps. 128M for the GPU, some for the cameras, wifi, etc... In the end, a little less than 400M is available. Then you have to add in system overhead from the kernel itself, Android's OS processes, etc.. That is quite limiting, IMO, so using it more efficiently is important to me.
Q: I don't like compression/swap.
A: Then don't run this kernel.
Download 1.5.1 (older cm7 builds): goo.gl/B2LSW
Download (CM7/Trigger) v1.5.2: http://goo.gl/rl7VY
Scripts: http://goo.gl/M4SzG
Code:
Changelog:
v1.5.2
* Added patch from CM repo for booting 173 and newer builds.
v1.5.1
* Possible BT/CAM fixes (Change clock options based on Morfic's info)
* Integrate some config changes
v1.5
* Possible SOD fix from vork/CM
* Faster SHA-1 from kernel git
* Faster memcpy/memset from kernel git
* Various other patches from the kernel git
v1.4.1
* Updated ramdisk for the latest APN fixes
v1.4
* Disappearing APN fix from cm_acree
* Misc. little fixes
v1.3
* Added morfic's changes to the voltage control code
* Increased voltages
* Added JRCU patch from morfic's repo
* Tweaked various VM options also per morfic's repo
* Made deadline scheduler the default
v1.2.2
* Update to work with latest CM nightly builds
v1.2
* Updates from the CM repo
v1.1
* Update various drivers from the LG source drop
* Increase voltages and switch to max 1.5Ghz
* Switch to the CM based battery driver

Great to see you back, ttabal! Been missing your work since the dragon kernels on the Vibrant. Always nice to find another dev working on the G2x! Looks alike a great start to an aggressive kernel, just what we need
You have any plans of working on a kernel based off the LG's OTA 2.3.3, the source was released last week?

Thanks bro. how do we run the script to turn on/check.

use a terminal emulator to cd to sdcard/scripts folder and type "su" then "sh enable_zram.sh" all without the quotes.... am i right? i did it and the command ran just fine and applied...

fcisco13 said:
Thanks bro. how do we run the script to turn on/check.
Click to expand...
Click to collapse
Unzip the scripts.zip and use gscript or Script Manager to run them... you can also just run them in a shell if you prefer. Lots of options. They are to run on the phone, not your computer.

zimphishmonger said:
Great to see you back, ttabal! Been missing your work since the dragon kernels on the Vibrant. Always nice to find another dev working on the G2x! Looks alike a great start to an aggressive kernel, just what we need
You have any plans of working on a kernel based off the LG's OTA 2.3.3, the source was released last week?
Click to expand...
Click to collapse
Thanks man! Still getting up to speed on the OC options and such for Tegra, but looks easy enough. I'll be getting dirty later, this is just to get started. I've already got the source building thanks to Faux again, just need to get an OTA based ROM installed so I can test it. If only the dual boot thing worked on G2x, would save me some time. Owell. I sent that dev the info he should need to make it work... don't know what the deal is.
Anyway... nandroid almost done... time to try booting.

thanks ttabbal your way was easier... i am just used to shell... lol i was going to give him a breakdown of the script.... thanks....

I loved your stuff on the vibrant and hope to see more of the same with the G2X.

Awesome! Bring some of the Dragon love here to the G2X. My other Vibrants are still rockin' your kernels dude!

What should happen when i run script with script manager??
I get setting up swap space version 1 size =xxxxx

Thanks. Love seeing new devs
Sent from my LG-P999 using XDA Premium App

ttabbal said:
Thanks man! Still getting up to speed on the OC options and such for Tegra, but looks easy enough. I'll be getting dirty later, this is just to get started. I've already got the source building thanks to Faux again, just need to get an OTA based ROM installed so I can test it. If only the dual boot thing worked on G2x, would save me some time. Owell. I sent that dev the info he should need to make it work... don't know what the deal is.
Anyway... nandroid almost done... time to try booting.
Click to expand...
Click to collapse
Excellent! Cant wait for one of your kernels. Feel free to PM or DM me if u need a test.
Glad you got the source compiling w/o issue (I know Faux was having major issues w/ that and maintaining stability), now u just gotta make sure you dont have the same freezing\"black wake screen" issue and you're solid. From what I hear, Tegra's CPU governor is really different from other chips, and its very sensitive\strict to voltage changes in between stepping (<=100mv per stepping). I'm running OTA (well, WeaponG2x, but thats OTA based) FT at the moment cause I use A2DP, but I jump back to CM every once and a while when major developments happen. Feel free to shoot me a test if u need another device to try your code on. More than happy to help!
Crossing fingers for the boot

Same here but I'm on weapon also, we need an oc-uv kernel
sooo bad for the ota. no ones made a working one yet for 2.3.3 it would be much appreciated Sent from my LG-P999

KingDavid63 said:
Same here but I'm on weapon also, we need an oc-uv kernel
sooo bad for the ota. no ones made a working one yet for 2.3.3 it would be much appreciated Sent from my LG-P999
Click to expand...
Click to collapse
Haha I spy a typo in your signature.

Uh oh it is oc and uv got us a mac book made kernel, lets hope it don't freeze and I'll be one happy man. Thanks dude!
Edit: didn't get as far as script with ota kernel, froze 10 minutes in had to do a battery pull, if you need a log cat just say the word...
Sent from my LG-P999

when i apply this with script manager whats it suppose to say? how do i know it worked?
and do i have to do it everytime i reboot? or just check the box root and run at boot when i apply?
thanks in advance

Hey man voodoo included?,
Very nice kernel dude! Good job man

This kernel is smooth as silk. I can't wait to see how you improve on it
Sent from my LG-P999 using XDA Premium App

moeahmad1995 said:
Thanks. Love seeing new devs
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
+ 1 ttabal is a badass kernel dev. He did awesome stuff for the vibrant with his dragon kernels.
This kernel is solid , nice work. Running the script as well and all seems really smooth.
Sent from my LG-P999 using Tapatalk

This work for eagle blood 2.3.3???
Sent from my LG-P999 using XDA App

Public Beta testing now open for WildKernel

As some of you may know, I've been working on a custom kernel for ICS/JB and its about done (for a first release). Current kernel features include: (If feature begins with a * then check below for more information)
Compatible with all AOSP ICS & JB roms
rebased to CAF Linux 3.0.40 kernel
Built in Low-memory killer w/ Fugeswap (as seen in the v6 Supercharger)
Optimized ram usage/handling (Swap & Zram)
Increased Wi-fi connectivity range
*Low & High power Wi-fi scaling steps
*Badass Governor (Default)
Lazy Governor
Imported Snapdragon optimizations used by the Sensation (Thanks Romanbb)
Lagfree Governor
Fast charging for unknowns
HIGHLY Tweaked for the perfect battery life and performance
Updated Bluetooth code from CAF
V(R), simple, deadline, noop, and CFQ I/O schedulers
*Ondemand & Intelli(gent)demand Governor
Stable Undervolting of the CPU
increased SDcard readahead speed
Tweaked Flashlight
Added more clock steps to the GPU for compatibility with low power browsing and GPU OC @ 320 mhz
I think 6 testers should be enough for now, thanks for participating
If you wish to join in this this beta testing please feel free to shoot me a PM or hit me up on GTalk @ [email protected]
You may find my source hosted @ Github
Current testers (in order of request sent):
AgentCherryCola
sino8r
onebornoflight
phone77
jjbz
WeekendsR2Short
CoNsPiRiSiZe
More information:
Badass Governor: This governor has built in profiling (like used in SetCPU but not as battery & Ram consuming). This is also the default and highly recommended governor. This governor features a 3 phase system CPU profiling system. This will change your CPU speed based on usage. This saves a lot of power as your speed doesn't just keep at one clock no matter how much your using you phone. A similiar profiling system is also used for the GPU and such.
Ondemand and Intellidemand Governor: Intellidemand is based off the Ondemand governor but features a 2 phase CPU profiling system with some added tweaks.
Wi-fi Low and High power scaling steps: This is a feature that will determine whether to use High or low power voltages on the Wi-fi chip to save battery. eg: Wi-fi will be turned to low power when idle or screen off. Wifi will be turned to high power when actively in use or in progress of a download. Take note that high power wi-fi voltage isn't necessarily "High" power but more of just "Stock HTC" power.
Thanks:
TeamDS
Strapped365
faux123
showp1984
RomanBB
and any others I may have missed

I'll test out this Kernel. I'll test CM9, AOKP, and MIUI.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

I'm ready!
ditto dude... thanks!

Il do it!
::Respect::

So how's the kernel testing going out guys! This looks really promising
Sent from my myTouch_4G_Slide using Tapatalk 2

Ok I think thats enough testers for now, Testing will begin soon just making some final adjustments

Quite psyched to check this out!
Sent from my HTC MyTouch 4G Slide using xda app-developers app

sorry for the delay, Ive been troubleshooting battery issues which started after upgrading past 3.0.30, im thinking about downgrading back to that version to see if the problem persists

xmc wildchild22 said:
sorry for the delay, Ive been troubleshooting battery issues which started after upgrading past 3.0.30, im thinking about downgrading back to that version to see if the problem persists
Click to expand...
Click to collapse
Battery issues are nothing new with the latest kernel commits. Just take a stroll through the CM9 thread
Honestly, I've seen better battery life on the old 2.6 kernel

gtmaster303 said:
Battery issues are nothing new with the latest kernel commits. Just take a stroll through the CM9 thread
Honestly, I've seen better battery life on the old 2.6 kernel
Click to expand...
Click to collapse
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::

CoNsPiRiSiZe said:
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
Click to expand...
Click to collapse
Yea, I don't know how you do it... Possibly a fluke, or just your setup

CoNsPiRiSiZe said:
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
Click to expand...
Click to collapse
Then I'll make sure to include the "Conspirisize ultra performance" version

Soooooo how about that kernel release for all of us (;
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

I think his Kernel was lost in Goo.Im crash.
::Sense 4.0::

I believe he had most of it on Github?

WeekendsR2Short said:
I believe he had most of it on Github?
Click to expand...
Click to collapse
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE

strapped365 said:
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
I had 30+ commits that I were going to push to git fixing a lot of problems but my hard drive fried at the same time goo went down. (I have a live network backup of my hard drive hosted on goo) So I lost those commits.

strapped365 said:
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
Well CRAP! :crying:
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
..
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
xmc wildchild22 said:
I had 30+ commits that I were going to push to git fixing a lot of problems but my hard drive fried at the same time goo went down. (I have a live network backup of my hard drive hosted on goo) So I lost those commits.
Click to expand...
Click to collapse
..