i'm running virtuous unity ROM on my htc inspire 4g. i'm trying to underclock my phone to save battery. i read info on this from this webpage on xda:
http://forum.xda-developers.com/showpost.php?p=14529333&postcount=5
in the 'wake governor' file, its originally set to 'ondemand'. i'd like to edit it to save battery, but not to kill too much smooth performance. below are the options given. can you please rank the the following in terms of performance and battery life? and which is the best for my needs?
- SavagedZen
- Scary
- smartass
- interactive
- conservative
- userspace
- ondemand
- performance
.
There's now smartass v2, has all the benefits of smartass(no set cpu required, v. quick swiych of freq. after screen on/boot) but also v. stable. It's built in to my custom kernel (xperi arc) but google it
sinkster
sinkster said:
There's now smartass v2, has all the benefits of smartass(no set cpu required, v. quick swiych of freq. after screen on/boot) but also v. stable. It's built in to my custom kernel (xperi arc) but google it
sinkster
Click to expand...
Click to collapse
hi, sinkster.. thanks for the reply. but i really dont know what these terms mean. can you tell me what ranking they have on a scale from 1 to 10 in terms of battery life and also in terms of perfomance?
this is importsnt for me to decide what to set my phone at. especially when i want to save battery but at the same time, not sacrifice performance. thanks.
trapzz said:
hi, sinkster.. thanks for the reply. but i really dont know what these terms mean. can you tell me what ranking they have on a scale from 1 to 10 in terms of battery life and also in terms of perfomance?
this is importsnt for me to decide what to set my phone at. especially when i want to save battery but at the same time, not sacrifice performance. thanks.
Click to expand...
Click to collapse
The rom your running has its own custom kernel, which still only has the original smartass governor, which the thread you posted a link to talks about the flaws of it and came up with their own solution to bypass those flaws. There is a newer version of the smartass governor that fixes those flaws, so you dont have to manually edit the files that the thread is talking about doing, like your trying to do. In order to get the new version of the smartass governor, the developer of the kernel that your rom's dev. is using has to update it (i would recommend searching the forum for the original thread of the kernel). Or you could find another kernel that will work with your current rom but is also updated that includes the new smartass governor. As for the differences of the profiles, Smartass seems to be the most complex but best option for saving alot of battery while not affecting performance of the phone. It saves battery while the screen is off, and when the phone doesnt need to use its cpu fully. It basically learns and throttles between the cpu frequencies you have set based on phone usage while always using the bare minimum frequency while the screen is off and when no applications are being used and a higher/highest frequency you have set for when your using applications so they still run smooth. I would recommend getting Setcpu, it will detect what frequencies your phone is capable of and will allow you to set the smartass governor and the min/max frequencies for it to throttle between. I would also search your Rom's thread and the Kernel's thread(if there is one) to see what the min/max frequency people are having pleasant experiences with.
Synergies14 said:
The rom your running has its own custom kernel, which still only has the original smartass governor, which the thread you posted a link to talks about the flaws of it and came up with their own solution to bypass those flaws. There is a newer version of the smartass governor that fixes those flaws, so you dont have to manually edit the files that the thread is talking about doing, like your trying to do. In order to get the new version of the smartass governor, the developer of the kernel that your rom's dev. is using has to update it (i would recommend searching the forum for the original thread of the kernel). Or you could find another kernel that will work with your current rom but is also updated that includes the new smartass governor. As for the differences of the profiles, Smartass seems to be the most complex but best option for saving alot of battery while not affecting performance of the phone. It saves battery while the screen is off, and when the phone doesnt need to use its cpu fully. It basically learns and throttles between the cpu frequencies you have set based on phone usage while always using the bare minimum frequency while the screen is off and when no applications are being used and a higher/highest frequency you have set for when your using applications so they still run smooth. I would recommend getting Setcpu, it will detect what frequencies your phone is capable of and will allow you to set the smartass governor and the min/max frequencies for it to throttle between. I would also search your Rom's thread and the Kernel's thread(if there is one) to see what the min/max frequency people are having pleasant experiences with.
Click to expand...
Click to collapse
hi, Synergies14.. i truly do appreciate your in depth info. i got 3 questions:
1) you suggested i use 'smartass' as the best option to save battery life. but dont you think that this option sounds like a battery draining option?
2) you suggest i use smartass as the best option for increasing battery life. i set 'smartass' as the option for wake governor. should i also apply it to sleep governor? the sleep governor is currently set to conservative. let me know.
3) can you explain rank each of the 8 terms in terms of battery life and perfomance?
thank you. i appreciate it.
trapzz said:
hi, Synergies14.. i truly do appreciate your in depth info. i got 3 questions:
1) you suggested i use 'smartass' as the best option to save battery life. but dont you think that this option sounds like a battery draining option?
2) you suggest i use smartass as the best option for increasing battery life. i set 'smartass' as the option for wake governor. should i also apply it to sleep governor? the sleep governor is currently set to conservative. let me know.
3) can you explain rank each of the 8 terms in terms of battery life and perfomance?
thank you. i appreciate it.
Click to expand...
Click to collapse
Trapzz, my apologies for not responding to your post back on the 17th. As to question 1, the answer is no. The smartass governor throttles your cpu frequency based on the min/max frequencies you have set in Setcpu for when the screen is off, even if the screen is on and your not using any performance hog apps. The smartass governor is alot better at throttling between the frequencies than any of the other governors. For example, while your screen is off, it will have the cpu using the minimum frequency, even if the screen is on and your looking at text messages, it will only raise the frequency untill the text messages load and then it will scale back down after its done loading. Other governors keep the frequency raised the whole time your in your text messages, even after its loaded, untill you exit it and turn the screen off.
As for question 2, you shouldnt have any profiles set while using the smartass governor, as how the smartass governor works, you dont need any profiles set. Smartass takes care of it all on its own.
As for question 3, im not exactly sure how to rank each governor based on performance/battery life besides other than conservative is used for battery life, and performance is for performance and not saving battery. But with how smartass works, its auto scales the frequencies automatically. Its the best for saving battery, but its also best for performance as it scales to the highest frequency you have set and keeps it there for as long as your app needs it.
Hope i helped answer what you were asking! If you need anything else or any other questions feel free to reply or shoot me a personal message.
Sent from my Mik'd Supersonic OG Evo using xda premium
Synergies14 said:
Trapzz, my apologies for not responding to your post back on the 17th.
As for question 2, you shouldnt have any profiles set while using the smartass governor, as how the smartass governor works, you dont need any profiles set. Smartass takes care of it all on its own.
Click to expand...
Click to collapse
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
trapzz said:
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
Click to expand...
Click to collapse
You are running Setcpu, correct?
Sent from my PC36100 using xda premium
My apologies, it seems that your not, your actually manually editing files for it. I dont have access to a computer right now but i will soon and i will help you futher.
Sent from my PC36100 using xda premium
---------- Post added at 10:27 PM ---------- Previous post was at 09:33 PM ----------
trapzz said:
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
Click to expand...
Click to collapse
Alright, i apologize, i got a bit confused myself there. Judging from your Rom and what the Devs of it say, DO NOT install setcpu like i have mentioned. You will need to install a terminal app. You can go to the market and search for the app "Android Terminal Emulator" and install it. Then in the terminal app, type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" (without the quotation marks) and that will give you a list of available governors to use. Tell me the list of governors it gives you. Then type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies". That will tell you the available Min/Max frequencies that your phone will allow. Tell me the list of frequencies that it gives you. Then i shall help you from there after providing that info to me.
A better option would be to undervolt by 25mv a time if ur kernel supports it
Synergies14 said:
You will need to install a terminal app. You can go to the market and search for the app "Android Terminal Emulator" and install it. Then in the terminal app, type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" (without the quotation marks) and that will give you a list of available governors to use. Tell me the list of governors it gives you. Then type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies". That will tell you the available Min/Max frequencies that your phone will allow. Tell me the list of frequencies that it gives you. Then i shall help you from there after providing that info to me.
Click to expand...
Click to collapse
hi synergies.. below are the available governors and frequencies on my phone:
governors:
SavagedZen
Scary
smartass
interactive
conservative
userspace
ondemand
performance
freqs:
245760 368640 768000 1024000 825600 844800 864000 883200 902400 921600 940800 960000 979200 998400 1017600 1036800 1056000 1075200 1094400 1113600 1132800 1152000 1171200 1190400 1209600 1228800 1248000 1267200 1286400 1305600 1324800 1344000 1363200 1382400 1401600 1420800 1440000 1459200 1478400 1497600 1516800 1536000 1555200 1574400 1593600 1612800 1632000 1651200 1670400 1689600 1708800
Actually can you update your Rom first? if you haven't updated it, there is an update for it that came out a few days ago, before we do anything i want to make sure you have the latest piece of the software.(updating might actually help with the call vibration issue your having too). If you update it, tell me if you have a custom kernel installed or if you leave it with the stock kernel that the rom uses. The type of kernel you use will affect your available frequencies and also if everything is outdated. After you update your Rom, look to see if there is a program on there called "Daemon Controller". If not, then follow this link http://bit.ly/oDeBtV and install the .apk on your phone. This is the new graphical UI for changing and managing your virtuous_oc so you dont have to manually edit the files yourself.
Synergies14 said:
Actually can you update your Rom first? if you haven't updated it, there is an update for it that came out a few days ago, before we do anything i want to make sure you have the latest piece of the software.(updating might actually help with the call vibration issue your having too). If you update it, tell me if you have a custom kernel installed or if you leave it with the stock kernel that the rom uses. The type of kernel you use will affect your available frequencies and also if everything is outdated. After you update your Rom, look to see if there is a program on there called "Daemon Controller". If not, then follow this link http://bit.ly/oDeBtV and install the .apk on your phone. This is the new graphical UI for changing and managing your virtuous_oc so you dont have to manually edit the files yourself.
Click to expand...
Click to collapse
hi synergies. the problem with the update to my rom (virtuous unity), is that its got some issues. but i'll install it. and hopefully i wont experience the same issues.
one other important thing.. how do i do a EXT4 wipe?
.
trapzz said:
hi synergies. the problem with the update to my rom (virtuous unity), is that its got some issues. but i'll install it. and hopefully i wont experience the same issues.
one other important thing.. how do i do a EXT4 wipe?
.
Click to expand...
Click to collapse
I recommend doing a full nand backup before upgrading so that way if you do run into any issues that you dont like, you can just restore from that nand backup. What Recovery are you using?
Synergies14 said:
I recommend doing a full nand backup before upgrading so that way if you do run into any issues that you dont like, you can just restore from that nand backup. What Recovery are you using?
Click to expand...
Click to collapse
hi synergies.. i'm backing up through booting into recovery.
trapzz said:
hi synergies.. i'm backing up through booting into recovery.
Click to expand...
Click to collapse
Thats good. I need to know what recovery your using so i can help you with doing a ext4 wipe.
Synergies14 said:
Thats good. I need to know what recovery your using so i can help you with doing a ext4 wipe.
Click to expand...
Click to collapse
hi synergies.. i dont understand your question. the recovery i use is the one rooted users use... i boot into recovery and choose backup and restore and then backup my phone.
trapzz said:
hi synergies.. i dont understand your question. the recovery i use is the one rooted users use... i boot into recovery and choose backup and restore and then backup my phone.
Click to expand...
Click to collapse
There are different types of recovery that have different names, when u boot into your recovery it should tell you the name and version of the recovery your using
Sent from my Blazed out OG Evo using xda premium app.
Synergies14 said:
There are different types of recovery that have different names, when u boot into your recovery it should tell you the name and version of the recovery your using
Click to expand...
Click to collapse
hi, synergies. i got clockworkmod revovery v3.0.2.5.
trapzz said:
hi, synergies. i got clockworkmod revovery v3.0.2.5.
Click to expand...
Click to collapse
Alright, when you boot into recovery, as always, make a nand backup (as you've said you have already). When you wipe, please note that everything will be erased from your phone including all apps and settings, EVERYTHING. Also as a precaution, ALWAYS go into your contacts in your phone and select to export them to your SDcard. Then connect your phone to your computer and copy EVERYTHING thats on your sdcard to your computer (easily make a folder on your desktop, then select everything on your sdcard, copy it and paste it into the folder). This is so that all your contacts and all your pics/videos and your nand backup are backed up on your computer just incase the wiping process does completely wipe your sdcard (i highly doubt your sdcard will be erased, but its always good practice to take extreme caution as accidents do happen). Then copy the new Rom's zip file onto your sdcard.
*Once you have done all this, boot back into your recovery.
*From the main menu, select "wipe data/factory reset".
*Once that is done, select "wipe cache partition".
*Once that is done, select "mounts and storage".
*In that menu, select "format system".
*Once that is done, select "format data".
*Once that is done, select "format cache".
*Then, judging that you have ext4, i assume your sdcard is partitioned and has the ext on it, if you do, then select "format sd-ext".
*Then go back to the main menu.
*Select "advanced".
*Select "wipe dalvik cache".
*Return to the main menu. Now to install the rom!
*Select "install zip from sdcard".
*Select "choose zip from sdcard".
*A list will appear of the files on your sdcard, select the rom's zip from the list.
*It will ask to confirm installing the zip, go ahead and confirm.
*Once it is done installing, you should be back at the main menu, if not, navigate back to the main menu.
*Select "reboot system now" and you should now reboot into the new ROM. If you have any issues during this process with any of the steps let me know!
also, to get your contacts back into your phone, judging that your sdcard wasnt erased, go into your contacts and select to import from sdcard and you should be good to go!.
I installed Setcpu everything was working great till I lowered the the minimum Frequency to around 700MHZ & I checked the "Set On Boot". It started to reboot the phone continuously I went back unchecked the "Set on Boot" which helped but when I go back in Setcpu it would reboot again.
I tried setting the frequency to the max & it would freeze & reboot quicker. I tried putting the Setcpu safemode in the root of the sd card but it didnt do anything.
I uninstalled SetCpu & updated the RUU on my Rezound it solved the reboots & it seemed everything was running as normal until when the phone was auto-syncing the phone froze for about 10-seconds then everything was back to normal. I heard about flashing the .zip file but I don't know how & I'm not installing Setcpu again to find out.
I'm wondering if the freeze had anything to do with the SetCpu. Everything is deleted once you update the RUU so I don't believe there should be any left over files from the SetCPU. I'm not sure if there on my sd card I was thinking of formatting the SD.
It would never freeze like that before I installed the new update but I never did have Setcpu installed once I got the phone. So I'm wondering if this problem lies with the Setcpu or the new RUU update for the Rezound which is 2.01.605.11?
Probably SetCPU, if you tweak the setting too much (or putting it in awkward settings) it can create errors.
Might have to do with which kernel you are running. Some kernels, such as dsb, play better with certain cpu apps. dsb likes Antutu CPU Master.
Hmm could be something on the user side like kernel or perhaps if you installed a bad downloaded stock rom because I have have been using setcpu since day one with no errors on stock kernel on any rom. If you had a kernel installed prior it may still be installed which allows the cpu to ramp up to unstable speeds such as >1512 mhz.
Even if you were to try set an OC kernel to stable speeds, it will always ramp up to highest speeds, even higher than set. All in all, I would recommend to reflash stock kernel and made sure to flash boot.img which is most important. Hope this helps!
feralicious said:
Might have to do with which kernel you are running. Some kernels, such as dsb, play better with certain cpu apps. dsb likes Antutu CPU Master.
Click to expand...
Click to collapse
eh, dsb hasn't given me problems with SetCPU.
Weird
I only use setCPU, I have all the other ones too just about but they are all uninstalled because they usually just don't work as well, I use incredicontrol for undervolting, and that's it. Dsbs works with incredicontrol too... The kernel could be the issue and not the app but who knows
I'm trying to undervolt the CPU to squeeze as much battery life out of my phone as possible. I've been playing around with the Awesome Sauce and Enoch kernels, both of which should support user controlled undervolting. I'm running Viper4G and was able to flash both kernels no problem...the kernel info in Settings reflects the appropriate kernel after flashing. My problem though, is that I haven't been able to undervolt with either of them using any of the usual apps (SetCPU, Voltage Control, No Frills, System Tuner).
With SetCPU, I can modify the voltages and I see my custom voltages in the "Saved" section, but the "Current" voltages are still stock. This persists through reboot...my custom voltages are still saved, but they never become the current voltages.
With Voltage Control, the voltages just display as "Not Detected: 0mv".
With No Frills, I don't even see a voltage menu.
With System Tuner, I can modify the voltages but I get a popup saying "Voltages will not be saved after reboot. Check boot settings." If I go in and change it to apply the CPU settings on boot, I still get the same message. Same with applying in the init script.
So something obviously isn't right here. For both kernels, I've tried flashing the entire boot.img via fastboot as well as just the kernel via recovery with the same results. Since the one constant here is Viper4G, I'm wondering if the OC Daemon is preventing any changes from being made. I've checked the Viper Control script and it does say that the daemon is not running, so I'm not sure. Has anyone else been able to change voltage with either of these kernels? If so, what ROM are you on and which app did you use?
Thanks in advance...
premo15 said:
I'm trying to undervolt the CPU to squeeze as much battery life out of my phone as possible. I've been playing around with the Awesome Sauce and Enoch kernels, both of which should support user controlled undervolting. I'm running Viper4G and was able to flash both kernels no problem...the kernel info in Settings reflects the appropriate kernel after flashing. My problem though, is that I haven't been able to undervolt with either of them using any of the usual apps (SetCPU, Voltage Control, No Frills, System Tuner).
With SetCPU, I can modify the voltages and I see my custom voltages in the "Saved" section, but the "Current" voltages are still stock. This persists through reboot...my custom voltages are still saved, but they never become the current voltages.
With Voltage Control, the voltages just display as "Not Detected: 0mv".
With No Frills, I don't even see a voltage menu.
With System Tuner, I can modify the voltages but I get a popup saying "Voltages will not be saved after reboot. Check boot settings." If I go in and change it to apply the CPU settings on boot, I still get the same message. Same with applying in the init script.
So something obviously isn't right here. For both kernels, I've tried flashing the entire boot.img via fastboot as well as just the kernel via recovery with the same results. Since the one constant here is Viper4G, I'm wondering if the OC Daemon is preventing any changes from being made. I've checked the Viper Control script and it does say that the daemon is not running, so I'm not sure. Has anyone else been able to change voltage with either of these kernels? If so, what ROM are you on and which app did you use?
Thanks in advance...
Click to expand...
Click to collapse
Smw6180 posted somewhere on viper thread how to disable oc daemon. You should do a search on that thread. You are correct about system tuner, you need to undervolt every time you reboot the phone.
Sent from my lair.
I'm currently using meanrom ics 2.6 and I've tried butteredtoast kernel and anthrax and mac kernel and none will allow me to change frequencies on the fly. I'm wondering if it is a rom script or if anyone knows how to fix it. I have read that many people have had problems with anthrax kernels but i can't get them to stick with any and there isn't any real clear answers i could find, but a few of the same question.
and help would be greatly appreciated:good:.
If I remember right, meanrom has post boot scripts that set frequencies. You'll have to remove Mikey's tweaks. Look in init.qcom.post_boot.sh .
Do you know where his scripts are because i have deleted the init.qcom.post_boot.sh and the problem still persists
I have tried setcpu and cpu master and neither will keep the settings. They have changed for anywhere between 1 minutes to about 3 hours but i will turn on the screen and the widget and app will show the default speed of 1.5ghz
rockerdudelive said:
Do you know where his scripts are because i have deleted the init.qcom.post_boot.sh and the problem still persists
Click to expand...
Click to collapse
Also are in /system/etc/init.d/