Related
Evo Switch v1.1.1 NovaFreq v1.2.1
(APP NAME CHANGED TO SOMETHING MORE APPROPRIATE)
This is an Android application developed to change the panel frequency for Novatek Panels for the Sprint HTC EVO 4G, in conjunction with ffolkes' Novatek Kernel and netarchy's Kernel,
and any kernel that has maejrep's T2 Interface built in. Every device is different, and with that, those specified kernel's default settings may or may not be optimized with your device.
With this application, you can change those settings on the fly and find the best setting for your device.
[ Please use this application with extreme caution! I am not responsible for any damage this may cause to your device. ]
Requirements:
-HTC EVO 4G
-Android 2.1 +
-Any custom kernel that is built off of toastcfh's htc source
-Novatek Panel
-Root Access
Uses:
-Use as an fps frequency turbo switch for when you need extra fps.
-Use as a debugging tool to test frequencies.
-Use to keep frequency settings even beyond reboots. (new)
Settings:
-340 [Stock] is how HTC intended the EVO to be. This frequency works out to 61hz, but we are capped at 30hz.
-370 [Kernel Default] sets the panel frequency lower than stock, yet provides most around 55fps.
-250 [Stable High Freq] sets the panel frequency higher than stock, which usually gives around 40fps.
-400 [Stable Low Freq] - V2's setting.
-Favorite Setting - Find the most stable setting, and if it's not one of the listed, then "Set Favorite".
-Sticky Settings - Now you can reboot and not have to re-apply your settings!
Custom Setting:
You can put arbitrary settings here, but be warned this may mess up your screen, but usually you can reboot your phone
to change it back to default. Minimum Recommended: 250 Maximum Recommended: 999.
Please do not go lower then the minimum recommended of 250, nor higher than the maximum recommended 999.
To Do:
-Favorite Setting - So you can save the best setting for your device. 07/04/10 - Done!
Change Log:
-Changed app name from Evo Switch to NovaFreq (Novatek Frequency / Freek)
-Totally redid code, should be more optimized.
-Frequencies stick beyond a reboot
-Changed a few of the defaults
-Changed back sleep time to 500ms so the current displayed setting can update (v1.2.1)
Don't be alarmed if you see NovaFreq running in the background. To be able to sticky settings beyond a reboot, NovaFreq has to be run at boot up.
After that you can kill NovaFreq if you want, android will kill it when needed so don't worry.
Thanks To:
ffolkes, netarchy, maejrep, toastcfh, halfline, Cicitrize, geyes30, kpkimmel, joeykrim, and many others involved in trying to uncap the EVO.
Reserved...
Reserved again.
woah, this is badass. I will check it out soon
works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?
Awesome!! This is the first time I've been able to break 30 fps! (thanks to your app!)
I'm on Froyo and the v4 had never worked, but now v4 + high frequency with your app = 40 fps.
I love you.
this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??
Great little app, I would recommend users experiment with the values just ever so slightly for optimum performance. Using the default value of 361 netted me about 50-51 fps, whereas using 365 nets me about 54-55. Not a huge bump, but even a little bit is nice
Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.
timgt said:
works great! Whats the number I set it at to equal the V2 setting of ffolkes kernel? I think its 400, is that correct?
Click to expand...
Click to collapse
Yes, I think V2 was 400.
madunix said:
this may a silly question... but would this fix camera when i have it disabled as to if i switch it on the camera is now broke? or just the kernel itself breaks the camera??
Click to expand...
Click to collapse
Every custom kernel does not have a working camera, because we do not have the source code for it. When HTC finally releases the source code, then we will be able to fix the camera.
antiphon said:
Great application. May I suggest adding maybe a quick cycle to move between frequencies so users can go through a number of settings at once? Kinda like the Scan feature in most radios to pick the best frequencies.
Click to expand...
Click to collapse
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.
Well done!! Thanks
AssassinsLament said:
This sounds like something to think about. Only problem is, while scanning, no one will know what the fps is unless they have their favorite fps app running, but then we wouldn't know what the frequency setting is since the fps app is running in focus. Might be a bit difficult to pull off without building an fps test into the app.
Click to expand...
Click to collapse
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!
antiphon said:
Yeah I agree it would be difficult to implement without a built in fps counter. I was thinking more along the lines of something that would flag or eliminate the frequencies that are really bad (ie the ones which make your screen go haywire). So maybe the user could, for example, pick frequencies 300-310 and then the app would cycle through them 1 second at a time. From there the user would be able to run FPS2D or whatever to test out those frequencies that didn't make their screen all blotchy.
Anyways, just something to think about. Great work nonetheless!
Click to expand...
Click to collapse
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.
maejrep said:
This won't work, because the interface that is used to write these settings to the panel cannot handle both full-speed graphics, and setting panel registers. I tried this when I first created the sysfs attr file, and if fps2d is running, it seems impossible to set or query the current T2 value. the display pretty much has to be idle for this to work.
Using a mutex lock might help, but I didn't look into it any further.
Click to expand...
Click to collapse
Yep, that's why I had to put in a "sleep" command in my app so that the system could process the change and update the app on if the register changed or not. Thanks for the interface maejrep!
Where is the link to the switch app?
Sent from my PC36100 using XDA App
Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?
Force close only.
apollooff320 said:
Where is the link to the switch app?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
VoXHTC said:
Yeah? Where is version 1.1.1? 1.1.0 is the only available for download? Or am I a special needs kid?
Click to expand...
Click to collapse
Sorry, maybe I forgot to change the version in the app, 1.1.1 should be the only one linked in the original post.
Sprockethead said:
Force close only.
Click to expand...
Click to collapse
Do you meet the minimal requirements on the original post? Because you have to be running a custom kernel with the T2 interface in it.
wont recognize
im not sure whats wrong, i downloaded this on my phone and it says it dosent recognize the file i downloaded
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,
Read new informations in installation guide
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IF YOU HAVE REBOOTS WHEN YOU ARE USING THE PHONE, IT'S BECAUSE YOU SET A UV TOO AGGRESSIVE, SO, YOUR CPU CAN'T BE STABLE. CHOSE A LOWER UNDERVOLTAGE
IF YOU WANT TO KNOW HOW VOLTAGE CAN REACH YOUR CPU, START STABILITY TEST (DOWNLODABLE FROM MARKET) AND USE IT FOR ABOUT 10 MINUTES, IF PHONE REBOOTS IN THAT TIME, THAT VOLTAGE IS TOO LESS FOR A STABLE CHIP
NOT ALL CHIP ARE THE SAME, IF YOU HAVE A LUCKY CHIP, YOU CAN REACH A LOWER VOLTAGE (AS MINE)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ok Guyz, since show creates the badass governor, i'd want to use it for a better one multicore configurtion
What's the advantages of multicore sistem?
Symply, more parallelization means more performance per second, as i can say, 2 core can compile at last the double quantity of threads than 1, so, 1 core at double frequency can't compile the same number of thread, but it do it faster..
ex..
if you have 2 thread (impossibile), 1 audo and 1 video, a single core @ 2ghz compile firstly the audio, than the video.. the dualcore architecture can compile on core0 the audio and on core1 the video!! this is the powerfully of multicore system.
Ok, since i say it, i create a MOD witch TRY to use this logically.. this MOD uses the limitate frequency of the badass governor, that's why, with ondemand, all of 2 core goes at maxFreq too fast, now, with this badass, the system will not grow up the first limitate frequency until the single core uses more than that frequency.. so.. we can limitate the "ondemand" issue in 3 freq phases..
thus, the actual MOD configuration is it:
Click to expand...
Click to collapse
SCREEN ON:
- dualcore with all cores TURNED ON (hope you understand now )
- governor badass for all of 2 cores
- min freq at 384mhz for all of 2 cores
- max freq at 1.566ghz for all of 2 cores
- first phase freq at 810mhz for bla bla bla
- second phase freq at 1.188ghz for bla bla bla
- third phase freq at 1.566ghz (is the maxfreq)
SCREEN OFF:
- only core0 is TURNED ON
- governor conservative
- minfreq 192mhz
- maxfreq 540mhz
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Badass governor has the same configuration as last show's ondemand governor
So, now, with this MOD we have a pure functional dualcore with the advantages of multicore system, with limitate frequency. The stock situation is 384-810mhz, if the single core (is the same, qualcomm uses asyncronic frequency) needs more than 810mhz, it increases the max freq to 1.188ghz (the sensation original frequency), if 1.188 isn't sufficently, it increeses at 1.566
remember, qualcomm has asyncronic frequency, so, one core can be run at 1.56ghz, the other at minimum mhz..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How to use it?
Click to expand...
Click to collapse
INSTALLATION:
-) flash a kernel witch has badass governor (i advise bricked 1.1) with NO GPU OC and what governor you want, the same for the frequency, mod autochanges those, chose what scheduler you prefer.
1) Flash MOD zip file by recovery
2) Select what MOD YOU want
3) Reboot.
#) You have to reinstall at every Rom Upgrade
# If you want only the UV, select Remove in mod choseing (it's the same as no installing it); you can use the UV mod with all kernels, and all governors
# If you come from V2.0 to 3.0, go to recovery, wipe, format system partition, after that, reinstall rom, reinstall bricked kernel (if it hasn't), reinstall other mods (like battery %), install my mod, reboot.. You will not loose your data
# ONDEMAND VERSION IS NOT FOR GOOD BATTERY CONSUPTION, IF YOU HAVE HUGE BATTERYDRAIN (IT'S WHAT YOU'LL HAVE) INSTALL THE BADASS - BOOST+BOOST VERSION.
DISINSTALLATION:
1) Boot in recovery, flash the Mod
2) Select Remove
3) Reboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Code:
bricked 1.2 -above
V 11.9
> Fixed Screenoff chose
> Changed DEFAULT first phase for better reactive with less power usage
> Other minor changes
###
Added Version for AOSP kernel (NoSense)
V 11.8
> Changed some settings
V 11.7
> Changed some settings for a better fluidity
V 11.6
> Added Remove chose
> Fixed an installation issue of the Aroma
V 11.5
> Added possibility to know if MOD is working, you have to give a cycle on/off of the screen, after that, if it works, you will find a new file in home of sdcard!
V 11
> Changed configuration for less battery drain
V 10.5
> Tweaked badass experience for better battery life (only with bricked kernel 1.4)
V 10.1
> Tweaked screen off conservative
V 10.0
>> BIG RELEASE
> Added possibility to chose frequency
> Added possibility to chose screen off governor
V 1.01
> Fixed freq values in Aroma installer
V 1.0
> Initial Release
HaVe FuN!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FAQ in second post
VIDEO
Click to expand...
Click to collapse
FAQ
Click to expand...
Click to collapse
Witch version could you chose?
The versions of the mod are two:
The 3.7 is the older, it's for the bricked 1.1 version AND for other kernels (don't know if all rom will boot up with my mod, some has issues)
The version 10 and above are for bricked 1.36 and 1.40
What setting could you use?
You can intall what you want, i create those (expecially the 10 versions) witch has the possibilities to be changed as users experience.
I advice to use default settings if you don't know how change, but, you should try to, it will not brick your phone, in fact, you could find a new setting could it be better for your use.
So, try try try
One EX:
If you want a faster phone, grow up the minfreq to 300-400mhz, grow up the first phase at 1.2ghz, put the second to 1.2 or more, and change the maxfreq as you would, OC too.
If you want a better battery experience, decrese minfreq, the first and second phase, decrese the maxfreq too, maybe, with this settings: 192 - 648 - 1020 - 1180 mhz
If you want the lowest battery experience, try with this setting: 192 - 648 - 1020 - 1020 mhz
Be careful, you could have some lags if you chose the lower setting, but, for ex, if you don't play, you can chose a setting as like, 192 - 810 - 1020 - 1180 mhz
So, you have to install, select one setting with you think it's ok, try, if you have lags in some situation, grow up some setting, an re-try til you find your best settages. I don't have your use, so, i don't know if you could have a good esperience with my setting.
How to see if mod is working?
If you have the version 10 or above, you will find a new file in SD card, it calls IBA21ModWorking. if you don't find that, turn on the screen, wait 5 seconds, turn on, refresh the explorer app, and try to see if there is.
If you have the 3.7v you have to download and install system tuner, and see if all cores are turned on.
Why my phone doesen't boot after apply the mod?
Not al roms has the same quality, some doesen't have some little features; my mod uses a whyle cicle witch chages settings from screen-on use to screen-off (standby). If phone doesen't boot up, rom doesen't have the possibility to use the cycles in the script, so, script is unusefull.
Do you need to delete or wipe the rom at every upgrade?
ABSOLUTELY NO, mod auto removes the old script and changes that with the newer one, so, YOU DON'T NEED TO DO ANYTHING, ONLY FLASH THE UPGRADE OR THE NEW SETTINGS WITCH YOU ARE CHANING!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
enjoy my work and, press a lot of thanks buttons! :d
Very very good, the system is smooth and stable, I've only a lag after reboot, and sometimes when start synchronization...
Good work!
Hi nice script. Must the CPU values be truly stock ? Could it take something like 384-1566?
Sent from my Sensation running HyperNonsense v2.3
remus82 said:
Hi nice script. Must the CPU values be truly stock ? Could it take something like 384-1566?
Sent from my Sensation running HyperNonsense v2.3
Click to expand...
Click to collapse
Yep, i could do it.. but.. i tryed it, and.. it only increase the power consuption
framir said:
Very very good, the system is smooth and stable, I've only a lag after reboot, and sometimes when start synchronization...
Good work!
Click to expand...
Click to collapse
Lags depends on badass governor.. it's "normally".. but.. 1 lag per day is not bad, remember, with my configuration you have a better badass configuration with lower power consuption than faux kernel..
Looks awesome
Noticed bug appears after every reboot?
How to change second phase to 810-1134 and delete third phase? Or I don't need it
And soo.. It's fully better than original badass?
http://i.imgur.com/gavOn.png
Standby power consuption with data active!
D-SHEL said:
Looks awesome
Noticed bug appears after every reboot?
How to change second phase to 810-1134 and delete third phase? Or I don't need it
And soo.. It's fully better than original badass?
Click to expand...
Click to collapse
You don't need to delete it since system uses third phase (1.2 to 1.5) only in heavy games and web browsing+flash player.. in web usage cores goes to 1.2 max
Btw.. third phase is the maxfreq governor.. i can change it by script if you want to try
Take.. flash it as you would.. you can come back with stock script
For who doesen't understand.. the phase limis is a real limit.. since system needs more performance, system use the lower limit.. as i can see in my use:
For home scrolling 1 core goes to 1.2ghz, the other is at 192mhz (low power consuption)
For notice bar scrolling 1 or 2 cores goes to 810mhz, it depends on other app.. 1 core at 810mhz can calculate the notify bar
For chrome beta browsing.. in web rendering ( page loading) all of 2 cores goes to 1.2ghz, after that, core goes to 192-810 since heavy scrolls, heavy zoom, or animations in the web page (in google page cores goes to 192mhz )
For browser + flash player, 2 cores are uset at 100% at 1.56ghz since it comes down.. after that.. system uses 192-810.. sometimes only one core goes to 192-1.2
In games core i dont know why i dont play games
So.. the third pase is only a turbo boost, it's used only when system needs more and more power.. the phase is a real limit..
For example.. you have a stock 192-810.. when system needs more than 100% (810mhz) badass grow up the frequency to second phase.. it's the same for third phase.. so.. if system doesen't need more power, badass doesen't grow up the cpu frequency..
In my test i see.. ondemand tweaked + core1 off at my usage has a cpu temperature at about 55degrees C.. with badass, 47
So.. lower tenperature.. lower power consuption!
Sure.. ondemand has a faster one response.. since it grow up frequency every time, for low needs too..
you couldn't have performance plus heavy power..
The "busg" is too.. until system needs more than phase freq, it doesent grow up, so, when there's the necessity of more freq, upgrading is slower than ondemand, and it creates a little lag..
On boot, don't know why but.. only one core is turned on.. it's a system fault of reading script.. if you turn off screen, and turn on, it returns at normally (so.. needs an off-on cicle)
iba21 said:
You don't need to delete it since system uses third phase (1.2 to 1.5) only in heavy games and web browsing+flash player.. in web usage cores goes to 1.2 max
Btw.. third phase is the maxfreq governor.. i can change it by script if you want to try
Click to expand...
Click to collapse
Thanks! Maybe really don't need this
Noticed bug appears after every reboot?
"69force192-1188.zip"
As I can see, this is version without third phase?
D-SHEL said:
Thanks! Maybe really don't need this
Noticed bug appears after every reboot?
"69force192-1188.zip"
As I can see, this is version without third phase?
Click to expand...
Click to collapse
Yep that has only 2 phase.. 192-810 and 810-1.2
I edited last message with informations about your questions
Shouldn't this be in the Development section?
nope.. it's not a developement app.. those are some settages..
if you load the script, and delete it, the settages has been changed..
when you turn on display
screen ON:
- dualcore able
- governor badass for all of 2 cores
- min freq at 192mhz for all of 2 cores
- max freq at 1.566ghz for all of 2 cores
- first phase freq at 810mhz for bla bla bla
- second phase freq at 1.188ghz for bla bla bla
- third phase freq at 1.566ghz (is the maxfreq)
when you turn off
screen OFF:
- only core0 able
- governor conservative
- minfreq 192mhz
- maxfreq 540mhz
it changes that values at every turn on-off of the display.. only 1 time.. so.. if you load the script, and delete it, at display turning off, the script doesen't change the values, and, you will not have the "screen off" setting, so, you'll have the stock badass, so, more power consuption
i repeat, my script is only a numerical setting, it's not a kernel, it changes only the superficially values of the kernel, after that, is the kernel governor the real fault of frequency changing
sure.. with my script you have that 2 configuration.. and.. if you see.. conservative in standby means low power consuption (from 20 to 70ma in standby, depends on the system performance needed)
Is step 6 necessary? I don't have that function in root explorer
Sent from my Sensation running HyperNonsense v2.3
remus82 said:
Is step 6 necessary? I don't have that function in root explorer
Sent from my Sensation running HyperNonsense v2.3
Click to expand...
Click to collapse
it's not obbligatory.. but.. you have it.. long press.. OPEN WITH -> LINUX script (it's the third link from top)
http://i.imgur.com/BbeS0.png
Or you can reboot 2 times.. in first run script changes the name of the file witch turn on the second core.. the mpdecision.. so.. or you do a first manually run.. or you do a first reboot.. script changes the name, but the mpdecision script is already loaded.. second reboot use only my script
Thanks! Will report back after a day of use!
Sent from my Sensation running HyperNonsense v2.3
Edit: solved.
Sent from my Sensation running HyperNonsense v2.3
Iba I notice that media scanner takes extremely long to complete after applying the script. Is it possible to use badass or on demand as screen off governor?
Sent from my Sensation running HyperNonsense v2.3
Sure.. but you loose the advantages of low power consuption..
What is media scanner? How many mhz does it needs?
SmoothMod Kernel (SMK) for Samsung Galaxy Tab 3 8.0 3G (SM-T311), also may work on WiFi version (SM-T310), all stock and CM ROMs.
Development discontinued, read reason here.
This kernel is developed to give you more smoothness and stability than you can have on stock kernel and others.
Warning. Kernel may work on your device/ROM and may not. For me it works at all ROMs and for many people (on 4PDA.RU forum) it works too. Some people say (or said before kernel worked, this also can be) it doesn't work. So do a kernel backup please before you flash it first time. I've never had boot or usage problems with SMK, but it could be because i'm its developer (though it can not be the reason for that I'm always successfully boot it..). So it seems that our devices of the same model might be different. Be careful as I can not help you.
Features:
- Kernel version updated up to 3.2.26 and keeps updating
- Safe CPU overclock to 1.9 GHz with CPU-Boost kernel driver developed also by myself
- Custom (and only here) governor Smooth that is made to give both good battery saving and absolute smoothness. Uses GPU load and io_wait to additionally increase frequency at the right time.
- Kernel has a custom Android service smkd that controls all its features and provides many tweakable settings that you can change very simply: through terminal command "smkd" (instructions below) or "by hands" at folder "/smk" (like usual linux kernel settings at "/proc/sys/{kernel|vm|net}"). The program is written in C language, not as a script, for performance (shell-scripts are very slow when comparing with optimized C-programs).
- Tweak Menu that can be found if you type 'smkd' in your terminal.
- SmoothnessControl - one of smkd's functions that tries to guarantee UI smoothness to your tablet even if there are very CPU-hungry (but not I/O) apps/programs running like android.process.media and others. By default disabled. To enable, type this: 'su -c "scd --enable"' in terminal emulator. To disable, type 'scd --disable'.
- CPU Undervolt controlled through smkd.
- DynBS program (also developed by me) used by smkd to improve battery saving by 40% and more.
- Boeffla Sound Engine with custom settings, not working with Boeffla Sound Control app because smkd controls them (it's needed because smkd fixes engine's sound effects bug). Settings are stored folder "/smk" in files beginning with "boeffla.".
- Cron scheduler configured from file /sdcard/cron/root.
- All the custom tweakable settings described upper are reloading instantly after you change them or on delete (cron schedule file is also under the same watch).
- Kernel is compiled with optimized HYPER-TOOLCHAIN with gcc version 6.0 and maximally optimized compiler configuration.
Customizing kernel:
There is now nothing that needs to be explained, as customizing is pretty simple! Just type command 'smkd' (without quotes) and go through the menu (by entering appropriate symbols) as you want, changing parameters as you need.
Ask, if you have questions
If you have questions or suggestions about my kernel, feel free to write about that here and I will try to answer.
F.A.Q.:
Q.: Do I need to wipe Dalvik/ART cache before/after flashing this kernel?
A.: It is even not useful to wipe caches because they are used by Android only, not by kernel. So, it's not needed.
Q.: The kernel does not boot! What do I have to do to boot it?
A.: Write a message in this thread providing info about what ROM do you use, what Android version it is and what kernel build (kk/lp/mm) and version you are trying to boot. I will reply to that message and try to fix that problem.
Author: me, igoryan94
Download from Google Drive
Before flashing this kernel please do a backup yours first!
Warning! If you have a Jellybean/Kitkat rom, then download the smoothmod-kernel-kk-... build. If you use Lollipop (CM12), then your build to download will be ...-lp.... If it is a Marshmallow (CM13), then download mm build.
Other choice will cause your device to not be able to boot!
(Sorry for my (maybe )bad english)
Plans:
-
Developing now:
-
Changelogs (old*):
1.2.1/1.2.2:
- Returned possibility to load a profile from command line (command 'smkd --load [name]' or 'smkd ld [name]')
- Added custom setting for apps CPU time, now it has two groups: idle and high.
Idle group gives an app very small amount of CPU time, use for hungry apps that you don't need.
High group grants an app a 95% of all CPU time. Use to speed up some apps or games.
It is all very similar to Greenify and others, excepting that this is not battery saving solution, only to smooth up your Android, as Greenify disables an app and CGroup lowers app's CPU execution time available to it.
- I/O settings fully rebalanced for smoothness for system processes and apps processes
- Also added control group for I/O that does like one for CPU, but for I/O and developed its correct (for Android) behavior.
- Current configuration name in smkd menu now correctly saves and loads after reboot.
- Default LMK level changed to 125
XDA->SMK:
1.2:
- Got a smoother UI with better CGroup tweaking
- In case of some situations smkd will notify user with drawing a small square of some color at the left upper screen edge (portrait orientation). For overheat the color is red. When SmoothnessControl gets to work, color is light blue/cyan. If device's load is too high, the color will be blue.
"Notification" will blink when screen updates because the framebuffer devices are not support this method of screen drawing. But it works for now and I think that it is very useful to know the reasons of device's lags and freezes.
- Menu now immediately reacts to input, instead of pressing some characters and then Enter. Modified all menus that way so the interface is now much better.
- When exiting menu, parameters are automatically saved to default profile. No need to care about it anymore...
- Added Quick settings also to RAM and I/O
- Main menu: moved all "p)" menu elements to main menu level, it is quicker to access now
- Some more Quick settings options added
- Added Quick settings to my menu templates, so I will add this to most of the new menus in the future
- Main Quick settings colors changed to blue, additional are still white
- Overclock to 1920 MHz lowered to 1800 MHz because 1800 is much more stable (1920 causes reboots on Marshmallow on my tablet)
- Device now reboots when charging speed is too bad. By default this is disabled. Also added setting "Charge cycle time" and Quick settings for that so you can quickly set up to what charge speed you need (reboots are helpful but not very good for users that want to play device when it charges).
- 'Boost' feature disabled so now DynBS will work as always even when device is laggy
Previous:
1.1.22:
- CPU, Boeffla Sound and Network setting menus in smkd now have the Quick settings feature that helps to configure them by one click instead of tweaking them each
1.1.21.1:
- DynBS updated: now it uses frequencies from 350 to 700 MHz too, so more battery can be saved.
1.1.21:
- smkd now has menu interface which opens by default by command 'smkd' without options.
- All setting commands are removed. Use menu instead.
- In Cyanogenmod ROMs SystemUI is restarted every time when screen becomes disabled, so you may never see it lags or freezes again.
- PCS renamed to SC (SmoothnessControl).
- Overclock enables when device is laggy even when it is disabled in settings
- Redone temperature control: now smkd monitors a device temperature instead of CPU. It leads to better smoothness. Also overheat situations disable some functions like I/O readahead, ZRam, KSM.
- Overheat prevention function fully removed
- Governor Smooth now enables both cores on gestures with two or more fingers instead of simple tap.
1.1.20:
- Added charging compensation: now when battery charging is too slow, CPU Topology and voltage will be changed appropriately for quicker charge.
- Touch boost changed from 1400 to 1000 MHz, but it also boosts busfreq to 400 instead of 267 MHz. Results in better reaction on screen touch.
- Governor Smooth's default sampling_rate changed from 27000 to 16000 for quicker reaction
1.1.19:
- Added ARM CPU Topology for better multithread scheduling
- Some CPU Scheduler changes for smoothness or power saving (tweakable)
- Improved smkd UI code
1.1.18.1:
- Fixed performance/smoothness problems.
1.1.18:
- Added new default configuration "throughput"
- GPU acceleration is now forced for all apps and it is changeable from smkd.
- I/O scheduler SIOPlus added.
- DynBS is returned (one user asked for it as it really saves battery, as he said).
1.1.17:
- User profiles are no more exist, replaced with default configurations" instead. They are: smooth, battery, ram and cool. After each launch of smkd (mostly on reboot) configurations are removed and recreated to always be fresh and up to date.
- Added ability to create, rename and delete profiles by normal way, but default profiles cannot be replaced, deleted or renamed through smkd (only "by hands").
- GPU settings: composition and forced GPU-acceleration from Android settings for developers.
- Tripndroid and Zen I/O schedulers are added.
1.1.16.1:
- Configurations loading is now be always successful (but only if appropriate file exists), without that annoying errors "try again later, please..."
- Small tweaks optimization
1.1.16:
- Overclock now disabled by default, as it was on 1.1.14 and before, for battery saving (overclock eats too much battery). Can be enabled with command 'smkd -c -o 1'. Temperature control is now optimized for both CPU overclock and hardware maximal frequency modes.
- smkd interface improved a little.
- KSM functionality added with some fixes for Mali GPU driver bugs in userspace.
- Default temperature limit is now 64 C (before it was 67 C). This is done for more stability when the weather is hot.
- Some changes for smoothness and stability...
1.1.15:
- Overclock is enabled now for any time when screen is enabled (no more boost).
- Developed overheat preventing functions that cool device when temperature is between 90% of threshold and higher. CPU frequency will be set according to temperature for the moment (for every 2% will be a different frequency). Function can be disabled but it is not recommended.
- All cooling functions now control voltage too to be more effective.
- Governor Smooth tweaked for more balance (oc_nr_run_threshold->6)
- Governor Smooth: changed logic: half-overclock (to 1.7 GHz) will occur if number of processes running is a half of oc_nr_run_threshold tunable.
- smkd now controls I/O scheduler and I/O readahead settings, they are tweakable with smkd command. Profiles change this parameters too.
1.1.14:
- smkd tweaker program fully translated to english and comes now in two languages. Now it uses Android's property 'persist.sys.language'.
If your device configured for any language excepting russian, then program will be in english for you. At the other case it will print out text and messages in russian.
- Improved custom configurations in smkd. Now it loads profiles synchronous with service (by using mutex) instead of relaunching it with shell stop/start (it was too slow and even buggy to do that).
- DynBS will not be in kernel anymore, it is not so effective as needed. Instead, I've added a profile tweaks for my governor Smooth, that tweaks easily changeable from smkd (cmd. "smkd -c -s [0-2]").
1.1.13:
- Cron scheduler now works correctly (i'm happy ), doing exactly what was scheduled by the user at the exact times.
- I don't remember what was in this version because forgot this as I worked on 1.1.14 intensively.
-----
* Newer versions contain changelogs in install archive itself.
Very good kernel. Use [5.1.1] Resurrection Remix 5.5.9 + SMK 1.0.20.1 lp.
Nerovinger said:
Very good kernel.
Click to expand...
Click to collapse
Thanks
stuck at bootanimation..
Sent from my SM-T311 using XDA-Developers mobile app
so.hell said:
stuck at bootanimation..
Sent from my SM-T311 using XDA-Developers mobile app
Click to expand...
Click to collapse
What ROM do you use? Android version, SMK version?
AICP BY GR8NOLE.
SMK V-1.1.12
i try dirty flash n clean flash.stuck at bootamination..
Sent from my SM-T311 using XDA-Developers mobile app
so.hell said:
AICP BY GR8NOLE.
SMK V-1.1.12
i try dirty flash n clean flash.stuck at bootamination..
Sent from my SM-T311 using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like it will not work on AICP ROM, on Cyanogenmod 13 and ResurrectionRemix kernel works fine (I've tested that)... Sorry The reason for that I can not fix this problem is that I do not know (even cannot know) how to make an init.rc (this file starts all Android services on boot) file universal (to support absolutely all ROMs at one time). This is also the reason for three builds of kernel: kk, lp and mm...
Nice kernel. But can you please make a version of your kernel work with the T310 (WiFi)?
Stuck at Bootanimation
ROM: Resurrection Remix 5.6.9 by powermetza
Android Version:6.0.1
SMK version 1.1.12
pawas99 said:
Stuck at Bootanimation
ROM: Resurrection Remix 5.6.9 by powermetza
Android Version:6.0.1
SMK version 1.1.12
Click to expand...
Click to collapse
Try to flash on a clean ROM (with backup of cource)... All fine for me on RR.
Luis_0 said:
Nice kernel. But can you please make a version of your kernel work with the T310 (WiFi)?
Click to expand...
Click to collapse
I can't as i don't know much about modding in '/init.rc' script and also about what differences it has in kernels for T310, T311 and T315... Sorry.
There are too much incompatibilities with builds that are now (they must work everywhere but they don't)...
Ok. Added one question to poll. There are three variants for ROM and two for working or not (six at all), for me all works fine, so I voted for the first three answers.
Version 1.1.14 developer testing ends now, smkd fully translated to english. I will now build the kernel and then begin uploading it to Google Drive.
(sorry for my incorrect english)
igoryan94 said:
Try to flash on a clean ROM (with backup of cource)... All fine for me on RR.
Click to expand...
Click to collapse
Stuck at bootanimation even after flashing on a clean ROM.
waiting for update..
Hey @igoryan94,
Thanks a lot for making this great kernel!
I've flashed the KK version along with the stock ROM http://forum.xda-developers.com/showthread.php?t=2789510. It works very nicely. Would you please show an instruction (or a specific terminal command for newbies like me) of how to overclock CPU to 1.9GHz? Currently the max speed is 1.5Ghz according to kernel audit.
Thanks again
Hey I cant change the cpu frequent through kernel adiutor. As soon as i change the freq to 1920 it changes back to 1500.
igoryan94 said:
I can't as i don't know much about modding in '/init.rc' script and also about what differences it has in kernels for T310, T311 and T315... Sorry.
Click to expand...
Click to collapse
@gr8nole could help him in this?
xdaSEx10 said:
Hey @igoryan94,
Thanks a lot for making this great kernel!
I've flashed the KK version along with the stock ROM http://forum.xda-developers.com/showthread.php?t=2789510. It works very nicely. Would you please show an instruction (or a specific terminal command for newbies like me) of how to overclock CPU to 1.9GHz? Currently the max speed is 1.5Ghz according to kernel audit.
Thanks again
Click to expand...
Click to collapse
CPU frequency is automatically changed to 1920 MHz when special conditions are met (they are: "blocked" processes and waiting for I/O).. Version 1.1.5 will have full 1920 MHz CPU frequency.
I will now upload "developer" version of kernel 1.1.15_dev for KitKat users. If you want, test that) It is not fully contains all changes that i've done, but I'm not at home now and cannot compile new build... For now it has smooth overheat prevention and overclock fully enabled.
Hunter97 said:
Hey I cant change the cpu frequent through kernel adiutor. As soon as i change the freq to 1920 it changes back to 1500.
Click to expand...
Click to collapse
Please wait for SMK version 1.1.15, it will use 1920 MHz as a default frequency always excepting overheat moments (that will disapear very quickly) and governor's battery saver mode.
You can also use a developer version 1.1.15_dev if you use JellyBean/KitKat as your ROM.
Ok, "dev" version released for testing.
When I will return home, I will release another testing version that has an I/O scheduler change functionality, optional Overheat Prevention and changing min_freq to minimal (50 MHz) when temperature event occurs. Maybe it will have even more features (I have smkd code with me, PC is only needed for compiling kernel and ramdisk).
on NoleKat.T310. v1.1 KK 4.4.2 not boot. on CM13 it's ok, but, for me, the best android versioni for this tablet is kk stock and i install NoleKat.T310. v1.1.
jamax80 said:
on NoleKat.T310. v1.1 KK 4.4.2 not boot. on CM13 it's ok, but, for me, the best android versioni for this tablet is kk stock and i install NoleKat.T310. v1.1.
Click to expand...
Click to collapse
SMK will not boot on T310. Only T311.