First off this is not my write up but is taken from this web site> http://www.pokedev.com/setcpu/ please visit as it has screen shots.
I thought this was a good read for those using SetCpu it should help anyone not sure about cpu scaling overclocking and battery usage.
Mods please remove this post if it is not allowed..
SetCPU for Root Users
SetCPU for Root Users allows you to manage the CPU frequency settings of your Android device. It works with most commercial Android devices that have root access enabled for applications. Combined with custom profiles, SetCPU can help you manage your CPU settings to optimize performance and battery life. On many phones, oftentimes with the help of custom kernels, SetCPU can also manage overclocking on your device. SetCPU is currently available on the Android Market and the SlideME Market.
SetCPU works on most devices running Android 1.5 to Android 2.2, with Android 1.6 and above recommended. If you have an HTC device, you may need to disable perflock (see 10) depending on your kernel.
Contents
1. Benefits
2. Main Tab and Basic Usage
3. Profiles
4. Advanced
5. System Info
6. About
7. CPU Scaling Governors
8. Custom Frequency Config
9. Task Managers
10. Disabling Perflock
11. Changelog
1. Benefits
The CPU drains more power if it is running at a higher frequency. If the processor is running faster, the phone will be faster and more responsive, but the battery may drain more quickly. If the processor is running more slowly, the phone will be less responsive and take longer to complete tasks, but battery life will be increased. With SetCPU, you can set up profiles to manage the CPU speed based on certain conditions.
2. Main Tab and Basic Usage
To get started with SetCPU, start the app, read the introduction, and pick "autodetect frequencies." If you ever need to access this screen again, press the Menu button in SetCPU's Main tab, then choose Device Selection.
If your kernel doesn't support autodetect, you won't see it choose the device that best matches your phone from the list. After you've passed the introduction screen, you may get a request from Superuser Permissions. Depending on your version of Superuser Permissions, either check the box for "remember" and press "allow" or press the "always allow" button.
The sliders here allow you to manually control the CPU scaling bounds. The CPU frequency will always be between these two values. By default, the CPU should scale between the max and min frequencies based on need. The sliders also control the "main" profile as explained later.
The "scaling" drop-down list is an advanced feature that allows you to control the behavior of the CPU scaling mechanism. See explanations for the different governors in the CPU Scaling Governors section.
SetCPU also includes a widget for your home screen. Add SetCPU's widget like you would any other widget: long press on your home screen, select Widgets, and select the SetCPU widget. A screen will pop up so you can configure the widget's appearance. If you would like it to show current CPU speed, set the Active Refresh Interval to something other than "Passive," though a passive refresh interval is recommended to save battery.
HTC device users: If the green "current" display doesn't change as you change the sliders, you may be using an incompatible HTC kernel with a driver called "perflock" that prevents SetCPU from changing frequencies. To enable SetCPU, press the "Menu" button in SetCPU's main tab and select "disable perflock." Read through the notice and then press the button in the dialog. If successful, you should be able to change the frequency with SetCPU. If this process fails, please e-mail the developer with your kernel version and device so support can be added. For more details, see the perflock section below.
SetCPU Main Tab
3. Profiles
Profiles allow you to configure SetCPU to set your CPU speed under certain conditions. This is useful to manage battery savings. To get started with profiles, check the "Enable" button in the Profiles tab and press "Add Profile" to add your first profile.
Your profile settings will be triggered if the condition you set in the profile is met. For example, if you choose "Screen Off," the profile settings will be set when the screen is off. If no profiles are met, SetCPU reverts to the default profile specified in the Main tab. Several conditions are available:
* Charging/Full - Set when the phone is charging from any source and when the battery is full while charging.
* Charging AC/Full - Set only when the phone is charging from a wall plug (AC adapter) and when the battery is full while charging from a wall plug.
* Charging USB/Full - Set only when the phone is charging from a computer (USB port) and when the battery is full while charging from the USB port.
* Screen Off - Set when the phone's screen is turned off.
* Battery < - Set when the battery falls below a certain point. You will also be able to specifiy battery level for this profile.
* Temp > - Set when the battery or system temperature rises above a certain point. SetCPU will notify you with a ringtone notification if you check the "Audible Warning" checkbox here. You will also be able to specify a temperature for this profile.
* CPU Temp > - Limited to phones whose hardware and kernels support it. Set when the CPU temperature rises above a certain point. SetCPU will notify you with a ringtone notification if you check the "Audible Warning" checkbox here. You will also be able to specify a temperature for this profile.
The priority of each profile specifies the order in which it will be evaluated. If the conditions of two profiles are both true, the one with the higher priority will be set. For example, if you have both a Screen Off and a Charging profile and the screen is off and charging at the same time, the one with the higher priority will be set.
You can add as many profiles as you want, and selectively enable and disable profiles by using the checkbox next to them. To edit profiles, click on them, make the necessary changes, and press "save." To remove profiles, click on it to edit, and press "delete."
Some things to keep in mind: For multiple battery level profiles, assign the profiles with lower percentages higher priorities. For multiple temperature profiles, assign the profiles with higher temperatures higher priories. Generally, battery level profiles should have lower priorities than other profiles, and temperature profiles should have higher priorites than other profiles.
Check the "Notifications" box to enable a persistent notification in the top bar showing exactly which profile is currently active.
SetCPU Profiles TabSetCPU Profiles Edit
4. Advanced Tab
The Advanced menu allows you to tweak the finer aspects of certain CPU governors. It is only activated when you choose the ondemand or conservative governors.
* Sampling Rate - An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
* Up Threshold - Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
* Down Threshold (conservative only) - Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU down.
* Ignore Nice Load - If this value is "1," the system will ignore "Nice" processes when deciding to scale up or down.
* Powersave Bias (ondemand only) - Setting this value higher will "bias" the governor toward lower frequencies. This is a percentage, where 1000 is 100%, 100 is 10%, and 0 is 0%. The ondemand governor will scale the CPU to a frequency lower than its "target" speed according to this value.
* Freq Step (conservative only) - Defines how much (as a percentage of the maximum CPU speed) the conservative governor will increase the CPU speed by each time the CPU load reaches the Up Threshold.
Choose the "Set on Boot" checkbox to apply advanced settings when the phone boots. This option is completely independent of the similar option in the Main tab.
5. System Info
The System Info tab allows you to view information about your kernel, CPU, battery, phone, and memory status. It also includes a few tools for benchmarking the speed of the phone.
The lower the benchmark score, the faster the phone is running. Keep in mind that this score can only be used to accurately compare different frequencies across the same ROM and kernel. The score may fluctuate between runs due to interference by background processes. For best results, use the "performance" governor.
There is also a "stress test" function. Stress testing allows you to test the stability of undervolted kernels or higher overclocks. The stress test will peg your CPU usage to 100% The phone may be somewhat unresponsive during this time. The stress test will continue forever, so you have to manually end it after some time. To do this, simply press the back button.
To copy the text of the System Info menu to the clipboard, press the Menu button on your device and press "Copy to Clipboard."
6. About
The About menu prints information about SetCPU, including the current version. You can change the theme of the Main tab from using the drop down box. Restart SetCPU to apply it.
7. CPU Scaling Governors
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
* 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 the CPU load. This governor is recommended for stable benchmarking.
* 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.
8. Custom Frequency Config
In rare situations and in older kernels, SetCPU may not be able to autodetect the full range of speeds supported by the kernel. If this is the case, you can configure SetCPU to use custom frequencies. To get started, you'll need the list of frequencies your kernel can support in kHz (not MHz!). Only certain frequencies work, so be sure you know which speeds your kernel supports before using the custom option.
Create a plain text file called "setcpu.txt" and place it on the root directory of your SD card or on your SD card's ext partition (/sdcard/ or /system/sd/). The text files should sort the frequencies on one line by comma, from lowest to highest. For example, the following is a valid config file for some Motorola Droid kernels:
125000,250000,500000,550000,600000
To store the custom frequency list on your phone, save it as "setcpu" with no extension and put it in /data/local/. SetCPU reads from the SD card first and uses that text file if present, then tries to read from /data/local/.
To configure SetCPU to read your custom frequencies, go back to the device selection screen (in the Main tab, press Menu > Device Selection), choose "show other frequencies" if necessary, and choose the custom config option at the very bottom.
9. Task Managers
SetCPU does not run a background service unless profiles or the widget are enabled. Due to how multitasking works on Android, the Android system will automatically free up SetCPU if memory is needed and SetCPU isn't being used.
If either profiles or the widget are enabled, SetCPU does run background processes that keep them running. It's important that you add SetCPU to your task manager's "ignore" list, or otherwise avoid disabling the SetCPU process, if you have either profiles or the widget enabled. You should not have to use task managers to disable SetCPU at any time.
To disable all SetCPU background processes, remove the widget from the home screen and uncheck the "enable" box in the profiles menu. Anything else should be taken care of the Android system when memory is needed, just like any other app. Note that SetCPU briefly runs (and then immediately disables) a service upon startup to perform its "start on boot" duties. This is normal and should not add to memory usage.
10. Disabling Perflock
On most stock HTC kernels and some custom kernels, HTC has enabled a driver called "perflock" that constantly resets SetCPU's Max and Min settings. This does not apply to mostly "Google experience" HTC devices such as the T-Mobile G1, the myTouch 3G, any Google development device, or the Nexus One. It does, however, apply to "HTC Sense" devices such as the HTC Hero, Droid Eris, HTC Desire, HTC Incredible, EVO 4G, and myTouch Slide. Non-HTC devices never have perflock enabled.
SetCPU can disable perflock on newer HTC kernels, giving you control of the Max and Min settings of the CPU. To do this, press the Menu button on your device in the Main tab and choose "Disable Perflock." Read through the notice and then press the button in the dialog. If successful, you should be able to change the frequency with SetCPU. If this process fails, please e-mail the developer with your kernel version and device so support can be added.
Keep in mind that disabling perflock does not enable overclocking, though some overclocked kernels may require perflock to be disabled. Overclocking, in most cases, requires a custom kernel.
11. Changelog
1.4.0: Revamped the main interface quite a bit, and fixed a few minor bugs.
1.4.0a: fixed a bug where 122MHz was being called 128MHz.
1.4.1: * Using Eclair API. Will work on QVGA devices (Tattoo) and WVGA devices (Sholes)
* Major performance enhancements - setting frequencies should be much faster in every situation (in the main application, profiles, upon startup, etc.).
* Added a small home screen widget that shows the current maximum and minimum frequencies. Clicking this widget launches SetCPU.
* Frequency lists for Snapdragon devices, Samsung Galaxy, Motorola Cliq, and HTC Tattoo have been included, though support for these devices is experimental. The device can be selected on the introduction screen.
* Custom frequency lists are now supported. To enable custom frequencies, place a file called setcpu.txt on /sdcard/ or /system/sd/, sorting frequencies in kHz, separated by comma, from lowest to highest, then select the corresponding option on the introduction screen.
* There is no longer a "set" button - changing the seekbar positions will immediately set the frequency. As a result, all seekbars in the application will now snap back if the user attempts to place the maximum frequency below minimum.
* Instead of refusing to work at all, SetCPU will now operate in a read-only mode if root access is not detected.
1.4.2: Instead of choosing between performance (always max) and ondemand CPU governors, there is now a drop down list with all the available governors on the device. Thanks morfic! Added CPU scaling configurations for the OMAP3 processor of the Motorola Sholes/Droid/Milestone. This is strictly in beta. Custom frequency list now reads from /system/setcpu in addition to setcpu.txt on SD FAT or EXT.
1.4.3: Includes compatibility fixes for HDPI devices and UI enhancements. Frequency lists for the Samsung Moment (untested), the T-Mobile Pulse, and the Acer Liquid have been included. The application will no longer sometimes re-set CPU frequencies upon launch.
1.4.3a: Added more frequencies for the Nexus One.
1.4.3b: Fixed a widget issue on the Nexus One. Sorry for the rather rapid succession of updates the past few days!
1.4.3c: Adds support for 600MHz kernel patches on the Motorola Droid. On the Droid configuration. SetCPU will attempt to detect the existence of 600MHz and adjust the frequency list accordingly.
1.4.4: Adds an "autodetect" option that works on newer kernels (at the bottom of the device selection screen). This should enable the supercharged speeds in some of tasmanian_droid's newer kernels. Fixes a force close crash when selecting some frequency lists that were not compatible with the device (thanks Julian).
1.4.5: - Streamlined/refactored profiles code.
- Added "battery temperature" profile. SetCPU is now able to set a certain speed when the battery goes above a user-defined threshold. This would optimally be set to throttle the CPU lower at a high temperature. To ensure compatibility with your device, see if a valid temperature is displayed in the "System Info" menu. This profile does not take effect immediately and does not replace being cautious - it is not based on CPU core temperature, and must wait for a battery state change before reacting.
- Added an "About" button to the main screen with simple themes. Default color scheme is now "Dark"
- Adjusted the widget to display four digit speeds properly (thanks Berzerker).
- Various bugfixes and UI tweaks.
1.4.6: Fixed issues with the battery profile. Included a much better icon thanks to Josh Deere (dphase).
1.5.0: * CPU governors can now be defined in profiles.
* Included a notifications service for profiles - turn this on using the relevant checkbox in the profiles menu.
* Profiles now log which speed and governor is being set.
* Added "advanced" tweaking capability for conservative governor.
* The system info menu and profiles menu now show temperature in both Celsius and Fahrenheit, and the widget also now displays battery temperature in Celsius and Fahrenheit.
* Added a "long benchmark" option to the system info menu, which should be more consistent than the "short benchmark."
* Also added a simple stress test to the system info panel to test the stability of overclocks.
* Autodetect is now the default for devices that support it, and will be the first option in the menu if available.
* Improved I/O performance.
* Various bugfixes, especially in profiles.
1.5.0a: * Charging profile now no longer takes effect when the phone is at 100% battery and unplugged.
1.5.1: * Two more battery profiles added. Lower battery readings will always take priority (eg. under 80% will always take priority over under 100%).
* Governor will now refresh alongside the other readings. Added governor reading under current frequency reading.
* Added an auto-refresh checkbox to the main screen. If checked, SetCPU will periodically refresh the current frequency reading without the need for pressing the refresh button. This checkbox applies to the system info panel as well.
* Tweaked the widget, and attempted to fix the elusive bug where the widget did not update correctly sometimes.
1.5.1a: * Fixed widget being cut off in landscape mode.
* Fixed Fahrenheit temperature reading in profiles.
1.5.2: * Added optional failsafe notification warning system that plays a ringtone and flashes the LED red when the failsafe profile is active (thanks WootRoot!).
* Added "copy to clipboard" function for the System Info menu (press Menu).
* Added an optional "active" widget, which will refresh CPU speeds at an interval like the main interface.
* Added support for the OMAP3 temperature sensor for the Droid. If present, use of the OMAP3 temperature sensor can be enabled in the failsafe profile.
* If available, the OMAP3 temperature can also be read in the system info menu.
* CPU temperature settings will only appear if the sensor is present and support for the temperature sensor is enabled in the kernel! Right now, this is only for the Droid.
* The about menu now defaults to a "default" theme where SetCPU will not mess with any backgrounds defined in the XML layout.
* Fixed stress test failing when JIT is enabled.
1.5.2a: * Temperature sensor used in the widget for the Droid is now controlled by the failsafe setting. I will implement a proper appwidget configuration activity in a later update.
* Fixed an issue with the audible warning notification not being properly dismissed.
* Profiles optimizations.
1.5.3: * Memory/performance footprint decreased.
* Battery drain should be fixed on the Droid.
1.5.3a: * Active widget CPU usage optimized.
* Further profiles optimization for the Droid.
* Uncommon I/O force close fixed.
1.5.4: * Switched to the Android 2.2 SDK.
* Enabled external storage support (install location is automatic).
* Eliminated the distinction between the active and passive widgets, and replaced it with an appwidget configuration activity for the widget, allowing the user to choose the color of the max/min text, temperature display, temperature sensor (Droid), and refresh interval.
* Optimized the active widget refreshing.
* SetCPU will now hide non-autodetect frequencies by default on devices where autodetect is available, but hard coded frequencies and the custom option can be re-enabled with a button.
* Custom frequency list can now read from this exact file: /data/local/setcpu (in addition to the previous setcpu.txt on SD fat or ext).
* Includes various bug fixes and minor UI changes.
1.6.0: * Ported parts of the app to the NDK to improve performance.
* Fixed a bug where the widget was resetting colors upon reboot or launcher orientation change.
* Autodetect now works for all devices. It is recommended by default.
2.0.0: * User interface has been completely redesigned, and now uses tabs for switching between menus instead of buttons. Landscape mode in the main tab no longer requires scrolling down. The Advanced menu and Profiles menu have also been redesigned for a better landscape experience.
* The "auto-refresh" option and refresh button in the main interface and system info menu have been retired - SetCPU always auto-refreshes automatically.
* The profiles menu and service have been recoded from scratch, and now allows the creation of unlimited profiles with custom priorities. The "priority" meter for each profile determines the order in which it is evaluated - if two profiles apply to a given situation, the profile with the higher priority will be set. If you had profiles set before 2.0.0, you will need to set them again.
* Profiles have been further optimized for performance footprint as a result of the re-structure.
* Added "Charging AC/Full" and "Charging USB/Full" profile conditions to distinguish between fast charging and slow charging modes on some devices (thanks Julian).
* Added a beta "perflock disabler" feature that will enable frequency changing on stock HTC 2.6.29 kernels. Access the perflock disabler this by pressing Menu in the main interface. If this gives you an error, does not work, or crashes your phone, your kernel is not compatible - pull your battery to reset if necessary. E-mail me with your ROM, phone model and kernel information in "System Info" (thanks to Richard for a lot of help with the low-level stuff, and no thanks to HTC for implementing perflock in such a way . To access the perflock disabler, press Menu in SetCPU's main interface.
* Code cleanup and more.
* A big thanks to everyone who tested, especially those who gave feedback on this one, all the people who purchased SetCPU from the Android Market, as well as all my users.
2.0.0a: * Fixed a permissions error that was causing SetCPU to autodetect incorrectly and force close on some ROMs.
2.0.0b: * More fixes, sorry guys.
* Fixed an issue with profiles and custom frequency lists.
* Clarified the profiles priorities introduction.
* Fixed a bug with the Advanced menu erroneously reporting values if the governor was changed after onResume was called, and fixed a crash that sometimes occurred as a result.
* Fixed a bug where the passive widget acted like the active widget after frequencies were manually set.
2.0.0c: * Fixed issues with the Advanced menu and Advanced settings not being applied on boot.
* Fixed an issue in where temperature warnings were not being dismissed properly.
* SetCPU 2.0.0 no longer force closes on Android 1.5 devices, but the UI in some menus is flawed. I recommend that you update to a more recent version of Android if possible.
2.0.1: * Added a few widget backgrounds. Configure this when adding the widget.
* Added the ability to "swipe" to the next tab.
* Fixed various bugs.
* New documentation is up.
SetCPU and content is (c) 2009-2010 Michael Huang/coolbho3000.
Dont know if this issue has been reported.
On my ZTE Blade, Japanese Jellyfish rls 7, SetCPU only works the first time you use it. After that you only get the black screen problem.
I restarted SetCPU, black.
Force close, black.
wipe data, black.
Then I tried delete permission in Superuser and after that SetCPU worked! Now I have to delete SU permission every time I want to use SetCPU.
I seem to be the only user with Blade +JJ7 that got this problem.
(site is down so I cant report the problem)
Hmm found thread way back on google, maby link to it?
http://forum.xda-developers.com/showthread.php?t=505419
Thanks for sharing
I'm very interested in pushing my device to the limits, and want to OC. I didnt really understand the "voltage control" app so i installed "set cpu"
I thought that by setting the MHz it was all kind of automatic.. I set it to 1300, as my kernel should let me run at these speeds. I'm hearing this particular ROM can run as fast as 1.4ghz. The phone was getting impressive benchmarks and linpack scores, but when i ran neocore it froze almost instantly. What should i set the minimum to? is that the problem?
Can anyone give a detailed explanation of the governors? Like how is hotplug compared to conservative?
the best way to find the maximum stable speed of the cpu is to let it run bechmarks and heavy games without any crash for long time.
leonisk said:
the best way to find the maximum stable speed or the cpu is to let it run bechmarks and heavy games without any crash for long time.
Click to expand...
Click to collapse
Well on the Desire, I've reached the conclusion that 1113 MHz is the maximum speed
at which the device could run on most rom/kernels with Heavy Games, or App Running.
I've done the test and the Desire lasted 1 hour playing N.O.V.A 3 without charging before
shutting down, while when charging it lasted 25 min for the device overheated and crashed shutdown.
428 MHz is the lowest at which you can be running a heavy app and not have a
deep device freeze assuming you kill the app as soon as you reach this frequency.
But as with all rom, kernels, device hardware (which can really vary) all these value
can change.
So I advise to be careful when putting an underclocking profile in setCPU add an App
Condition so that the profile doesnt start as long as all your heavy apps are running in
the foreground, or when closing the screen.
Sheiji said:
Well on the Desire, I've reached the conclusion that 1113 MHz is the maximum speed
at which the device could run on most rom/kernels with Heavy Games, or App Running.
I've done the test and the Desire lasted 1 hour playing N.O.V.A 3 without charging before
shutting down, while when charging it lasted 25 min for the device overheated and crashed shutdown.
428 MHz is the lowest at which you can be running a heavy app and not have a
deep device freeze assuming you kill the app as soon as you reach this frequency.
But as with all rom, kernels, device hardware (which can really vary) all these value
can change.
So I advise to be careful when putting an underclocking profile in setCPU add an App
Condition so that the profile doesnt start as long as all your heavy apps are running in
the foreground, or when closing the screen.
Click to expand...
Click to collapse
Would you happen to know if setting your CPU to low causes phantom presses, or is it just related to hardware/screen malfunction.
Sent from my HTC Desire using xda app-developers app
twics said:
Would you happen to know if setting your CPU to low causes phantom presses, or is it just related to hardware/screen malfunction.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
If by Phantom press you mean the device react to touch action when you are not touching it then it is most probably because you are under clicking a semi- stable speed.
In sum: yes it can cause phantom presses. You touched the screen, the device registered it but processed the information slowly and delivered the output much later.
Although if those Phantom presses occur at a higher speed, try to clean the screen as grease and other conductive substances can offset the Desires capacitive touchscreen.
________________________________
Please press thanks if I helped you in anyway.
Sent from my HTC Desire using the xda app.
Sheiji said:
If by Phantom press you mean the device react to touch action when you are not touching it then it is most probably because you are under clicking a semi- stable speed.
In sum: yes it can cause phantom presses. You touched the screen, the device registered it but processed the information slowly and delivered the output much later.
Although if those Phantom presses occur at a higher speed, try to clean the screen as grease and other conductive substances can offset the Desires capacitive touchscreen.
________________________________
Please press thanks if I helped you in anyway.
Sent from my HTC Desire using the xda app.
Click to expand...
Click to collapse
Thanks for your reply, I think you may have solved a long time thorn in my side so to speak, for a good few months now almost a year or so iv been getting this phantom press syndrome while using keypad very annoying, also some flickering of screen back and forth without me actually touching the screen, but simply just turning off/on screen solved it until it returned, always trying to conserve battery power never gave a thought that by setting my CPU low could cause this, I just happen to read your above post about setting CPU to 428mhz, mine is now set to 422mhz lowest and Since doing so my phone feels great and while typing this iv had no phantom presses I shall monitor this for a few days to be sure, many ppl report this issue but i don't think its been said low setting of CPU can cause this.
Thank again
Sent from my HTC Desire using xda app-developers app
No problem! It's good to hear that let's hope the problem has been solved now
________________________________
Please press thanks if I helped you in anyway.
Sent from my HTC Desire using the xda app.
Ok well although my phantom presses is still present its a lot less active:thumbup:, iv tried cleaning the screen but no difference, so I guess ill have to return it to my network for service, thanks for trying to help.
Sent from my HTC Desire using xda app-developers app
Nice start for a person like myself that knows nothing about the program.
Is this guide still up to date enough?
Why does my SETCpu have 0 as max and 0 as min when i clearly have it set up?
{
"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"
}
Cant view the screen shot for some reason, also I have not used setCpu for a few years now, I don't think the app has been updated that much so the information here should still be of good use.
Sent from my HTC One using Tapatalk
(952) 300-5200
Related
First of all, sorry for my bad english ...
.. a few days ago, i have rooted my wildfire (Unrevoked 3.21), ...that was okay, no problem was
... after that i have the superuser thing ... so i have installed setcpu 2.0.4.
After this, i flashed HCDR.Jacob's kernel...
At the first time, a lots of popup window came, but no force close, or other error message ... i thing its working
i created the profiles like this:
- main: 768 max, 122 min
- Screen off: 245 max, 122 min
- Temp: 518 max, 122 min at 50 Celsius degree
- Battery: 576 max, 122 min
- Charging, Full: like main
Everything in Ondemand ...
After this setting, not alwasy, sometimes, when the screen is off and i have an incoming call, the screen is a little bit yellowy ... like old tv-s?!
Is it possible, the high cpu framerate can glitch the screen colors?!
Should i set lower cpu rate, in main and charching profiles?!
I cant understand, becasuse when the screen is off, the cpu is running on 245 ... this isn't so high ... also maybe a little low
Any ideas, or common "yellow effects"?
And another thing .. do i need perflock disabler to HCDR.Jacob's kernel??
thx
Lazlo
It's a known problem, just set you screen off profile to 325 max, 245 min. this fixes it
I can confirm this bug. I been wondering myself what was happening but couldn't be assed to investigate. I just figured its a ROM problem, I use OpenFire, but apparently its not..
EDIT: Post above wasnt posted when posting this.. Did you mean 352 or 325mhz, Wockawocka?
LeandroMarceddu said:
Did you mean 352 or 325mhz, Wockawocka?
Click to expand...
Click to collapse
Mine is set to 352 I can't select 325mhz. please find attacted a copy of my profile backup. Extract file to your SD cards root and restore profile from setCPU
wockawocka said:
Mine is set to 352 I can't select 325mhz. please find attacted a copy of my profile backup. Extract file to your SD cards root and restore profile from setCPU
Click to expand...
Click to collapse
thank you wockawocka your attachment i restored it to setcpu ... and i will test it for few days ... and will report what happened
i didn't know this yellowy screen is a known problem
and another thing,.. do i need perflock disabler with the HCDR.Jacob's kernel??
i haven't enabled it yet
thx again
cheers
lazlo
pazirez said:
and another thing,.. do i need perflock disabler with the HCDR.Jacob's kernel??
i haven't enabled it yet
Click to expand...
Click to collapse
I don't know, I've not selected it... you could try the following that I found in another post..
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 122000 (122Mhz). Make sure the green xxx max xxx min label above the sliders show 122 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 (710000) and Min all the way to the left (122000), 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 - I've edited some of the above to make it look right for the Wildfire, was copied from Evo post
okay, i tested the perflock disabler post .... but nothing happened ... i tried to enable it, but it said "You can't, there is no perflock" or something like that ....
by the way ... with your profiles, its workin, no yellow screen, so i'm happy .... and i'll leave it alone ... and it looks like the battery and setcpu is a good friend too
I would like to get to know the CPU governor settings with CM7 bootmenu settings in order to increase battery life. Maybe others too - hope so.
The below description I found in hrk post:
- powersave will always set the "min" and never change it
- performance will always set the "max" and never change it
- ondemand (usually the default) will raise the value by a step up when the cpu is used, and lower the value by a step down when the cpu is not (much) used.
- conservative is like ondemand but will be slower when changing frequencies
- interactive is (conceptually) like ondemand but will be quicker when changing frequencies.
- smartass is (conceptually) like interactive, but I haven't understood yet why it's so much smart and loved by users.
- userspace will do nothing at all, so don't choose it. I may hide it in a future release to avoid confusion
Anyone can add information about above modes in CM7 bootmenu?
So there are like those prefixs there:
con - this goes to conservative governor mode;
int - this one is for interactive governor;
ond - is for ondemand mode;
smt - is smartass governor mode.
But what about Clk1, Clk2, Clk3 and Vsel1, Vsel2, Vsel3 settings?
To which governor modes this Clk and Vsel settings apply?
Anyone can help/explain?
well.... Clk1, Clk2, Clk3 and Vsel1, Vsel2, Vsel3 basiclay apply to all.
Clk1, Clk2, Clk3 are the clock speeds that the proccesr will run when stepping up or down, the defaults with no overclock are 300,600,800.
Vsel1, Vsel2, Vsel3 are the voltages that the proccesor runs at when working at coresponding clock. tweaking these will make ur battery last loger.
for example
default clk3 is 800 at vsel 58
currenty i have clk 3 at 1000 with vsel3 52.
hope you have understand what i mean.
ps sorry for my bad english
There is a ready made app that can help you with the changes.
Have a look at
http://forum.xda-developers.com/showthread.php?t=898036
What about the threshold?
What it does and does it apply to every governor mode?
kaljam said:
There is a ready made app that can help you with the changes.
Have a look at
http://forum.xda-developers.com/showthread.php?t=898036
Click to expand...
Click to collapse
As stated in this thread at point 15 you should'n install Setvsel.
15) How to overclock/undervolt in CM7?
CM7 already comes with 1000/600/300 clock, but if you want to modify these settings or undervolt:
- Reboot and enter Bootmenu
- System -> Overclock
Remember that if you experience freezes, reboots and other problems OC/UV can be the cause. Try to disable in this situation.
Also, DON'T INSTALL SETVSEL!
http://forum.xda-developers.com/showthread.php?t=1065798
When I install Setvsel on CM7 and went back to Bootmen /CPU settings - it was disabled.
So installing Setvsel on CM7 disables CPU settings in Bootmenu, previously enabled there.
m_zet said:
When I install Setvsel on CM7 and went back to Bootmen /CPU settings - it was disabled.
So installing Setvsel on CM7 disables CPU settings in Bootmenu, previously enabled there.
Click to expand...
Click to collapse
Well i want my phone to be lightweight so if i can do some settings without an aplication running on my system, i'm up for it
I've tried both and I'm more satisfied with setvsel.
Setvsel is great for the ones who has no CM7 and its bootmenu with setvsel functionality implemented there.
BTW
Anyone can explain why smartass governor is so awsome?
As I said i've tried both with CM7 and I prefer setvsel.
I get better battery time with setvsel. Probably because there is a load of parameters in bootmenu you can apply but nobady cares to explain what they do
kaljam said:
As I said i've tried both with CM7 and I prefer setvsel.
I get better battery time with setvsel. Probably because there is a load of parameters in bootmenu you can apply but nobady cares to explain what they do
Click to expand...
Click to collapse
I got the same results with settings done by Setvsel and done in bootmenu CM7 CPU settings.
I compared Defy running using CM7 bootmenu CPU settings and Setvsel.
It was the same - so why bother to install an app when it is in bootmenu.
Though the CPU menu got more options to get to know and set, what this thread was made for.
As always the choise is yours - the phone is yous you can do anything with it.
well, can someone answer a question posted before? what are the thresholds and the rest of the settings?
m_zet said:
When I install Setvsel on CM7 and went back to Bootmen /CPU settings - it was disabled.
So installing Setvsel on CM7 disables CPU settings in Bootmenu, previously enabled there.
Click to expand...
Click to collapse
Do you mean we can actually use Setvsel in CM7?
I think this should help you:
http://forum.xda-developers.com/showpost.php?p=30779799&postcount=1
And this:
http://forum.xda-developers.com/showthread.php?t=1377587
About
avsMon lets you easily enable or disable avs module via simple button click or even enable it on every boot. Moreover it provides information about current state of avs module, cpu frequency and voltage.
thalamus kernel comes with disabled avs module. We can easily enable this functionality for some power usage improvements (like drop to 3-4mA in screen off state) if cpu can handle those voltages, by 'echoing' 1 to /sys/module/avs/parameters/enabled. But this requires opening a terminal application and some struggle with onscreen keyboard. Inconvenient and time consuming.
A bit annoyed, I've ended up with this little application. It's basic functionality is to help to enable or disable avs module, by providing GUI to those 'echo' commands.
Additionally, it displays info about current avs state, cpu frequency and cpu vdd (pooled in user configured intervals).
This post and application originates from here: http://forum.xda-developers.com/showpost.php?p=15988562&postcount=934.
Click to expand...
Click to collapse
Current version v.0.0.4.1 (download from attached files)
Screenshoots
{
"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"
}
Todo
investigate devNull compatibility
Changelog
Code:
[b]v.0.0.4.1 | 31-07-2011[/b]
- default maximum voltage changed to 1250mV,
[b]v.0.0.4 | 31-07-2011[/b]
- option to set maximum voltage ([I]vdd_max[/I]),
- option to set minimum voltage ([I]vdd_min[/I]),
- option to apply user-specified voltages on boot,
- user interface improvements,
- bug reported by [url=http://forum.xda-developers.com/showpost.php?p=16128093&postcount=10]theyau[/url] fixed,
- multilingual support ([I]strings.xml cleanup, now ready for translations[/I]),
- about view modified - donate link added,
[b]v.0.0.3 | 28-07-2011[/b]
- option to set avs module to enabled on boot,
- user interface improvements,
- some minor code optimizations and cleanups,
- one bug traced and fixed.
[b]v.0.0.2 | 26-07-2011[/b]
- options menu in main view,
- cpu frequency and vdd information,
- user configured pooling interval for frequency/vdd,
- GUI improvements,
- changed basic program icon,
- about view & settings view,
[b]v.0.0.1 'proof of concept'[/b]
- initial release with basic functionality:
* avs status,
* enable/disable avs module
Manual
1. Enabling avs module on boot.
To enable avs module on boot, press menu key. This will open options menu pane. From there, select settings. You'll be transferred to settings view, where you have to click Enable AVS on boot option.
avsMon will now request superuser rights. If you haven't already done this, su popup will appear. For best results, check Remember box and allow.
2. Applying user-specified voltages on boot.
To apply custom voltages, go to settings, select Voltages and then check Enable user-specified voltages on boot.
avsMon will now request superuser rights. If you haven't already done this, su popup will appear. For best results, check Remember box and allow.
3. Changing voltages.
To change voltage levels, go to settings, select Voltages and then either Minimum voltage or Maximum voltage. Changing default value will result in immediate writing new values to vdd_min or vdd_max files in sysfs.
Requirements
Requires 2.3 and su privileges to toggle avs module.
Fetching avs and cpu states is done with normal privileges.
Disclaimer
I don't take responsibility for any damage or data loose.
Application was tested on Oxygen 2.1.6 with thalamus kernel 2.6.35.13_r4.
I recommend to uninstall earlier version and then install current rather than update already installed one.
Final notes
If you like this little app, don't forget to press thanks button.
Donations are off course welcome.
Any features requests and comments are much appreciated.
Stay tuned, for updates....
This is nice. I shared your pain fiddling with terminal and keyboard.
Good job
Nice idea! However, I think one would not enable or disable the feature too often. I would rather put a script in /system/etc/init.d to enable it at each boot (and so I have done). I would suggest you a new feature: add a button Make it permanent to make the setting be restored at boot (if you haven't implemented it already). The implementation should write a specially crafted script in /system/etc/init.d to restore whatever setting was chosen in the GUI. Of course, your application would need a root privilege.
AlxMAX said:
Nice idea! However, I think one would not enable or disable the feature too often. I would rather put a script in /system/etc/init.d to enable it at each boot (and so I have done). I would suggest you a new feature: add a button Make it permanent to make the setting be restored at boot (if you haven't implemented it already). The implementation should write a specially crafted script in /system/etc/init.d to restore whatever setting was chosen in the GUI. Of course, your application would need a root privilege.
Click to expand...
Click to collapse
Tanks. I already have peresistent avs enabling through android service @ boot on my todo list. I think that it's much elegant solution, than writing anything to /system/etc/init.d/ (which is not so easy thou and requires remounting /system).
Simple service will start at boot, check if avs is enabled or not, then it'll enable (if user has selected so) it. Same result. No flashing or writing to init.d needed. Root privileges usage should be kept at minimum.
This will be included in one of next versions.
New version available.
Code:
[b]v.0.0.3 | 28-07-2011[/b]
- option to set avs module to enabled on boot,
- user interface improvements,
- some minor code optimizations and cleanups,
- one bug traced and fixed.
Any chance for a version for DevNull?
laba82 said:
Any chance for a version for DevNull?
Click to expand...
Click to collapse
If devNull incorporates the same kernel (thalamus), then just try it and let us now if it works. If devNull has the same kernel as Oxygen and avsMod doesn't work, then please send me PM with logs and problem description. I'll look into this.
Afaik, DevNull uses the same kernel as Oxygen, 2.6.35.13-stable [email protected] #1.
Pressing Turn on AVS does nothing only says that avsMon has superuser rights.
laba82 said:
Afaik, DevNull uses the same kernel as Oxygen, 2.6.35.13-stable [email protected] #1.
Pressing Turn on AVS does nothing only says that avsMon has superuser rights.
Click to expand...
Click to collapse
Please, send me logs. I'll look into this.
Mine says its using 1300 mv and the frequency is 1mhz
Sent from my HTC Desire using XDA App
theyau said:
Mine says its using 1300 mv and the frequency is 1mhz
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Do you have AVS enabled? avsMon now tries to read cpu states even if avs is not enabled and this could provide to such values. It's normal and will be corrected in future version. Try to enable AVS and then check readings.
If AVS is enabled and avsMon still shows such readings, then please send me logs and describe all actions and steps you've made.
New version available:
Code:
[b]v.0.0.4 | 31-07-2011[/b]
- option to set maximum voltage (vdd_max),
- option to set minimum voltage (vdd_min),
- option to apply user-specified voltages on boot,
- user interface improvements,
- bug reported by theyau fixed,
- multilingual support (strings.xml cleanup, now ready for translations),
- about view modified - donate link added,
Yay my name is in the thread
Sent from my HTC Desire using XDA App
am using oxygen 2.1.6 with thalamus kernel, setting voltages doesnt work, have tried but its still reporting old voltages, im settingmin as 850 maximum as 950 (i know my phone can take it ) but its still reporting higher voltages.
dannylill1981 said:
am using oxygen 2.1.6 with thalamus kernel, setting voltages doesnt work, have tried but its still reporting old voltages, im settingmin as 850 maximum as 950 (i know my phone can take it ) but its still reporting higher voltages.
Click to expand...
Click to collapse
When you change minimum or maximum voltage, avsMon will write this new value to either vdd_min or vdd_max in /sys/module/avs/parameters/. The rest is up to kernel and avs module implementation. Basing on thalamus comments, it should read vdd_min/vdd_max in sysfs and use those values.
Values reported as cpu frequency and voltage status are taken from /sys/module/avs/parameters/status. And here is the same as with voltages. It's up to kernel and avs module to update this file in sysfs.
avsMon is just an interface to commands you'd normally have to write manually. Nothing more.
I haven't tested voltage settings much. They're implemented based on assumption, that "this should work, because avs should read those files in sysfs". Try to change voltages and then observe your power consumption. If your phone uses less mA than normally, then it's working. If not, then we should ask thalamus for his opinion, it's his kernel
thanks for the reply buddy, im not expecting miracles from the app, just letting you know. cool app, for all i know it could be working, just the reported values are wrong, ill see how it goes and if necessary, a word with thalamus to see if he can shed any light on it may be in order.
I originally posted this in an existing thread, and considering other users reporting it actually helps, I figured I'd start a new thread specific for this.
I want to share what I found, considering it has helped a bit with the issue. The missed taps and all still happen, just not as often before I made these changes.
WARNING, do not adjust values that you are unsure of. Setting any of the following values lower than default will cause touchscreen issues.
You will need root
I downloaded Kernel Adiutor from the Play Store (link: https://play.google.com/store/apps/d....kerneladiutor), and changed a couple values pertaining to the CPU. Here's what I did and how you can try it out too:
1. Open the app, open the hamburger menu and select "CPU".
2. Scroll down until you get to the "CPU Boost" category.
3. There are two values you're going to change here.
A. Input Interval: Default is 40ms, I changed mine to 150ms
B. Input Boost Frequency Core 1: Default is 1248MHz, I changed mine to 1440MHz
4. Be sure that "Apply on boot" is checked at the very top of the screen.
Another user reported that changing "Interval" to 150ms and "Sync threshold" to 1440MHz help more as well. You can use these values as well at your own risk.
And, obviously, if you change anything else and your phone goes haywire, its your fault. Know what you're changing before you go and change it.
For those here who know a little bit more about these values, and others surrounding the CPU itself, I'd recommend messing with these settings to find a perfect level to wash out any touch issues for the time being.
--Update 9/7--
With more changes that I've made, I found that leaving the value for "Input Boost Core Frequency 1" at the default of 1248MHz has the same effect as changing the value. So I would suggest not changing it since that doesn't help with the issue.
What I did find that helped a little more is the "Input Interval" value being set to 200ms is slightly better than the previous 150ms value.
Here's what I have set now:
Under CPU Boost:
1. "Interval" = 200ms
2. "Sync Threshold" = disabled
3. "Input Interval" = 200ms
4. "Input Boost Frequency Core 1" = 1248MHz
I made these changes(1-4) and it made a significant difference. Thanks.
Something to add... @shbang had mention something along the lines of lowering entropy. Any dev know if it's possible or recommended with kernel auditor?
Just did this and phone seems more responsive. Will report back later. Thanks!
Does increasing the boost frequency to 1440 mhz have any adverse effect on battery drain?
Sent from my VS986 using Tapatalk
I've been using this for a couple days so far, and I wanna say that it has impacted slightly but I'm still unsure. For right now, I'm gonna give it another couple days and see.
Changing the input boost frequency value won't stick for me. It changes back immediately.
Sent from my VS986 using Tapatalk
Wow, this is fantastic. Thanks.
Doesn't really affect my battery life. Maybe a couple %. Tough to tell though.
A little (?) offtopic, but i also made some governor tweaks and also extended them by making a cpu hotplugging script.
Using these - i have nice responsive phone with some battery saving profile.
Try:
https://github.com/meneves/lg_g4_cpu_hotplug
More info at http://forum.xda-developers.com/g4/general/mod-lg-g4-cpu-hot-plugging-shell-sh-t3194702
If "Apply on boot" doesn't stick
I had an issue getting apply on boot to stick, but I believe I found a solution.
1. Follow all steps in the first post, in order.
2. Install CPU tuner (Rooted phones) https://play.google.com/store/apps/details?id=ch.amana.android.cputuner
3. Tap the icon that looks like a picnic basket with a black sqaure in front. (At the top)
4. Choose Power User, hit save.
5. If you get a message that says no usable configuration, tap load, otherwise tap the wrench.
6. Scroll down System Configurations, select extreme, or if you choose another, if you'd like. (Haven't tried the others)
7. Let the app load configuration. Then uninstall (or not)
8. Reboot
Hopefully this helps, it seems to add a bit more responsiveness for me. I only uninstalled cause it runs a service in the background, and the changes made stick on apply on boot, as long as you don't re-open Kernel Adiutor before you reboot. Weird way but it works for me, don't know what CPU tuner does to get it working.
So after you made the changes and rebooted you were able to delete the app and the settings stuck?
Big thanks and All Credits to @soniCron, @xSilas43, @kraatus90, and @Vinnom
Usual Disclaimer
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* Others and I are not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about these kernel tweaks
* before implementing them! YOU are choosing to make these modifications, and if
* you point the finger at me or other's mentioned for messing up your device, I will laugh at you.
*/
Original thread is below by @soniCron and additional tweaks by @xSilas43.
- Settings in that thread are meant for Nexus 5X and Nexus 6P but he provides a guide that should be understood thoroughly.
- Do Not Forget To Give THANKS To Both. Worked with me on understanding process and settings.
Warning: Read the original post and understand. Settings I provide further down are perfected for my use and Moto X. Further tweaking might be needed on your end.
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
---------------------------------------------------------------------------------------------------------------------------------
For Our Moto X (2nd Generation):
[Please read everything below at least TWICE]
Warning:
1. Read above "the line (-----)" if haven't already
2. Settings are CM13 based
3. Other ROM and Kernel, settings and frequencies could differ (see above linked thread for how to determine appropriate settings)
What's need
1. Root (duh!)
2. Backup up ROM using TWRP
3. Store Backup somewhere safe
4. Kernel Adiutor or similar (to change kernel settings)
5. Make changes as below (be sure to toggle "Apply on Boot" at sections used)
6. Reboot into TWRP
7. In TWRP file manager, backup and move (or delete) power.msm8974.so file. Located in system/vendor/lib/hw/power.msm8974.so or system/lib/hw/power.msm8974.so. (CM13 won't let changes like go_highspeed_load otherwise)(need to do this everytime you flash a new nightly)
8. Reboot, wait about 30s, go into Kernel Adiutor and verify settings
Settings Beta (based on @soniCron's Ghostpepper v1.1 and @xSilas43's DarkSpiceBeta)
Above_HighSpeed_Delay:50000 652800:60000 883200:20000
Go_HighSpeed_Load: 200
HiSpeed_Frequency: 300000
Min_Sample_Time: 70000
Target_Loads: 98 300000:64 422400:55 652800:12 729600:74 883200:9 960000:83 1036800:15 1190400:85 1267200:18 1497600:86 1574400:10 1728000:13 1958400:16 2265600:99 2457600:100
Timer_Rate:50000
Time_Slack:-1
io_is_busy:0
Max_Frequency_hysteresis:0
Boostpulse_duration:0
CPU Boost:
Interval- 0
Sync Threshold- Disabled
Input Interval: 0
Input Boost Frequency- Disabled for all cores (everytime reboot will have to change, it doesn't stick reboots).
I/O Scheduler- fiops (BFQ might be good (CM team keeps it updated and better for multitasking))
Read Ahead-1024kB
GPU:
Governor- simple ondemand
Click to expand...
Click to collapse
Settings 1Alpha (more aggressive than Beta)
Above_HighSpeed_Delay:50000 729600:60000 1036800:20000
Target_Loads: 98 300000:64 422400:55 652800:12 729600:21 883200:83 960000:83 1036800:15 1190400:85 1267200:18 1497600:86 1574400:10 1728000:13 1958400:16 2265600:99 2457600:100
Everything else same as Beta
Click to expand...
Click to collapse
Settings 2Alpha (more conservative than Beta)
Above_HighSpeed_Delay:50000 729600:60000 883200:20000
Target_Loads: 98 300000:64 422400:55 652800:81 729600:21 883200:9 960000:83 1036800:15 1190400:85 1267200:18 1497600:86 1574400:10 1728000:13 1958400:16 2265600:99 2457600:100
Everything else same as Beta
Click to expand...
Click to collapse
If running @kraatus90's kernel (stock ROM) try @Vinnom's setting first (http://forum.xda-developers.com/showpost.php?p=65346117&postcount=11). My settings would need modified.
Notes:
1. Still a work in progress
2. Goal is to use most power to voltage efficient frequencies, determined to be 1574400 on research elsewhere
3. Adjust as needed using guidance from @soniCron's thread linked in above section
Respond how it works. Better battery? Worse Battery? Smooth? Lag?
Improving Stationary idle drain (doze).
Big Thanks and All Credits to @p0isonra1n and @Arstoien
- Do Not Forget To Give THANKS To Both.
Usual Disclaimer
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* Others and I are not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app or other important functions failed. Please do some research
* if you have any concerns about these Doze settings
* before implementing them! YOU are choosing to make these modifications, and if
* you point the finger at me or other's mentioned for messing up your device, I will laugh at you.
*/
What's need:
1. Doze Settings Editor (http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130)
2. Knowledge of various "Doze Settings Editor" settings and flow of Doze. Helpful in fine tuning settings to you. Summarized by @Arstoien here (http://forum.xda-developers.com/showpost.php?p=63962529)
@Arstoien's recommended settings
Arstoien said:
Here's what I use (in seconds):
inactive to – 900 (15 min)
sensing to – 20
locating to – 0
location accuracy – 20.0
motion inactive to – 900 (=15 min)
idle after inactive to – 0 (after sensing and locating are passed, don't wait further)
idle pending to – 150
max idle pending to – 600
idle pending factor – 2
idle to – 1800 (=30 min)
max idle to – 21600 (=6 hrs)
idle factor – 2
min time to alarm – 900 (=15 min)
max temp app whitelist duration – 120
mms temp app whitelist duration – 60
sms temp app whitelist duration – 20
things I'd consider changing depending on usage:
inactive to – depending on how often you turn on the screen. Generally my idea is that if I haven't turned it on for 15 min, I probably won't do so again any time soon.
motion inactive to – this timeout basically does this: after the device has detected movement (either from Sensing state or from Idle), it'll wait this much before using the sensors again to check for motion. So if you move a lot, increase the value for better battery. If you don't move a lot, decrease for better battery.
idle pending to – if you have apps that sync media, or other big files, you may want to increase this. I think Titanium Backup, or other similar apps, will need much more time to do scheduled backups, so keep that in mind also. Otherwise one minute seems to be enough for most apps to do their job. You can use 2–3 minutes + a little higher max_idle_pending_to, to be on the safe side, if you're worried. I don't think it'll make that much of a difference.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64810397&postcount=954
Notes:
1. Have not had time to work on different settings yet. Using @Arstoien's recommended settings until then.
2. Will see better idle battery if tweaked to your usage tendancies. See Step 2 of "What's Need" above.
Additional
Usual Disclaimer
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* Others and I are not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app or other important functions failed. Please do some research
* if you have any concerns about these additional settings
* before implementing them! YOU are choosing to make these modifications, and if
* you point the finger at me or other's mentioned for messing up your device, I will laugh at you.
*/
Screen Calibration (remove yellow (warmness))
Thanks and All Credits to @wrinklefree (http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017)
Warning: These are meant for the Nexus 6. It shares same generation Samsung AMOLED as Moto X.
1. CM13: In Settings -- Display -- Live Display. Change Display Mode to Disable all Adjustments (possibly could leave on)
2. Kernel Adiutor -- Screen
3. Toggle Apply on Boot
4. Red to 32125
5. Green to 32125
6. Blue to 32768
Notes:
1. Still on warm side. Not as extreme as stock.
Trying now, thanks
FYI, I couldn't get to power.msm8974.so from the TWRP file manager, so I just booted up and used the CM File Manager. Had to redo the kernel settings and restart, see how it is.
jmsfang said:
Trying now, thanks
FYI, I couldn't get to power.msm8974.so from the TWRP file manager, so I just booted up and used the CM File Manager. Had to redo the kernel settings and restart, see how it is.
Click to expand...
Click to collapse
Important make sure Go_HighSpeed_Load doesn't reset to 50. It usually happens when the screen is turned off for about 10s and back on. If you removed power.msm8974.so it shouldn't reset.
Also remember Input Boost Frequency should be disabled for all cores. It needs to be set whenever you reboot. For whatever reason it doesn't stick through reboots.
Use an app like BetterBatteryStats to monitor the CPU frequencies. It will determine if there is a problem.
Thanks, I checked and everything is running accordingly
I usually use my phone for music (bluettooth speakers) and I've noticed that with this setup, google play music tends to hiccup particularly when the song is about to change. Any idea on how I can narrow that down?
jmsfang said:
Thanks, I checked and everything is running accordingly
I usually use my phone for music (bluettooth speakers) and I've noticed that with this setup, google play music tends to hiccup particularly when the song is about to change. Any idea on how I can narrow that down?
Click to expand...
Click to collapse
1. Did you change the Doze settings? If so reset back to original. See if issue persists.
2. Did you change I/O Scheduler to FIOPS? Try changing to BFQ. See if issue persists.
3. Using Kernel Adiutor. Go to frequency table and reset timing. See what the frequency is like while playing music at that spot.
4. Try changing first number in Above_HighSpeed_Delay from 50000 to 45000. See if issue persists. If issue persists try 40000. See if issue persists.
5. If does we have to modify your Target_Loads values.
Visi0nofExcellence2 said:
1. Did you change the Doze settings? If so reset back to original. See if issue persists.
2. Did you change I/O Scheduler to FIOPS? Try changing to BFQ. See if issue persists.
3. Using Kernel Adiutor. Go to frequency table and reset timing. See what the frequency is like while playing music at that spot.
4. Try changing first number in Above_HighSpeed_Delay from 50000 to 45000. See if issue persists. If issue persists try 40000. See if issue persists.
5. If does we have to modify your Target_Loads values.
Click to expand...
Click to collapse
Thank you for all the help!
I'll work through these suggestions, it'll probably take a few days to test them all thoroughly. I'll let you know what I find
Thank you again for your help!
Anyone experiencing same Bluetooth issues as @jmsfang?
Would like to verify if single or widespread issue.
Can i use it into Kraatus90's v3 kernel?
WOW man! I liked the idea of sharing our profiles here, as we can get more views and spread the word.
I'm still trying to balance better my settings, and I'm getting good performance and apparently, better battery saving (not confirmed yet, has to test more).
I'll share things here, so ppl can try other settings to, if they want.
Guys with hiccups problems, I suggest you to take a look at my profile.
Ah, I didn't test your suggestion for Doze settings yet. I'll try from now ^^
Download here
To apply my profile, just save it somewhere (lets say /sdcard/ to keep it simple), then run in terminal emulator:
su -c "sh /sdcard/profile"
Updates-
1. Updated Interactive Governor Tweaks (Beta)
2. Added additional Interactive Governor Tweaks (Alpha1 and Alpha2)
3. Added Screen Calibration Settings (http://forum.xda-developers.com/showpost.php?p=65339931&postcount=3)
4. If running Kraatus90's kernel (stock ROM) try Vinnom's setting first (http://forum.xda-developers.com/showpost.php?p=65346117&postcount=11). My settings would need modified a bit.
I forgot the Above High Speed Delays for the Alphas. Added to OP. Make corrections if used either Alpha1 or Alpha2.
Have you tried MadDog? I was actually using that config before this, I think out of all (4?) of them, that one was best for me.
jmsfang said:
Have you tried MadDog? I was actually using that config before this, I think out of all (4?) of them, that one was best for me.
Click to expand...
Click to collapse
Yes; tried all. I stopped using it couldn't tell you why. Goal is find what works best for you. My configs work best for me and aren't the end all.
I think I could balance good enough my settings.
download.
Here is what I could get:
{
"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"
}
Enviado de meu XT1097 usando Tapatalk
Vinnom said:
I think I could balance good enough my settings.
download.
Here is what I could get:
Click to expand...
Click to collapse
Your governour is just using full time full speed, because of mistakes in file.
heineken78 said:
Your governour is just using full time full speed, because of mistakes in file.
Click to expand...
Click to collapse
In fact, it wasn't using full time full speed. At least, "time in state" told me it. The most time was spent at 268 MHz, later at 1038 and later 1728 (tha max I set).
I noticed that min_freq was written wrong, fixed it, but now I can't nothing more. My phone is hard bricked and I don't know when I'll have another
This is random, srry...
Visi0nofExcellence2 said:
Updates-
1. Updated Interactive Governor Tweaks (Beta)
2. Added additional Interactive Governor Tweaks (Alpha1 and Alpha2)
3. Added Screen Calibration Settings (http://forum.xda-developers.com/showpost.php?p=65339931&postcount=3)
4. If running Kraatus90's kernel (stock ROM) try Vinnom's setting first (http://forum.xda-developers.com/showpost.php?p=65346117&postcount=11). My settings would need modified a bit.
Click to expand...
Click to collapse
Hi, I understand that you guys hav the moto x 2014, and I really feel like there is potential for these interactive settings to also help the moto x pure(2015). I hav been reading the sonicron thread and have applied the Nexus 5x eclipse profile, apparently the profile with the best battery. And it has been a alright not that great really, but can you guys help me what interactive values are best for the new moto x, I am trying hard to understand, but I don't know, thanks a lot..
harshi1 said:
Hi, I understand that you guys hav the moto x 2014, and I really feel like there is potential for these interactive settings to also help the moto x pure(2015). I hav been reading the sonicron thread and have applied the Nexus 5x eclipse profile, apparently the profile with the best battery. And it has been a alright not that great really, but can you guys help me what interactive values are best for the new moto x, I am trying hard to understand, but I don't know, thanks a lot..
Click to expand...
Click to collapse
Moto X Pure (2015) uses Snapdragon 808, same chip as Nexus 5x. We do not have that chip, it is hard to help. Try original Nexus 5x thread.