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.
Related
I've compiled a kernel for Cyanogenmod 7 that OC's up to 1.8ghz (along with a few other tweaks I forgot about). Just use setCPU. It's pretty much Kali-'s kernel, but with a few minor config changes that I just had to enable. If you feel the need to donate, please donate to Kali- as I just changed around a few files. A few more tweaks will come around as soon as I have spare time (school's a b*tch sometimes and I have a tattooing apprenticeship to juggle). Just request what you guys want for the next version and I'll do my best to add it.
Thanks to Kali- and the rest of the cyanogenmod team for creating our port, and to everyone who helped them out. Hope I'm not violating anything by posting this.
DOWNLOAD:
http://www.mediafire.com/?pq7y7sb5dhz1fnv
TO DO LIST:
edit OC Code, attempt to make more stable
Add BFQ
Add SLQB
Add 122mhz at 850 mv (if possible)
How to install if you're already on CM:
NANDROID! NANDROID! NANDROID!
move zip to /sdcard
flash with ROM Manager
SetCPU it!
PROFIT
Source: https://github.com/DOAlaboratories/cm-kernel
1.3.2-
Updated CPU Freqs once again, hope have gotten it stable again...
Added VDD levels sysfs interface (edit your voltage tables through "/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels")
Re-patched SLQB, should be better now
Added BFS scheduler
Increased GPU memory allocation
1.3-1.3.1-
Internal Releases
1.2-
Added SLQB allocator
Set BFQ as default
New OC Code (should be more stable)
1.1-
Fixed Wifi
added [email protected] step
1.0-
Initial release
CREDITS:
Lee, for helping me get my VDD levels set up and the GPU mem alloc tweak
snq-, for the original VDD patch for the original desire
Kali-, first and foremost, for making our original kernel for CM7
Must....resist...urge to make CM7 even faster...
Sent from my CM7 Inspire
Good job. My request kindly post the user manual guide for installing this CM7 or send me PM. I will post. Thanks
1.1 coming tomorrow with the [email protected] step It seems stable enough for a daily driver.
1.1 is up!
will this work for MIUI as well?
how stable is this?
ogwilson said:
how stable is this?
Click to expand...
Click to collapse
seems pretty stable right now. a few reported crashes but it's alright.
I had a few issues with 1.0 @ 1.8, just updated to 1.1 and went to 1.7.
This is perfect, was just looking around for how to go past 1.2
LOL 1) Put your source up
LOL 2) Compile a proper wifi driver module
LOL 3) I don't think you know how the kernel works if you can't even compile a proper wifi module.
Watch your language, remember you are a senior member
1)I'm new to kernel compiling.
2)the source is going up today.
3)if you have a problem with me posting this, compile this **** yourself and don't troll. I do this out of my free time, I'm busy as hell, and I don't ask for donations. I'll put up the source later so you can do it yourself and post it better.
Sent from my Desire HD using XDA App
maxisma said:
LOL 1) Put your source up or GTFO
LOL 2) Compile a proper wifi driver module
LOL 3) This OC is BS and I don't think you know how the kernel works if you can't even compile a proper wifi module.
Click to expand...
Click to collapse
Lol, at this guy. Give people a chance to learn. Judging from your other posts you seem to be doing the same to other people who want to learn but don't know stuff yet.
If you know a lot now, you didn't always. These people are at that stage, give them a chance rather than posting comments that don't advance the discussion or help them in an way.
DOAlaboratories said:
1)I'm new to kernel compiling.
2)the source is going up today.
3)if you have a problem with me posting this, compile this **** yourself and don't troll. I do this out of my free time, I'm busy as hell, and I don't ask for donations. I'll put up the source later so you can do it yourself and post it better.
Click to expand...
Click to collapse
+1
Speaking of wifi, is anyone having problems with it on 1.1? It works perfect on my phone and I'm on CM7RC1, but I haven't tested it on nightly 8.
Sent from my Desire HD using XDA App
Benchmarks?
Wow 1.8 ghz is fantastic...good work!
Have you tried the Quadrant/Linpack to see what kind of results this overclock can achieve?
I'm predicting very high benchmark scores for this.
wifi is fine for me on 1.1
Thanks again for doing this.
kvs678 said:
Wow 1.8 ghz is fantastic...good work!
Have you tried the Quadrant/Linpack to see what kind of results this overclock can achieve?
I'm predicting very high benchmark scores for this.
Click to expand...
Click to collapse
I got about 61 on linpack and 2700 on quadrant
Sent from my Desire HD using XDA App
Nice to know, pretty good for single core.
Anything you guys want to see in 1.2? And source should be up about 6pm Pacific.
Sent from my Desire HD using XDA App
Tried this Kernel and it is not very stable for me.
I get constant phone freezes at 1.7 and 1.8Ghz.
I have tried the other Kernels available , Genocide, Twilight etc. The performance gains are real and it is amazing what the developers are doing.
However I have significant instability with these Kernels compared to Stock. I use my phone for business and stability is #1 priority for me. The only fix I really need is the skipped key press bug. I am running stock now but the keyboard is unusable without the fix.
Would one of the developers that knows what they are doing have time to compile a stock kernel with only the skipped keyboard fix implemented?
Thanks!
violinbf said:
I have tried the other Kernels available , Genocide, Twilight etc. The performance gains are real and it is amazing what the developers are doing.
However I have significant instability with these Kernels compared to Stock. I use my phone for business and stability is #1 priority for me. The only fix I really need is the skipped key press bug. I am running stock now but the keyboard is unusable without the fix.
Would one of the developers that knows what they are doing have time to compile a stock kernel with only the skipped keyboard fix implemented?
Thanks!
Click to expand...
Click to collapse
The closest thing I've found is this:
http://forum.xda-developers.com/showthread.php?t=1039991
I'm like you, I want stability above all else and I only wanted the skipped keyboard fix. I don't care about overclock/undervolting and what not. Just want something stable. Although this kernel has some other minor changes, it's pretty much stock.
I just flashed this kernel this morning and haven't had any issues thus far but it's only been a few hours.
I'll report back tomorrow and let you know if I run into any issues.
Wrong section dude this need to be in general.
Sent from my SPH-D700 using XDA Premium App
Clean Kernel EC05 should suit you well, and finally has a proper post here:
http://forum.xda-developers.com/showthread.php?t=1053252
It has no volting done, and has the same performance as the stock kernel.
Hope you like it!
DRockstar said:
Clean Kernel EC05 should suit you well, and finally has a proper post here:
http://forum.xda-developers.com/showthread.php?t=1053252
It has no volting done, and has the same performance as the stock kernel.
Hope you like it!
Click to expand...
Click to collapse
Just wanted to say thanks again for compiling that kernel. Downloaded voodoo controller from the market as well. Didn't realize what I was missing as far as sound quality!
Not to rudely question your decision, but have you tried any customs that support voltage control? (Currently only genocide, but twilight is promising it soon). I used to have terrible instability, but it was because my phone couldn't handle undervolting... genocide + voltage control removing undervolt fixed that.
On a side note, if you decide to try genocide make sure you go to the end and look for the 1.0.1 test build, it fixed the kswapd0 high cpu usage bug (rare, but definitely made the phone less stable). I've had 18 hours of perfect uptime (not battery of course) since installing the update, and I have large tendancy to max out my phone.
Sent from my SPH-D700 using XDA App
I'd like to have stock, ext4, and keyboard fix. Stability is my #1 priority as well...that being said, I'm running the Genocide kernel at stock speed, and it seems pretty stable. Been using now for a matter of weeks.
Sent from my SPH-D700 using XDA App
Thread in the wrong section. Please post in the proper section. Thread closed.
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
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).
Also I was previously planning on a beta testing for a selected few, but I released I won't have enough time to be hosting testing sessions, so how about this. The kernel is know free to use for the public, but all I ask is that your report and compare. I'd like to see if there's improvement or loss between the A6 kernel and this (battery, performance, etc.). Also please report anything good and bad so that I know what to keep and what not to keep for a final release. This also helps me push out fixes faster when presented with lots of information.
Current kernel features include: (If feature begins with a * then check below for more information)
Universal kernel compatible with all AOSP (NOT SENSE) ICS & JB roms
rebased to CAF (custom) Linux 3.0.39 kernel
Optimized 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
Lazy Governor
Imported Snapdragon optimizations used by the Sensation (Thanks Romanbb)
Lagfree Governor
Fast charging for unknowns and when plugged in to computers
HIGHLY Tweaked for the perfect battery life and performance
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
Please wipe cache and dalvik cache
I dont suggest using SetCPU as it may cause bugs such as reboots, use CM or AOKP's built in cpu speed feature
Download Universal flasher for ICS and JBhttp://www.mediafire.com/download.php?q9bhv68k8dvai13
(Flashable for S-ON coming tomorrow when I have time)
You may find my source hosted @ Github
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. Ondemand also now has early suspend support for low power browsing to save battery.
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.
View all public kernel releases
Changelog:
Code:
[B]Sep 3 - ver003[/B]
1. Bluetooth updates upstream
2. Downgrade to linux Kernel v3.0.39 with custom libs to *really* fix lag
3. Badass back to default governor as the most stable
4. More LMK tweaks
[B]Sep 2 - ver002[/B]
1. Implemented USB forced fast charge v3.1
2. Downgrade to linux Kernel v3.0.40 to fix lag
3. Ondemand tweaks, early suspend updates, and is now default governor because of balance of stababilty, battery, and speed.
4. LMK tweaks
5. Updates to bluetooth from CAF (more battery saving and stable)
6. Updates to scheds from faux
7. mpdec ready but disabled until stabalized
8. A lot of improvements since ver001
Thanks:
TeamDS
Strapped365
faux123
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
reserved for James (He'll be supplying statistics such as battery reports, cpu logs, benchmarks etc.)
Post statistics and they will be copied here
Nice
Hastily spouted for your befuddlement
Awesome. Hope this fixes the battery drain problem from the A6 kernel.
Sweet. Will test tonight.
Il test this but not until Saturday morning will I have solid feedback
I'm going to have to use both Ankers plus my stock battery for tomorrow as I have school, then a football game, then a roadtrip so I will definitely take shots and post back with great contrasts I'm sure
Thanks XMC
::Respect::
---------- Post added at 10:02 PM ---------- Previous post was at 09:31 PM ----------
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Sorry wild, can't get it booting. Been trying forever. I'll redownload again when I get home.
P.s: it boots, but it goes right into a reboot after I hit homescreen. I don't think I can use alogcat to pull one, so I'll have to wait till I get back to my computer. Perhaps a dmesg a well.
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Riyal said:
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Click to expand...
Click to collapse
Hey maybe even if xmc your planning on doing a sense one... Maybe if no offense allow Riyal access to those things as you might learn from his enhancements to a sense kernal and such... Also additional development for DS
:what:
::Respect::
well im on my computer. the error (though im no expert) seems to be here
if you need the full logcat let me know and i'll try grab it again. that's the error going on right when the homescreen gets laggy on boot, right before it reboots.
i don't know if this is important to you, but this is what i get in logcat right before reboot
I'm sure i followed directions. I hope I'm not doing something wrong.
Edit: yep. Definitely not an expert. So it stopped rebooting after I unchecked "set on boot" under performance. Will be reporting back.
CoNsPiRiSiZe said:
Il test this but not until Saturday morning will I have solid feedback
I'm going to have to use both Ankers plus my stock battery for tomorrow as I have school, then a football game, then a roadtrip so I will definitely take shots and post back with great contrasts I'm sure
Thanks XMC
::Respect::
---------- Post added at 10:02 PM ---------- Previous post was at 09:31 PM ----------
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Click to expand...
Click to collapse
I flashable for S-ONs will come soon sorry
Riyal said:
You also plan on making something for sense ROMs?
If not would you mind if I grab your patches and implement it to a more enhanced virtuous kernel?
Click to expand...
Click to collapse
to be honest I hate sense and I doubt I'll be developing anytthing for it anytime soon.
Riyal, i'm open source so feel free to do whatever you wish. If you need help with me pointing out specific commits lemme know
ekoee said:
well im on my computer. the error (though im no expert) seems to be here
if you need the full logcat let me know and i'll try grab it again. that's the error going on right when the homescreen gets laggy on boot, right before it reboots.
i don't know if this is important to you, but this is what i get in logcat right before reboot
I'm sure i followed directions. I hope I'm not doing something wrong.
Edit: yep. Definitely not an expert. So it stopped rebooting after I unchecked "set on boot" under performance. Will be reporting back.
Click to expand...
Click to collapse
are you using setcpu?
No, I'm running cm 9.1.0. Under settings > performance > cpu settings or whatever it is, if you have set on boot checked, the phone runs funny. I unchecked it in a desperate attempt to figure out what's going on, and it's been pretty stable ever since.
xmc wildchild22 said:
reserved for James
Click to expand...
Click to collapse
LMAO! :laugh: You GO James!!! :good:
CoNsPiRiSiZe said:
CRUD! I got to my PC, downloaded it and read its not in Boot.img format! IM S-ON D:
Click to expand...
Click to collapse
Can't we just extract the zImage from the universal kernel flasher, rename it boot.img, and flash? I thought they were analogous...
Edit: I tried it. Didn't work. "Boot Magic check failed". Guess I was thinking of Samsung devices. Bummer, I really wanted to try this.
Ok after a 10 minute self lesson on kernel kitchen I managed to compile a boot.img. Booted right up but I had nofrills with an "apply on boot" setting which screwed me over. Severe lag. I managed to access that app in slow motion and deselect the apply on boot nonsense. Now we are in business
Don't forget to uncheck all governor apply on boot settings before flashing! Also, on first boot go to a view CPU frequency place on your phone so you can wait until the phone settles before rebooting/doing stuff. Takes a little longer than you would expect.
So far the performance seems good, I'll report back on battery life later.
Edit: 3 consecutive reboots during 3 consecutive calls. Switching back to 3.0.30 (A5) for now. Since I didn't flash this officially I'd take this experience with a grain of salt but it is similar to what ekoee is reporting so IDK.
Hi xmc! Not that I question the knowledge of the senior htc community developers here but this battery issue I am facing with ROMs like virtuous is already nagging me out.
Now compiled yours and shocked that it also has the battery bug.(The not going to 100% bug)
So I decided to really look up the battery driver carefully awhile ago and noticed something strange in it. I noticed this days ago and thought this was ok but thought I would stand up and ask today.
In
arch/arm/mach-msm/htc_battery_8x60.c
htc_batt_get_battery_info
Could you tell me why calculation of battery is like this?
htc_batt_update->batt_current = htc_batt_info.rep.batt_current - htc_batt_info.rep.batt_discharg_current;
Click to expand...
Click to collapse
instead of this?
htc_batt_update->batt_current = htc_batt_info.rep.batt_current;
Click to expand...
Click to collapse
Seems like the batt_discharg_current is making my battery report less than the real value so I'd like to know why is the calculation like that?
I'm sorry for asking but I think you're the only developer on doubleshot who is approachable enough for me to ask to.
Riyal said:
Hi xmc! Not that I question the knowledge of the senior htc community developers here but this battery issue I am facing with ROMs like virtuous is already nagging me out.
Now compiled yours and shocked that it also has the battery bug.(The not going to 100% bug)
So I decided to really look up the battery driver carefully awhile ago and noticed something strange in it. I noticed this days ago and thought this was ok but thought I would stand up and ask today.
In
arch/arm/mach-msm/htc_battery_8x60.c
htc_batt_get_battery_info
Could you tell me why calculation of battery is like this?
instead of this?
Seems like the batt_discharg_current is making my battery report less than the real value so I'd like to know why is the calculation like that?
I'm sorry for asking but I think you're the only developer on doubleshot who is approachable enough for me to ask to.
Click to expand...
Click to collapse
I'll take a look once I get home. Lol and just to be clear, i'm not the only dev for the DS. We got Blue6IX, jeffakajeff, strapped365, tbalden, Riyal , kornyone, and nbetcher. (Dont kick my a$$ if I skipped your name )
Flashed this with a fresh install of your JB ROM. Phone is really laggy when waking from screen off for a few seconds but then its ok. I'll look more in to this but thats what I'm seeing so far.
Flashing over CM 9.1 now, will test it out and report back with results. Really hope this takes care of the battery drain issue in 9.1.
xmc wildchild22 said:
I'll take a look once I get home. Lol and just to be clear, i'm not the only dev for the DS. We got Blue6IX, jeffakajeff, strapped365, tbalden, Riyal , kornyone, and nbetcher. (Dont kick my a$$ if I skipped your name )
Click to expand...
Click to collapse
Lol! If I were a dev here I wouldn't have asked you this woot now I'm an ass kicker :highfive:
The goal of this ROM and kernel is to tweak voltages as much as possible and adding overclocks where necessary. I first aim for extra battery life and then the speed improvements will arrive.
Reason for starting this ROM is that I want my own stable ROM, with extra battery and speed just the way I want it.
Instead of making a github account I will upload my patch sets to comply with GPL, other developers can use these patches easily
Features
- More speed
- More battery
- Tweaked governors
- Removed crap
Downloads
- https://sites.google.com/site/jonashendrickxcommunity/
Changelog
- https://sites.google.com/site/jonashendrickxcommunity/
Iam a bit confused.
Sent from my Nexus 7 using Tapatalk 2
based on latest cm10? kernel?
CM10 is actually not very good for the Nexus 7. The builds are unstable and it's not working properly yet. For now I stick with building AOSP ROMs for the Nexus 7
I need to know to the device manager is for the Nexus 7 so I can push my changes.
Until then I refuse to work for CM10. I tried their latest build and I did not like it at all.
I am still experimenting with programming for the Nexus 7.
Due to lots of school work Java, ADO .NET 4, Networking, Math in my university I have not much freetime. I also have a Google Nexus to manage. Again there CM10 is also unstable, and they refuse to accept my patches, which are known to fix those problems they are having. But I have been using those patches because they helped for me.
I have applied to join the AOKP team. I am still waiting for an answer.
Would love to try it out, but the service you're using to offer downloads 1) pops up porn ads and 2) won't let me download after I tried clicking had to wait, and came back to it 10 min later.
Seems like you're in it more for the income you could make and not the user experience, yeah?
djjonastybe said:
CM10 is actually not very good for the Nexus 7. The builds are unstable and it's not working properly yet. For now I stick with building AOSP ROMs for the Nexus 7
I need to know to the device manager is for the Nexus 7 so I can push my changes.
Until then I refuse to work for CM10. I tried their latest build and I did not like it at all.
I am still experimenting with programming for the Nexus 7.
Due to lots of school work Java, ADO .NET 4, Networking, Math in my university I have not much freetime. I also have a Google Nexus to manage. Again there CM10 is also unstable, and they refuse to accept my patches, which are known to fix those problems they are having. But I have been using those patches because they helped for me.
I have applied to join the AOKP team. I am still waiting for an answer.
Click to expand...
Click to collapse
Since this is based on aosp, I'm guessing that there isn't notification toggles?
Edit: I'm very interested to try this. awaiting your answer
anyway the site you host your rom on doesn't allow me to download, it says i exceed the daily limit. if you intend to go far with this rom please at least share it on a more accessible site, maybe google docs?
nihonjintaylor said:
Would love to try it out, but the service you're using to offer downloads 1) pops up porn ads and 2) won't let me download after I tried clicking had to wait, and came back to it 10 min later.
Seems like you're in it more for the income you could make and not the user experience, yeah?
Click to expand...
Click to collapse
I will use zippyshare as an alternative mirror.
About the porn ads, I don't know but they don't come from rapidgator thanks for sharing your freetime activities.
I am in it for the user experience. Since I use the rom and kernel myself 24/7 and I don't like to flash roms and kernels.
bervin said:
Since this is based on aosp, I'm guessing that there isn't notification toggles?
Edit: I'm very interested to try this. awaiting your answer
Click to expand...
Click to collapse
I am still trying to find a commit that gives me these notification toggles. You can always help me finding them. Eventually they will arrive. At least I hope they do. I am doing my best.
My main goal is putting extra battery life into this thing, next cleaning up the messy code from Asus or Google who-ever is responsible, next user experience. I will be mailing a few people for the dropdown notifications.
bervin said:
anyway the site you host your rom on doesn't allow me to download, it says i exceed the daily limit. if you intend to go far with this rom please at least share it on a more accessible site, maybe google docs?
Click to expand...
Click to collapse
I will upload version 2 on zippyshare and rapidgator.
Version 2 is coming with:
- Fixed power_profile.xml: it looks like the whole file was being treated as crap. The Nexus 7 doesn't have a 3260mAh battery... So I fixed that. I also fixed the cpu power consumption. Since there are no real values I hope to solve it as soon as possible to be a little more accurate. But now it looks very clean which is a huge improvement.
- Interactive governor has been nicely tweaked. Before my cpu frequency was always sitting at 1200mhz while playing Dead Trigger. I tuned:
- sustained_load: 80 --> 85
- go_highspeed_freq & go_maxspeed_freq: 85 --> 90
- min_sample_time: 30ms --> 60ms
- Extra patches from Nvidia, Google and Asus
thanks for your reply, i'll wait for v2 then. anyway i'll try to find the commit when i have free time. Hopefully you'll manage to implement it in time for v2
Same here. Can't download v1 and can't wait for v2!
If you can, you should implement these clemsyn uv to the kernel internal voltages on this thread http://forum.xda-developers.com/showthread.php?t=1903304
and also add user tweakable cpu uv via init.d script maybe? seems like a exxcellent way to save battery..
Looks very interesting this Rom. Bugless, extra battery life and then speed (though seriously even stock is pretty damn smooth) is what counts for me. On the nexus 7 not even the power widget's important let alone any other bloating features.
I'll flash on the weekend and report how it goes!
Sent from my Nexus 7 using xda app-developers app
Would you consider offering the kernel as a separate download? I'm still using your r41 kernel on cm10 and its the best kernel out there, in terms of battery life and smoothness
Verstuurd van mijn Galaxy Nexus met Tapatalk
Any info on v2?
Sent from my Nexus 7 using xda app-developers app