Related
Hi!
I was just wondering if anyone could tell me what the best setCPU settings for HD2, with respect to battery life and stability(no lag), are?
I've been searching for the answer on many forums but haven't been able to find a definite answer.
Thanks for your thoughts and recommendations!
Personally, I don't see the need for setCPU. I get no more than 7mA drainage per minute when in standby and my phone is already as fast as I'll ever need it to be. Am I missing something? I can easily get 30+ hours out of my phone with moderate to heavy usage.
Oh, I've had these same battery results on Shubcraft, SuperHD2, Hyperdroid, Bangsters, and the new Desire HD ROM.
Chuckydroid ROM
2.12 Radio
Stock 16gb microsd
Max to 245
Min to 245
That will guarantee long battery life
You really should search tho
Sent from my HTC HD2 using Tapatalk
setCPU Settings
~~~~CREDIT GOES TO BANGSTERS~~~~
on main screen:
max 1190
min 245
governor = interactive (better than ondemand)
profiles:
Enable it
Add profile:
Screen Off
Max 245
Min 245
Priority 100%
interactive as well
Add profile:
Battery <40%
Max 768
Min 245
Priority 80%
interactive as well
Add another profile:
Advance Tab
Min Sampling Rate = 50000
Enable it
Remember aside form this set spare parts windows animation and transition animations to FAST
And in ADW launcher, set the following:
screen preferences -> desktop scrolling speed around 50 - 100
drawer settings -> zoom effect speed 325
drawer settings -> fade app labels unchecked
system prefernces -> scrolling cache auto
Hope this helps.
I agree with alpinestars
i think ondemand is bit buggy the kernel dont choose the right Scall
sometime its choose 1000mhz with 20% cpu used that is wasting
my setting in adv
Up Threshold 55
down "" 50
freq step 20%
screen off
245-384 interactive
battery 1.5%ph [4 hours test]
its might be laggy a bit from idling to full using like watching movie
but its should stop after 100ms berrly noticeable
Question
Ok BIGGGG newbie question i know but i got to ask this lol, what do you mean by governor=interactive? I mean i know how to use setCPU been using it for a while now but...i don't seam to have that scaling.
I'm using setCPU 2.0.3 full version.
is there a kernel with higher max clockrate than 1190 ??
Ahmun_Ra said:
Ok BIGGGG newbie question i know but i got to ask this lol, what do you mean by governor=interactive? I mean i know how to use setCPU been using it for a while now but...i don't seam to have that scaling.
I'm using setCPU 2.0.3 full version.
Click to expand...
Click to collapse
It depends if its activated in the kernel you are using.
Sent from my HTC HD2 using XDA App
souljaboy said:
is there a kernel with higher max clockrate than 1190 ??
Click to expand...
Click to collapse
That i know No there is not, its the higher safe clockrate of the HD2. Higher is trying to make your phone a fryed egg lololol
I dont see Interactive on my SetCPU, I see:
Conservative
Ondemand
PowerSave
Userspace
Performance
Do I have a different version?
SetCPU 2.0.3
gattaca714 said:
I dont see Interactive on my SetCPU, I see:
Conservative
Ondemand
PowerSave
Userspace
Performance
Do I have a different version?
SetCPU 2.0.3
Click to expand...
Click to collapse
What kernel and Android are you running? Some Android build has interactive while others don't.
Ahmun_Ra said:
That i know No there is not, its the higher safe clockrate of the HD2. Higher is trying to make your phone a fryed egg lololol
Click to expand...
Click to collapse
making a fryed egg out of this crap would be the best thing i do
I have an easier solution.
Just send it to me and I'll send you a fried egg --postage paid.
jamesbryant said:
I have an easier solution.
Just send it to me and I'll send you a fried egg --postage paid.
Click to expand...
Click to collapse
+1
I could have a better use for it, I am not into eggs anyway.
Ahmun_Ra said:
That i know No there is not, its the higher safe clockrate of the HD2. Higher is trying to make your phone a fryed egg lololol
Click to expand...
Click to collapse
Seen pics of a Milestone @1400
now thats crazy as they begin with a 600Mhz
I found that 245max 245 min setting in screen off is not a good setting
i use 576 max/min in screen off makes a result that only 1% drop in 75 min
i test it last night when i sleep hehe (average 3-7 ma)
Try these settings I posted in the thread "If you're using setcpu, try these profiles."
Tomorrow I am going to test a set up I just made. It should be called the Step Setup.
The purpose of this setup is to trying to keep the phone running smooth while being proportional and saving battery. This is my first attempt so I will be tweaking it as I test it and receive input.
Keeping the same priority settings as I have listed is crucial because if the order is out of place it will not downclock at the right time.
Here are the settings:
Main - Max:1036 Min:245 Scaling:Interactive (set on boot checked)
Profiles
Screen off - Max:245 Min:245 Scaling:Interactive Priority:100
Battery<10 - Max:384 Min:245 Scaling: Interactive Priority 75
Battery<15 - Max:422 Min:245 Scaling:Interactive Priority 70
Battery<20 - Max:499 Min:245 Scaling:Interactive Priority 65
Battery<30 - Max:576 Min:245 Scaling:Interactive Priority 55
Battery<40 - Max:614 Min:245 Scaling:Interactive Priority 45
Battery<50 - Max:652 Min:245 Scaling:Interactive Priority 35
Battery<75 - Max:768 Min:245 Scaling:Interactive Priority 10
Battery<85 - Max:883 Min:245 Scaling:Interactive Priority 0
Advanced - Min Sample Rate:20000
This should be speedy and give great battery life. If your kernel doesn't allow Interactive scaling try setting everything to On Demand and in the advanced tab set the Up Threshold to 30.
EDIT: Using this with a combination of the VBN Android Rom has achieved some insane battery life. Yesterday I listened to music for a majority of the day, on and off, using the internet a few times and texting and when I went to bed the battery was around 30%, and that was around 12 hours of having my phone on me. My battery is old and has been charged a lot, a new battery or extended battery would provide crazy results.
Click to expand...
Click to collapse
2.14 Radio, Mdeejay Evo Sense
alpinestars said:
~~~~CREDIT GOES TO BANGSTERS~~~~
on main screen:
max 1190
min 245
governor = interactive (better than ondemand)
profiles:
Enable it
Add profile:
Screen Off
Max 245
Min 245
Priority 100%
interactive as well
Add profile:
Battery <40%
Max 768
Min 245
Priority 80%
interactive as well
Add another profile:
Advance Tab
Min Sampling Rate = 50000
Enable it
Remember aside form this set spare parts windows animation and transition animations to FAST
And in ADW launcher, set the following:
screen preferences -> desktop scrolling speed around 50 - 100
drawer settings -> zoom effect speed 325
drawer settings -> fade app labels unchecked
system prefernces -> scrolling cache auto
Hope this helps.
Click to expand...
Click to collapse
Hey thanksz but i dont think u can set your advanced settings without the main profile being on governer=ondemand.
alpinestars said:
~~~~CREDIT GOES TO BANGSTERS~~~~
on main screen:
max 1190
min 245
governor = interactive (better than ondemand)
profiles:
Enable it
Add profile:
Screen Off
Max 245
Min 245
Priority 100%
interactive as well
Add profile:
Battery <40%
Max 768
Min 245
Priority 80%
interactive as well
Add another profile:
Advance Tab
Min Sampling Rate = 50000
Enable it
Remember aside form this set spare parts windows animation and transition animations to FAST
And in ADW launcher, set the following:
screen preferences -> desktop scrolling speed around 50 - 100
drawer settings -> zoom effect speed 325
drawer settings -> fade app labels unchecked
system prefernces -> scrolling cache auto
Hope this helps.
Click to expand...
Click to collapse
i tried pm'ing you but you need to change your pm setting to recieve message
Changed pm settings
Could anyone please tell me the settings and profiles that will give my x10 mini the best battery save? thanks
actually there is already a preset for that ..the "powersave" one..
Easy, just put both bars in 122880MHz..
Your phone are going to be rrrrreeeaaaallllyyy slow, but you save lots of milliamps
Use ondemand only. And set min to 122 and max to 600.
I use a profile when screen is off that set min to 128 and max to 320, ondemand too.
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Has anyone had problems with random freezes and reboots with SetCPU installed? I've had a couple random reboots, so for now I've uninstalled SetCPU to see if the problem goes away. I also have Advanced Task Killer installed but it wasn't set to kill tasks automatically.
raiderkilo said:
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Click to expand...
Click to collapse
Setting SetCPU like that is not very smart. For example, You have Your screen off, someone is calling You, what happens? You get the call ringer after few seconds (sometimes even 10-15!). Reminds of old Symbian versions? But just this. Next example - You have Your screen off, and You receive sms. What happens if You are using Handcent, and have to go to the app manually after phone wakes up? It takes ages... But if You have more than 1000 massages in Your inbox, and a new one come, and You get it after screen wakes up it can even lead to a reboot.
Lets add some random weird situations if You are listening to Your player while the screen is off... using some third party apps, etc...
Setting the minimum CPU for the screen off is not a good idea. Don't do that, or the phone will fail You in most unwanted cases.
so what are you guys using?
I am 122-600 on normal ondemand
and screen off on 122-256 ondemand
Anyone with better profiles?
just dont overclock!!!
why not? I see you are running 729/600.
WHY is your min 600?
Use smartass governor - auto profile, just upgrade to gingerbread.. best profile yet..
Set normal use 122Mhz-729Mhz 100% Priority
Set for charging: 122Mhz-245Mhz (or similar) - 100% Priority
Set for screen off 122-245 (or similar) - 100% Priority
^ this saved me battery when I used my phone for so much else besides calling and texting.
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
achyut said:
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
Click to expand...
Click to collapse
Only a handful devices supports being clocked to 825Mhz but it's very dangerous.
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
ruifung said:
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
Click to expand...
Click to collapse
Some have succeeded, but I doubt their phones lasted very long after that.
Just wondering, is the phones processor under the right side of the keyboard? cause after a few minutes @ 710Mhz, that area is hot. Since I switched to the smartass governor, it rarely is hot anymore (due to the fact it mostly spends time @ 245/320Mhz
Um... question?
Shouldn't the phone go into deep sleep when the screen is off with no cpu activity?
Also install cpu spy and see what the cpu is doing for how long.
https://market.android.com/details?id=com.bvalosek.cpuspy
1. The cpu does not make the most heat... it's the 3G radio.
2. Cpu should deep sleep automatically.
My OC prifile for mini pro:
Standard profile- 122 - 825mhz
If Battery < 15% then 122 - 600 "this gets rid of crashes due to low power OC"
Also.. i asked some of the developers that made the modules for overclocking and undervolting.
It's undervolting there is no upward voltage bump so it can't really nuke a cpu.
But you can nuke the power circuits if you use heavy internet on 3G and charge at the same time.
How can I put over 600 Mhz?
My SetCPU makes 600 Mhz the max. I want to put just on 700, but I can't. What is the problem?
@Felimenta97:
You don't have any overclock-enabler module installed/insmodded or if using any CM-based ROM, the corresponding setting is disabled.
I'm using smartass with 122-320 for screen off and ondemand with 320-729 for normal, no problems so far
The max MHz I could get was 729MHz, 748MHz worked but after some time the CPU got 'pegged' as said in the logcat
Tried the 825MHz setting that only caused a freeze and boot loop, forcing me to do some fast adb commands to get rid of the overclock
Hi all,
I couldn't find the relevant information anywhere else, so thought I should ask if someone has experienced this.
Well I'm using setcpu on my razr and it is quite a brilliant app to be honest, helps me save battery quite alot by setting up profiles.
But recently I've been having crashing problems with the phone whenever i set the scaling to hotplug.
Previously, i was just using the default scaling, I guess Interactive it was, and was working quite happily. And, then i read about advantages of using Hotplug scaling, that it enables/disables cores depending on the amount of load on the cpu, which is really good for saving battery.
And before how I was using the phone, was to set a profile for screen off to drop the cpu down to 300MHz, using the default scaling.
But as soon as I changed from default scaling to Hotplug, it starts crashing randomly, and I've to restart the phone using keys.
Scenarios tried:
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 300MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Hotplug -- Screen off scaling: Interactive, Ondemand, Performance, Hotplug -- Processor Max: 600MHz
Result: crashing as soon as u turn the screen on, or sometimes while the screen is off.
- Main scaling: Interactive -- Screen off scaling: Hotplug -- Processor Max: 300MHz
Result: In process of checking, hasn't crashed yet for more than an hour. :fingers-crossed:
Can someone kindly point out the obvious mistake I'm making here?
I really want to use hotplug, both as main and screen off.
FYI: I haven't done anything else to the phone apart from gaining root access.
i had issues with setcpu, i recommend no frills cpu control, and setting it down that low more then likely is also an issue, the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS) and above id say. uninstall setcpu give no frills a try and let me know would be glad to help with what i can!
Thanks for ur reply, yes I'll try no frills, but
mr4r4n said:
setting it down that low more then likely is also an issue
Click to expand...
Click to collapse
I thought the same, but while i was using interactive scaling, it worked perfectly, no issues at all. Probably because both cores were active by default, so both on 300MHz when screen was off.
mr4r4n said:
the second core i couldn't see turning off at a low clock and also i think it would max out easily causing instability (especially ICS)
Click to expand...
Click to collapse
No, I've checked cpu usage visa adb shell, and if the screen off is in hotplug, like what it is right now, the phone stays at 300MHz with the second core turned off, most of the time. And the phone has been running now for more than 3hrs with screen off profile set to Scaling: hotplug -- Max: 300MHz, and the main scaling set to Interactive.
The problem I've seen is, when main scaling is set to hotplug. Doesn't matter whatever u set in screen off profile, it crashes if the main scaling is set to hotplug. But, if no screen off profile is set then, hotplug in main works flawlessly.
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Nikorasu said:
That's weird. I've been using SetCPU for a year or so on my RAZR GB/ICS and never encountered any crashes with hotplug or the default ICS's interactive.
I have even tried unofficial governers like smartass2, boostedassv2 and etc, no crashes.
I personally set my phone to use u/c 200-200 for screen off and I find it really saves a lot of battery, and even o/c to 200-1300 when it's on.
Are you using the setcpu from xda or from playstore? I'm using the one from playstore with Razr asia ICS.
Click to expand...
Click to collapse
I think I downloaded it from here.
But I think, they both are the same, from same developer
hsyasin said:
I think I downloaded it from here.
But I think, they both are the same, from same developer
Click to expand...
Click to collapse
This means that you're using an old July 2011 version.
Do make use of playstore's 15 min return policy to test the newer ver. Maybe it will solve your problem.
Ktoonsez presents:
{
"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"
}
KT-SGS5 kernel features
•Must have a S5 model G900T or G900P or G900V (Dev Edition ONLY!!!) or G900F or G900M or G900W8 or G900I
•Must have a Touchwiz Rooted ROM
•Must have CWM/TWRP based recovery installed
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•KTweaker app for kernel control
•KTweaker Widgets
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz and AOSP
•F2FS compatible with AOSP 4.4, 5.0 and 5.1
Click to expand...
Click to collapse
Touchwiz Lollipop 5.0 VERSION:
05.02.2015: http://bit.ly/1EN5UtG
Click to expand...
Click to collapse
AOSP Lollipop 5.0 VERSION:
05.02.2015: http://bit.ly/1JJhnxv
Click to expand...
Click to collapse
AOSP Lollipop 5.1 VERSION:
05.02.2015: http://bit.ly/1DTVhBf
Click to expand...
Click to collapse
TWRP Recovery by Ktoonsez:
04.06.2015: http://goo.gl/LgBsuk
Click to expand...
Click to collapse
AOSP /system F2FS converter:
03.31.2015: http://bit.ly/1IOdXpX
Click to expand...
Click to collapse
What you can expect to get benchmark wise:
******* END OF LIFE *******
Touchwiz Kitkat 4.4 VERSION:
02.26.2015: http://ktoonsez.jonathanjsimon.com/sgs5/TW/KT-SGS5-KK4.4-TW-G900-02.26.2015.zip
Click to expand...
Click to collapse
AOSP Kitkat 4.4 VERSION:
11.06.2014: http://goo.gl/t3H5oK
Click to expand...
Click to collapse
KTweaker Shop and previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/showthread.php?t=2784319
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
Post #2 will be reserved for change logs
Post #3 will be reserved for MY Settings, Extras and FAQ's
Sources can be found here:
https://github.com/ktoonsez/KTSGS5
Change Log 05.02.2015
1. KTweaker 9.3
2. Cleaned up some FC issues
3. "Get Phone Information" screen was pretty'd up and added CPU "Time in State" grid including Deep Sleep and Total up Time items.
4. ktoonservativeq: Adjust alloc_workqueue(). Remove WQ_UNBOUND to assure it always runs on CPU0 and add WQ_CPU_INTENSIVE to assure these work items will not prevent other work itemsin the same worker-pool from starting execution. This is useful for bound work items which are expected to hog CPU cycles so that their execution is regulated by the system scheduler.
5. CM ramdisk updates.
Change Log 04.06.2015
1. Removed the RED text when booting that warns about NOT SEANDROID ENFORCING for TW 5.0 and AOSP 5.0
Change Log 04.05.2015
1. Merge in ramdisk update for CM call lag problem
2. Removed the RED text when booting that warns about NOT SEANDROID ENFORCING
Change Log 03.27.2015
1. fastcharge: Add some blocking code for functions reducing chargin current and setting some variables for 3rd party apps
2. cpufreq: Add some protection when setting policy changes. Add some disabled debug messages in case I need them later. Remove usleep call after calling cpu_up()
3. cpufreq: Add main_cpufreq_control global var to make other modules aware that the main cpufreq code is bringing a core up so they will not take the core down.
4. ktoonservativeq: Modify some code to make sure hotplug cores obey touch_boost_cpu_all_cores during boostpulse while sync cores is off
5. cpufreq: Disable some extra booster code on wake for testing
Change Log 03.25.2015
1. ktoonservativeq: Totally revamped
2. NEW tunable lockout_changes_when_boosting used to lockout changes to frequency and hotplugging activities during touch/button boost (this basically makes touch boost behave the old way before all the new code)
3. NEW tunable cpu_load_adder_at_max_gpu_ignore_tb used to ignore gpu cpu load adder during a touch/button boost
4. Modified all global vars placement so governor can run on all 4 cores instead of controlling them thru proxy
5. Optimized code adding more sub functions to reduce code
6. Moved global counters into cpu_dbs_info_s struct so each core keeps there own version
7. sing new debug_enabled tunable from previous commit added a few more debug lines for keeping track of load and hotplugging activities
8. All hotplugging activities are mutex protected
9. Added some more effective boost code upon wakeup
10. KTweaker version 9.1
11. KTweaker: Fix up previous screen tracking for Governor Adjustments screen
12. KTweaker: Will now set the selected governor to ALL 4 CORES!
13. Ramdisk update for AOSP version from CM latest
14. New ktoonsified v4 in Shop for new kernel, works great on TW or AOSP, currently running TW and I can not believe how much faster it is on this new version!!!!!!!!!!!!!!!!!!!!!!!!!
Change Log 03.22.2015
1. ktoonservativeq: Optimized ktoonservatieq governor during boost sequence (more from the previous test) and a bunch more cleanup and fixes for hotplugging and mulit-threaded flags.
2. ktoonservativeq: Added new tweak item called "debug_enabled", this will enable some cpu info that can be viewed using the "dmesg" command in adb shell.
3. Added ktoonsified v3 profile to Shop
4. ktoonservativeq: Optimize the boost sequence to allow upscaling during a boost
5. Merge OB1 from TMO source drop
6. video: mdss: Color temperature interface using PCC
Change Log 03.18.2015
1. CM ramdisk sync.
Change Log 03.10.2015
1. CM ramdisk sync.
Change Log 02.25.2015
1. Changed KTweaker to remember to go back to Profile/Script type list when pressing back button from the List of profiles in that type.
2. Changed KTweaker to remember to go back to the 3 choices of ktoonservativeq when pressing back button from Governor Adjustments
3. Fixed touchscreen issue with certain games like Snes9x EX+ thanks to @DevVorteX!!!!!!!!!!!!!!!!!!!!!!
4. Updated ramdisk for TW 5.0 to OB1.
5. FINAL build for TW 4.4
Change Log 02.25.2015
1. Set TW 5.0 SELinux to permissive.
2. Updated ramdisk for AOSP version.
3. KTweaker version 9.0!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
4. Added slider drawer for easy navigation
5. Profiles and set on boot options can be easily loaded from the drawer
6. Menu button still retained the easy navigation items like CPU, GPU, Scheduler Settings....
7. Old "Tools" screen is now called "Utilities"
8. New "Utilities" item: SELinux changer
9. New "Utilities" item: Get Phone Information
10. New "UI Settings" item: Startup Drawer Status is used to set whether the drawer is open or closed when starting the app
11. New "UI Settings" item: Startup Screen is used to set which screen starts up when opening the app. You can pick from the list of screen available for startup or specify "Remembeer last screen" to make it go back to the last screen you were on.
12. New "UI Settings" item: Main Background is used to set the color or an image to be used as the background in the main part of the screen. I have predefined ones and you can also pick from a image that you place in the /KTweaker/ThemeManager/Backgrounds folder
13. New "UI Settings" item: Main Fore Color is used to set the color to be used as the fore color in the main part of the screen.
14. New "UI Settings" item: Drawer Background is used to set the color or an image to be used in the Drawer part of the screen. I have predefined ones and you can also pick from a image that you place in the /KTweaker/ThemeManager/Backgrounds folder
15. New "UI Settings" item: Drawer Fore Color is used to set the color to be used as the fore color in the Drawer part of the screen.
16. New "UI Settings" item: Main Screen: Show Icons is used to specify if you want the icons to show in the main part of the screen.
17. New "UI Settings" item: Drawer: Show Icons is used to specify if you want the icons to show in the Drawer part of the screen.
18. New Menu item: "Reset Color Scheme" is used to reset everything back to stock if you mess up a setting for back/fore color items.
19. All icons are now customizable too!!!! So if you dont like my icons all you have to do is download http://ktoonsez.jonathanjsimon.com/sgs5/StockKTweakerIcons.zip, extract them onto your PC so you can see the names of the icons for the different items, replace the ones you want with yours, then place them in the KTweaker/ThemeManager/Icons/ folder on your phone, DONE !!!!
20. As a result of all these options in UI Settings this give you the aility to share your Theme if you want by zipping up the KTweaker/ThemeManager/Settings/, KTweaker/ThemeManager/Backgrounds/, KTweaker/ThemeManager/Icons/ folders
21. Thats all I can think of right now, ENJOY THE AWESOME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Change Log 02.16.2015
1. Remove all OA6 source to see if that clears up reboot for some people.
2. Re-added GPU 266 Mhz step.
3. KTweaker 8.1, general fixes for GPU items.
Change Log 02.11.2015
1. Update ramdisk for CM version
2. Update ramdisk for TW version for OA6 knox screwage
Change Log 02.09.2015
1. Update ramdisk for CM version
2. Merged in OA6 code for AOSP and TW versions
3. Many CM patches for call lag/hang issues
4. AOSP guys, this is the same as the test from earlier
Change Log 01.25.2015
1. Update ramdisk for CM-12 changes
2. Merged in albinoman's commits
Change Log 12.21.2014
1. Update ramdisk for CM-12 changes
2. msm8974_sec: Enable IDLETIMER
3. SELinux: Fix possible NULL pointer dereference in selinux_inode_permission()
4. Enable setting security contexts on rootfs inodes.
Change Log 12.04.2014
1. Update ramdisk for CM-12 changes for LP 5.0.1
Change Log 11.27.2014
1. AOSP 5.0 Version is born!!!!!!!!!!!!!
Change Log 11.06.2014
1. Ramdisk sync with CM
Change Log 10.30.2014
1. msm: vidc: Send resolution along with output buffer
Change Log 10.20.2014
1. Linux 3.4.104
2. Ramdisk tweaks for universal compatibility
Change Log 10.15.2014
1. Added key disabler that allows user to disable the Recents and Back buttons (you can change it by setting /sys/class/sec/sec_touchkey/keypad_enable to a 1 or 0 until I have time to add to KTweaker).
2. Updated ramdisk on TW so MTP works on 900F variant
3. Updated ramdisk to sync with CM for AOSP version
Change Log 10.07.2014
1. Merged in NI2 from 900V source drop
2. MAJOR update for 4.4.4 platform: 1,104 changed files with 23,268 additions and 8,923 deletions.
3. Firmware updates for almost all devices
4. GPU updates
5. media/video updates
6. exFat upgraded to 1.2.9
7. Many updates to sound driver and various codecs
8. Touch screen updates
9. Too many more to list, you guys get the point...
Change Log 09.21.2014
1. Sound Control: add line gain to cached and register lock
2. i2c_qup: Massive rewrite to improve pm_runtime handling
3. WLAN subsystem: Sysctl support for key TCP/IP parameters It has been observed that default values for some of key tcp/ip
parameters are affecting the tput/performance of the system.
4. Trying different flags in KTweaker widget to try and stop it from getting killed by the ROM
Change Log 09.11.2014
1. Sync with latest stuff for CM
2. Add in my NFC selective code from my TW version
3. Ramdisk sync
Change Log 09.03.2014
1. Sync with latest stuff for CM
2. Added F2FS support
3. Added vibration strength control.
Change Log 08.25.2014
1. Added in kernel commits from elelinux
2. Sync ramdisk
3. Tweaked defconfigs
Change Log 08.21.2014
1. Added faux sound to AOSP version
2. Added SmartAss gov to AOSP
Change Log 08.10.2013
1. The first 2 are the stuff from the OTA only release from 08.03
2. Merged in Faux sound
3. Linux 3.4.100
4. Linux 3.4.101
5. Linux 3.4.102
6. On AOSP, merged in all the latest stuff from "intervigilium" which will be the standard stock kernel for official CM.
7. Adjusted ramdisk so Sprint can run the newest kernel
Change Log 08.04.2013
1. Merged in Faux sound
2. Linux 3.4.100
Change Log 07.26.2013
1. cpufreq_limit: stop overriding user's max freq
2. Bump up max allowable voltage since we are OCing higher
3. vibe: Remove the moronic amount of dmesg spam from vibration motor
4. synaptic: Remove dmesg spam
5. cpu: Try some bandwidth tweaks on the upper steps
6. msm: kgsl: Fix nice level for higher priority GPU start thread
7. PM: devfreq: Use high priority workqueue
8. mm: slub: Default slub_max_order to 0
9. block: Reserve only one queue tag for sync I/O if only 3 tags are available
10. mmc: disable CRC check for speed
11. deadline: Allow 0ms deadline latency, increase the read speed
12. fs: Add sysfs module to allow enabling/disabling of fsync
13. KTweaker: Add toggle to enable/disable fsync under "Main Settings->Scheduler/SD Settings". This function will increase your write speeds by up to 3x, but reads do suffer by going down by about 20%!! Disabling this can cause corruption or loss of data if you have a random reboot so be careful!!!!!!
14. SELinux: Fix memory leak upon loading policy
15. Linux 3.4.1 thru 3.4.99 for the TW version from albinoman!!!!!!!
16. Merged in NG2 code from source drop which include the items below!!!!!!!!!!!!!!!!!!!!!!
17. GPU fixes optimizations
18. Display patches
19. Wifi driver update
20. Camera updates
21. Various sensor fixes/updates
22. GPU governor fixes/updates
23. Video codec updates
24. Encryption updates
25. ext4 updates
Change Log 07.18.2013
1. OC CPU to 3072, thanks to albinoman for finding the field that was limiting CPU to 2900!!!!!!!!!!!
2. 2899 CPU step is no replaced with 2918 to keep steps uniform
3. Tweaks to the bandwidth output for the new upper steps
4. Lots more demsg spam removed
5. Major over-haul to AOSP version along with merging in garwynn's latest code that is used for the stock CM kernel
6. Add touch screen patches to stop touch driver while screen is off. The ROM is not shutting down the touch screen or the 2 haptic buttons as many of you have probably noticed. I will work on getting the button shutdown when I get more time.
7. Some ramdisk tweaks
8. Update KTweaker to accomidate the new OC steps
9. AOSP kernel is now getting crazy stupid battery life at idle, I am currently at 21 hours 5 minutes on battery and still have 78% left with about 45 minutes screen time.
10. Fix ups for screen 2 wake functions for AOSP.
Change Log 07.14.2013
1. Add 657500 step to possible gpu boost values
2. More booster tweaks
3. DRIVERS: SLIMBUS initial overclock
4. readahead: make context readahead more conservative
5. net: loopback: set default mtu to 64K
6. cpufreq: Memory leak with sysfs when stats table are freed
7. Input: Send events one packet at a time
8. softirq: reduce latencies
9. sched: remove redundant update_runtime notifier
10. devfreq: Re-enable simple_ondemand. Also fix simple_ondemand crashing from GuneetAtwal
11. Merge in code from NF6 source drop
12. auto_hotplug: make enable_load configurable
13. ktoonservativeq: Add cpu_load_adder_at_max_gpu parameter so user can bump up CPU perceived load when GPU is at max Mhz
14. Screen wake and sleep functions, (I.E. doubletap2wake, sweep2wake)!!!!!!!!!!!!!!! In KTweaker the wake lock options are still disabled since it was not needed to make these function work. Same rules apply as the test kernels, if you get in a situation where the screen doesnt respond to touch, using the power button to turn it on and letting it timeout on its own then turning it on again has always restored touch.
15. Added ktoonsified v2 profile to KTweaker Shop with updated settings including the new ktoonservativeq parameter.
Change Log 06.27.2013
1. AOSP version is born
2. All caught up with all the features that are in TW.
Change Log 06.22.2014
1. OC CPU to 2899!!!!!!!!!!!
2. OC GPU to 657!!!!!!!!!!!!
3. GPU: Add "kt-simple" governor that is based on fauxs simple_gpu_algorithm function, made it configurable thru sysfs and made it a stand-alone module
4. Made GPU default Mhz speed 200 Mhz instead of Samsung standard 320 Mhz
5. ******* IF YOU THINK THAT THE UI DRAWS SLOWER WITH NEW 200 Mhz DEFAULT, CHANGE GPU Min Mhz TO 320 TO MAKE IT ACT LIKE STOCK!!!!!!!
6. ******* WITH CHANGE ITEMS 1 AND 2, THIS MAY REQUIRE YOU TO DELETE THE KTWEAKER FOLDER ON YOUR INTERNAL SD CARD AND START OVER IF YOU HAVE PROBLEMS!!!!!!!!!!!!!!
7. Add TCP congestion flag for TCP_CONG_BIC
8. Add TCP congestion flag for TCP_CONG_HSTCP
9. Add TCP congestion flag for TCP_CONG_HYBLA
10. Add TCP congestion flag for TCP_CONG_HTCP
11. Add TCP congestion flag for TCP_CONG_VEGAS
12. Add TCP congestion flag for TCP_CONG_RENO
13. Add TCP congestion flag for TCP_CONG_SCALABLE
14. Add TCP congestion flag for TCP_CONG_LP
15. Add TCP congestion flag for TCP_CONG_YEAH
16. Add TCP congestion flag for TCP_CONG_ILLINOIS
17. NE5 source merged in from Sprint's source drop (only about 30 lines of code have changed from TMobile's source)
18. Added Screen OFF Governor and Scheduler. This allows user to set a seperate governor and scheduler while screen is OFF.
19. Added GPS scheduler and governor selection. This allows user to set a seperate governor and scheduler when GPS is in use.
20. Add GPU Max mhz while screen is OFF
21. Updated ramdisk to support NE5 changes on Sprint variant.
22. Update ktoonsified v1 in the KT Shop.
Change Log 06.19.2014
1. Improve Max Mhz limit code for people that OC and use mpdecision or thermald.
2. More booster code to improve in coming call lag when using super_conservative for screen off. If you still get lag, turn super_conservative_screen_off to a 0 to get rid of it completely.
3. Made G900I compatible with main stream kernel!!!!!!!!!!!!!!!!!!!!!!!
4. Enable code for the Music/Media min/max Mhz and hotplugging settings in KTweaker
5. Couple of other minor miscellaneous patches.
6. Updated KTweaker with a couple of fixes.
7. Finally remembered to upload the OTA file so the checker will report a new kernel when available
Change Log 06.16.2014
1. Re-order cpug/gpu boost calls.
2. vfp: Some tweaks from around the net.
3. Add some build flags from some of the other variants.
4. Remove optimize for size flag.
5. KTweaker: Changed "Charging Settings" to "Charging Mhz Control" under the "Main Settings->CPU Settings" screen.
5. NEW! Add code for "Battery Mhz control" which lets you set a Max Mhz based on battery level. (found under "Main Settings->CPU Settings->Battery Mhz Control").
6. NEW! Add code for "Charging Settings" (found under "Main Settings->CPU Settings->Charging Mhz Control").
7. NEW! Trinity Colors goes live!!!!!!
8. sched: set mc_power_savings=2 this feature packs tasks together and try to bind them to cpu0, which in theory will let cpu1 idle longer, thus improving battery life.
9. smp: patches from mainline 3.5 to hopefully help with hotplug efficiency
10. kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
11. cpufreq: Break out early if freq equals to target_freq
12. NEW! KThermal: Add option to disable/enable kthermal so user has a choice between this and Samsung thermald (3 options listed below)
13. NEW! KThermal: Option to use KThermal (this disables thermald and is what stops Smart Stay from working.)
14. NEW! KThermal: Option to use KThermal+thermald in the background (this will use my thermal throttling engine and still let you use Smart Stay).
13. NEW! KThermal: Option to use thermald (Use stock Samsung thermald for thermal throttling)
14. CHROMIUM: mm: Fix calculation of dirtyable memory
15. mm: Adjust dirty writeback for IO boost
16. mm: optimize Kernel Samepage Merging(KSM)
17. Async I/O latency to a ssd greatly increased, 34% gain (Creds: kleikamp)
18. mm: Increase VM_MAX_READAHEAD to 512
19. NEW! sched: Make GENTLE_FAIR_SLEEPERS configurable thru sysfs
20. video: re-order booster hooks for more speed
21. FIX NFC for Sprint variant!!!!!!!!!!!!
22. Lots of new profiles uploaded to the KTweaker Shop by me and LuigiBull23!!!!!
23. Updated to latest June Linaro from @Christopher83
24. bfq: Upgrade to BFQ-v7r4
Change Log 06.12.2014
1. OC to 2841600!!!!!!!!!!!!!!!!!!!!!!!
2. Increase bandwidth table for new OC step
3. Add LTE support for Sprint users
4. Added conditional code for mpdecision to interact with for people that like the stock full bore all cores mode for smoothness
5. Fix interactive permissions so it can be tweaked
6. Updates from latest Samsung source
7. Adjustments to kthermal settings
8. Miscellaneous KTweaker fixes.
9. Adding missing flag to allow more than 1200 mA when screen is on and charging on A/C charger.
Change Log 06.09.2014
1. Initial Release
2. There are many configuration items in KTweaker, so here is what is working so far since this is just initial release:
3. ktoonservativeq governor
4. Voltage Control
5. CPU Min/Max Mhz control
6. GPU Min/Max Mhz control
7. Screen Off Max Mhz
8. Lots of governors and schedulers
9. 3 choices of hotplugging (stock mpdecision, KT Hot plug, and disabled)
10. FAST Charge
11. LED Settings are active
12. OTA
ktoonservativeq explained:
***** NOTES *****
Any item with the word cycle in it refers to how many sampling_rate's have occurred.
Examples:
A "boost_hold_cycles" of 28 and a sampling_rate of 35000 equates to 1 second of holding your Mhz at the boost level.
A block_cycles_offline_screen_on of 14 and a sampling_rate of 35000 equates to a half of a second block before it takes cores offline.
***** NOTES *****
block_cycles_offline_screen_off =1
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is OFF.
block_cycles_offline_screen_on = 11
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is ON.
block_cycles_online_screen_off = 11
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is OFF.
block_cycles_online_screen_on = 3
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is ON.
block_cycles_raise_screen_off = 11
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is OFF.
block_cycles_raise_screen_on = 3
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is ON.
boost_2nd_core_on_button_screen_off = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_2nd_core_on_button_screen_on = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_3rd_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_3rd_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_4th_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_4th_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_hold_cycles = 22
How many sampling_rate cycles need to occur before going out of CPU/GPU boost mode
cpu_load_adder_at_max_gpu = 0
When set to higher than zero, this will add to the actual CPU load to create a perceived higher load when an app is using alot of GPU but not CPU.
cpu_load_adder_at_max_gpu_ignore_tb = 0
When set to 1, this will ignore cpu_load_adder_at_max_gpu during touch/button boost. When set to 0 cpu_load_adder_at_max_gpu will be used all the time.
debug_enabled = 0
When set to 1 this will output the current cpu load and whats online using dmesg so you can follow what is going on.
disable_hotplug = 0
When this item is a 1, it disables hotplugging so all cores stay on full time. 0 lets all cores turn on and off when needed.
disable_hotplug_bt = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while paired to a bluetooth device and doing bluetooth activities like playing music, transfering files.... 0 doesn't do anything extra to the cores when doing bluetooth functions.
disable_hotplug_chrg = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while charging the device. 0 doesn't do anything extra to the cores while charging.
disable_hotplug_media = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while playing music or movies. 0 doesn't do anything extra to the cores while music or movies are playing.
down_threshold_screen_off = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is OFF.
down_threshold_screen_off_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is OFF.
down_threshold_screen_on = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is ON.
down_threshold_screen_on_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is ON.
down_threshold_screen_on_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is ON.
down_threshold_screen_on_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is ON.
freq_step_lower_screen_off = 8
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is OFF.
freq_step_lower_screen_on = 2
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is ON.
freq_step_raise_screen_off = 1
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is OFF.
freq_step_raise_screen_on = 5
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is ON.
ignore_nice_load = 0
If this value is 1, the system will ignore "Nice" processes when deciding to scale up or down. Nice processes are used by the IO scheduler to designate a low-priority process. Ignore nice load basically tells a governor to disregard processes with higher nice values.
lockout_2nd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_2nd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_3rd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_3rd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_4th_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_4th_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_changes_when_boosting = 0
If this value is 1, all CPU changes to all cores will be ignored while executing a touch/button boost. If 0 all cores will be allowed to scale and hotplug.
no_extra_cores_screen_off = 1
When set to a 1, this option keeps all extra CPU cores offline while the screen is OFF. 0 lets it hotplug them on and off as needed
sampling_down_factor = 1
NOT USED!
sampling_rate = 35000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is ON.
sampling_rate_min = 10000
READ-ONLY value that specifies the lower value that "sampling_rate" and "sampling_rate_screen_off" will accept.
sampling_rate_screen_off = 40000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is OFF.
super_conservative_screen_off = 0
With the screen OFF: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items.
super_conservative_screen_on = 0
With the screen ON: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items to create a smooooooth UI experience.
sync_extra_cores_screen_off = 0
With the screen OFF: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.
sync_extra_cores_screen_on = 0
With the screen ON: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.
touch_boost_2nd_core = 1
When set to a 1, this option turns on the 2nd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_3rd_core = 0
When set to a 1, this option turns on the 3rd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_4th_core = 0
When set to a 1, this option turns on the 4th core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_cpu = 1804800
The Mhz that you want the online CPU's to jump to when the screen is touched.
touch_boost_cpu_all_cores = 0
When set to a 1, this option sets the current Mhz on all online cores to the selected touch_boost_cpu value.
touch_boost_gpu = 462400
This value specifies what Mhz the GPU should jump to when the screen is touched.
up_threshold_screen_off = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is OFF.
up_threshold_screen_off_hotplug_1 = 58
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is OFF.
up_threshold_screen_off_hotplug_2 = 68
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is OFF.
up_threshold_screen_off_hotplug_3 = 78
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is OFF.
up_threshold_screen_on = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is ON.
up_threshold_screen_on_hotplug_1 = 52
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is ON.
up_threshold_screen_on_hotplug_2 = 65
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is ON.
up_threshold_screen_on_hotplug_3 = 68
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is ON.
Other Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
Now it's time for the REAL party to begin!! Great to see you back boss!!!!
Good stuff! Glad to see ya!!!
Loved your work on the lg g2. Great to have you aboard the s5
Sent from my SM-G900T using XDA Free mobile app
pluginre said:
Loved your work on the lg g2. Great to have you aboard the s5
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Lol. You must be thinking of someone else I don't own an LG.
Sent from my SM-G900V using XDA Premium 4 mobile app
ktoonsez said:
Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
Enable ZRAM: Flashable zip
http://db.tt/8vssawIO
Click to expand...
Click to collapse
What does the zram flashable zip do?
Sent from my SM-G900T using Tapatalk
raw2000j said:
What does the zram flashable zip do?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Oooops. Ill remove that, thats for old school TJ ROMs on the S4.
ktoonsez said:
Oooops. Ill remove that, thats for old school TJ ROMs on the S4.
Click to expand...
Click to collapse
Lol thank godd i didnt flash it lol
Sent from my SM-G900T using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:13 PM ----------
Can we use faux123 or just ktweaker?
Sent from my SM-G900T using Tapatalk
raw2000j said:
Lol thank godd i didnt flash it lol
Sent from my SM-G900T using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:13 PM ----------
Can we use faux123 or just ktweaker?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Either or, doesnt matter. But once I get all my features merged in you will miss out on a lot of settings that are only in mine.
ktoonsez said:
Either or, doesnt matter. But once I get all my features merged in you will miss out on a lot of settings that are only in mine.
Click to expand...
Click to collapse
Cool one other thing wifi calling isnt working stuck on enabling
Sent from my SM-G900T using Tapatalk
Updated the Change Log post. I forgot that FAST Charge is also working. Also Fading LEDs is active.
Kernel is working great so far, only issue is wifi calling not working, stuck on enabling
woo hoo! Time to get Ktoonsified!
Was go-to for my S4
Thank you @ktoonsez.
Where is the ktweaker app?
Sent from my SM-G900F using Tapatalk
raw2000j said:
Cool one other thing wifi calling isnt working stuck on enabling
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Not really sure what that is, mush be a Tmobile thing. I would guess that it doesnt want to work when a custom kernel is loaded maybe.
Brava27 said:
Where is the ktweaker app?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
In your app drawer.
ktoonsez said:
Not really sure what that is, mush be a Tmobile thing. I would guess that it doesnt want to work when a custom kernel is loaded maybe.
Click to expand...
Click to collapse
I used blaze kernel wifi calling works must be something else
Sent from my SM-G900T using Tapatalk
raw2000j said:
I used blaze kernel wifi calling works must be something else
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
I made some ramdisk updates, redownload with same link as earlier (also has the same file name) and give it a try:
http://goo.gl/WGCntg
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
Netrunner157 said:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Click to expand...
Click to collapse
Mpdecision.. Qualcomm closed source. Hate it.
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
How do I do this?
> Mpdecision.. Qualcomm closed source. Hate it.
Is this a tool that fixes this?
So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
This is from the program kernel adiutor program you can find here( http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
Davinci50 said:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
Click to expand...
Click to collapse
Oh man I did not know how to use google. You opened my eyes. /s
> kernel adiutor
kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
CM drops to 300.. Turn off mpdecision.
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol
Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
Moody66 said:
CM drops to 300.. Turn off mpdecision.
Click to expand...
Click to collapse
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
Its in snapshot phase. Of course its stable.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
Its fine. Read the cm forum thread.
@Moody66
No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.
Make a backup, load the rom ,and test drive it like we all do.
God I love Google NO /s
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Moody66 said:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Click to expand...
Click to collapse
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
Isn't that easy. It will always default of there isn't something to takes its place.
Moody66 said:
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.
Noone has made a custom kernel for it. Obviously since it has emui.
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?