{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh, you'll love this.. So what actually is different in this kernel?
Core
Updated to 2.6.39.1
Brain F*ck Scheduler implemented for fast task switching, smooth scrolling and possible power saving
Code cleaned and optimized in the right places
Updated Android Binder, Ashmem and Timed GPIO drivers from 3.10-rc5 upstream sources
Compressed with the fastest compressor on the market: LZ4
Processor
Updated CPUFREQ drivers
Voltage Control (undervolted by default to a range of stable values)
Aggressive Overclock
PLL2 Overclock possible inside the app
Updated all the governors to their latest versions
Zen Governor written exclusively for our SoC
Zen
Borrows part of its scaling logic from SmartassV2
Adds Zen Dynamics
This feature makes the governor's parameters completely dynamic. The parameters change by themselves based on various system information (cpu load, suspended state etc.) This ensures that the governor will not bump to high frequencies when it is not needed, and that it will provide enough computational power in high workload cases.
Performance Bias parameter
This is a simple number between 0 and 15 and the only tunable parameter of the Zen governor. When this is changed every other parameter is recalculated through different formulas based on this value. A higher value will make your phone snappier, at the cost of some battery life and viceversa.
TouchPulse and SweepPulse interfaces
TouchPulse is the updated and much more accurate version of the older BoostPulse. This works by giving a slight boost on user input (key or touch).
SweepPulse shoots the CPU frequency to the maximum value when a Sweep function is activated to ensure best responsivity. Don't worry, this happens very fast, so no battery life is wasted in the process.
Suspend profile
When the screen is turned off, the governor keeps the power usage at minimum by re-tuning its parameters
Memory
LowMemoryKiller updated from 3.10-rc5 upstream sources
LMK Whitelist
This is a list of apps which will never be killed by the system, unless you do it intentionally.
I didn't have time to implement a better way for adding apps to this list, so I'll explain the primitive and only usable way right now.
In /system/etc/Badass you will find a file called whitelist. This file can only contain apps in java class path form, separated by commas. Like this:
com.touchtype.swiftkey, org.adw.launcher, com.whatever.app
All the apps that you add to this list, will be written to the LowMemoryKiller at every boot.
LMK Aggressivity: this parameter makes app-killing more or less aggressive. It can be controlled inside the app.
Latest ZRam driver with LZ4 compression (activated at boot so you won't have to bother)
Sweep functions
When the screen is off...
Sweep2Wake
This gesture wakes the phone by sliding your finger from left to right in the middle of the screen
Its sensitivity is controlled by a single parameter (factor) which can be modified inside the app
DoubleTap2[Wake/Play/Pause]
This gesture wakes the phone with a double tap on the screen if the lock timeout of 5 seconds hasn't passed yet. If the timeout has passed, double tapping the screen will Play/Pause the music.
The Media Control feature (Play/Pause) can be disabled, making DoubleTap2Wake work even after the lock timeout has passed.
Pocket Keyguard
This feature prevents accidental unlocks when the phone is inside your pocket.
When the screen is on...
Sweep2Lock
Sweep4Menu
SweepKeys
All these functions work by swiping up from the first 3 pixels at the bottom of the screen(deadzone).
The Deadzone and the Sweep sensitivity are changeable in the app.
Internet
Westwood+ TCP Congestions Algorithm
Adaptive RED net scheduler backported from 3.4 upstream sources
Congestion window values tweaked
TCP Proportional Rate Reduction
Performance
Zen and ROW I/O schedulers
Triple Buffering
TinyRCU
Dynamic Filesync
Using the 20-50x faster frandom generator instead of the default random.
Never depleting entropy using Haveged and some new kernel code.
Dynamically changing kernel values based on suspend profiles (writeback ratios, cache pressure etc)
System cleaning every 3 days:
Zipalign every apk
Vacuum and Reindex every SQLite database
Clean the garbage data created by the system
Clean app caches
SpeedMod (disable kernel debugging)
Remove 98% of the active debugging code
USB Fast Charge
Native Multitask Enhancer
Replace services.jar Supercharging with a more native approach
Make Home app unkillable
Raise PreviousApp priority to make task switching faster
Handle CPU time allowed for the foreground app
Raise priority of the following processes
Kernel Threads
ALSA driver (audio playback)
Keyboard
SystemUI
Restrict resources used by the media scanner
Dev's last words (a.k.a. read this carefully before saying anything stupid)
This is a stable version and I call it final. I won't update it, unless there are some major bugs like setting phones on fire, giving them artificial intelligence or sh*t like that.
DON'T USE ANY OTHER TWEAK ON THIS KERNEL. These tweaks include, but are not limited to:
Performance Pack
Fly-On Mod
CrossBreeder
I/O Tweaks
V6 Supercharger
Whatever else with a cool name which has the words script, pack or mod in it
Don't get me wrong, these mods are good (most of them), but what's good is already included in the kernel itself
Use Greenify. It is an awesome app, and it does its job very well. I couldn't fully replicate its' features inside the kernel because I don't have access to Android APIs.
The first boot will be slow, due to the zipaligning and SQLite optimizing. Don't freakin' panic. This will happen only once in three days.
If you feel that the system is slow with the kernel, raise the Performance Bias, the LMK Aggressivity and maybe your max CPU frequency. The default values are optimized for ICS, not JB. Play with those values until you find that sweet spot.
Change your damn Superuser app. Use SuperSU or an insecure SU binary. The original SU binaries found on ROMs are freakin' slow nowadays.
Even better, use ICS. JellyBean is not for our low-end phones. But, your choice..
The key settings for the SweepKeys are ROM dependant. For example Recents SweepKey might not work on some JB ROMs. I can't do anything to fix this.
Don't be lazy. I'm here to help, but please show me that you've made some effort on the research for your questions.
And the thanks go to..
Androidarmv6 Team
Erikcas
psyke
A_U
Franco
Boype
Benee
AOKP Team
Paul Reioux (Faux)
Stratosk
zeppelinrox
Ezekeel
Downloads
Badass.v2(AOKB-JB).zip - 6.65 MB
Badass.v2(AOKP-ICS).zip - 6.63 MB
Badass.v2(AOSP-ICS).zip - 8.29 MB
Badass.v2(CM9.2).zip - 6.62 MB
Badass.v2(CM10.1).zip - 6.65 MB
Badass.v2(CM10).zip - 8.89 MB (UMS not working)
Installation
Boot into recovery
Wipe data
Re-flash your current ROM to avoid conflicts
Flash the appropriate kernel zip
Reboot and wait 5-10 minutes for the first boot to complete
Use the integrated app to control the kernel
Ramdisk sources:
Ramdisk-tass
XDA:DevDB Information
Badass.v2, a Kernel for the Samsung Galaxy Mini
Contributors
alin.p
Kernel Special Features: Sweep2Wake, DoubleTap2Wake, Native MultitaskEnhancer, Brain F*ck Scheduler
Version Information
Status: Stable
Created 2013-09-27
Last Updated 2013-09-27
Reserved
Hey guys. I will leave my town in 2 hours and I won't have access to a computer for at least one month. I will be able to respond from my Mini, but I surely won't be able to fix any bugs that might appear.
Until then, take care
You did it... it's happening )
---------- Post added at 03:15 AM ---------- Previous post was at 02:28 AM ----------
Ummmm.... what can you tell me about performance bias? I'm not familiar with this term...
Sent from my GT-S5570 using xda app-developers app
XDRdaniel said:
You did it... it's happening )
---------- Post added at 03:15 AM ---------- Previous post was at 02:28 AM ----------
Ummmm.... what can you tell me about performance bias? I'm not familiar with this term...
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Please read the whole thread before asking. Everything is written there. I know I could simply tell you what that term means, but I need people to read everything.
I don't have time to answer the same questions over and over again.
First impression: insanely fast
But a minute after boot, bad ass control crashes and all sweep2things stop working. I rebooted a few times and no change. So, i replaced superuser with supersu. Again after several reboots, control app keeps crashing thus stopping all sweep2things... to reuse them I have to reboot.
Steps I followed:
Wipe data and cache
Format system
install cm9.2 plus from erikcas
Install badass kernel v2 (for cm9.2)
I will reflash everything again and hope for better...
XDRdaniel said:
First impression: insanely fast
But a minute after boot, bad ass control crashes and all sweep2things stop working. I rebooted a few times and no change. So, i replaced superuser with supersu. Again after several reboots, control app keeps crashing thus stopping all sweep2things... to reuse them I have to reboot.
Steps I followed:
Wipe data and cache
Format system
install cm9.2 plus from erikcas
Install badass kernel v2 (for cm9.2)
I will reflash everything again and hope for better...
Click to expand...
Click to collapse
Not for me.app crashes only if it do not get su access in required time.
Otherwise it is awesome.yippe this kernel solves the problem of softkeys
Edit-Extreme right and left keys dont work for me(sweep4menu..lock)
Sent from my GT-S5570 using xda premium
Wich rom are you using?
XDRdaniel said:
Wich rom are you using?
Click to expand...
Click to collapse
My own port tw 5
Edit-menu is working after disable and enable
Edit-one think i want to ask.would these keys be disabled while playing games
Sent from my GT-S5570 using xda premium
Man!! Badass v2 arrived!! thanks alot @alin.p
I reflashed rom and kernel and the problem persisted so i deleted the app performance is still here and sweep2things are working.
arpitkh96 said:
My own port tw 5
Edit-menu is working after disable and enable
Edit-one think i want to ask.would these keys be disabled while playing games
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
As I said, these keys are ROM dependant. If your ROM has different key layouts, some keys won't work as expected. I'm using a modified ICS keylayout but I can't make it universal.
I wish I could disable them in some cases (keyboard, status bar expanded, games) but the kernel doesn't have access to android APIs and can't distinguish between the applications.
XDRdaniel said:
I reflashed rom and kernel and the problem persisted so i deleted the app performance is still here and sweep2things are working.
Click to expand...
Click to collapse
The kernel is stable, but the app has some problems. I'm not a good Java programmer, I did my best to make it work in normal cases. I never experienced su problems with the app because I have a binary that grants su permission instantly without my interaction. Install SuperSU and set it to always grant permission to get rid of this problem.
Thanks for this! Hope you can make this compatible with cm10.2 as well.
The time has arrived... Let's ROCK!
Sent from my GT-S5570 using xda premium
Yeah @alin.p great u finally did it!!
---------------------------------
Phone : Samsung Galaxy Mini S5570
OS:
•AOSP ICS Touchwiz V5 by A_U
•Android 4.0.4
•Baseband XWKS2
•Kernel: 2.6.37.6 Badass v1.9 by alin.p
•Recovery CWM v4.0.0.5
Mods:
PureAudio, Mounts2SD, ODEX through Universal ODEX script, AdBlock by AdAway
---------------------------------
Gesendet von Tapatalk 4 beta
awesome is the only thing i can say cause i cant find words to dscribe how supremely awesome you are @alin.p
Oh it surely is badass
Sent from my GT-S5570 using xda app-developers app
Well,after a few hours of usage,my impression is too good now my phone is really snappy.. multitasking works better than before.. my only concern is sweep2wake. It works well if the phone is not being idle for so long. But it didnt respond well when the phone is in idle for so long. Other sweep functions works perfect havent tried the battery life though, but till now its good
One suggestion to all: Do a fresh rom install,and then install Badass V2..
Rajesh_m said:
Well,after a few hours of usage,my impression is too good now my phone is really snappy.. multitasking works better than before.. my only concern is sweep2wake. It works well if the phone is not being idle for so long. But it didnt respond well when the phone is in idle for so long. Other sweep functions works perfect havent tried the battery life though, but till now its good
One suggestion to all: Do a fresh rom install,and then install Badass V2..
Click to expand...
Click to collapse
I didnt do a fresh rom install, because i have so many apps im lazy to backup them.But the badass works perfectly i didnt notice a problem
Rajesh_m said:
Well,after a few hours of usage,my impression is too good now my phone is really snappy.. multitasking works better than before.. my only concern is sweep2wake. It works well if the phone is not being idle for so long. But it didnt respond well when the phone is in idle for so long. Other sweep functions works perfect havent tried the battery life though, but till now its good
One suggestion to all: Do a fresh rom install,and then install Badass V2..
Click to expand...
Click to collapse
I do fresh install on cm10.1 and have the same like You sweep2wake doesnt responsive for long time blocked screen but i have solution for that, cover proxomity sensor for 1sec and then try sweep2wake for me work perfect
wytapatano z Ainol Novo 7 Fire PA 3.99
Charlie said:
I didnt do a fresh rom install, because i have so many apps im lazy to backup them.But the badass works perfectly i didnt notice a problem
Click to expand...
Click to collapse
Strange! Even i tried to do the same initially(i am lazy too ),waited for like 30 minutes,but it keeps on playing the bootanimation. Then i went to recovery,did a clean install,and everything was perfect
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Version 1.3 [Released 9/7/11]
Proton Voltage Control is an easy to use app that allows you to set custom voltages for Nexus S phones running a supported version of Netarchy and Matr1x kernels (1.3.0.6 for Netarchy and 4.0 for Matr1x and up) This means you no longer have to muck around with command line codes and scripts, just one easy to use app!
I am a busy highschool student, with no solid income. If you like my app, please consider a donation
Click to expand...
Click to collapse
Downloads
Update 16/9/11: Due to requests, I have built 1.3 again but with a different release key. Please UNINSTALL any old version before installing!
Version 1.3 ProtonVoltageControl-130.zip
Emergency Restore: proton_emergency_boot.zip
Usage
Enter in your new voltages in the 8 text boxes, or use one of the 3 buttons at the top to give you a base to try.
Hit Apply to set temporarily, and see how the voltages perform. If you reboot at this stage, the new voltages will be lost
If these new voltages work well on your phone, enter them in again and this time check 'Save on Boot' then hit Apply. These voltages should be applied upon startup every time now
Easy!
- It is easier to press one of the 3 voltages buttons to give you a base to work on
- The suggested voltages is mostly -20mV on all frequencies (from stock voltages) except for 1.4ghz and 1.3ghz which have been raised ever so slightly
- 'Save on Boot' creates an init.d script called proton_voltage_control with your entered values, so don't be alarmed if you see an extra init.d script
- Press Menu and Emergency Boot Zip to download a flashable update.zip to remove any 'Save on Boot' files in case you can't boot up due to setting the voltages too low. Boot into Recovery and flash like any other update.zip
Enjoy! Please ask if you have any questions, I will try to help with them. Standard disclaimer applies, I claim no responsibility for anything that goes wrong with your phone due to misuse of this app.
Also on the Market! https://market.android.com/details?id=com.jonathongrigg.proton.voltagecontrol
Proton Voltage Control is fully open sourced
Source is available at my Github, https://github.com/jonathongrigg/ProtonVoltageControl
Credits
Jonathon Grigg
Spiicytuna [New UI overhaul]
Xan [Original Galaxy S app which gave me inspiration to write my own from scratch for the Nexus S]
'Serge' (from MarketEnabler I believe) [ShellInterface code]
Donators
Tord Persson
Should work on all Nexus S models (including the 4G)
Sent from my Nexus S
Can I request custom settings save profile? In case something doesn't work you might want to go back to a profile and change things around.
Using it, and loving it so far
Sent from my Nexus S using XDA App
Good App. I will buy Pro Version if you publish one in the market.
Sent from my Nexus S using XDA Premium App
Had been using script manager with custom scripts to get settings loaded on boot, but have deleted them to use this
Really like the app, can't wait for UI improvements (even though it is fully working now).
Get this thing on the Market with a pro version!
Edit: Jonathon, maybe you could go in depth a tad more on usage , just for the moment because people new to UV may be confused what it does and how it works exactly
thanks dude, it's awesome! I've been waiting for an app like this to UV netarchy's kernels!
i'm running CM 7.0.3 with netarchy's 1.3.2, just did a -50mV across all frequencies and it has been working very well.
Please forgive my ignorance... but what exactly can be obtained by altering voltages??
Better battery life etc?
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Dario777 said:
Please forgive my ignorance... but what exactly can be obtained by altering voltages??
Better battery life etc?
Click to expand...
Click to collapse
Better battery life and lower temperatures.
Sent from my Nexus S using XDA Premium App
jello24 said:
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Click to expand...
Click to collapse
Do you have super user set up properly? Clear permissions from the app and try again
Sent from my Nexus S using XDA App
Thanks for this. Great app, makes it very easy.
Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (Perfection)
Great app! Definitely saves time when tinkering with the voltages.. Thanks!
Has anyone tried this with default kernel from superaosp 8.2? It looks very similar to netarchy....
Also any recommendations for voltage levels?
Sent from my X10i TripNMiUI-IRIS using XDA App
can you add support for trinity kernels?
shubu000 said:
Has anyone tried this with default kernel from superaosp 8.2? It looks very similar to netarchy....
Also any recommendations for voltage levels?
Sent from my X10i TripNMiUI-IRIS using XDA App
Click to expand...
Click to collapse
Voltage levels will depend on individual phones, some will go lower while others would bootloop so low (good idea to not use set on boot to start with until you've tested it for a bit). There is a suggested voltages button in the app which is -25mV across all 8 frequencies as a starting point. Most phones should be able to handle this, but there are a few exceptions.
Sent from my Nexus S
The only two reasons why you would want to decrease or under volt (UV) set your frequencies is to save battery and extend your processor life expectancy.
The only reason to to increase or over volt (OV) your frequencies is to get a higher clock speed on your processor. Some phones will not handle the default setting and need extra voltage for transistors to get a better and cleaner signal.
This is very much the same principle as in any desktop PC. You increase voltage to be able to overclock but if you have a good quality fabrication, ie later production processor or maybe manufactured in a different fabrication facility you might be able to get away with less voltage which in effect lowers your battery usage. You could also achieve the same by better cooling, but unless you expect to keep ice on your phone, this doesn't really make sense.
To dig deeper into the matter, as far as I understand, when higher clock speeds are requested of a processor, transistors give away more heat. This in turn will also swell them up and they will start to short from one to another and/or loose current flowing through them. Another effect is the slowing down of the transistor gate on/off. All these conditions may trigger an error and in some cases a major freeze of the processor.
There... a quick explanation to have this app available.
BTW, we should also thank Netarchy for making such settings available in his kernel. Cheers
jello24 said:
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Click to expand...
Click to collapse
bringonblink said:
Do you have super user set up properly? Clear permissions from the app and try again
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yeah SU was set up to allow the UI to work, but I cleared that permission and ran the program again allowing it to go but it still won't save on boot. Existing voltages always show the default, instead of my desired settings.
I even tried it where i'd have to keep clicking allow on SU to get it running but it still won't save.
any other suggestions?
jello24 said:
yeah SU was set up to allow the UI to work, but I cleared that permission and ran the program again allowing it to go but it still won't save on boot. Existing voltages always show the default, instead of my desired settings.
I even tried it where i'd have to keep clicking allow on SU to get it running but it still won't save.
any other suggestions?
Click to expand...
Click to collapse
Can you try the 'cat' command to list the voltages in Netarchys thread and see if its the same as the existing voltages shown in Proton.
Sent from my Nexus S
jello24 said:
Thanks for the UI for UV'ing! It makes life so much more easier than typing on terminal.
One concern though, my settings are not saving on reboot. I'm running SuperAOSP 8.0 with Netarchy 1.3.0.12 CFS 2.3.4 Universal and after entering my desired values and checking Save on Boot, upon restart the app reads back the default voltages again (1450 etc...).
The program does state that it saves it to init.d but other than that it doesn't save it. Am I doing something wrong or am I supposed to re-enter values everytime i make changes to my phone that requres a reboot, which is a lot considering i try out a lot of the ROMs out there often.
Click to expand...
Click to collapse
I think I might know what your problem is. You have to hit apply after you select set on boot, otherwise it won't save the changes.
I didn't realise this the first time either!!!
I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
Completely rewritten whole app! Epic 4G FCs gone thanks to theimpaler747
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot
xan said:
Hi I've seen some reports on market that new version is broken on Epic4g. Anybody knows whats goin on?
Logcat output welcome.
Click to expand...
Click to collapse
First!!!
I tried it with the Bonsai Rom a couple of days ago and it worked for me. I purchased the extreme and I undervolted straight across the board 250mv and I have no problems so far. I think it all depended if the kernel on the phone is compatible or not.
xan said:
Hi I've seen some reports on market that new version is broken on Epic4g. Anybody knows whats goin on?
Logcat output welcome.
Click to expand...
Click to collapse
It made me smile when I saw that you posted. Taking a personal interest and such.
I think you might be getting reports from Syndicate people. Syndicate's Twilight kernel didn't implement sysfs very well. Voltage Control will recognize it but changes can't be made and some clocks aren't read correctly. PimpMyCPU won't read it all.
Genocide kernel, Vision kernel, and Bonsai's kernels all work flawlessly.
Thanks
This rewrite costed me *a lot* of work seeing 1 star ratings on market makes me sad ;p
I'm using twilight kernel without any problems but I'm no longer on SFR anymore.
Sent from my SPH-D700 using Tapatalk
xan said:
Thanks
This rewrite costed me *a lot* of work seeing 1 star ratings on market makes me sad ;p
Click to expand...
Click to collapse
Yeah, that's not right. My Epic doesn't play nice with Voltage Control but I know better than to rate the app bad. These Epics each have a mind of their own. Some like undervolting, some dont. Some like certain ROMs better. I can run 1400 all day but no undervolting for me
Sent from my SPH-D700 using XDA Premium App
FCS on some kernels fixed ;p
Thanks going to theimpaler747, for detailed bug report and testing
I have found multiple issues with the Twilight kernel, I love the rom, just Genocide has been a lot more stable AND I never had any issues with Voltage Control. I was wondering if you might incorporate multiple profiles like SetCPU? I had to start looking for a different program when it would constantly lock my phone when trying to use them and then I found Voltage Control, and after the rewrite it just makes it that much easier to use.
This might be good, true.
Multiple profiles seem doable...
xan said:
FCS on some kernels fixed ;p
Thanks going to theimpaler747, for detailed bug report and testing
Click to expand...
Click to collapse
Happy to have helped out for a great app!
hey all, im running SFR 1.1.1 with its stock twilight kernel.
i use to run genocide, but i think i messed up with the UV features and i started getting a lot of lockups. right now i just run setcpu with 1300/400 and i seem to be ok.
i think i bought the WRONG voltage control app also. i bought voltage control extreme by sulph8.
i would love to get back to 1400/400, but im really unsure what the best course of action is. are there default voltage settings in this app? initially, i'd like to run 1400/400 with all the standard voltage settings to see if my phone acts normally again.
Well, Voltage Control by nitr8 is a unlock key for 'mine' voltage control. For now all money goes to him, he promised to send it to me.
To revert to stock settings -> Chose delete boot settings and reboot.
Viola, you have booted on stock settings!
Then set desired frequency limits and you are done
so i should set my setcpu back to 1000, remove setcpu, flash genocide kernel, install your voltage control and start from there?
Sounds ok
what should i set my governers to?
Well, depends on your experience with kernel, generally:
For battery saving try conservative.
For reasonable performance try interactive/ondemand or smartass.
Some kernels have bad implementation of some governors, which can make them unstable, so you need to test, test, test and observe
From my experience smartass (where implemented) is very smooth.
Stock Samsung Gingerbread kernels came with ondemand (not entirely sure)
Stock Froyo/Eclair was conservative.
useport80 said:
so i should set my setcpu back to 1000, remove setcpu, flash genocide kernel, install your voltage control and start from there?
Click to expand...
Click to collapse
Well, I just flashed it again on Genocide. I am running 1400/200 on demand. I am going to check CPU Spy to see if it performs similar to SetCPU. Curious if on demand still drops below 200 if its set as my minimum like Set did
Sent from my SPH-D700 using XDA Premium App
Voltage Control doesnt use any "hacks" for setting frequencies, it just works with standard implemented sysfs.
The governor is responsible for respecting max/min frequency, its kernel implementation that should keep CPU running within desired freqs.
Can the UI include a CPU temp and aninfo page?
Sent from my armed and operational battle station.
SGS's only thermal monitor is refferred as "battery"...
Info page is somewhat coming, but I have to be sure what and how to put there.
Hi all, welcome to SwiftExtreme MIUI/CM kernel
Version-20112011 is the final version of SwiftExtreme, I'm not going to release any kernel in MIUI/CM in XDA, there 2 reasons :
1. I got more than 800 downloads in kernel, but I rarely see people saying thanks(you can see my thanks only around 100, compared with 800 downloads), so I think I don't have a reason to publish my works in XDA anymore. I'm going to make SwiftExtreme to support ICS later, and only need to be release on our local forum that know how to thanks for hardwork
2. Some version of ROM include my kernel without notice me that kernel is used as their kernel ROM. I don't have a problem with that, but please tell me, so I know how is the kernel spread around the globe.
I hope everyone can enjoy my latest kernel, and work with patch that I provide againts CM kernel source code(October 19,2011)
WARNING : YOU'LL GET A LITTLE DELAY IN WAKEUP SCREEN PROCESS/CALLING ACCEPT
Kernel-20112011 - FINAL
Features :
-[20112011] Add autogroup to increase interactivity when screen on
-[20112011] Add autogroup to background process, it will reduce background process trying to get cpu attention by grouping process tasks, slightly increase battery lifetime
-[20112011] Update kernel to 2.6.32.48, more bug fixing
-[20112011] Reduce backlight voltage need, slightly increase battery lifetime
-[20112011] Introduce Powersaving version, the different is, powersaving doesn't have spare frequency at screen off, based on my testing, it increase lifetime around 10-20%, but gives you more delay when switching screen state
-[20112011] Introduce ability to turn off second core at specific frequency, slightly increase battery lifetime, read this http://forum.xda-developers.com/showpost.php?p=19419710&postcount=334
-[13112011] Reduce cpu voltage a little bit
-[20112011] Add voltage in some area to increase stability
-[13112011] Increase second core turn on frequency limit threshold and delay second core turn on, faster second core turn off. It should increase your battery lifetime when doing light task, like reading facebook, scrolling homescreen/drawer, watching movies, etc
-[12112011] Enable EXT2 and LED fix problem
-[12112011] DDR Undervolt
-[12112011] Return back to 216Mhz as lowest stock, introduce +100Mhz as spare frequency to make kernel can breath a little when doing task at screen off. It should make your screen turn on much faster and reduce MP3 glitch. With this method, kernel will work at 216Mhz-316Mhz at screen off
-[12112011] Add Simpe I/O as kernel default scheduler, watch out for tweakpack, it may change kernel scheduler on one its script
-[12112011] Now compiled with gcc 4.6 with -Ofast option
-[12112011] Implement some patch that fix memory leak, optimize lowmemorykiller function, and mmc sleep mode
-[05112011A] Now compatible in nightly CM and MIUI begins from 1.11.4 version
-[05112011A] reduce some volt in lowest clock and sdram
-[05112011A] use git SHA-1, it should speedup kernel boot process upto 11%
-[05112011A] Improve memcpy and memmove kernel performance
-[05112011A] CRC32 algorithm optimization. it should increase any activities that use CRC32 algoritm
-[05112011] Replace deadline with noop as kernel I/O scheduler
-[05112011] Compiler cflags optimization, use O3 right now....
-[05112011] Increase standby frequency clock to 256Mhz instead 216Mhz, slightly increase screen/phone call wakeup, battery drain itself doesn't change too much, still around 20% in 7 hours 3G, all sync ON in my area while standby.
-[05112011] cgroup speedup
-[05112011] Introduce file sync disabled, it boost kernel write algoritm with slightly increase rate data corrupt when your phone get crash(use androbench to bench the write speedup, bench first before flash the kernel to see the different). beside write access speedup, it make MIUI more smooth, faster installing apks, and in some games it seems the loading much faster
-[05112011] Increase TCP initial congestion window to 10 and initial receive window
-[05112011] Remove Jhash3, replace with Jhash speed tweak
-Provide 1.5Ghz and 1.2Ghz version(use PimpmyCPU to control clock and voltage)
-Excellent standby power management(Make sure you remove any script that control screen state ON/OFF when using this kernel, it will mess the kernel mechanism)
-[30102011]JHASH 3.0 patch
-SLQB as default allocator
-[30102011]Deadline I/O Kernel patch NAND storage optimize
-Improve scheduler latency
-Voodoo V1 sound driver
**********************
HOC-20112011
SwiftExtreme-1.5Ghz
LOC-20112011
SwiftExtreme-1.2Ghz
POWERSAVING-HOC-20112011
PowerSaving-SwiftExtreme-1.5Ghz
POWERSAVING-LOC-20112011
PowerSaving-SwiftExtreme-1.2Ghz
**********************
HOC-13112011
SwiftExtreme 1.5Ghz
LOC-13112011
SwiftExtreme 1.2Ghz
**********************
LOC-12112011-Preview works for MIUI begin 1.11.4 version and CM
SwiftExtreme 1.2Ghz
edit : an update if you get SOD when testing preview version
SwiftExtreme 1.2Ghz-Test
**********************
HOC-05112011A works for MIUI begin 1.11.4 version and CM
SwiftExtreme 1.5Ghz
LOC-05112011A works for MIUI begin 1.11.4 version and CM
SwiftExtreme-1.2Ghz
**********************
HOC-05112011 works for MIUI before 1.11.4 version
SwiftExtreme 1.5Ghz
LOC-05112011 works for MIUI before 1.11.4 version
SwiftExtreme 1.2Ghz
**********************
HOC-30102011
SwiftExtreme 1.5Ghz
LOC-30102011
SwiftExtreme 1.2Ghz
**********************
Credits :
Morfic, Benee, Cpasjuste, kiljacken, Supercurio, arighi, faux123, pals in kaskus.us forum
DIFF PATCH CODE: DIFF PATCH
Thanks for muffindrg that provide benchmark score Quadrant and Antutu...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tips increasing battery life :
1. Build your rom installation with Toogle2G, it helps a lot battery drain when screen off. 3G only active while screen ON, and get turn off automatically back to 2G when screen OFF.
2. Pick correct baseband, better signal, more battery life
3. When you're using script in init.d, just make sure you don't have lot of scripts that do looping on background. eventhough it only takes small amount resources
fire3d got it running on stock, based on his testing, brightness not working on stock, check it:
http://forum.xda-developers.com/showpost.php?p=19241088&postcount=181
nice work mate!
can you tell me what the benefits are when you compare it with VorkKernel?
owain94 said:
nice work mate!
can you tell me what the benefits are when you compare it with VorkKernel?
Click to expand...
Click to collapse
I can't promise anything, the only thing that I can tell, you'll get Excelent Standby Time...
fajarep said:
I can't promise anything, the only thing that I can tell, you'll get Excelent Standby Time...
Click to expand...
Click to collapse
then im gonna flash it right now
do i need to remove my setCPU screen off profile?
owain94 said:
then im gonna flash it right now
do i need to remove my setCPU screen off profile?
Click to expand...
Click to collapse
Yes.., it will mess the kernel screen off handling
fajarep said:
Yes.., it will mess the kernel screen off handling
Click to expand...
Click to collapse
thanks for your help mate! will give you feedback after a couple days of use
nice work buddy
I take it that this should also work with cm7?
deadmetal said:
I take it that this should also work with cm7?
Click to expand...
Click to collapse
I think it will work with cm7 rc1, because MIUI use that as base.
Sent from my Optimus 2X using XDA App
Thanks for your work, I'll try and report back
Thanks for your job
But i have BSOD after a call with SwiftExtreme HOC-30102011
on MIUI 1.10.28
el_liberator said:
Thanks for your job
But i have BSOD after a call with SwiftExtreme HOC-30102011
on MIUI 1.10.28
Click to expand...
Click to collapse
I'm already test it for 3 days, got no problem receiving call, there is a probability that your phone doesn't support low clock when in call... If your phone doesn't support it.., SwiftExtreme is not for you .
maybe on next version, gonna make SetCPU compatible, so it can make "on call" frequency control..
cheers
fajarep said:
I'm already test it for 3 days, got no problem receiving call, there is a probability that your phone doesn't support low clock when in call... If your phone doesn't support it.., SwiftExtreme is not for you .
maybe on next version, gonna make SetCPU compatible, so it can make "on call" frequency control..
cheers
Click to expand...
Click to collapse
i'm using Vorkkernel without problems
with your Kernel, Setcpu or CPU Master must be turned off?
When you're in call, screen off. When screen off, kernel down clock mechanism get triggered. So, your phone probably not support low clock when in call. This kernel down clock when screen off is the most important feature of this kernel.
Sent from my Optimus 2X using XDA App
el_liberator said:
i'm using Vorkkernel without problems
with your Kernel, Setcpu or CPU Master must be turned off?
Click to expand...
Click to collapse
just read his first post:
fajarep said:
-Excellent standby power management(Make sure you remove any script that control screen state ON/OFF when using this kernel, it will mess the kernel mechanism)
Click to expand...
Click to collapse
fajarep said:
When you're in call, screen off. When screen off, kernel down clock mechanism get triggered. So, your phone probably not support low clock when in call. This kernel down clock when screen off is the most important feature of this kernel.
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
OK , Thanks , i disabled option "in call" and "Screen off" on CPU Master
and works fine
Works great on 1.10.28, thank you.
Sent from my Optimus 2X using XDA App
Can't wait till someone gets this supported on the G2x
The same problems here. In call my phone freeze and i can't respond to any call. When i try to unlock it my phone don't wake up and i need to quit the batery and wait for a new freeze. I can uninstal this kernel or i need to put another one?
vladutz9 said:
The same problems here. In call my phone freeze and i can't respond to any call. When i try to unlock it my phone don't wake up and i need to quit the batery and wait for a new freeze. I can uninstal this kernel or i need to put another one?
Click to expand...
Click to collapse
just try with max OC 1.2..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits to codeworkx for the base aosp kernel!
Features:
More shedulers
row I/O scheduler
sio I/O scheduler
vr I/O scheduler
More governors
cpufreq_smartass2
cpufreq_lagfree
cpufreq_pegasusq
cpufreq_lazy
cpufreq_lulzactive
cpufreq_minmax
cpufreq_abyssplug
cpufreq_wheatley
cpufreq_scary
cpufreq_HYPER
Updated to linux kernel 3.1.0 -rc1
Dualboot support
Brightness adjustments for darker screen settings (good in low light conditions)
Synced with latest codeworkx fixes
Undervolting support
USB fastcharge support
Cleaned up arm source
Compiled with hard float instead of soft float
Greenblob 1.1.72 LTS (Changelog):
Added added row I/O scheduler
Added added sio I/O scheduler
Added added vr I/O scheduler
Upgraded from 3.0.72 to 3.1 -rc1
500 commits FTW! Happy changelogging on git
Greenblob 1.1.1 LTS (Changelog):
Updated kernel from 3.0.36 to 3.0.72 (We´re now on latest linux 3.0.x releases)
Updated ~700 commits (20 Github pages lool). Those are from 3.0.36 to 3.0.72
Hopefully working now on latest cm nightly (working here on my chameleon os)
Go for changelog on github!
Greenblob 1.1 LTS (Changelog):
Fixed auto reboot in recovery
Fixed rebooting during backup in recovery
Fixed some governor stuff
Updated dualboot
Greenblob 1.0 LTS (Changelog):
Added governors
Added 'long-time-support'
DevPrev 6.3 (Changelog):
Added usb fastcharge
Added undervolting support
Default cpu speed at 300mhz
Synced latest changes from cm repo
DevPrev 6.0 (Changelog):
fixed cpu staying at 600mhz
added DualBoot support (Credits to chuandinh for the method. Its the same as Galaxy Note 2 uses)
All dualboot related questions please visit the dualboot thread!!
DevPrev 5.2 (Changelog):
restart after quitting coding kernel
adjusted gamma values for smartphone usage in dark light
wifi driver update
mhard float instead of msoft float
cpu frequency change based on screen on/off
touchkey timeout 2 seconds
cleaned up arm source
TWRP for now - I was just trying something, will revert to cwm soon
Important:
There are no other features than mentioned in the changelog. I restarted the kernel and I think I wont add OC etc. This kernel is not ready yet but damn stable and fast. No need to oc anything (my opinion).
For brightness (gamma) adjustment: You will notice a heavy brightness drop between lowest and lowest +1 step brightness. The one before the lowest was the lowest brightness that comes with normal cm kernel. I will make a better transition between the last two steps within the next update.
DevPrev 5 (Changelog):
Now compatible with cm10.1
Some bugfixes
New control app now on google play!
DevPrev 2 (Changelog):
Updated to latest codeworkx sources
Added undervolting support
Added usb fast charge mode support
Readded 1.2Ghz slot
Greenblob kernel control:
This is the official app to control all features of Greenblob kernel (for now available on Galaxy S2G, visit XDA for infos).
But most features can also be used on any other device! (Ok, not any but for a big number).
You can:
- Change status of tweaks
- Cpu OC
- GPU OC
- Change voltage
Installation:
As usual: Flash the flashable .zip in cwm. Only working on aosp jellybean roms!
Download:
Download here
FAQ:
How do i change voltage?
Use the latest version of setcpu, leantweaks, cputuner, or your ROM's built-in tools.
Do i need to wipe dalvik/cache?
In general there's no need, but it doesn't hurt so if you have time go ahead. Posted Image I don't wipe.
What's the variable on the GPU OC?
The kernels GPU is now set to stock 307Mhz by default. You can adjust that by using Variable GPU OC (see a separate FAQ entry below).
When you go from say 307 to 512Mhz, you will not experience near double performance increase. Due to the factors outside the GPU module (ie. memory bandwidth limitation), you can't truly OC the GPU. In fact, most people can't tell the difference between 307, 384 and 512. Nenamark2 will roughly give you the following scores: 307/25fps, 384/28fps, and 512/31fps.
Some of you have seen the note from Colin, the Google kernel engineer, not to OC the GPU because using the OV_UV voltage slot will drain the battery. Greenblob kernel uses the same voltage for both OV and OV_UV slots. So there's no danger of battery drain there.
My phone doesn't seem to be deep-sleeping, what gives?
(assuming you checked in the right place like cpuspy) In terms of deep-sleep, there's not a whole lot going on in the kernel. It works or it doesn't - and I can assure you that I test every release (well almost every release) for deep-sleep before I release.
19 out of 20 times it's either 1) some sort of background process that's preventing your phone from going into deepsleep, or 2) something's misconfigured in your ROM, or both. Also connecting to USB will prevent phone from going into deepsleep.
I'm having unusual battery drain - help!
First of all, our i9100g (AS every Smartphone ^^) has very poor battery life while in active use. It's downright horrible while screen is on - screen is definitely the main culprit and there's not a whole lot I can do about that.
Custom undervolting can help or can hurt. This is mainly due to SmartReflex (class1.5) which auto-calibrates the ideal voltages for you. In fact, with SR you don't really need to use the custom undervolting feature for frequencies other than the 2 lowest. It does a great job calibrating higher frequencies. I personally don't touch it.
The "notrim" versions are an exception because I had to disable SR1.5 for the trim override to work. There's no auto-calibration going on there. Feel free to mess with custom undervolting on the notrim versions.
Now, if you've already accepted the horrible battery life while screen is on, but have questions about battery drain while idle - read the next question.
I'm having unusual battery drain while screen is off, or phone is sleeping - help!
First, let's find out if you're phone is going into deep-sleep. Install CPUSpy, unplug phone, turn off screen, and leave the phone alone for 5-10min. Turn the screen back on, launch CPUSpy, and see if you see an active entry for Deep Sleep. If so congratulations - read on.
If you've determined that your phone is not entering deepsleep by using the above method, read my entry above that says "My phone doesn't seem to be deep-sleeping". I've heard that removing SDM.apk helps as well as rebooting the phone. Also try turning your bluetooth on and off, and launching camera app and closing it.
If you've determined that your phone is entering deepsleep fine but still feel like battery drains, read the next question.
I'm having unusual battery drain while phone is in deep-sleep - help!
First make sure you are absolutely positive that deep sleep is working (read the previous question).
While on my kernel *and* connected to Wifi, you shouldn't drain more than 2% battery per hour *average* while in deep sleep (based on 5-8 hour continuous deep sleep). With wifi turned-off, my guess is probably no more than 3-6% per hour, depending on signal strength.
tip 1: If above is not happening for you, first charge the phone all the way and reboot. Let things settle a bit - give it a day or so. If you're using Battery Monitor Widget (which is not accurate for gnex), things should eventually settle between -2mA and -60mA per sample.
tip 2: Install BetterBatteryStats and look at which wakelocks dominate. Google search for names of the wakelocks to see how you can fix them.
tip 3: http://checkthis.com/d87t
If nothing seems to help, you can try the "notrim" version, but stick to speeds between 350 and 1350 (don't use OC slots). The notrim version has SR1.5 disabled which could help for those of you with drain issues on my other kernels.
What is SmartReflex?
SmartReflex performs continuous dynamic voltage scaling around the nominal operating point voltage according to silicon characteristics and operating conditions.
My stable and experimental builds will have SR Class 1.5 enabled by default.
You can disable SR via sysfs
How do I use Variable GPU OC?
You can use Lean Tweaks by Jake, or use the built-in "oc" script. Both leantweaks and my oc script will create an init.d script so the setting sticks at boot. My "checkt" script will also show the current GPU max speed. Note that 512MHz will probably not work for everyone.
307Mhz (stock) is set default by the kernel.
Open Terminal, and type for stock speed of 307Mhz: oc gpu 0
for 384MHz: oc gpu 1
for 512Mhz: oc gpu 2
FAQ partly taken from leankernel! I changed the important parts for us! Thanks to them! http://forum.xda-developers.com/showthread.php?t=1790675
An app for variable gpu oc is already in progress! For now please read the FAQ
Great work fuss. It says gnex somewhere in op btw.
Sent from my GT-I9100G
Such a Fast Releas
iXanza said:
Great work fuss. It says gnex somewhere in op btw.
Sent from my GT-I9100G
Click to expand...
Click to collapse
Thanks ^^ I changed it
And I also changed the battery life expectation
Sent from my GT-I9100G using xda app-developers app
Thanks for sharing，that works great.
any chance to get this kernel for stock rom..?
Sent from my GT-I9100G
+100 for the awesome Kernel !
Sent from my GT-I9100G using Tapatalk 2
First of all, WELCOME BACK FUSS.. Back with bang I can say. New Kernel and it's more powerful, efficient and features. WOW. You Rock. Thank you fuss :beer:
Sent from my GT-I9100G using Tapatalk 2
Is it safe to install with latest cm10 nightly?
Sent from my GT-I9100G using Tapatalk 2
ottomatteseo said:
Is it safe to install with latest cm10 nightly?
Sent from my GT-I9100G using Tapatalk 2
Click to expand...
Click to collapse
Yes
Sent from my GT-I9100G
iXanza said:
Yes
Sent from my GT-I9100G
Click to expand...
Click to collapse
Thnx
Sent from my GT-I9100G using Tapatalk 2
hi fuss, welcome back to XDA, i though you will disappear for long time :laugh::laughim joking)
and BIG THANK TO YOUR NEW WORKS Greenblob
may i flash it to codebox 1.9.0? any suggest to flash?(im still using codebox whatever it no longer support:good: because it is awesome)
IloveXDA512 said:
hi fuss, welcome back to XDA, i though you will disappear for long time :laugh::laughim joking)
and BIG THANK TO YOUR NEW WORKS Greenblob
may i flash it to codebox 1.9.0? any suggest to flash?(im still using codebox whatever it no longer support:good: because it is awesome)
Click to expand...
Click to collapse
Flash GreenBlob through CWM
Sent from my GT-I9100G using Tapatalk 2
My phone freezed in the instance i got to the menu. Now it boot loops when i has reached the lockscreen. What should i do now?
I've just installed it. I see in recovery version is now 6.0.1.9 is it still using blob crap for android? Thanks
Sent from my GT-I9100G using xda premium
kernel from the sky =) =) big big thanks fuss!!!!! =) =) what a speed!!!!! =P
cesco73 said:
kernel from the sky =) =) big big thanks fuss!!!!! =) =) what a speed!!!!! =P
Click to expand...
Click to collapse
Sorry thats FUSS not sky
Sent from my GT-I9100G using Tapatalk 2
im sorry to said that, but im still having the reverting back of the freqency....
any idea? ><??
This is a Kernel, based on Lord Boeffla's Kernel, "boeffla-kernel-4.1-CM14.1-g900f", which is based on LineageOS Kernel, which is based on AOSP (google) Kernel, which is based on Linux Kernel.
It should be installed via Recovery (TWRP or CWM) over any other LOS 14/15 ROM/kernel, just like boeffla kernel. It doesn't need any tweaking with any app. Install it and use it.
BUT you can use "boeffla config app" if you like tweaking. You will receive a Warning about "mpdecision", just ignore it.
It has:
- a different "low memory killer" algorithm
- zcache is disabled for really freeing memory that was used for caching files (when needed) instead of compressing it
- a different default cpu hotplugger. Every other kernel (even LOS/stock) relies on Qualcomm's MPDecision, I wrote my own, *****es
- Tuned governor (it's the default). It's basically the Interactive but with a lot of tuning.
- many compiler optimizations not found on boeffla or LOS
- many unused code simply REMOVED to free memory and CPU. People just add more stuff, I like to remove
- TV tuners removed from code. wtf...
- many unstable governors and i/o schedulers removed
Note that even though 2GB of RAM isn't too little, if you have too many memory-hungry apps, performance will always suffer; Most apps are started(loaded up to RAM) right after booting; There are ways to prevent this auto-start but I can't remember now..
Overall your phone will be snappier, and less battery hungry
XDA:DevDB Information
tuned, Kernel for the Samsung Galaxy S5
Contributors
fbs, lord boeffla, haggertk
Source Code: https://github.com/bemerguy/tuned-kernel-LOS-s5
Kernel Special Features: lighter, optimization-focused
Version Information
Status: Stable
Stable Release Date: 2018-08-22
Created 2017-10-08
Last Updated 2018-11-01
DOWNLOADS:
KTMonitor = an app that will show your cpus clocks in real time, in a overlay window. simple, fast, no ads.
If you only see the first cpu (CPU0), you'll have to change kernel selinux mode to Permissive instead of Strict. Boeffla config app can do it.
"tuned kernel" builds will show up here, from older to newer
klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
klteduos - SM-G900FD, SM-G900MD
kltedv - SM-G900I, SM-G900P
kltekor - SM-G900K, SM-G900L, SM-G900S
los14 = cm14 = android 7
los15 = cm15 = android 8
Reserved
220818:
-hstcp as tcp congestion control
090818:
-and zram disabled again
-compiled with the leanest toolchain type
-undervolt back on, I guess
-lowmemorykiller from xiaomi's stock kernel
-read ahead disabled completely
-more unused kernel parts removed
-more compiler optimization
280618:
-zram enabled again, now with lz4 that should have been used since forever but wasn't
-some kernel fixes from around the net. should be even faster
"tuned" governor tweaked a bit, and it's profiles too (for those who still uses boeffla app to tweak things)
210618:
-LOS 15.x build
-268mhz as default min speed and 2.6ghz as default max speed
-can't figure out why swap is being used A LOT even with swappiness=5, making battery life miserable, so zram disabled again
-"tuned" governor as default. It's a "interactive" with bugs fixed and tweaked
-"zen" scheduler as default, with some bugs fixed. it's fast, simple, almost like noop+deadline+row mixed
230418:
-latest boeffla-based
-wifi tweaked
-zram (swap) is back
-other compiler flags not enabled before
280218:
-beta22 based
-lmk faster than before while screen is on. slower than before when screen is off
-interactuned governor will save some cpu while screen is off
160218:
-now compiling with linaro 8.0
-"interactive" governor renamed to "interactuned" to get rid of conflicting values
-"interactuned" profiles updated on boeffla app (standard, performance, battery, battery extreme)
-tuned hotplugger tweaked a bit
110218:
-lmk will search, compare apps' scores, and kill them in groups. the stock lmk and the "less aggressive" lmk from build 020218 were killing one app at a time
-put tuned hotplugger to run more often when display is on. the cpu cost is minimal as it is extremely simple
-tweaked compiler flags again to not make code large
020218:
-boeffla's beta21 based
-less aggressive lmk again
-tweaked compiler flags
-tweaked interactive governor
-tweaked tuned hotplugger
301217:
-more aggressive lmk
-less aggressive tuned hotplugger
-tweaked the default interactive values in ramdisk (via anykernel), as they are modified by it on boot
-tweaked also the boeffla app interactive profiles
-performance governor will really drain your battery now, but it will be even faster (max cpu clock, all cpus on if using tuned hotplugger)
-compiling with O2 but with some O3 flags. it seems to be faster than 211217
211217:
-beta20 from boeffla
201217:
-tweaked some filesystem stuff
-it seems tuned hotplug was being ramdonly disabled, fixed
-changed how tuned hotplug enables/disables cpus:
it was based on the number of processes needing cpu. But the system itself didn't count as "processes", so I changed it to look at the cores frequencies instead. The cpu governors itself has a lot of code just to measure how busy the cpus are before raising or lowering frequencies, I think it's faster/lighter to just use that info instead of calculating again or in another way.. In practice: cpu0 at max frequency will turn on cpu1 and so on. Any cpu on lowest frequency for some time will turn it off. I don't really know if this will be better or worse than the code before(151217)
151217:
-beta19 from boeffla
071217:
-beta18 from boeffla kernel
-zram/swap fully disabled. The slowdowns are unacceptable. It seems we will always get a huge performance/battery hit with any kind of swap. For now I think it's better to let the "low memory killer" do its thing than swapping. Remember: Killing an app will instantly free RAM with zero CPU usage. Swapping means a lot of CPU usage, and (as swapping occurs in RAM), only 40-50% of ram will be freed.
011217:
-beta17 from boeffla kernel
-tweaked tuned hotplugger a bit. changing from mpdecision to tuned on config won't bug the lower frequency
-swapping should be faster
271117:
-hotplugers "mpdecision" and "optimized mpd" working again. zzmoove hotplugers removed (the governor itself was removed long ago)
"interactive" profiles changed a bit: "performance" will have more performance, and "battery" will really save more battery
-zram compression (swap) may be even faster now
-compiler toolchain updated to gcc-linaro-7.2.1-2017.11
-processor scheduler using logarithmic scaling
-"tuned" hotplugger logic was changed a bit. it will turn on/off cpus based only on average load, but will obey the "order" and may turn all on if the load is suddenly high. it may also use less cpu to compute
-"interactive" governor may also use less cpu
So it's safe to say that this kernel could just be flashed over beta12 , i would like to test it and see the difference at work .
Also , Thank you for the work you put into this.
I have found that using kernel auditor to turn off ALMK off in my variant of boeffla kernel has helped tremendously with ram management. I'm curious if what you have done here will work even better. Keep up the good work.
Sent from my kltespr using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KazuDante said:
So it's safe to say that this kernel could just be flashed over beta12 , i would like to test it and see the difference at work .
Also , Thank you for the work you put into this.
Click to expand...
Click to collapse
yes
The~Skater~187 said:
I have found that using kernel auditor to turn off ALMK off in my variant of boeffla kernel has helped tremendously with ram management. I'm curious if what you have done here will work even better. Keep up the good work.
Click to expand...
Click to collapse
Thanks. I think it would. This "ALMK" is a new feature that only made more obvious what was already broken. I was already trying to get rid or modify LMK when it was integrated to our LOS kernel.
You could, *at least*, drain less battery by installing this mod. If you have time, please compare before and after.. I think it does use less cpu and the phone won't "gag" when it needs more memory (like when opening a new app)
64MB for empty applications? That is TOO low. The default is 180MB. This way, lmk would/should only kill anything when all the system has only ~64MB to cache files.
The memory lmk really counts is not the real "free" ram, it's the "cached" ram. Our "free" ram is almost always ~44MB..
the Linux kernel will use available memory for disk caching, unless it's required by a running program.
This is considered good; say you have 4 GB RAM, and your programs are using only 1 GB. The other 3 GB are going to waste. Despite the "feel-good" impression from knowing you're only using 25% of your memory, the counterpart is that the other 75% is going unused. So the kernel uses that for caching files which significantly improves performance. It's automatic; unlike older operating systems you don't need to decide how much to devote to disk cache, or manually configure it.
"The Linux disk cache is very unobtrusive. It uses spare memory to greatly increase disk access speeds, and without taking any memory away from applications. A fully used store of ram on Linux is efficient hardware use, not a warning sign."
Click to expand...
Click to collapse
fbs said:
Thanks. I think it would. This "ALMK" is a new feature that only made more obvious what was already broken. I was already trying to get rid or modify LMK when it was integrated to our LOS kernel.
You could, *at least*, drain less battery by installing this mod. If you have time, please compare before and after.. I think it does use less cpu and the phone won't "gag" when it needs more memory (like when opening a new app)
Click to expand...
Click to collapse
From what I'm seeing this is working great. Free Ram seems to be holding steady between 700 and 800 MB.
Would you mind if I implement this into a test version of my kernel? I would like to see if it has any ill effects with the added features I have in mine.
Sent from my kltespr using Tapatalk
The~Skater~187 said:
From what I'm seeing this is working great. Free Ram seems to be holding steady between 700 and 800 MB.
Would you mind if I implement this into a test version of my kernel? I would like to see if it has any ill effects with the added features I have in mine.
Sent from my kltespr using Tapatalk
Click to expand...
Click to collapse
Of course! Let's try to make things better for our S5... !!!
fbs said:
Of course! Let's try to make things better for our S5... !!!
Click to expand...
Click to collapse
Awesome. I added you modified lmk.c to my source, compiling now. I will keep you posted on my findings. Thank you again!
Sent from my kltespr using Tapatalk
im loving where this is going so far.....heck if even in the future this could also be loaded on the 8.0 then our s5 still have a long way to go life wise.
awsome colab guys.:highfive:
and on top of that the official xposed is now out for Nougat , this is a good day.
The~Skater~187 said:
I have found that using kernel auditor to turn off ALMK off in my variant of boeffla kernel has helped tremendously with ram management.
Click to expand...
Click to collapse
VERY interesting! For me deactivating ALMK in Kernel Adiutor didn't help so far. But I didn't test this brand new kernel yet - just the older version based on boeffla kernel beta11. This new thread is one the most helpful of the last 3 month! Thank you so much, @fbs!
VERY good news! I have subjected your current kernel to a heavy stress test. Made a Nandroid backup triggered by SManager in the background. Half of the time (about 12 minutes) I chatted on WhatsApp and was surfing with Chrome while the backup was running in the background. This *never* had been working before without any issues. Afterwards I synchronized the 5 GB backup with my NAS via FolderSync in the background. This also worked perfect! In addition, there were no slowdowns or lags at work. Everything ran (and runs) absolutely fluently. At the first glance I'd say it's the far best kernel I ever used on my S5!
I've added another version, with ZCACHE disabled. It may speed up things when accessing files and may solve some bugs. (whispering: I think it was badly implemented, no one uses it anymore..). If anyone is interested in comparing the performance of both versions, including battery usage.. feel free to post!!
fbs said:
I've added another version, with ZCACHE disabled. It may speed up things when accessing files and may solve some bugs.
Click to expand...
Click to collapse
I will gladly give it a try. But I am truly more than satisfied with the current version! It runs smoothly and reliably. I couldn't detect any bugs. The most important thing is that we also get a beta13 and beta14 and so on...
The no zcache version seems pretty damn smooth so far. I haven't really stressed tested yet, but I'm not getting lockups and lag spikes as I was with normal one.
Please keep up the good work.
Battery life is outstanding but I did just drop a brand new battery from Anker this weekend. So. . . .
Sent from my SM-G900T using Tapatalk
PorchSong said:
The no zcache version seems pretty damn smooth so far.
Click to expand...
Click to collapse
I believe the whole thing is also strongly related to the swappiness-value. My swappiness is set to 30 and I can't see any advantages or disadvantages, whether zcache is switched on or off.
Can i using for RR rom ?
wayan_billie said:
Can i using for RR rom ?
Click to expand...
Click to collapse
Yes you can.