Related
HTC locked their stock kernel with a "perflock" to prevent users from underclocking the kernel. Well, good news is that a new function in the SetCPU app will now allow you to underclock your Evo and get you a real, tested increase in battery life.
According to my tests, my Evo with the screen off should theoretically get a 64 hour battery life!
{
"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"
}
Know what you're doing? Short version: Get latest SetCPU (version at least 2.0.0) and use Menu -> Perflock Disabler in the Main tab to enable underclocking.
Don't know what I'm talking about? Good, follow this tutorial:
Prereqs:
You need to have ROOT. Unrevoked root method is confirmed to work, and so is Toast's root method. Usually I wouldn't recommend using Unrevoked, but it's just so fast to set up, and perfect for those who have no clue what ROOT means.
Buy SetCPU from the market, or download it from XDA forums for free. Please support the developer of this incredible app! The version must be at least 2.0.0
Be on the STOCK kernel. If you're on a custom kernel, chances are that perflock has already been disabled, and you won't need this tutorial to underclock. Some custom ROMs come with the stock kernel (like Fresh 0.5.3) and some don't (like Baked Snack .9.6)
Alright, got the prereqs down? Lets start this.
HOWTO:
Open SetCPU and give it root permissions as necessary. As a control, go into the Info tab and do the Long Bench a few times. You should get around 1000ms.
Go to the Main tab, hit MENU, hit Perflock Disabler (read the warning!), and hit Disable Perflock Beta: May crash!
It will work for a while, and then say it's successful. You can then click the X on the top right to exit the Perflock Disabler.
Go into the Main tab and drag Max: all the way down to 245000 (245Mhz). Make sure the green xxx max xxx min label above the sliders show 245 for both and also disable any Profiles you've set. Go to Info tab, then hit Long Bench again. This time you'll get something ridiculous like 5000ms, meaning that the Perflock Disabler has worked!
Change your settings Profile tab to something similar to my settings. You can mess around with the Battery < xx% profiles to fit your needs. Your exact Profile priorities do not matter, it's only important that some have HIGHER priority than others. On the Main tab, set Max all the way to the right (998400) and Min all the way to the left (245000), Scaling to ondemand, and check Set on Boot. Do not check Set on Boot yet if you're the super careful kind. You can check it later when you've tested that your phone isn't crashing
Congratulations you're now able to underclock your Evo!
Comparison:
The only applicable parts is after the charging finishes (after the solid green bar ends)
Before Perflock Disabler:
After Perflock Disabler:
See that little dip at the end? That's when I was turning the screen on and messing with the phone for this tutorial. What a difference.
Disadvantages:
Yes, not everything is happy and pretty. As the Perflock Disabler warning says, you HAVE to apply the Perflock Disabler on every boot. If you forget, then your SetCPU settings will have no effect on the Evo. Install a custom kernel that already has Perflock disabled if you do not want to do this on every boot.
Also, since this clocks the Evo down when the screen is off, you may get a slight (super slight!) delay when you turn the screen back on. This is because the profile changes from Screen Off to Battery < xx% and SetCPU needs to clock the CPU from 245mhz to 998mhz.
FAQ:
What is Perflock Disabler?
HTC added a "perflock" in their stock kernels to prevent over/underclocking. SetCPU's Perflock Disabler, like its name implies, disables this restriction.
How come your screenshots show that you can go down as high as 1.19Ghz and as low as 128Mhz?
I'm using this custom kernel.
Will this work with OTA update xxx.xxx.xxx.xxx?
Yes, as long as you have root, and don't lose it when you update (do your research!) then this will work.
What are your settings?
Wifi ON, Bluetooth OFF, GPS ON, Mobile network Data OFF (ATT contract with dumbphone still not over), Screen Timeout 1MIN, Brightness AUTO, Advanced Task Killer Pro set to SAFE kill tasks when screen is off.
What is that cool looking battery monitoring app?
That's SystemPanel, paid on the market. A free alternative is JuicePlotter, also on the market. Screenshots were taken with Drocap2.
Thanks for this, I'll try this now.
engagedtosmile said:
Thanks for this, I'll try this now.
Click to expand...
Click to collapse
Let us know if it works for you!
Thanks man. Looking good so far
Sent from my PC36100 using XDA App
Awesome, Something to tinker with all night.
download link for setcpu plz...
kthejoker20 said:
download link for setcpu plz...
Click to expand...
Click to collapse
Trust me, it's so goddam easy to find. It's even on this forum!
I was putting in the info exactly the way you had it in your screen, now I'm attempting to put the "screen off" setting into the profile and every time I try it reboots the phone. I'm running baked snack 9.6 the normal volted (Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs) kernel.
Any ideas what could be causing this and how to fix it?
---> clicking on the widget also causes a reboot
davida72 said:
I was putting in the info exactly the way you had it in your screen, now I'm attempting to put the "screen off" setting into the profile and every time I try it reboots the phone. I'm running baked snack 9.6 the normal volted (Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs) kernel.
Any ideas what could be causing this and how to fix it?
Click to expand...
Click to collapse
Whao, weird. Try enabling Notifications on the Profiles tab to see if it tries to change into a certain profile that's clocked too high or low.
pingpongboss said:
Whao, weird. Try enabling Notifications on the Profiles tab to see if it tries to change into a certain profile that's clocked too high or low.
Click to expand...
Click to collapse
I can't, as soon as I tap the Profiles tab it reboots, just tried it...
davida72 said:
I can't, as soon as I tap the Profiles tab it reboots, just tried it...
Click to expand...
Click to collapse
Which version of SetCPU do you have? 2.0.1? Don't know if it's going to help, but try something in between 2.0.0 and 2.0.1 like 2.0.0b.
Does it happen only after you do the Perflock Disabler? Or does it happen every time you use SetCPU.
Try another kernel. There are tons. Maybe try this one that I'm using here http://forum.xda-developers.com/showthread.php?t=711964
pingpongboss said:
Which version of SetCPU do you have? 2.0.1? Don't know if it's going to help, but try something in between 2.0.0 and 2.0.1 like 2.0.0b.
Does it happen only after you do the Perflock Disabler? Or does it happen every time you use SetCPU.
Try another kernel. There are tons. Maybe try this one that I'm using here http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
That is the kernel I have, normal volted one - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
I am using 2.0.1, I'll see if I can find an earlier version and see if that works...actually I'll try reinstalling this one and giving it a try again and see if that works first.
Edit : It tells me I don't need to do the perflock
davida72 said:
That is the kernel I have, normal volted one - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
I am using 2.0.1, I'll see if I can find an earlier version and see if that works...actually I'll try reinstalling this one and giving it a try again and see if that works first.
Click to expand...
Click to collapse
Yea that's really bizarre. we have almost the same setup. Except I'm running the under-voltaged one.
Edit: Actually, that kernel already has Perflock Disabled by default. You shouldn't have to follow this tutorial. SetCPU should "just work" with your kernel.
pingpongboss said:
Yea that's really bizarre. we have almost the same setup. Except I'm running the under-voltaged one.
Click to expand...
Click to collapse
just got another reboot, maybe I'll try the under-voltaged one and see how that goes
davida72 said:
just got another reboot, maybe I'll try the under-voltaged one and see how that goes
Click to expand...
Click to collapse
Flashed the under voltaged kernel and it still rebooted on the profile tab....time to uninstall setcpu for now I suppose?
davida72 said:
Flashed the under voltaged kernel and it still rebooted on the profile tab....time to uninstall setcpu for now I suppose?
Click to expand...
Click to collapse
I guess so. Since this custom kernel already has perflock disabled, you can use another app like OverclockWidget to underclock the CPU. Try it out and let us know maybe.
pingpongboss said:
I guess so. Since this custom kernel already has perflock disabled, you can use another app like OverclockWidget to underclock the CPU. Try it out and let us know maybe.
Click to expand...
Click to collapse
appears as thought the overclockwidget works...just wish it had the profile setup like setcpu does.
I'll look and see if I can find an earlier version of setcpu.
davida72 said:
appears as thought the overclockwidget works...just wish it had the profile setup like setcpu does.
I'll look and see if I can find an earlier version of setcpu.
Click to expand...
Click to collapse
Nice, glad it worked out. OverclockWidget has very basic profiles, but they do the job. Any version of SetCPU should work for you, since you dont need the Perflock Disabler with that kernel.
ok, I got setcpu 2.0.0c and started doing the profile like yours, got to the second seting about the charge/full and saved, got the reboot...
davida72 said:
ok, I got setcpu 2.0.0c and started doing the profile like yours, got to the second seting about the charge/full and saved, got the reboot...
Click to expand...
Click to collapse
Lol I don't know what to say man. Something's screwy.
Trying to figure out what the optimal settings for CM7 on the EVO Shift.
CM7 is a very advanced ROM that gives you control over a LOT of settings and it can be very hard to understand and frustrating to get the optimal settings.
Cyanogenmod 7 latest nightlies and change log available here:
http://cm-nightlies.appspot.com/?device=speedy
As of this time the latest "official" gapps is 828 and is available here: http://www.goo-inside.me/gapps
If you're feeling adventerous CrashV2010 has a new gapps with newtalk and market 3.2 included here:
http://forum.xda-developers.com/showthread.php?t=1311342
How to flash:
1) Get rooted with Clockwork recovery.
2) Download/Open ROM manager, flash clockwork recovery.
3) Reboot into clockwork recovery
4) Upgrading to a new nightly: wipe dalvik cache, /cache partition, /system partition, and battery stats
Clean install: Choose wipe/data factory reset and wipe dalvik cache, /cache partition, /system and data partitions anyway (just to be sure).
5) Partition the sd card how you like (wanna do this on first installs only usually, this will erase your sd card, so copy all necessary files off sdcard to computer before doing this and then copy them back)
6) Choose zip from SD card -> Flash CM7 zip file
7) Choose zip from SD card again -> Flash google apps.zip and then google apps new talk.zip. As of this time the latest gapps is 828 and is available here: http://www.goo-inside.me/gapps
If you're feeling adventurous flash CrashV2010's gapps zip located here: http://forum.xda-developers.com/showthread.php?t=1311342
7a) Flash a custom kernel if you have one.
8) Reboot phone
9) Wait 5-10 minutes for dalvik cache to rebuild and phone to load
10) Once phone boots skip google account setup and get connected to wifi
11) Menu settings -> privacy UNCHECK automatic restore
12) Menu -> settings -> accounts + sync -> add account -> google, sign in.
13) Open market: search for "pub:Google Inc." to find all the google apps
14) IMPORTANT: After installing GMail go to accounts + sync settings -> google account and check the gmail check box. Otherwise gmail will not sync!
15) Flashing a kernel: Download kernel manager lite from the market, open kernel manager lite, load kernel list, allow super user request, menu -> advanced options, uncheck "Automatically flash", back, choose AOSP kernel, download, reboot in to recovery of your choice (clockwork in my case, wipe cache, wipe dalvik cache, install zip from sd card, go to sd-ext dir, kernelmanager, choose kernel zip file and install.
You should be good to go at this point and you can start tweaking CM7 using my settings below or however you want.
At the time of this writing I am running nightly 224, Crash V2010's Google Apps with Market 3.2 and new talk included and Scarystable kernel, latest Clockwork Recovery, Patriot 16GB Class 10 SD card on Sprint. Also, using Google voice for text/voicemail and Launcher pro as my launcher.
I'll usually reboot once every day or two just to make sure it's working properly.. I blame this more on bugs in CM7 than the kernel. Then again I haven't run toastcfh's (stock) kernel in a long time.
4G works
Wifi works
overclocking works
phone is fast
battery life is good
ONLY use ScaryGhoul's governors. (SCARY, TOASTY, BATTERYSAVE!)
ALL OTHER GOVERNORS HAVE STABILITY ISSUES! (interactive, ondemand, performance, etc. etc.)
2 things to take notice of: There is a notification power widget (which goes in your notification/status bar) and a power control widget (which goes on your home screen).
What I'm really not sure about is which takes precedence over the other and what network modes to use.
Update 10-6-2011: I am ALMOST 100% sure the power control widget that you add to your home screen takes precedence.
A lot of settings taken from here:
http://forum.cyanogenmod.com/topic/22620-settings-to-optimize-battery-on-cm7-last-updtd-may-8-2011/
Further explanation of settings here:
http://wiki.cyanogenmod.com/wiki/CyanogenMod_Settings
So here are my settings as of this time:
CYANOGENMOD7 settings (THE IMPORTANT STUFF!)
Application settings
Allow application moving: checked
Install location: automatic
Permission management: unchecked
Phone goggles: off
Display
Automatic backlight
Enabled: off
Light levels (updated 10-17-2011, didn't find this really beneficial and/or don't know how it works)
Use custom: unchecked
Screen dim level: 12
Edit other levels..: ???
Allow light decrease (??): unchecked
Screen-on animation: off
Screen-off animation: off
(saves battery off)
Accelerometer rotation:
0 degrees: checked
90 degrees: checked
180 degrees: unchecked
270 degrees: unchecked
Input settings
Long-press home settings: whatever you want
Long-press menu settings: whatever you want
search key behavior: whatever you want
Haptick feedback tweaks
Haptick feedback main: unchecked
Volume rocker wake: unchecked
Volume button music con: unchecked
(saves battery off)
Interface
Power prompt: checked
Notification power widget
Notification power widget: checked
Hide on change: unchecked
Hide indicator: unchecked
Hide scrollbar: checked
Haptic feedback: off
Widget buttons:
Everything unchecked except brightness, GPS, flashlight, sound, wifi, wifi AP, WiMax
Network modes (???): DO NOT TOUCH!
Screentimeout modes: 30s/2m/5m
Sound modes: Sound+Vib/Vib/Silent
Flash mode: High/Death Ray
Performance
CPU Settings:
Governor: Scary
Min CPU frequency: 184 mhz
Max CPU frequency: 1600 mhz
Set on boot: checked
Compcache RAM usage: disabled
Use JIT (??): checked
Use 16bit transparency: unchecked
Enable surface dithering (??): checked
Allow purging of assets (??): unchecked <-- beter performance unchecked
Lock home in memory(??): unchecked
Lock messaging app in memory(??): unchecked since using google voice now
VM heap size: 48m
Sound
Notification focus: unchecked
Silent state: checked
Vibrate during calls: unchecked
Always play on speaker
Notifications: checked
Ring tones: checked
Alarms: checked
System:
Anonymous statistics
Enable reporting: unchecked
POWER CONTROL WIDGET:
Get to this by going to menu -> add -> widget -> power control on your home screen.
Everything unchecked except the following:
Wi-Fi, Portable wi-fi hotspot, GPS, Mobile data, Wimax, Brightness, Flashlight, Round corners, Wi-Fi disables 3g, Wi-Fi enables 3G, Vibrate as ON
Network mode: 2G/3G only/3G+2G
Ring modes: Sound+Vib/Vib/Silent
Brightness levels: Auto/25%/100%
Screen time out 30s/2m/5m
======================
ANDROID settings:
Wireless & Networks:
Wi-Fi settings:
Network Notification: OFF
In this screen hit the menu button -> advanced
Regulatory domain = 14 channels (BUG: SEEMS TO NOT BE SAVING THIS SETTING ANYMORE)
Wi-Fi sleep policy = NEVER
Mobile networks:
Data Enabled: Checked
International data roaming: Checked
National data roaming: Checked
System select: Automatic
Display
Brightness
Automatic brightness: checked
Auto-rotate screen: checked
Animation: No animations (saves battery off)
Screen timeout: 30 seconds
Call settings:
Voicemail service: Google Voice (when you flash a new CM7 build you will need to delete your sprint number and re add it to google voice in order to get the Google voice choice back. Google voice will call you and you will enter a 2 digit code. Wait for Google voice to hang up on you and then you will be able to choose Google voice as your voicemail carrier.)
Google voice settings from http://voice.google.com :
Sprint integration: enabled
Receive text message on this phone: checked
Notify me of new voicemails via text: checked
These settings will allow you to use the android messaging app or google voice app to send texts and will also back up your SMS.
Vibrate on answer: off
Vibrate every 45 seconds: off
Vibrate on hangup: off
Vibrate call waiting: off
Keep screen awake: off
Always use proximity: off
Always back to call log: on
Missed call LED notify: off
Show nick/organization: off
Left-Hand mode: off
(explanation of left handed mode per otaking71: "It biases the presses/taps. Like if it's off...and you use the touchscreen keyboard......it biases the touches more to the right..vs to the left. Think about how you'd use your thumb one handed. it alters the bias of that.")
Enable sensor rotation: off
Incoming call in background: off
Hide hold button: off
Voicemail notifications: off
Voice Privacy: off
Use internet calling: only for internet calls
Location & Security
Use Wireless Networks: Have had problems disabling this
Use GPS satellites: checked
Use visible pattern: unchecked
Use tactile feedback: unchecked
Visible passwords: unchecked
Accounts & sync settings:
Background data: checked
Auto-sync: checked
(Per otaking71, autosync is not necessary for your accounts like google, facebook, and whatsapp to update. That is what background data is for. This will save you a considerable amount of battery life.)
^^This is wrong, you NEED auto-sync! And I don't know what code for strikethrough is obviously.
UPDATE: Auto-sync needs to be checked in order to receive gmail push notifications.
Background data is what apps like Facebook and Twitter use to sync data in the background.
In order to preserve battery life you should tweak the refresh interval in each application if possible. Other than that you are pretty much stuck with leaving both of these on unless you don't mind manually updating your applications.
Privacy
Backup my data: checked
Automatic restore: unchecked
(ANNOYING setting that will start downloading all your market apps all over again once you reflash!)
=============================================
Explanation of governors:
Quote
From XDA-Dev & setCPU :
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.”
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
interactive- The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
smartass (Available only in certain CFS kernels. Not usually avaialble in BFS kernels like CM.): - Based on interactive, but better. Performance is on par with the "old" minmax and smartass is a bit more responsive. CPU spends much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245. No need for sleep profiles any more!
Scarykernel specific governor explanations:
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/s...-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
===============================================
CHOICES OF KERNELS:
To download/flash a new kernel download kernel manager from the Market.
Differences between kernels are speed/battery savings/overclocking/underclocking/undervolting.
Right now I prefer ScaryKernel Stable. It is way faster than the stock CM7 kernel.
AOSP/CM7 based:
ScaryKernel SUV - ScaryGhoul
ScaryKernel Stable - ScaryGhoul
GirlyKernel - ScaryGhoul
V8 aka Pershoot - SparksCo
Tiamat_Shift - cayniarb
x99kernel-CM7 - x99percent
bcblend VR tinyRCU v - bcnice20
Official CyanogenMod 7 Kernel - toastcfh
You can use Antutu benchmarker (available from the market) to see the performance differences between the different kernels. I got over 4000 on Antutu with Scaryghoul's SuperStable kernel (which is available for download in the dev forum or kernel manager lite app, make sure you are on wifi before downloading through kernel manager lite) on Toasty governor at 1900mhz.
Your results will vary with performance. Not all phones can OC to 1900mhz and all phones will eventually get HOT running at 1900mhz constantly. There ARE different hardware versions of the phone. Mine is version 0004. You can check your hardware version ONLY with a Sense based ROM.
Sense based (DO NOT FLASH ON CM7!!):
ScaryKernel SUV - ScaryGhoul
ScaryKernel Stable - ScaryGhoul
Dodgekernel - dodgejcr
x99kernel-Sense - x99percent
Stock 2.2 Sense - Dodgejcr
Backups:
TITANIUM BACKUP OR BUST!
Please post your settings differences.. also if you could offer an explanation of the stuff I marked in ??? and which takes precedence the power control widget or the power notification widget that would be appreciated. Also provide the kernel you are running, nightly build number, and provider.
{
"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:
toastcfh
ScaryGhoul
riggsAndroid
jesusice
otaking
xIndirect
CrashV2010
ChaoticSheep
Everyone in #htc_evo_shift
This is great!
Yeah just going to come out and say this, I didn't read all of it but you SHOULD/MUST take your phone off of toasty.
Toast is performance renamed. It spends all of the time clocked at the max speed....So you've been spending all this time at 1.9ghz. I recommend either dropping your clock speed down to 1ghz -1.2ghz or doing that & changing governors. Should never spend a long period of time at high speeds/voltages.
Scaryghoul said:
Yeah just going to come out and say this, I didn't read all of it but you SHOULD/MUST take your phone off of toasty.
Toast is performance renamed. It spends all of the time clocked at the max speed....So you've been spending all this time at 1.9ghz. I recommend either dropping your clock speed down to 1ghz -1.2ghz or doing that & changing governors. Should never spend a long period of time at high speeds/voltages.
Click to expand...
Click to collapse
Updated the governor suggestion to Scary. I like having it at max CPU settings in case the phone needs to burst up to that speed.
In fact on either toastcfh's kernel or Tiamat's kernel Jesusice noticed that setting the max cpu speed to the highest actually improved his battery life. I don't know maybe it's different with your kernel.
VICODAN said:
Updated the governor suggestion to Scary. I like having it at max CPU settings in case the phone needs to burst up to that speed.
In fact on either toastcfh's kernel or Tiamat's kernel Jesusice noticed that setting the max cpu speed to the highest actually improved his battery life. I don't know maybe it's different with your kernel.
Click to expand...
Click to collapse
Having the max set higher is not a problem as long as your phone is stable at that speed. Personally I don't like to go above 1.5 but each device is different. The problem is having the governor set to Toasty or Performance. With those governors you're not going just get a quick boost to the max when your phone needs it, it's actually gonna stay at the max all the time. Currently I'm using Smartass on Tiamat's. Scary can correct me if I'm wrong but I believe Smartass scales to your max when actually using the device but scales all the way down to the minimum when screen is off. I believe Scary is a modified version of Smartass.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
Oh, and as far as performance settings I used to have purging of assests and lock home in memory checked and VM heap changed to 48 but lately I've gone back to the stock setting (unchecked with 32 VM heap) and I think I like it better. I've noticed no loss in performance and have noticed that Tapa used to require me to restart it frequently or it wouldn't refresh but now I don't have that problem. No comment on Compache since I'm not on Scary's kernel and that's the only kernel I've noticed that adds those settings.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
jesusice said:
Having the max set higher is not a problem as long as your phone is stable at that speed. Personally I don't like to go above 1.5 but each device is different. The problem is having the governor set to Toasty or Performance. With those governors you're not going just get a quick boost to the max when your phone needs it, it's actually gonna stay at the max all the time. Currently I'm using Smartass on Tiamat's. Scary can correct me if I'm wrong but I believe Smartass scales to your max when actually using the device but scales all the way down to the minimum when screen is off. I believe Scary is a modified version of Smartass.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
Click to expand...
Click to collapse
Tiamat's kernel kept freezing on me. I could try it again soon sometime.
As of right now Scary governor + ScaryStable kernel has not frozen at all. Running good.
@Jesusice, could you take a look at the rest of the settings and let me know what you think?
How's about the data and sycn buttons? I turn off the sycn thought it'll save battery.
Sent from my PG06100 using XDA App
dumper1234 said:
How's about the data and sycn buttons? I turn off the sycn thought it'll save battery.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
You can do that if you like, but I didn't really notice much of a difference..I find they are more trouble than they are worth and sometimes my sync stops working. The bigger question is notification power widget vs power control widget.. it's like 2 places to put in some of the same settings. Anyone know about this?
VICODAN said:
You can do that if you like, but I didn't really notice much of a difference..I find they are more trouble than they are worth and sometimes my sync stops working. The bigger question is notification power widget vs power control widget.. it's like 2 places to put in some of the same settings. Anyone know about this?
Click to expand...
Click to collapse
Using both the notification widget and the power control seems kind of pointless. Unless you would rather have the widget set for different toggles because you don't like scrolling the notification widget. I don't know...
Sent from Gingerbread Speedy 4G
crump84 said:
Using both the notification widget and the power control seems kind of pointless. Unless you would rather have the widget set for different toggles because you don't like scrolling the notification widget. I don't know...
Sent from Gingerbread Speedy 4G
Click to expand...
Click to collapse
There are settings you can change in power control widget that you cannot change in notification power widget settings. Add the widget to your homescreen and see for yourself since you ARE running CM7 after all.
Most of the settings you list are subjective and there's not a "best" setting or "better" setting. So, I'll just go over some of the settings that I have enabled and enjoy.
This is how I have my homescreen and power widget set up:
I don't have 2G/3G toggle enabled because I don't believe it actually does anything on our phones. I wish it did though. And I don't think you have to worry about which widget (power or status bar) takes precedence, they work together. For the status bar widget I have my media controls (prev, play, next) and my torch.
I've been using Tiamat 1.1.2 since release and have kept all performance settings at stock default. 1ghz max w/Smartass governor. I also use AutoKiller Memory Optimizer set to Optimum preset (40, 50, 60) with all the Advanced System Tweaks enabled except "Remount all partitions as noatime". I did have that enabled for a while but then I noticed that when using Gameboid it wouldn't keep track of my quick save correctly.
For me, the beauty of CM7 is in CyanogenMod Settings. There's just some small tweaks available that I don't think I've found in any other ROM that's not based off of CM7. (And I don't feel the need to use a ROM based off of CM7 when I can just skip the middleman and use CM7.) For example, long pressing volume keys while screen off to skip tracks is freaking awesome! (Big up to Bobtsunam for enabling it on MIUI, thereby removing one of the dozens of reasons that prevent me from using MIUI). Also, incoming calls in the background is genius. There is a small bug with it when using apps that exclude the notification bar since it locks the home button but otherwise it's awesome sauce.
If you turn off auto brightness then you can slide along the notification bar to adjust brightness. The long press action for Home, Menu, and Search can all be customized to open whatever app you want. I have my Menu set to bring up Subsonic when held. Whenever I want to leave an app that doesn't provide an easily accessible exit button I just long press Back and BAM!, app killed.
Oh, and I've also been using ViperMod and lowered voltages by -50mv yesterday and haven't had a problem yet. It may be a fluke or because I just wiped battery stats at 100% but I've been getting amazing battery life today. About half and half on wifi and 3G with moderate usage I've gone 7hrs 15mins and am still at 66% =)
I am on nightly #178.
BTW: To any new users reading this, you really shouldn't even bother with the CM7 RC for the Shift. That thing is way behind the curve. I know it's the only CM7 posted in Development but you should really check out the nightlies. 178 is my recommendation. The nightlies thread is in General if you have any questions.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
UPDATE:
I found that you DO need the Power Control WIDGET on the home screen. I was having problems after turning off switching from Wifi to 3G.
Still researching 4G/3G, updated some other settings.
updated, changed allow purging of assets to be unchecked. better performance.
THANKS!
Thank you Vico! It was a pleasure to meet you the other night =)
I am still trying to figure out if they have a Voicemail app that works well now..
Best
konichwa said:
Thank you Vico! It was a pleasure to meet you the other night =)
I am still trying to figure out if they have a Voicemail app that works well now..
Best
Click to expand...
Click to collapse
Google voice! Nice meeting you too!
VICODAN said:
Google voice! Nice meeting you too!
Click to expand...
Click to collapse
I love arguing voicemail! Lol, i personally use YouMail... Many nice features
Teleported from my Shifty Speedy using Tapatalk
updated the instructions, will make some more updates later today.
Updated how to flash instructions, added some more info, screenshots, and added credits to the people that have educated or helped me and contributed to the original post.
VICODAN said:
Google voice! Nice meeting you too!
Click to expand...
Click to collapse
Google voice won't stop the annoying text messages all the time, just a fyi.
Sent from my PG06100 using xda premium
In setcpu I set a profile to switch the governor to conservative. So when I open the browser I can tell it sets conservative by using cool tools, and when I close the browser, it switches my governor back to interactive but the tweaks (hispeed_freq, timer_rate) reset back to their default values, instead of the ones I set. And yes I checked "set with profiles".
Has anyone experienced this? I wanted to double check before I sent them an email.
Try Trickster Mod. That is what I use, and have had no problems. I haven't used SetCPU since my DD was a Captivate
peneoark said:
Try Trickster Mod. That is what I use, and have had no problems. I haven't used SetCPU since my DD was a Captivate
Click to expand...
Click to collapse
Thanks for the suggestion I'll give it a try. But I've experienced this before on my gs3 with another kernel app (ktoonsez ktweaker) which led me to believe its present on all apps.
I have an S3 and also use KT747, and have not had the issues with Ktweaker. Do you have them set to enable at boot? If so, try changing them to a delay of 15 seconds. That's what I had to do with Ktweaker, and do the same on all other kernel apps.
peneoark said:
I have an S3 and also use KT747, and have not had the issues with Ktweaker. Do you have them set to enable at boot? If so, try changing them to a delay of 15 seconds. That's what I had to do with Ktweaker, and do the same on all other kernel apps.
Click to expand...
Click to collapse
Yes, I did set it on boot, actually everything sets fine on boot. Its when switching governors, like when I set a different screen off governor, some governor adjustments stick, others like sampling rate get set back to default.
That sounds normal. Does SetCPU have a setting backup? If so, try backing up, then loading if you want.
Why are you changing govs that much?
peneoark said:
That sounds normal. Does SetCPU have a setting backup? If so, try backing up, then loading if you want.
Why are you changing govs that much?
Click to expand...
Click to collapse
Well I use interactive as my governor, but I tweak it for better battery life. Then I like the conservative governor when in the browser or when battery drops below a certain level. But when I close the browser and my gov switches back to interactive, some tweaks are set back to default instead of what I set.
I haven't read anything about this being intended or normal behavior but I guess that's an explanation..
Sent the developer an email this morning, still waiting to hear back
When I receive an incoming call, the screen remains blank for about 5 seconds to display the options to answer or reject the call. How can I reduce that time?
I have CM-11-20140201-NIGHTLY-mb526 (Also in 20140120 Build)
lfuentes said:
When I receive an incoming call, the screen remains blank for about 5 seconds to display the options to answer or reject the call. How can I reduce that time?
I have CM-11-20140201-NIGHTLY-mb526 (Also in 20140120 Build)
Click to expand...
Click to collapse
Use Aero control app > Set input_boost_freq to 1200 > suspend_enabled to 0
This way u can reduce to 1or 2 sec
lak2004mi said:
Use Aero control app > Set input_boost_freq to 1200 > suspend_enabled to 0
This way u can reduce to 1or 2 sec
Click to expand...
Click to collapse
Thanks, I´ll try
lak2004mi said:
Use Aero control app > Set input_boost_freq to 1200 > suspend_enabled to 0
This way u can reduce to 1or 2 sec
Click to expand...
Click to collapse
where did you find those settings in aero control? You mean put the cpu frequencies to 1200MHz and no deep sleep?
No, I'm using instead SetVsel, I've found it looking for Aero Control.
Anyway I thank you
Sent from my MB526 using xda app-developers app
pgreed said:
where did you find those settings in aero control? You mean put the cpu frequencies to 1200MHz and no deep sleep?
Click to expand...
Click to collapse
in Aero Control, go to CPU Performance, make sure the governor is set to "interactive", then tap the phone icon in the top right corner of the screen. Here are the settings I use.
By the way, this doesn't prevent the CPU from going into deep sleep. The suspend feature just prevents the CPU from going above 300 MHz when the screen is off, so disabling it allows the CPU to ramp up to higher speeds as needed, even when the screen is off. That can actually increase the percentage of time in deep sleep, because the CPU finishes its tasks faster and then goes back to sleep.
Proverbs2 said:
in Aero Control, go to CPU Performance, make sure the governor is set to "interactive", then tap the phone icon in the top right corner of the screen. Here are the settings I use.
Click to expand...
Click to collapse
I don't have the possibilities to fine tunning settings in Cpu Performance (the "phone icon" from top right missed). and yes I am in Interactive
pgreed said:
I don't have the possibilities to fine tunning settings in Cpu Performance (the "phone icon" from top right missed). and yes I am in Interactive
Click to expand...
Click to collapse
You're probably just looking at the "Overview" screen. To change settings in Aero Control, swipe from the left side of the screen (or tap the icon in the upper left) and select CPU Performance.
Unfortunately these settings aren't helping for my defy+ according wake up times (tried it again with 05-02 nightly as well)
Proverbs2 said:
You're probably just looking at the "Overview" screen. To change settings in Aero Control, swipe from the left side of the screen (or tap the icon in the upper left) and select CPU Performance.
Click to expand...
Click to collapse
Nice one. No I'm not that stupid. I've search in CPU performance tile bu only thing that appear in the pen -weird but true.
I google it but i'm not understand very well.
What is intelliplug? It is a type of governor or a improvement for governors?
Rotondo said:
I google it but i'm not understand very well.
What is intelliplug? It is a type of governor or a improvement for governors?
Click to expand...
Click to collapse
first you have to understand what hotplugging is. this is my understanding. hotplugs are used for screen off and on cpu usage. example: when the screen is off the cpu only uses a certain amount of cores. when the screen is on it uses all the cores. also it reduces the wake time of your device by ramping up the cpu frequency to get a faster response. they reduce the on screen lag. this was introduced by qualcomm with mp-decision. but mp-decision is a little aggressive.
intelliplug is a hotplug replacement for qualcomms mp-decision. it's supposed to be more "intelligent". it has a set of parameters that's usually not tweakable and set by the kernel. this is why you normally can only enable or disable it. you dont want to use mp-decision and intelliplug at the same time.
hope this helps.