Related
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.
I'm listing here 2 different 2.6.35 based kernels :
The 1.x series exist for Froyo and Gingerbread. They are based on a 2.6.35.8 linux kernel. They are CFS only (no BFS version), and forked from Richard Trip's kernels (https://github.com/richardtrip/cm-kernel)
The 2.x series are for GingerBread only. They have CFS and BFS versions. They are based on a 2.6.35.13 kernel and forked from _thalamus' kernels (https://github.com/thalamus/kernel)
All of my kernels have the following characteristics :
Go from 128Mhz to 1190Mhz. If your phone crashes at those speeds, then don't use them. Not all phones are equal and they won't all accept these frequencies.
The noop IO scheduler is defined as default. I think that all the other schedulers are unnecessary with flash disks. They are too complex and consume more CPU for the same result.
Two-way call recording thanks to avs333 (http://forum.xda-developers.com/showthread.php?t=993793)
The following characteristics are available in some kernels :
BFS. Brain F*ck Scheduler. Only available on the 2.x kernels.
CFS. Completely Fair Scheduler. Choose which scheduler suits your needs the best. Check here for a description of both : http://www.stackednotion.com/2010/06/04/what-are-bfs-and-cfs
AXI. AXI optimisation is available in some kernels : http://forum.xda-developers.com/showthread.php?t=665110. When it is enabled, the AXI bus speed is lowered to 64Mhz instead of 128Mhz when the screen is off. In the other kernels, the AXI bus speed is throttled according to the current CPU speed.
HAVS. Hybrid Adaptive Voltage Scaling. Dynamically changes the phones voltage. Should use up less battery than SVS. In comparison with Richard's original kernel, I upped the maximum voltage in the overclocking frequencies to 1350mV instead of 1300mV because it didn't seem enough (at least on my phone). I also set the minimum voltage to 900mV. I feel it's a good compromise between 875 and 925...
SVS. Static Voltage Scaling.
On the ManU kernel series, it is possible to change the voltages table on the fly using the following method. On the SVS kernel, the following method was used : http://forum.xda-developers.com/showthread.php?t=821372. See the post below for a simpler description of this
The following kernels are based on an OLD version of the Android kernel. The main advantage is the battery usage : it's very low compared to the latest kernels. The source code is available at http://github.com/eviollet/cm-kernel.
As of versions 2.1, SVS versions are no longer supported. Only HAVS versions are available.
2.6.35.13 ManU-Version 2.1 - Gingerbread ONLY
Gingerbread-HAVS-CFS ----------------
Gingerbread-HAVS-AXI-CFS ----------------
Gingerbread-HAVS-BFS ----------------
Gingerbread-HAVS-AXI-BFS ----------------
2.6.35.8 ManU-Version 1.4
Froyo-HAVS-CFS ---------------- Gingerbread-HAVS-CFS ----------------
Froyo-SVS-CFS ---------------- Gingerbread-SVS-CFS ----------------
Froyo-HAVS-AXI-CFS ---------------- Gingerbread-HAVS-AXI-CFS ----------------
Froyo-SVS-AXI-CFS ---------------- Gingerbread-SVS-AXI-CFS ----------------
Many thanks to Richard Trip for helping me out with the 1.4 kernel, and to thalamus for help on the 2.0 kernel.
Version history :
11/01/12 ManU-V2.1:
HAVS only. The voltages run from 1000mV to 1350mV which means that they should be stable on all phones. Feel free to play around with the voltages using a script, or IncrediControl
LED notification should now work on GingerVillain 2.8 and upwards thanks to Richard Trip.
Added smartassV2, thanks to erasmux.
Fixed VPN on MIUI (and perhaps other ROMs) thanks to [email protected]
Fixed "adb devices" id name bug
Fixed battery calibration
Added lazy governor thanks to Ezekeel : http://forum.xda-developers.com/showthread.php?t=1276092
Added system files to display the current state of the vdd levels
Optimized onDemand governor: ondemand: Remove the iowait-is-busy tunable code. Thanks to someone (I don't know who, sorry...)
Changed the Lazy governor default values to the ones recommended by Dr Byte (80/30000)
Added debug information in the AVS module when voltage changes occur. Especially if they fail.
Added working VPN back again (credits go to mondilv)
Started changing the AVS vdd changing logic. Now only changes the frequencies that are directly impacted.
Add WiFi screen off power level switch
Fix sound issue when using voice commands when bluetooth is connected (??)
28/05/11 ManU-V2.0:
kernel rebased on V2.6.35.13
07/04/11 ManU-V1.4:
added 2-way call recording thanks to avs333 (http://forum.xda-developers.com/showthread.php?t=993793)
updated the battery driver to be compatible with "Battery Calibrator" (https://market.android.com/details?id=net.jonrichards.batterycalibrator.ui)
ZIPs are now signed
128Mhz is now available even when the screen is on with AXI kernels
Higher BlueTooth audio sound
ManU-V1.3:
added CPU Vdd levels sysfs interface for HAVS kernels as well
changed the audio settings
changed the modules location
ManU-V1.2:
added CPU Vdd levels ("undervolt") sysfs interface for SVS kernels (http://forum.xda-developers.com/showthread.php?t=821372)
fixed video recording crashes
updated most of the drivers to most recent versions
changed the kernel name in the Android about box (now reports version number as well)
changed the zip flash to (hopefully) fix problems when flashing on phones with bad sectors
fixed some kernel versions having CPU governor performance by default
ManU-V1.1:
fix battery charging issue between 90% and 100%
disable 128Mhz when the screen is on, in the AXI kernels
ManU-V1.0: Kernel based on an old version (approx. October 2010)
V1 : Fix for IPV6 on MIUI. 6.1 and 6.1se kernels
V0 : First version : 6.1 and 6.1se kernels
FAQ:
How do I know which version I'm running? : Look at the "About the phone" screen at the kernel version. It should display which options you're currently using.
Which kernel do you recommend? : I'd say ManU-HAVS-AXI-CFS. On my phone on idle, I'm using up approx. 2-3ma/h instead of 6-7 with the default kernels with this kernel. So I'm very happy with it, and am currently using it as my main kernel. If you do any testing, feel free to tell us about your own experience!
Do you recommend any settings with SetCPU? : I currently use 128-440 conservative governor when the screen is off, and 128-1130 interactive when the screen is on and it gives good results.
After some time my phone feels sluggish. Why? : Apparently there seems to be an issue when switching governors, especially with "interactive". I recommend not to use it, or stick with it and don't change. This may be fixed in the future.
*Something* doesn't work with this kernel. Can you fix it? : First of all, my knowledge of the current state of the kernel is very limited. I just changed a few things in the DeFrost kernel to suit my taste and thought that this kernel may be of interest to some other people. If you have a problem, try explaining it, and give the following details : Name and version of your current ROM, previous kernel that worked, which version of the kernel you are now trying and any other details that may be of interest. I can't guarantee that I'll be able to fix it, because I don't develop the kernel, but I can try to help.
If you have a problem, try disabling the 128Mhz and overclocking options. They may be the culprits.
If 128Mhz saves battery, why isn't it enabled by default in other kernels? : Good question, and I don't know exactly. why. Apparently it causes issues on some phones. So, if you have a problem, try disabling 128Mhz. Also, 1190Mhz is a very high value and can also cause issues. So try lowering the maximum frequencies if you have issues.
On which ROMs do these kernels work? : 1.x series work on DeFrost 6.1, probably earlier versions as well, MIUI and GingerVillain, Redux, and probably others. The 2.x series only work on GingerBread.
On which ROMs do these kernels NOT work? : Oxygen 2. I recommend directly using _thalamus' kernels for Oxygen 2 : http://thalamus.ineige.org/kernels/2.6.35/
Here is a description of how to use the sysfs interface to configure voltage levels :
For SVS kernels, the file name is "/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels" and on HAVS kernels, the file name is "/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs".
This file is used to read the current voltage state of write new voltage settings.
How to read the settings with the HAVS interface:
connect to the phone using a terminal, or adb shell, and type "cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs". The phone will display the frequencies and the associated high and low voltages.
If you want to change the voltages, just send "echo 128000 875 1000 > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs". This will configure the minimum voltage to 875mV and max to 1000mV for the 128000 frequency.
Another useful command is "echo -25 +25 > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs". This will lower the minimum voltage by 25mV and raise the maximum voltage by 25mV on ALL frequencies.
As for the SVS interface, the commands are similar.
"cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels" will display the frequencies and the voltages, and "echo 128000 900 > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels" will set the voltage to 900mV when the CPU is at 128Mhz.
Please note that voltages are multiples of 25mV. So, accepted values are 800, 825, 850, etc. Other values will be rounded.
There is also the possibility to visualize how the kernel is managing the HAVS voltages by using the following system files: /sys/devices/system/cpu/cpu0/cpufreq/vdd_table_havs and /sys/devices/system/cpu/cpu0/cpufreq/vdd_tables_havs
The first file lists the voltages being used for each frequency at the current temperature range.
The second file first displays the current temperature range index (starting at 0) and then the voltages being used for each frequency and for each temperature range.
The WiFi screen off power level can be configured by modifying the following file: /sys/module/bcm4329/parameters/wlLowPower
By sending 'echo 1 > /sys/module/bcm4329/parameters/wlLowPower' the WiFi will switch to low power level when the screen is switched off. By default maximum power is used at all times.
Test versions:
The following section contains test materiel. This means that I need feedback on this version, as it may (or may not) become the next official version.
For the moment, no beta/test version available.
Bien joué/Well played
difference between base and "se" version?
I'd be interested in seeing the AXI patches please, if not I'll go the hard way and fix up the ones off that thread
vivmar said:
difference between base and "se" version?
Click to expand...
Click to collapse
The base version is the current state of the art of Richard Trip's kernel, as used in DeFrost 6.1. However there seems to be battery drain issues for some using this kernel, so he put up a 6.1se version that removes all the latest patches/addons to fix the drain.
I find the normal version quite stable and works well for me, but some may prefer the se version...
I hope this answers your question?
EViollet said:
The following characteristics are available in the different kernels :
HAVS. Hybrid Adaptive Voltage Scaling. Dynamically changes the phones voltage. Should use up less battery than SVS. In comparison with Richard's original kernel, I upped the maximum voltage in the overclocking frequencies to 1350mV instead of 1300mV because it didn't seem enough (at least on my phone). I also set the minimum voltage to 900mV. I feel it's a good compromise between 875 and 925...
Click to expand...
Click to collapse
Boooo my phone works fine at 875 and 1300... but I want to try your kernels for axi....
I'll have to start work on that /proc/havs interface, since no-one else seems to want it. At least I'll have a week over xmas
Incidentally, the AXI thread you mentioned suggests that the modification is already in HTC's Desire kernel... what do they do at 128MHz?
coutts99 said:
I'd be interested in seeing the AXI patches please, if not I'll go the hard way and fix up the ones off that thread
Click to expand...
Click to collapse
I just enabled the AXI patches in the kernel. Apparently the functionnality is already included in the kernel.
Am I missing something? I must admit that I didn't look any further than that. Perhaps what I wrote is completely wrong...
EViollet said:
I just enabled the AXI patches in the kernel. Apparently the functionnality is already included in the kernel.
Am I missing something? I must admit that I didn't look any further than that. Perhaps what I wrote is completely wrong...
Click to expand...
Click to collapse
Did you patch the kernel or was it already in? Did richardtrip patch it?
Marsbar said:
Boooo my phone works fine at 875 and 1300... but I want to try your kernels for axi....
I'll have to start work on that /proc/havs interface, since no-one else seems to want it. At least I'll have a week over xmas
Incidentally, the AXI thread you mentioned suggests that the modification is already in HTC's Desire kernel... what do they do at 128MHz?
Click to expand...
Click to collapse
Do be honest, my phone also works fine at 875mV. But I had a few issues with the latest kernel that were fixed by setting it to 900mV. So I believe that 900mV is a little bit more stable. I don't intend on compiling 2 versions of the HAVS kernels, so 900mV seemed a nice compromise. Especially as quite frankly I don't see a difference in battery usage between 875 and 925...
I don't think it's worth the bother...
And as for the higher voltage for the higher speeds, it's just that I allowed HAVS to go higher. It doesn't mean that it will though. It depends on your hardware and what HAVS decides to do with it. If your phone works fine @1300mV it won't try to go any higher. HAVS adapts the voltage automatically by using 2 boundaries (high and low), and it works it's way between them...
As for the 128Mhz... the thing is that the AXI patch lowers the AXI bus to 63Mhz instead of 128Mhz. The problem is that in order to lower the CPU speed to 128Mhz, the kernel relies on the AXI bus speed. So if the AXI bus is lowered, so will the CPU. And, it will crash. Because it can't really go below 128Mhz.
That's why you can't use 128Mhz AND the AXI patch.
In any case, that's what I figured out by looking at the source code and trying it myself (I had a few crashes before understanding why... )
Regards,
coutts99 said:
Did you patch the kernel or was it already in? Did richardtrip patch it?
Click to expand...
Click to collapse
It's already in it. I doubt that Richard added it because he doesn't use it.
I guess it's already in the Cyanogen kernel (which is the base for Richard's)
EViollet said:
It's already in it. I doubt that Richard added it because he doesn't use it.
I guess it's already in the Cyanogen kernel (which is the base for Richard's)
Click to expand...
Click to collapse
Ah ok no problem, thanks
great work man, i was looking forward a kernel with hvas/bfs/noop and max freq 1190. min freq of 128 and axi are welcome!
only thing i dont like is the min freq, but its ok.
are you building straight from richard's repo? can you share the sources? and the config file?
thx!
@EViollet
First of all excellent work!
But I have one question.
You say in order to use AXI in your kernel, you have to choose at least 256MHz when the screen is on. In other words this means when it scales from 128MHz to let´s say 998 MHz AXI is automatically disabled?! So I have to choose 384MHz at SetCpu as minimum in order to use AXI?
1 issue, after enabling wifi it does nothing just keeps scanning.
Its necessary to turn airplane on/off or reboot.
Im using bfs havs axi @ 1190 max.
Sent from my HTC Desire using XDA App
crapula512 said:
great work man, i was looking forward a kernel with hvas/bfs/noop and max freq 1190. min freq of 128 and axi are welcome!
only thing i dont like is the min freq, but its ok.
are you building straight from richard's repo? can you share the sources? and the config file?
thx!
Click to expand...
Click to collapse
I'm adding a tgz file to the first post that lists all the changes I made to Richard's source code, and the configuration files I created for all the kernels. Hope this helps.
Tweak³ said:
@EViollet
First of all excellent work!
But I have one question.
You say in order to use AXI in your kernel, you have to choose at least 256MHz when the screen is on. In other words this means when it scales from 128MHz to let´s say 998 MHz AXI is automatically disabled?! So I have to choose 384MHz at SetCpu as minimum in order to use AXI?
Click to expand...
Click to collapse
If you use AXI, the CPU frequency must be higher than 128Mhz when the screen is on. If you leave 128Mhz, in reality it will get much lower, so will eventually crash.
So, the values I use are :
Screen off : 128-450
Screen on : 256-1190
Regards,
crapula512 said:
1 issue, after enabling wifi it does nothing just keeps scanning.
Its necessary to turn airplane on/off or reboot.
Im using bfs havs axi @ 1190 max.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hi.
I'm afraid I won't be able to do much here.
I'm not a developper of the kernel, so I don't know where to start.
Which ROM are you using? And which version of the kernel? 6.1? Or 6.1se?
Regards,
6.1se, rom is ginger villain 0.2.
I think its kernel related as it was working fine with 6.0c.
maybe is just a coincidence, but today benee updated his vorkkernel and ppl was having this same problem and later on he made anew version with wifi fixed.
Hope that helps and good work!
Sent from my HTC Desire using XDA App
crapula512 said:
6.1se, rom is ginger villain 0.2.
I think its kernel related as it was working fine with 6.0c.
maybe is just a coincidence, but today benee updated his vorkkernel and ppl was having this same problem and later on he made anew version with wifi fixed.
Hope that helps and good work!
Click to expand...
Click to collapse
OK. Thanks for the update.
Did you try the 6.1 kernel? It has more a more recent WiFi driver. Maybe it works better...
Edit : I just checked GingerVillain 0.4 and can confirm that the WiFi driver doesn't work correctly.
It ends up connecting but it takes a VERY VERY long time to scan.
The WiFi update in the CyanogenMod kernel probable fixes this, so I'll have a look into it.
But, for the moment I'm afraid there is no support for Gingerbread...
Regards,
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
Changing some values at governor tab (setcpu), after rebooting the device, the changes i made are gone.
Any ideas?
by the way: using promethius rom 1.5v+, promethius kernel v-ex+ (very stable, the only problem i get is with setcpu)
Do you mean the frequencies or changes like Threshold/Sample-rate/Save Power bias
For frenquencies i would try another app like Rom toolbox lite (changes sticks)
For second im having the same problems, i think they are presets in build prob, so after each reboot this settings are used.
Pät said:
Do you mean the frequencies or changes like Threshold/Sample-rate/Save Power bias
For frenquencies i would try another app like Rom toolbox lite (changes sticks)
For second im having the same problems, i think they are presets in build prob, so after each reboot this settings are used.
Click to expand...
Click to collapse
Yes, it's the same here, frequencies, profiles, those changes sticks, but changing at governor tab (up treshold, sample rate, etc... ), not sticks after reboot! so if they are presets in build, how can i change those settings at build level ? which software?
thansk!
Hey guys. First off, Apologies if this has been created or discussed before. I have searched before this posting; as I am not big on creating new threads, and the stigma related.
Anyway, On my HTC EVO 3D, I used Kernel Manager, as it had a great layout, allowed cpu/gpu adjustments, AMAZING widget, mpdecision support, ThermalD suppport (I do know the support comes from the kernel, Im saying the app allowed me to customize it), set vsync, color depth, whole nine yards. Im looking for something like it that would work well with the Infinity. Ive noticed kernel manager and ROM Toolbox are both finnicky with the tablet and it doesnt do as well. Kernel tuner works best, still it seems to not get along with the extra 2 CPUS. their governors always revert, it wont display CPU temp properly, no GPU settings, The battery drain is always +/-errmA (i guess error Milliamps) and the widget only displays two of the four CPUS. Anybody have any suggestions, or a solution to make kernel tuner work? Anything is welcomed and appreciated. Thanks in advance.