To All,
I have Compiled a kernel, compatible with Derartem's CM10.1 (4.2.2). It is actually a clone of DerArtems kernel tree, with overclock additions (some borrowed from Xoom and AC100).
Overclock up to 1400Mhz (1600Mhz is also available in the overclocking list, but crashes hard on my Folio, altough it uses similar speed&voltages as the Xoom) -> Update: works at 1.6Ghz (Folio can't handle the overvolting of the Xoom, but is stable at lower voltage). However.. It does not really benefit from 1.6Ghz in benchmarks (probably due to worse multipliers)
I have also changed parameters of the 3D clocks to become similar to the Xoom overclock, so it might also have overclocked the GPU (but I'm not able to test this)
In V2 I have tried to reclaim some memory. GPU uses 128Mb, but 64Mb won't work in Jelly Bean. The HDMI Framebuffer uses 16Mb, so I have reclaimed this space (result: probably broken HDMI)
->361Mb usable
In V3: LP1 state
In V4: LP2 state seems to work better than LP1 (immediate wake-up, no double click of power button). No SOD on my unit up to 1.4Ghz. Not sure what it will do for battery life in sleep (processor still goes to deep sleep state, so impact might be limited). Also first step made to disable battery alarm.
V1: only OC (1.4Ghz works)
V1 OC boot image
V2: OC up to 1.6Ghz, + some memory remapped
V2 OC+mempatch boot image
V3: OC up to 1.6Ghz, + LP1 sleep
V3 OC+mempatch+LP1 boot image
V4: OC up to 1.6Ghz + LP2 sleep
V4 V4 second download source
V4b: OC up to 1.6Ghz, buth with (standard) LP0 sleep
V4b
V5: OC up to 1.6Ghz, LP0 sleep and some clock cleanups (e.g. removed 216Mhz)
V5
V6: V5 + Workaround for 1.6Ghz SOD
V6 link
V7: V6 + Deadline I/O scheduler (can be enabled in developer mode or your favourite overclock app). Default stays the NOOP scheduler
V7
V8: Try SOD workaround on the MMC
V8 link
Source:
Source
Be careful. I'm not responsible to damages to your Folio. Overclocking might destroy your tablet
(Tough, a burned Folio it is a perfect excuse to buy a new tablet... I can really recommend the Nexus 10 or the Galaxy Note 10.1 )
How to install:
Be sure to have DerArtem's CM10.1 release (only tested with alpha2)
run these commands with fastboot (check forum on how to install this on your PC. Enter fastboot mode on the folio by 3xpower+Volume Up):
Code:
fastboot erase linux
fastboot flash linux boot-ovc.img
Overclock can be enabled in "Instellingen -> Prestaties -> Processor -> Maximale kloksnelheid"
(translated to English this should be something like "Setup -> Performance -> Processor -> Maximum clockspeed")
Don't be too quick to set the overclocking speed at boot until you tested it well.
What to expect?
1000Mhz (no overclock)
Antutu: 8211
Linpack Multithread: 80
3DMark: 1461 (on Par with a stock Xoom)
1400Mhz (max overclock)
Antutu: 11654
Linpack Multithread: 121
3DMark: 1915
Credits:
DerArtem
Nopy
m32
guevor
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100, Xoom)
EDIT (known issue): Some more SOD issues come up when putting the Folio on standby at high clocks, but it is quite stable during use.
SOD's
Apparently not everyone has SOD's, but for some it is still a problem.
- Many use advanced wifi lock: this works, but keeps the tablet completely on (hight battery usage)
- At 1.6Ghz I also have an SOD (reproducable), but can be worked around with the app "Overclock Widget". Here you can set a max speed of 1600 in use, and 1000 when screen is off. Maybe this is also usable for the SOD at 1000Mhz (set e.g. to 600 when screen is off, overclock kernel is not necessary).
Nice job spicyalan.
Just one question, why OC instructions are in german ? Does this mean that the menu will switch to german or the ui will remain as it is now ?
Onother question, whay did you try to reclaim memory ?
Thanks
miazza said:
Nice job spicyalan.
Just one question, why OC instructions are in german ? Does this mean that the menu will switch to german or the ui will remain as it is now ?
Onother question, whay did you try to reclaim memory ?
Thanks
Click to expand...
Click to collapse
They are in dutch, but you will get them in the language your system is setup.
After compiling and installing the kernel several times, I was just too lazy to set the language of my folio to "english" for explaining
(You also need to set the setup app in developer mode (tapping on the build number numerous times)
One of the problems the folio is slow in 4.2, especially task switching, is the lack of memory (even zram does not solve this).
Out of 512mb:
- 128Mb is reserved for the GPU
- 8Mb for the framebuffer
- 16Mb for the hdmi framebuffer
Setting the gpu memory to 64 works, but fails to accellerate some 3d content (even outside games). This would have worked in gingerbread, but not jelly bean. I couldn't try 96Mb (crash at boot), so it needs to stay at 128. Framebuffer is also a nono, but the framebuffer ram of the hdmi can be reused (if you don't use the hdmi)
For the SOD, more investigation is needed.
No folio ROM was ever free of SODs (not even stock), but some roms have more problems with it than others. For me, gingerbread (7.2?) And the most recent derartem was the most stable in that regard. It is not easy to know where the SODs come from, but with the overclocking, I noticed it is worse at higher overclock. I'm starting to guess it has something to do with the processor going from total sleep to max speed too fast (if you prevent cpu sleep, it also helps the sod, but using a lot of battery during sleep. Some roms did this).
Same with wifi.
I'm going to test a new version of the rom soon (derartem's version, with cm10.1 upstream, and oc kernel), so stay tuned (but be patient...)
Very nice work! Finally an overclocked kernel that can increase a bit performances.
Thank you man
Inviato dal mio folio100 utilizzando Tapatalk
I have put an experiment online with the LP state
According to tegra documentation, there are 3 states:
-LP0: shut down everything, only a few interrups can wake the device
-LP1: shut down a lot, but more things can wakeup the device
-LP2: shut down less.
If I look in the the sources, there are only 2 devboards that use LP0, and the betelgeuse (folio) is one of them. But, as all other boards can only use LP1 (andseeing the exceptionally bad SOD track record of the folio), I would be surprised if the folio as actually able to to this.
I have places a version online that uses LP1 state, that I will test (but as I don't have the problem as often, it could be nice if others could also test to confirm if it is better or not). I was not able to have an SOD today on a clock lower than 1.2Ghz.
I did experience sometimes that I have to push twice on the power button to wake it up (reminds me of CM7.2)
next to that, I also suspect the wifi driver of some SOD'in (especially in higher overclock mode). It shouldn't actually shut down in sleep mode....
Hello,
I was on the way to try V3: OC up to 1.6Ghz, + LP1 sleep but the lik seems dead...
Can you check ?
Thanks
PS: V1 works great
miazza said:
Hello,
I was on the way to try V3: OC up to 1.6Ghz, + LP1 sleep but the lik seems dead...
Can you check ?
Thanks
PS: V1 works great
Click to expand...
Click to collapse
Sorry,
Typo in the filename.
I think the lp1 sleep might nog be the answer to the sod (which is worse on higher clocks). But worth a try.
Probably the wifi driver is te cause (wifi lock is the only thing that keeps sod away at high clocks). At 1000mhz, my folio has no sod.
spicyalan said:
At 1000mhz, my folio has no sod.
Click to expand...
Click to collapse
This is really something struggleing me. I have SOD:
- every boot is I do forget to unlock my profile before of sleep (I have two profiles)
- almost every time i put the tablet in std-by
what a strange behaviour and difference...
miazza said:
This is really something struggleing me. I have SOD:
- every boot is I do forget to unlock my profile before of sleep (I have two profiles)
- almost every time i put the tablet in std-by
what a strange behaviour and difference...
Click to expand...
Click to collapse
the same is here - any action with screensaver ends with reboot
branch android-tegra-nv-3.1 i my case is stabler - i'v no sods than rel-15r7
m32 said:
the same is here - any action with screensaver ends with reboot
branch android-tegra-nv-3.1 i my case is stabler - i'v no sods than rel-15r7
Click to expand...
Click to collapse
I have compared both tree's, and it seems rel-15r7 is +500 patches ahead, but also 136 behind. Most changes are now useless (e.g. many refer to the old partition system), but I have found a few wifi and SOD fixes in there not present in rel15r7. But they need to be hand-picked and checked.
For me this ROM update-cm-9.0.0-RC0-2012.03.04-betelgeuse-KANG-signed have NO SOD.
Sometimes have a problem with WiFi connection, but when you clear all saved and then connect again, then have no problem.
Cantdownload de kernels.. it shows only another page with te text.
Or may i have to copy the text?
spicyalan said:
I have compared both tree's, and it seems rel-15r7 is +500 patches ahead, but also 136 behind. Most changes are now useless (e.g. many refer to the old partition system), but I have found a few wifi and SOD fixes in there not present in rel15r7. But they need to be hand-picked and checked.
Click to expand...
Click to collapse
Waiting for you to make the miracle...
miazza said:
Waiting for you to make the miracle...
Click to expand...
Click to collapse
No luck yet...
Most of the patches conflict, and the few others result in an unbootable kernel...
I'm not an experienced kernel developer, so I'm kind of flying blind (and using the trial and error method)
My folio doesn't show sod's that often in cm 10.1 (maybe once every 2 weeks), but is do have them at 1400mhz and up. The only thing keeping them away at this speed is advanced wifi lock.
I'm going to move the file hosting to goo.im soon (the files seem to download fine in firefox on windows, but in the default android browser, I also get a .txt.... weird)
spicyalan said:
No luck yet...
Most of the patches conflict, and the few others result in an unbootable kernel...
I'm not an experienced kernel developer, so I'm kind of flying blind (and using the trial and error method)
My folio doesn't show sod's that often in cm 10.1 (maybe once every 2 weeks), but is do have them at 1400mhz and up. The only thing keeping them away at this speed is advanced wifi lock.
I'm going to move the file hosting to goo.im soon (the files seem to download fine in firefox on windows, but in the default android browser, I also get a .txt.... weird)
Click to expand...
Click to collapse
U have to much free time ?
Cant follow U I'm like U not so expirenced in linux kernel drivers building, perhaps we can share our/ouus findings with nopy and artem ?
My folio works few days without sod - but it weakups time to time when battery goes too low - as i'm in home, i can see it - screen blinks for few seconds, derartem has ported drivers from 2.6 to 3.1. In my opinion it's worth to wait for him.
m32 said:
U have to much free time ?
Cant follow U I'm like U not so expirenced in linux kernel drivers building, perhaps we can share our/ouus findings with nopy and artem ?
My folio works few days without sod - but it weakups time to time when battery goes too low - as i'm in home, i can see it - screen blinks for few seconds, derartem has ported drivers from 2.6 to 3.1. In my opinion it's worth to wait for him.
Click to expand...
Click to collapse
Not too much time... but sometimes I have
Waking up on low battery is still normal (many phones do it), but it shouldn't sod, nor should it wake up at random
Did anyone have contact with nopy or derartem these last months?
miazza said:
Waiting for you to make the miracle...
Click to expand...
Click to collapse
New tryout online
This time with LP2, and some clock fixes. no SOD on my unit up to 1400Mhz (still at 1600).
At 1600Mhz, I just benchmarked sunspiper in Chrome: 982ms. There is now 1 benchmark making this Folio faster than a stock Galaxy Note 10.1 (2012) -> Actually, just proves that javascript is quite single threaded
spicyalan said:
New tryout online
This time with LP2, and some clock fixes. no SOD on my unit up to 1400Mhz (still at 1600).
At 1600Mhz, I just benchmarked sunspiper in Chrome: 982ms. There is now 1 benchmark making this Folio faster than a stock Galaxy Note 10.1 (2012) -> Actually, just proves that javascript is quite single threaded
Click to expand...
Click to collapse
v4 just hangs on cm splash
m32 said:
v4 just hangs on cm splash
Click to expand...
Click to collapse
Weird... Is the size correct ? (maybe something happened in the download)
EDIT: I have added a new download source... Hosting at goo.im is stll not working
EDIT2: found a trick to work around the 1.6Ghz SOD (see 1st post), might give a clue for other SOD's?
According to kernel code, the CPU is set to max speed when resuming (max speed during board initialization might be a bad idea). I think this should be throttled (e.g. 600Mhz) until the screen is on. This can be simulated with overclock widget and its "screen off clockspeed profile".
Again something to test for someone with SOD's
I'm right now testing v4 at 1600. It looks stable. Nice job.
Edit: when the tablet goes to sleep with the blinking led I cannot wake it up. I need to maintain wakelock at 5.
Sent from Folio 100 using tapatalk
Related
*** THIS IS EXPERIMENTAL ***
Thanks to toastcfh, maejrep, AssassinsLament, Estimated Prophet, Cicatrize, joeykrim, geyes30, kpkimmel and all the others from the kernel & display cap threads who have been working tirelessly, and continue to do so. This isn't over until we can find the real cap! But I think this avenue has progressed enough for it to have its own thread, if only to give hope, since we now know both Epson and Novatek panels physically can do it!
What Doesn't Work
Nothing. Now based on the official kernel with everything working.
About This Kernel
This is just a dirty hack. We haven't yet figured out where the real cap in framerate is coming from. But until we do, this is the best we have. At least it shows the display itself can handle a higher framerate and isn't physically incapable like HTC would have us believe.
Novatek panels can now get up to 46fps pretty reliably. Run fps2d a few times.
Stdev depends on system activity. If you're going to be judging stdev, DON'T measure it immediately after booting, set your CPU throttle mode to "performance", be sure to run fps2d several times, then average those stdev numbers in your head.
The changes are now immediately applied upon boot. There is no need to cycle your display anymore.
This kernel has support for overclocking/underclocking, up to 1.119 MHz. Also includes my own undervolting and overvolting for higher speeds to increase stability.
You can get dramatically tighter stdev numbers by setting your CPU governor to "performance" in SetCPU. It seems scaling really messes with the framerate. Obviously this will drain your battery faster, as your CPU will constantly be running at full speed. Set it back to "ondemand" if you don't need it.
Some people are reporting their touchscreen grounding issues have been cured.
Support to change the T2 value on the fly [thanks to maejrep]
Support for 5 simultaneous touch points! Use Dotty (in the Market) to see it in action. It'd be cool if someone would make a simple app to demonstrate what can be done with more than the mere 2 points we are used to. People have suggested new lock types, security locks, ways to rotate things, etc. [thanks to maejrep]
Some hardware fails to accept 5 points, so a fail-safe has been added to default back to 2 points for some EVOs
AssassinsLament has created an awesome app to provide an easy way for people to change their T2 timing. Check out his app here: http://forum.xda-developers.com/showthread.php?t=716659 [thanks to AssassinsLament]
Changes to display timings are now sticky until rebooted (w/ the above app, or set manually)
What's New
v5.1.1: Using the official kernel. We've lost some fps, but we've gained camera, video, 4G, etc. 46fps is now average.
v5.1.1: Expanded user-modifiable timing settings. Change at your own risk.
v5.1.1: Audio patched [thanks Geniusdog254 and KERKEDAGAIN]
Instructions
Do a nandroid backup, and flash this over pretty much any ROM. If you have problems, you can just flash a stock boot.img again. There should never be any need to wipe anything.
IMPORTANT: This will only work with the stock bcm4329.ko! Using the newer files and flashing this kernel will result in wifi being unable to start, and vice versa. To correct this, you'll need to flash over the correct wifi files.
Changing Timing Settings
You can use the following commands from adb shell to temporarily change timing on the fly. Do it while your screen is on.
Set: echo NUMBER > /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Check: cat /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Parameters:
t2 - 245 to 1023 [Default Eclair: 437, Froyo: 432]
t3 - 0 to 7 [Default Eclair: 1, Froyo: 0]
fte - 0 to 879 [Default Eclair: 35, Froyo: 60] (Frame Tearing Effect, change this if you have tearing problems)
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Note: Certain things like the camera still don't work, since our Froyo ROMs aren't official.
Flashable ZIP - WiFi-N + 4G for all custom kernels based on toastcfh's GoDmOdE kernel (compatible with v5.2+)
Flashable ZIP - WiFi-N + 4G for stock/custom kernels (compatible with v5.1 and below)
Flashable ZIP - WiFi-N + 4G for the OTA kernel (NOT compatible with the kernel in this post)
*** REMEMBER! No one here is responsible if you damage your phone! ***
See the Evo, Droid X and Nexus One benchmarked together here: http://androidspin.com/2010/06/25/droid-x-vs-htc-evo-vs-google-nexus-one-in-benchmark-face-off
Want NenaMark1? It usually doesn't show in the Market, so get it here: http://nena.se/downloads.html
Awesome, just flashed and it is soo smooth, thank you devs.
This works great for me.
Not really related to this but my phone locks up when I change the cpu frequency with setcpu. EDIT: (How do I overvolt the phone?)
Oh and yes I do get 50hz.
Is there 2.2 support or no
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Nope I wish there was. Droid X skin + 50hz would be very cool.
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Second this question..I'm loving the EvolutionX froyo rom and would be sweet to get this baby on board with froyo.
Does this work for Epson panels too?
This works great. Touchscreen SEEMS a bit more responsive in in multitouch vis test. Grounding issue is nowhere near as bad, but still there. If you pull the same trick that everyone is doing to test grounding problem, you won't notice it at first, and very rarely will it stop sensing you finger all together, but it definitely does cut out for an instant every now and then, and I had it drop visibility where it normally does a few times for a split second.
Epic delete
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Can you zip your modified files and post them too? Source would be nice
sweteg said:
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Click to expand...
Click to collapse
This thread was made to avoid the clutter from the Godmode thread.
Thanks for the excellent dev work!
You might want to add to the first post that this kernel breaks 4G. it will turn on but not able to find any network.
Other than that, works as described
The device feels so much smoother!
Great work! I get 52 in fps2d, 680 in quadrant, and 51 in gears. I can't wait until this is completely fixed but I'm loving it and the undervolt and oc patches are awesome additions.
automatic brightness still does not work with this kernel though. At least not for me. Is it possible I have a different light sensor as no custom kernel has worked with auto brightness yet and other reports say it works just fine.
Also... fps2d spikes into 99 fps and at one point I watched it flash past 100
Definetly works
Installed the kernel and got over 50 fps on my nova panel i have hardware config 002 it runs much much smoother thanks devs for the hard work.
wow this kernel is insane, I mean FPS hack and overclock hack without force closes...wow is all I can say. Used the OC widget and it detects the oc clocks quickly.
Man if this kernel makes it to Froyo..Evo will be truly evil
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Mrtankjump said:
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Click to expand...
Click to collapse
My Evo has an Epson panel so I can't use this fix but, my understanding was that this method didn't cause the tearing like we saw from Toast's custom kernel on Epson displays, so your problem might be something else and not necessarily the fps cap being raised.
Thanks for the kernel, but I still have one big problem- my battery still will not charge with this kernel installed. It will only charge when I turn off the EVO and turn it back on. But as soon as I unplug and replug it in, it will look like it charges for 5 seconds, then the orange light shuts off and it stops charging. I've enclosed a dump of my dmesg. Can someone please take a look at this?
NOTICES: If you are noticing abnormally high battery drain and/or uptime, and you've updated to PRI 1.90, it has come to my attention
that this PRI has been problematic for a number of people, often resulting in large uptimes and/or poor battery life.
This issue affects people regardless of whether or not they are using a custom kernel
Downgrading your PRI and NV to 1.77 has been reported to resolve this issue.
You can find all PRI and NV versions by clicking here.
Due to troubling reports of battery issues possibly caused by the SBC battery charger modification, it is worth mentioning that by using any SBC build, you
fully assume any and all potential risks that the SBC modification may pose.
"netarchy-toastmod" is a kernel originally based on the GoDmOdE sources (Courtesy of Toast) integrating my work on fixing the fps for the Epson panels, and as of version 3.6.1, also integrating a fix for the Nova panels that does not require the use of Evo switch or manually setting any registers, etc, courtesy of work done by AssassinsLament (Well done on the nova fix). Special thanks needs to go out as well to Cyanogen and the cyanogen mod team, as a number of bugfixes and updates to the kernel in recent revisions have been ported over from cyanogen mod to enhance the overall netarchy-toastmod experience.
Click to expand...
Click to collapse
So what's in the kernel?
- Overclocking Support
- HDMwIn (As of 4.3.4)
- Audio gain tweaks (read: make it louder!)
- Fps Fixes
- tun.ko for openvpn users
- CIFS support (as of 4.2.2)
- BFS (in select builds)
- BFQ (in select builds)
- HAVS (as of 4.1.9)
- Assorted fixes/tweaks (that are sadly too numerous to list here)
- An army of rabid naked bunnies
Click to expand...
Click to collapse
The zipalign script in the kernel's modified inits is based on code in the Damage Control rom, and extended to check more places for apps.
The Dalvik code in the inits is courtesy of Ninpo/Hacre from the VillainRom team (over in the HTC Hero forums).
Click to expand...
Click to collapse
mroneeyedboh has written a handy little kernel starter guide with a lot of general information about custom kernels and various terms you might see flying around (such as cfs/bfs, havs/nohavs, etc).
You can view this guide Here
Click to expand...
Click to collapse
Current Revision: Stable: 4.3.1 - For Froyo Sense roms | Beta: 4.3.4
Click to expand...
Click to collapse
A note on multitouch:
Some of you may have used my 5point multitouch test builds with success, others with failure. Research has shown that the Evo's contain at least 2 different versions of the touch sensor, one of which does not support 5point multitouch (but it DOES support 3point). You can check which sensor you have using adb by issuing the following command: "adb shell cat /sys/android_touch/vendor" and examining the result. If your result is ATMEL_x0080_x0016, your phone can support 5point. If your result is ATMEL_x004F_x0016, your phone will only support up to 3point.
Click to expand...
Click to collapse
Disclaimer:
While these builds have been deemed generally safe, it is not feasible to account for all possible combinations of custom roms and uses,
custom roms may experience some breakage depending on how some features are set up, as these builds are not aimed at any one particular rom.
As such your mileage may vary, use these at your own risk.
Click to expand...
Click to collapse
2.2 Kernels (THESE WILL NOT WORK ON 2.1 ROMS):
These have only been tested against the rooted HTC 2.2 stock rom, they *may* work on the various custom 2.2 roms,
but this is NOT guaranteed. MAKE A NANDROID BACKUP JUST IN CASE!
Click to expand...
Click to collapse
If you get force closes on the camera, go to Menu -> Settings -> Applications -> Manage Applications -> All -> Camera -> clear data.
Click to expand...
Click to collapse
-----------------------------
2.6.32-based Kernels:
Click to expand...
Click to collapse
Beta Testing Builds
When making a post about any issues concerning beta builds, please include ALL of the
following information if possible:
1. Which kernel build(s) (ie; bfs/cfs havs/nohavs etc) are you using with the issue?
2. What Rom are you using?
3. If known, what OTA base is your rom using (ie; is it based on 3.29, 3.30, 3.70, etc)?
4. Does the issue persist if you go back to a stable kernel build?
5. The issue being experienced (obviously ;D)
4.3x:
To clear up some confusion that is apparently being spread around,
4.3x builds do in fact work on all current evo models, not just the newest model.
4.3.4:
--CFS builds--
No SBC:
4.3.4-cfs-nohavs-noUV-nosbc (No Undervolting)
4.3.4-cfs-nohavs-suv-nosbc (Static Undervolting)
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-nosbc (More Aggressive HAVS)
SBC: Use sbc builds at your own risk.
4.3.4-cfs-nohavs-noUV-sbc (No Undervolting)
4.3.4-cfs-nohavs-suv-sbc (Static Undervolting)
4.3.4-cfs-havs-less-sbc (Less Aggressive HAVS)
4.3.4-cfs-havs-more-sbc (More Aggressive HAVS)
For older beta builds click here.
---------------------------------------
Stable Kernels:
Universal Builds:
4.3.1:
--CFS builds--
No SBC:
netarchy-toastmod-cfs-havs-nosbc-universal
netarchy-toastmod-cfs-nohavs-nosbc-universal
--BFS builds--
No SBC:
netarchy-toastmod-bfs-havs-nosbc-universal
netarchy-toastmod-bfs-nohavs-nosbc-universal
These use Koush's anykernel for installation and should theoretically work on -any- rom.
*note* This is designed to be flashed over a phone that already has a working kernel of some kind flashed,
whether it's a stock kernel, or another custom kernel. In other words, if you can currently boot up your phone into whatever rom you have, this should work. ;D
The universal kernel also does not contain the tweak scripts of the normal build (ie; zipalign on boot and the dalvik tweak), it's intended to be a universally compatible kernel.
This also happens to mean the universal builds will probably work on CM
For older builds click here.
-------------
FAQ:
Code:
Havs: Hybrid Adaptive Voltage Scaling, basically tries to undervolt as much as possible to conserve power, but adapts to things like cpu load and temperature.
No Havs: Static voltage scaling, every cpu speed pulls a specific amount of power from the battery, no variation
CFS: http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Q: Do I need to be rooted to use this kernel?
A: Yes, you need to be rooted, preferably a full root with nand unlock,
Q: How do I flash this kernel?
A: Copy the zip to your sdcard, and flash it from recovery mode
Q: My phone is suddenly unstable after using this kernel and I experience
weird things like reboots or other bugs
A: Are you overclocking? Try lowering the max speed of your overclock.
If the problems stop, you were overclocking too hard. If not,
please include the following information when reporting issues:
1. Your Baseband
2. What rom you're using
3. Your software number
4. Your panel type (Nova or Epson)
5. A Description of what's happening
Q: Why can I only overclock to 1152mhz? (In builds prior to 4.1.x)
A: Frequencies above 1152 have repeatedly turned out to be unstable for
a large percentage of users, so they have been removed to
eliminate the temptation to use them (and then complain because
they are unstable ;D).
Q: Does this kernel work with 2.2 (Froyo) roms?
A: The "Froyoized" kernels do
Q: Will this kernel work with my custom rom?
A: Maybe. The general population build of the kernel should work with
*most* custom roms, but as each custom rom can have it's own
customizations, your mileage may vary. In some cases, particularly
when a lot of customizations are in the rom's ramdisk, the kernel
must be repackaged with the ramdisk from the custom rom to be compatible.
Release notes:
Code:
Notes for Revision 4.3.4
- HDMwIn support added, you still need to download the free HDMwIn app
from the android market to use HDMI mirroring
- Timer tick set to 1000hz
- Unnecessary extra debugging turned off for public builds, should result in a small speed boost
Notes for Revision 4.3.2
- Wimax code updated, 4g should behave a bit better
- SD card read ahead fixed, higher class SD cards should
have an easier time reaching their potential speeds
Notes for Revision 4.3.1
- Screen tearing issues on sense roms should be fixed
Notes for Revision 4.3
- Camera drivers updated to support phones with the newer camera sensors
- ms79723's SBC v7 mod integrated for enhanced battery charging
- Misc speed tweaks/optimizations
Notes for Revision 4.2.2
- Kernel updated to 2.6.32.27
- Conservative set as default governor again
- Conservative governor defaults tweaked
- Less aggressive build has even more relaxed undervolting to aid those with REALLY picky phones
Notes for Revision 4.2.1
- Kernel updated from a 2.6.32.15 to 2.6.32.25
- Interactive governor added and tentatively set as default in some test builds
- Smartass governor added and tentatively set as default in some test builds
- Added BFS 357 smartass builds
Notes for Revision 4.1.9.1
- HAVS has made a return, this should help improve battery life by automatically dynamically undervolting the cpu when possible
Notes for Revision 4.1.8
- Added the BFQ I/O scheduler
- Split out kernel editions, now users have a choice between a CFS or a BFS kernel, if you don't like one, try the other ;D
- Enabled shadow writes on the gpu, which may result in better performance in opengl applications
Notes for Revision 4.1.7
- Add BFS to the kernel
- Allocate more memory to the gpu, this may result in better performance in opengl applications
- A rabid naked bunny vampire has materialized under your bed. Be afraid.
Notes for Revision 4.1.6
- Users with touchscreen issues should find their touchscreen is no longer as responsive as a stereotypical wife on her 10th anniversary
Notes for Revision 4.1.5
- Banished HAVS into the fiery pits of hell for now due to its inability to remain stable with any attempts to overclock. I'll be working on this on the side for possible future re-inclusion
- Clock frequency table remains opened up, with static undervolting in place
- Thanks to l33tlinuxh4x0r for being a guinea pig and helping test this build
Notes for Revision 4.1.4
- The beast responsible for the ridiculous overclocking instability at *any* speed beyond stock has been severely beaten and castrated by rabid naked bunnies (without anesthetic)
- Update scripts redone in the interests of making sure people who have had issues flashing the kernel in the past can do so
- The conservative governor has had some more tweaks to give it better out of the box performance, but you are free to set ondemand as your governor in setcpu if you wish. (If you want to migrate to ondemand you'll also need to set it as the governor in your setcpu profiles)
- The clock frequency table is fully opened up (re-detect frequencies in setcpu to see them) As always your mileage in overclocking may vary, but for some perspective, I ran 1152 through many loops of neocore and quadrant just fine.
Notes for Revision 4.1.3
- The ondemand governor is enabled as an option (switch to it in setcpu if you want to use it, remember you'll have to update your profiles to use it as well).
The default currently remains conservative to have a balance between performance and battery.
- The small segment of users getting bootloops due to the undervolting being too aggressive should be able to boot the kernel now (though if it persists the undervolting can still be adjusted)
Notes for Revision 4.1.2
- All frequencies above 1152 should now be properly visible/usable in setcpu (You may need to re-detect speeds in setcpu first)
Notes for Revision 4.1.1
- Hot on the heels of 4.1.0, a minor versioning fix ;D (4.1.0 reports itself as 4.0.3)
Notes for Revision 4.1.0
- Adapted HAVS for the evo, this may improve battery life by allowing the cpu to run at lower voltages when possible
- The overclocking range has expanded to allow attempting to clock above 1152, Remember that overclocking is unpredictable and potentially unstable by nature, if you encounter problems overclocking, lower the speed.
- Some threshold adjustments to the conservative governor in the interest of improving performance without obliterating battery
- Wired tethering should theoretically work, however if there are problems with the app, an alternative is azilink for wired tethering
Notes for Revision 4.0.3a
- An experiment of sorts, changing from the ondemand speed governor to the conservative governor (with some tweaks), in the interests of keeping good performance with less impact to battery life.
- Rewritten update scripts to hopefully alleviate the small number of people who seem to be having a problem flashing the kernel
Notes for Revision 4.0.2:
- People having stability issues with overclocking to 1152 *may* find it is a bit more stable (your mileage may vary)
Notes for Revision 4.0.1:
- Speed range should now allow underclocking to 128mhz (You may need to re-detect frequencies in setcpu)
- The Nova panel T2 register should be changeable again (for you Evo Switch/Novareq users)
Notes for Revision 4.0:
- Updated to the latest HTC released kernel sources (2.6.32)
- Camera should now be working properly
- HDMI output should be working in Froyo again
Notes for 3.7.8b-Froyoized
- Camera should no longer take dark snapshots when using the flash, the monster responsible has been severely beaten with a twig.
Notes for 3.7.8-Froyoized
- Camera app should no longer crash when changing from 5:3 widescreen to 4:3 standard ratio
- Camera app should properly allow 720p video recording and playback
- Japanese researchers have begun construction on a mecha-rabid naked bunny, codenamed: Bunnytron.
Notes for 3.7.7-Froyoized
- Re-integrate zipalign check and Dalvik cache tweak from the 2.1 line
- Some adjustments made to bluetooth-specific audio tweaks to combat distortion
- Audio adjustments to combat background noise overpowering the voice on the other end of a call
- Set version tag correctly (har har!)
- Super-mutant rabid naked bunny successfully created in lab conditions, however it disintegrates upon exposure to reality.
Notes for 3.7.6c-Froyoized
- SDcards with ext partitions added on should now cease confusing Froyo and allow the card to be mounted properly (Special thanks to Ninpo for directing me to the fix)
Notes for 3.7.6b-Froyoized
- Touchscreen adjustments, this may fix those who had touchscreen issues with 3.7.6
Notes for 3.7.6-Froyoized:
- Compatibility with the leaked 2.2 ota (and probably other 2.2-based roms)
- Working Camera (Limited to 3megapixels) EDIT: Reports indicate it claims 3mp but actually functions at 8mp
- Fps fix (of course ;D)
- Wireless Tether is reported as working with this as well
- 4g is confirmed as working
Notes for 3.7.5:
- Toned back audio boost tweaks a little to address distortion issues
- Updated gpu code for some 3d speed improvements
- Prevented the horde of mutant hairy toe-monsters from spreading toejam
all over the thread.
Notes for 3.7.4:
- Updated bluetooth code, courtesy of cyanogenmod
(You may have to re-pair your bluetooth devices)
- A new audio boost tweak has been applied
(This should not have the issues of the previous audio boost)
- Fixed an issue that would cause some Nova users to mysteriously
revert to 30fps. (Bad nova! no cookie!)
- Successfully avoided maiming any sabretooth'd tiger-striped cows
during the production of this update.
Notes for 3.7.3c:
- Some more tweaks to default performance (when not using setcpu/overclock widget)
Notes for 3.7.3b
- Killed that damn bug monster that decided yet again to sneak into one of my builds. Bad monster! No cookie.
Notes for 3.7.3:
- Adjusted the behavior of the speed scaling governor to give better performance out of the box for people that don't use setcpu or overclock widget
- Made adjustments to the general population build in the interests of making it compatible with Apps2SD by request.(Damage control users should have already been unaffected)
Notes for 3.7.2a
- Gave the monster holding wifi and 4g hostage a spanking (read: wifi/4g should be fixed)
Notes for 3.7.2
- Tweaked Nova settings in the interests of making sure everyone with a nova panel benefits from the fps fix
Notes for 3.7.1:
- Kernel should now have 100% more working HDMI output, no really, we mean it this time!
Notes for 3.7:
- HDMI output should now work in conjunction with boosted Nova/Epson fps
- tun.ko is now included by default for VPN users
Notes for 3.6.4:
- Behold, the return of 5point multitouch! This build should now automatically enable 5point multitouch for all phones that can support it. If the phone does not support 5point, it will default to 3point.
Notes for 3.6.3:
-Removed problematic audio boost patch that was giving issues with bluetooth
-Adjusted overclocking frequency tables to remove some problematic frequencies (Yes I know a small selection of you are going to be disappointed with the lowered cap, but I felt that the problems were more important at this time.)
-Evo switch ideally should not be required for decent framerates on Nova panels, but if users desire, by popular request, they can now use Evo Switch to tweak their T2 register [U]without[/U] it resetting after a screen cycle
-Default T2 value adjusted to 370, AssassinsLament believes this to present a good balance between out of the box performance and compatibility
-No fluffy pink bunnies were harmed in the making of this build
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Awesome, I have a Novatek. /facedesk.
jerryparid said:
Can this be flashed with clockwork? Or just amon ra?
Is this a Froyo or Eclaire kernel? Any radio requirements?
Click to expand...
Click to collapse
Should be flashable with either Clockwork or Amon Ra. Theoretically it might work on Froyo, but I've only tested it on Eclair.
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
mattrb said:
This was not answered in the Godmode kernel thread. Does Camera work on this for 2.1.
Click to expand...
Click to collapse
Yes the camera works on this in 2.1
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
jerryparid said:
Just flashed on Snacks v0.8 w/ Clockwork.
fps2d, avg 53-55, ~12 std
fixes touchscreen delay
can observe tearing
camera works
screen seems to be less responsive?
Click to expand...
Click to collapse
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
imaxreed said:
me too. I am going to wait till things cool down a bit and bother HTC for another phone.
Click to expand...
Click to collapse
umm? http://forum.xda-developers.com/showthread.php?t=711964
Best kernel on my epson screen. I like how i can overclock as well
jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Thanks. I have seen that thread a hundred times but never entered it. The FPS doesn't bother me too much I am going to mess with this tomorrow i have the day off thank you.
jerryparid said:
umm? http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
Yeah i'd love to see this fix for nova
netarchy said:
I haven't noticed any loss of responsiveness on my end, if anything I'd swear it feels more responsive. Touch lag seems fairly significantly lessened.
I wonder if it could be related to the fact that I'm using a 1.47.651.1 based rom plus the latest radio/etc, curious.
Makes one wonder what all HTC changed in the update...
Click to expand...
Click to collapse
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
jerryparid said:
I just flashed back to the Snacks kernel (v0.8 is 1.47 based); there is a substantial difference in sensitivity (not delay) between the two kernels.
Click to expand...
Click to collapse
Hrmm, is it glaringly obvious in any particular app? I'd like to see if I can reproduce the experience myself.
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
krazyflipj said:
My phone keeps locking up when trying to watch youtube videos. Sorry if this is already a known issue.
Click to expand...
Click to collapse
Trying it out now, no problems with youtube for me.
Tearing doesn't seem as bad as I remember, but still bothersome.
when i seen this, i jumped into the air with my fist up like a touchdown at the superbowl.
flashing in juuusssst a second..
VoXHTC said:
Awesome, I have a Novatek. /facedesk.
Click to expand...
Click to collapse
same !!!!
Hi. The following kernel is presented to you by
vorkKernel Team:
- kiljacken
- Benee
Click to expand...
Click to collapse
This kernel is for Cyanogenmod (and in theory any other CM based rom). *Could* be incompatible with latest kangs or nightlies (after a kernel update from CM team). No support for sense...
New vorkKernel Twitter Bot: Here
First I wanted to thank Thalamus for his awesome base kernel - Thanks man . Than I wanted to thank the CM Team for the awesome developement work. Without you guys the Desire weren't such a great device.
Features:
Oc to 1113 Mhz
toggable AVS via app or flags (Credits to dzo and thalamus for avs)
Default IO-Sched is Deadline with a special flash storage tweak
Slub allocator
Tiny-Rcu
BFS Cpu Sched
compiled with a tweaked toolchain (base linaro gcc)
overall compiler optimizations
flags! (more below in the flag section)
A App for easy downloading and configuring. Credits to kiljacken!
Click to expand...
Click to collapse
The standard part:
I'm not responsible for melted phones or something like that...
Click to expand...
Click to collapse
And the source code here.
Download (Market)
Credits to kiljacken for this awesome app! You need OI File Manager for the app (Comes with CM)!
(and if you refuse to use the app - or the app is refusing to work with you: here)
Only change something, if you want to enable OC - No need to touch anything else (like govenors, schedulers)
What are flags and how can I use them?
I recommend to use the App kiljacken made, because it's super easy for you guys. If you not want to use the app *sadpanda* then you can click this link. This is the file the app is fetching to generate the UI.
The layout is following:
Available for following device/Element style (more below)/the flag you need to add/Flag name in App/Description for general Flag/Choice name in app/actual value you need to add after flag name
If the last two points are added you first enter the flag name and than the value. For example: density230
You connect the flags with a: -
Example: -camera-ring ...
The script is configured to detect flags after vorkKernel-VERSIONNUMBER. So you can add some flags after this.
Element style
c = Checkbox
l = List you can choose things from
e = you can enter your own value
Click to expand...
Click to collapse
Error Reporting Guide
Start with rebooting, if that doesn't help, reflash CM and then the kernel, and check again. If you're using the updater app (make sure you have the latest version), use the error report function (and describe what you're problem is). If you're not using the app, then post what flags you are using, along with what your problem is.
Click to expand...
Click to collapse
Additionally I just want to point out that I'm not doing this as a fulltime job, so don't expect daily updates or something like that. I will try to fix a problem as fast as possible but in some cases it can take a while.
If you want to support me you can sign up on dropbox via my referral link or just push this nice thanks button .. If you want to donate you can donate to thalamus or the cm team something. I'm learning C and linux and vorkKernel is my learning project and it is a hobby for me. Anyway if you still want to support a poor student, I have a link above my avatar
Thanks to:
the whole CM Team
thalamus (for base kernel and being totally awesome)
Erasmux
All guys that made pull request and contributed in any possible way
Donators to our project (app or kiljacken's donate link)
the android community
and a very big thanks to b3ndech0 for his buildbox.
Thanks! Will test it soon.!
Did you tested it with Defrost 4.1? Get random reboots with his kernels hope your will solve this!
I run it with cm. And df and cm are nearly the same so maybe it will work for you. (My desire don't like high oc so this slight oc could fix your problems)
I'm using opendesire 4.0.15 and the wifi doesn't work with this kernel. When i try to activate wifi, it says "Error" in the menu. If I try a full wipe will it help?
Oh, and what's the difference between havs and svs kernels (i installed havs, it was first on the list)? Now if it's a "when you ask this you really shouldn't be here" type of question, I apologize for spamming...
Thanks a lot Desire ftw
Sent from my HTC Desire using XDA App
Benee said:
I run it with cm. And df and cm are nearly the same so maybe it will work for you. (My desire don't like high oc so this slight oc could fix your problems)
Click to expand...
Click to collapse
Ah thanks .... oc was not the problem i dont use OC ;-) because i need SetCPU for it. Is this the same with your Kernel? Do i need SetCPU?
Will look into the wifi issue when I'm at a PC again. And SVS (static voltage scaling) is the standard to set the Mhz and HAVS is a method from intersectraven which mixes SVS and AVS (AVS uses the temperature of the cpu to set the clock). HAVS uses slight less battery.
Hope I managed it to explain this good enough.
xtcislove said:
Ah thanks .... oc was not the problem i dont use OC ;-) because i need SetCPU for it. Is this the same with your Kernel? Do i need SetCPU?
Click to expand...
Click to collapse
I don't use it and don't see a reason for using it, because the max voltage from standard max clock (1275mv) to the oc (1113 Mhz) (1275mv) is the same.
it is work for opendesire?
I'm sure this was asked above this post, however, I'm confused if I should use SetCPU with this Kernel, or it automatically sets it at 1.1GHz? Would I still need SetCPU to increase the frequency?
First I pulled the release because I forget to add the wifi module. Will upload it tomorrow again. Then fully working.
Then no need for setcpu. The Kernel will set the clock itself (max 1113 Mhz).
Both Kernals work with OpenDesire 4.0.17 (experimental) but I had problems with ADW Launcher f/c Launcher Pro/Zeam/GDE and Stock Launcher seem fine. Notice Wi-Fi so no further testing. Will be interesting to see what if any affect HAVS has on battery with OD as this does give good life already. Used to use PAYS Rom with HAVS and that made big difference to batt so we will see. Look forward to tomorrow.
Thanks for your contribution to Desire and good luck.
please
pls add exact values for uv and axi.
make aversion with cfq.
fixed Wifi now
bongmaster2 said:
pls add exact values for uv and axi.
make aversion with cfq.
Click to expand...
Click to collapse
What extra values? and why cfq? BFQ runs bette imo
kfasheldon said:
Both Kernals work with OpenDesire 4.0.17 (experimental) but I had problems with ADW Launcher f/c Launcher Pro/Zeam/GDE and Stock Launcher seem fine.
Click to expand...
Click to collapse
Thanks. Will look into the ADW Problem
How is batterie drain with this Kernel? Now use Defrost with svs 1113mhz and Batterie drain is big, bigger than the OD Kernel with the same MHz.
I'm using the HAVS one mainly and I'm quite satisfied with the Battery. But hard to tell because it variates thru different usage and settings (like Display brightness)
Benee said:
What extra values? and why cfq? BFQ runs bette imo
Click to expand...
Click to collapse
the values for axi bus speed. how much mhz at which processor frequency. and the millivolt values for every processor frequency. just 2 tables for comparism with other kernels.
bongmaster2 said:
the values for axi bus speed. how much mhz at which processor frequency. and the millivolt values for every processor frequency. just 2 tables for comparism with other kernels.
Click to expand...
Click to collapse
acpuclock-scorpion line 68
The batterie drain with auto brightness and much Internet use. Compared to svs kernel from Defrost 4.1a with svs 1113mhz.
This is the restarted thread of my ICS Kernel
-
Codename Harmony
Current features are the following (more will follow) :
EVERY firmware avaiable is supported ! This means you can use my kernel on every ASUS-based roms like Revolver, Frozn or ARHD, but also on AOKP, CM9 Nightlies, Megatron, EOS, CNA, TEAMGUMMY, and all other AOSP-based roms out there.
Full 3G support on roms which support 3G
Stable Overclock up to 1.6 GHz
Stable GPU - Overclock ! -- Better 2D and 3D performance !
This is a HV (HighVoltage) Kernel. This means voltages are increased, but I use lower voltages than guevor does.
Extended File System support : Full CIFS, JFS, XFS, NTFS and REISERFS Support inbuilt in the kernel - no need for modules !
Added back missing powersave governor. This is nothing useful other than setting up profiles in setcpu, powersave governor for "screen off" profile does make much sense here.
Added Deadline I/O Scheduler for fancy testing.
Added Simple I/O Scheduler for ultimate I/O performance.
Readahead tweak for massive I/O performance boost.
Added minmax, wheatly, intellidemand, lagfree, smartassv2 governors.
That's it for now. You shall know I'm always open for user's request and will do my best to implement things from your wishlist if others and I do approve.
Changelog
Code:
[COLOR=Red][B]#FINAL[/B][/COLOR]
[LIST]
[*]Governor improvements - SmartAssv2 fully fixed !
[*]VooDoo sound added
[*]Countless overall improvements and code updates
[*][B]Remember : [/B]Downloads are now at my GITHUB !
[/LIST]
[COLOR=Red][B]UNIVERSE - Branch :[/B][/COLOR]
[LIST]
[*]Revision 1 (rev01) : Added support for all roms avaiable to our beloved transformers. WiFi should work on all versions now, including CM9 Nightlies, which was a huge hassle. 3G support is now added for use with roms, that support 3G ! Kernel Modules like NTFS, CIFS, File Systems, etc. are now all inbuilt, so you don't need to insmod anything. That's why my update.zps are so small - There are hardly any modules to copy over to system. Only NTFS automount is missing on CM9 for now, as it's a bit more complex, but it will be fixed in Revision 2; all other versions should work.
[/LIST]
[LIST]
[*]Revision 3 (rev03) : Improved overall stability, fixed misformed memory management, 3g enabled on all versions now, aosp kernel uses slightly lower voltage than asus one.
[/LIST]
[COLOR=Red][B]RELEASE - CANDIDATE Branch[/B][/COLOR]
[LIST]
[*]RC1 :
Completely recoded from scratch.
Based on 9.2.2.6 Asus Kernel Source.
Yet the biggest fixes to governors ever made by me.
Intellidemand governor fully fixed, smartassv2 is now somewhere near-stable.
Fixes to clocks and voltages, no more freeze at 1.2 GHZ.
FINALLY, GPU overclocking ! (--> stable !)
Tweaked SIO scheduler, now working perfectly on our device.
Readahead tweak for massive I/O performance boost.
Added in new CIFS and NTFS modules directly integrated into the kernel.
Revamped the updater script; more eye candy over here.
Other small changes and fixes to asus code.
[*]RC2 :
Recoded the voltage table, giving more juice to the gpu unit, raised read ahead value. Added CIFS and XFS modules kernel-builtin, will release the modules seperately for you to insmod once I rebuild with CIFS and etc. modular. IMPORTANT : IF THE KERNEL DOESN'T BOOT, HOLD DOWN POWER UNTIL IT REBOOTS. IF IT STILL DOESN'T BOOT, DO THE SAME AGAIN. IT WILL BOOT, TRUST ME.
[/LIST]
[COLOR=Red][B] BETA - Branch :[/B][/COLOR]
[LIST]
[*]BETA5 : initial public upload, after +- 20 hours of testing.
[*]BETA6 : added hotplug governor, added simple I/O scheduler,improved governors and cpu driver + deep sleep code.
[*]BETA7 : removed hotplug governor, caused me and the kernel headaches. Fully fixed the minmax governor, you should choose it as it delivers the best battery life at maximum performance. Lowered voltages, improved battery life and optimized sleep codes once again to get the maximun out of our battery life. Changed kernel versioning system, because of this build number has started at #0 again, is now #2 on BETA7. Also I added some suspending code, you should have no more deep sleep /RR with my kernel from BETA7 on.
[*]BETA8 : Using a new kernel config that fixes the random hangings. Excluded the 'smartassv2' governor for now, will include again in BETA 9, when it's fixed again. Improved SIO I/O scheduler, fixes to cpufreq and block.
[*]BETA-X : Massive fixes to governors, added some new (wheatly, lag free, intellidemand). Optimised voltages, increased frequency bus on overclock. Massive improvements on stability, more reliable in all situations. Improvements on battery life.
[/LIST]
CREDITS
I want to thank everyone who supported and helped me.
marcellusbe
dharam_maniar (formerly dharamG3)
guevor
hillbeast
All my testers, but especially scottyf79 (Gummy and AOKP Tester), cholywell (AOKP tester), ajohn117 (3G Tester) !
DOWNLOADS
NEWEST DOWNLOADS ALWAYS AT GITHUB
giving the kernel a run out now......smartassv2 with noop is blazing for web browsing! works pretty awesome with smartass and deadline aswell.
tried to change to interactive with noop and the tf locked up and i had to force a reboot......il see if i have logcat and post it up.
Will this work with AOKP? I think build 38 switched to the nl80211 wifi driver and the wifi won't work on custom kernels.
scottyf79 said:
giving the kernel a run out now......smartassv2 with noop is blazing for web browsing! works pretty awesome with smartass and deadline aswell.
tried to change to interactive with noop and the tf locked up and i had to force a reboot......il see if i have logcat and post it up.
Click to expand...
Click to collapse
Yeah, I encountered this as well, but I couldn't see any kernel panic in this, might be something else.
My next goal ist to port the linux 3.4 kernel, as they already included android source code in the mainline branch. Thsi would take the kernel to the next level.
But most of my worktime still goes into this kernel
cholywell said:
Will this work with AOKP? I think build 38 switched to the nl80211 wifi driver and the wifi won't work on custom kernels.
Click to expand...
Click to collapse
You're absolutely right. Everything will work fine except for wifi. If more users want this, I will make a aokp version with different wifi driver.
I think a CM9 AOKP version would be very popular. I don't think there any custom kernels for those roms and all the ones based off them.
+1.......the Cm9 builds like Skank etc could do with some loving
scottyf79 said:
+1.......the Cm9 builds like Skank etc could do with some loving
Click to expand...
Click to collapse
Did you try some cm9 rom with my kernel ?
I'm not aware of them having changed the wifi driver to something other than bcmhd...ko , in other wirds, asus stock.
Correct me if I'm wrong.
I'm on a trip the next days, so I will be able to continue work on this kernel let's say.. next tuesday if everything goes well. Just tell me which wifi driver to use and I will compile it
ok ive just tried Skang (cm9) and Gummy (aosp/cm9) with the kernel and neither connect to wifi. also when i tried to change the cpu speed with the baked in cpu controller i found they auto reverted back to 1000mhz with interactive and would not stick on 1200mhz or the selected guvenor.
I'll ask the respective devs what may be required to fix.
thanks for the work..i'm not going to test it due to stocked tf before assistance centre sending,but when i'll receive back my tablet,i'd love to be able to try this kernel...for my taste,i'd love to see wheatley governor inside..for me it's a very efficent governor.think about that mate.cheers and keep up the hard work!
A little update in the meantime : Beta6 is ready, added fully working sio-scheduler and hotplug governor. There is a bug because of which hotplug gov is rebooting instantly after being woken up from deep sleep.
More changes are :
Improved smartassv2 governor, working almost perfectly now !
Improved minmax governor. Ths does now work, but actually needs some further love from me, I think.
Will update the thread next week, along with Beta7.
Beta6 currently avaiable at : http://db.tt/XSK0na2Y
What about version for AOKP? All kernel brake wifi on b38
Seems like I miss my own deadline. Beta7 will be avaiable in a few minutes.
Random governor lockup while changing in setcpu or nofrills etc. should be fixed now.
I also improved all governors balancing and fully fixed the minmax governor.
Added sio scheduler to get the best I/O performance possible.
I will have a look on an AOKP and CM9 version with enhanced wifi drivers next week. Stay tuned !
Hi and thanks for your work.
Here's my experience with BETA7
TF101 b50, always docked with microsd always inserted
rom: revolver 4 rc2, kernel: harmony beta7
I tried your kernel after a long time using guevor's v20, because v20 gave me SOD after 3-4 days of normal operation.
I just wiped cache and dalvik, and then flashed beta7. It seemed to work smooth enough - had some stuttering in Modern Combat3, but that went away after a few minutes of playing.
The major problem was that it just RR while i was in a fring video call. Talking, as usual and then just bam! speakers started making this weird clicking noise for 1-2 seconds, video froze, and my tablet rebooted. This never happened before - i actually didn't have the RR problem even on stock rom+kernel.
I decided to test it overnight, only to wake up and see it rebooted again. It wasn't charging, it was only docked.
The good thing was that battery consumption was good ~1% per hour, with wi-fi on. It goes into deep-sleep, but also, before it does that, it does some random wake-ups.
So here's a summary of MY experience with BETA7 kernel
PRO's:
- no SOD
- good battery life (~1%/hour with wi-fi on, in deep sleep)
CON's:
- Random Reboots
- some random wake-ups
- some stuttering in 3d apps that seems to be loading-related
I'll be going back to guevor's, but i'll definitely keep an eye on this one.
Sorry, i didn't think of saving any kernel logs...
Keep up the good work!
Kernel based on Asus 9.2.2.4 ?
Hi,
is your kernel based on the Asus 9.2.2.4 stock kernel?
Because I've a TF101G 3G model and this the only kernel wich is stable (for about a week no RR or SOD's at all) on this tablet version while using Wifi and 3G functionalities.
BTW I'm using ARHD 3.3.1_3G rom.
I would like overclock it but this is not supported which the stock kernel.
Many thanks in advange.
zdalin2003 said:
Hi and thanks for your work.
Here's my experience with BETA7
TF101 b50, always docked with microsd always inserted
rom: revolver 4 rc2, kernel: harmony beta7
I tried your kernel after a long time using guevor's v20, because v20 gave me SOD after 3-4 days of normal operation.
I just wiped cache and dalvik, and then flashed beta7. It seemed to work smooth enough - had some stuttering in Modern Combat3, but that went away after a few minutes of playing.
The major problem was that it just RR while i was in a fring video call. Talking, as usual and then just bam! speakers started making this weird clicking noise for 1-2 seconds, video froze, and my tablet rebooted. This never happened before - i actually didn't have the RR problem even on stock rom+kernel.
I decided to test it overnight, only to wake up and see it rebooted again. It wasn't charging, it was only docked.
The good thing was that battery consumption was good ~1% per hour, with wi-fi on. It goes into deep-sleep, but also, before it does that, it does some random wake-ups.
So here's a summary of MY experience with BETA7 kernel
PRO's:
- no SOD
- good battery life (~1%/hour with wi-fi on, in deep sleep)
CON's:
- Random Reboots
- some random wake-ups
- some stuttering in 3d apps that seems to be loading-related
I'll be going back to guevor's, but i'll definitely keep an eye on this one.
Sorry, i didn't think of saving any kernel logs...
Keep up the good work!
Click to expand...
Click to collapse
Random reboots are definately rom - related, try ARHD rom, has been the bost rom ever for our transformer, I always put my trust in it. Revolver is halfway abandoned, outdated and not frequently updated.
Random wake-ups are rom related, too. I do not encounter any of your errors, sorry.
Maybe if you could get me a kernel message (kmsg, google it) , I could help you.
antond57 said:
Hi,
is your kernel based on the Asus 9.2.2.4 stock kernel?
Because I've a TF101G 3G model and this the only kernel wich is stable (for about a week no RR or SOD's at all) on this tablet version while using Wifi and 3G functionalities.
BTW I'm using ARHD 3.3.1_3G rom.
I would like overclock it but this is not supported which the stock kernel.
Many thanks in advange.
Click to expand...
Click to collapse
Kernel is based on 9.2.1.24 . I haven't found any newer source on the asus site, but you may redirect me to it, then I will use it.
Alright so here's the first release of this kernel for codeworkx's CM9 with hardware acceleration.
Again this is for codeworkx's cm9.
Also, this is for codeworkx's cyanogenmod 9.
One more time, this is for cm9 only.
Finally, this is for cm9 and cm9 only!
Don't let the "alpha" title fool you into thinking it's not stable... it is... It's only alpha because it's still in the "testing" phase.
FEATURES/CHANGES
Overclockable to 1.38GHz
Underclockable to 150MHz
GPU overclocked to 384MHz (highest possible without bottlenecking and battery waste)
Tuned OnDemand Governor (recommended)
Interactive Governor with time view concept (learns from your use and adjust parameters accordingly)
Wheatley Governor (optimized use of C4 state)
Hotplug Governor (turns of one of the cpus to save power when load is very low)
Pegasusq Governor (A better version of Hotplug, but experimental and not designed for our devices)
SIO scheduler for speed/performance with flash storage
Linaro Toolchain
Linaro optimizations and patches
Linaro makefile compiler flags
Makefile Optimizations to boost performance
Optimized CRC32
Optimized ARM RWSEM algorithm
Tiler Memory increased to 32MB (linaro)
Other Tiler patches/tweaks to improve 2D gpu performance
SLQB allocator
lib/string use glibc version for speed
lib/memcopy use glibc version for speed
lib/sha1: use the git implementation of SHA-1 and removed ARM sha1 routines
I/O backport from 3.2 linux kernel for less dirty throttling
Tweak CPUIDLE to enter deep sleep faster thus saving battery
LowMemoryKiller backported from 3.4 kernel
Disable GENTLE_FAIR_SLEEPERS for improved performance
Allow Deep Sleep to occur when media decoder is active allowing the cpu to shut off when playing music or video.
Allow MPU logic to power down when in deep sleep to save power.
Increased default readahead value to 1024KB for faster sdcard reads
A lot of stuff I probably forgot I did.
Also includes a ridiculous amount of bugfixes, patches, and tweaks that can found on my github commit log.
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
Let me know how it "feels" especially by default without overclocking or underclocking. Also I'd be interested in how the battery treats you. Thanks!
DOWNLOAD
a1 - Only for 7 inch
a2 - Only for 7 inch - Changes to: Wifi, GPU, Low Memory Killer, others
a3 - Only for 7 inch - Changes to: ondemand, interactive, add wheatley, add pegasusq, deep idle, compiler flags, SDcard read, others
a4 - not working... fix soon - Changes to: Compiler flags, CPUidle, RCU, others.
a5 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_10.1_CM9_a5.zip - reverts and bugfixes, use 10.1 ramdisk in 10.1 version.
a6 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_10.1_CM9_a6.zip - CLASSIFIED change, NEED feedback on speed, slowness, smoothness, and lag compared to stock and a5. Reverted some revets. Reverted changes to RCU to fix SODs. For 10.1 fixed overclocking.
Thanks go out to - CodeworkX, Ezekeel, Francisco Franco, Imoseyon, Faux123, Fugumod, Sonicxml, Texas Instruments, Samsung, Google, and all the others I probably forgot about. Sorry!
Source
https://github.com/Metallice
______________________________________________________________________________________________________________________
So, I'm a broke college student without a job this summer - instead taking extra classes and studying like crazy for the MCAT. If you like my work and want to thank me, feel free to buy a coffee or an energy drink so I can continue to stay up late studying and working on Android stuff (or help me pay for med school ). I don't want to have to choose! Thanks and I appreciate your support!
Metallice said:
Alright so here's the first release of this kernel for codeworkx's CM9 with hardware acceleration.
Again this is for clockworkx's cm9.
One more time, this is for clockworkx's cyanogenmod 9.
Finally, this is for cm9 and cm9 only!
Don't let the "alpha" title fool you into thinking it's not stable... it is... It's only alpha because it's still in the "testing" phase.
NO CLUE IF THIS WILL WORK AT ALL. I DO NOT HAVE THIS DEVICE.
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
Let me know how it "feels" especially by default without overclocking or underclocking. Also I'd be interested in how the battery treats you. Thanks!
DOWNLOAD
a1 - Only for 7 inch
a2 - Only for 7 inch - Changes to: Wifi, GPU, Low Memory Killer, others
a3 - Only for 7 inch - Changes to: ondemand, interactive, add wheatley, add pegasusq, deep idle, compiler flags, SDcard read, others
a4 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_10.1_CM9_a4.zip - Changes to: Compiler flags, CPUidle, RCU, others.
If you would like to overclock but your device can't handle it... and are willing to suffer through extreme battery drain to try this - Link
Thanks go out to - CodeworkX, Ezekeel, Francisco Franco, Imoseyon, Faux123, Fugumod, Sonicxml, Texas Instruments, Samsung, Google, and all the others I probably forgot about. Sorry!
Source
https://github.com/Metallice
______________________________________________________________________________________________________________________
So, I'm a broke college student without a job this summer - instead taking extra classes and studying like crazy for the MCAT. If you like my work and want to thank me, feel free to buy a coffee or an energy drink so I can continue to stay up late studying and working on Android stuff (or help me pay for med school ). I don't want to have to choose! Thanks and I appreciate your support!
Click to expand...
Click to collapse
I LOVEEEEEE YOU i absulutely love you MAN!~~~~~~~~~~~~~~~
His kernels and ROM's for the 7 are right on.
Good luck with this Metallice.
Thanks, but it didn't seem to go past the boot screen for me.
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Thanks, but it didn't seem to go past the boot screen for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Which boot screen. I think I know the issue if its not the cyanogenmod one.
Sent from my GT-P3113 using xda premium
I have this issue too and it's the Tab2 10.1 screen. (the first one that shows during boot)
It's the Tab 2 Splash screen. I can adb, go into DL, and get into CWM so it's fine... it just won't boot.
Yeah its probably because I forgot to use the 10.1 ramdisk. I'll upload a fixed version shortly.
Sent from my GT-P3113 using xda premium
No worries man.
Thanks for getting started anyway, a lot of devs can use your fork now.
New version up. In addition to some bugfixes and reverts, this time the espresso10 ramdisk is actually used instead of the 7 inch version
Now it installs fine. What app should I use to control it? NSTools, Voltage Control, CPU Master, etc...
MultipleMonomials said:
Now it installs fine. What app should I use to control it? NSTools, Voltage Control, CPU Master, etc...
Click to expand...
Click to collapse
Glad to hear it. Let me know how it runs.
Really doesn't matter what you use as they all modify the same sysfs entries. I like no frills CPU control because its simple and only does what I need it to do.
Sent from my GT-P3113 using xda premium
Changing OC settings with NSTools or CPU control causes reboot. Settings don't change.
I can change min freq and governor (tried it with interactive and wheatly), just not max freq.
Works like a charm now. I'll keep you up to date on performance once I've done some testing.
Works fine in voltage control, and stable at 1380 so far with little heat. I haven't really stressed it though but it does run smoother and more responsive than before. The GPU seems snappier too. Great job.
Sent from my GT-P5113 using Tapatalk 2
Can you post a complete "feature list" with next version ? Oh, and can Voodoo sound be integrated for better (sound) quality ? I'll keep pressing the thanks button.
Thanks for the kernel, will test it later this day.
Maybe you can add an how to flash guide for the n00bs who want to flash but don't know how to do it?
works works works!!!!!!!!!! like an awsomeness thing! hehe i know that i can trust on you m8, but i did ask for it..yet and you made it! thx really THX!!!!!!
Hi,
Thank you for work but is what I am to have a problem of hangs and of connection with WIFI
Been testing the kernel with default settings for some hours now ... started using it since 11.oo this morning and started with a full battery. After playing some games (tablet/battery temperature stayed normal) and browsing the net, checking emails and some more stuff i must say the kernel works smooth and my tablet runs faster. Am using the kernel for 3.5 hours and the battery is at 71%. No weird things happened so far. WiFi and bluetooth both work fine in other words...
the kernel feels goOOOood