Database Users

SetCpu guide on how to use

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

[Q] SetCpu - Yellow Screen - possible?

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

imilka GNote ICS AOSP Bug Repport

I can't post in the development section that's why I poste here.
This is my bug repport for the wonderfull "imilka's AOSP ICS v05"
Sorry for my english, I'm french.
First of all I'de like to thank imilka for is greate work.
Bug list :
-Google wallet should not be present on the Note
I think, (no NFC).
-In the setting, "Status bar toggles" menu is in english while the reste of my phone is in french.
-In the status bar toggles when you set an odd number of options, the switch of the last option is on the right while the icon is on the left.
-In the camera, the panoramic mode does not fit all the screen.
-The processor settings is in english and the Max CPU frequency is set to 1200Mhz while it should be 1400Mhz for the Note (Am I right?)
-The voice recognition is half in english, half in french (in my case) like "open état du téléphone".
That's all for now.

sp_setsuna said:
-The processor settings is in english and the Max CPU frequency is set to 1200Mhz while it should be 1400Mhz for the Note (Am I right?)
Click to expand...
Click to collapse
base rom is the leaked chinese ics which set the max cpu at 1200Mhz

Kindle app doesn't work. When launching any book from within the app it crashes. Imilka is aware of this and will be fixing it once all the important bugs are squashed. Worth mentioning though as this might be a deal-breaker for some looking for a rom.

New possible fix for touchscreen issues (All variants) [Updated 9/7]

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?

[GUIDE] [Osprey] Advanced Interactive Governor Tweaks

Any information in this thread is based on @soniCron's guide here. If anyone would like more information on how exactly this works, head over there.
Introduction
After having read through all of soniCron's posts, I was really impressed and I wanted to test if for myself, but I do not have either a Nexus 6P of a Nexus 5X. I do however have a Moto G 2015, and since instructions were provided to apply his technique on other devices, I decided to give it a go. So after quite a bit of testing and calculating, I have been able to come up with some tweaks for our little phone. Now, I have not yet fully tested the battery life with these tweaks. I feel like they will work though, and so far, performance has been better than before and according to some frequency tables, the frequencies are staying lower.
Some more details
These tweaks should work on any ROM and/or kernel. However, there seem to be issues with the stock ROM, where either the target_loads and/or the above_hispeed_delay are not sticking. Please test for yourself. For a list of confirmed working ROMs, check below.
Your phone must be rooted. If you are not sure how to do this, check this guide.
With this out of the way, we can finally start with some numbers. In accordance with soniCron's thread, I have started with calculating the nominal (minimum required to do anything smoothly) clock rates for scrolling, watching video and loading apps. These clock rates were calculated using the performance governor, limiting the maximum clock speeds while performing a given task. These are only my observations and yours may vary depending on your settings and how well you have optimised your system and browser etc. Be sure to check if the clock rates are similar to those that you need to run the given task smoothly, you should be good to go.
For idle, I observed a nominal clock rate of 400000 MHz.
For scrolling, I observed a nominal clock rate of 998400 MHz.
For video watching, I observed a nominal clock rate of 1094400 MHz.
And finally, for app loading, I observed a nominal clock rate of 1209600 MHz.
With these values in mind, I then proceeded to calculating the maximum and minimum loads that were most efficient. (For more details, please see soniCron's thread)
Here they are:
200000:1
400000:68
533333:50
800000:25
998400:82
1094400:86
1152000:10
1209600:80
These values are essentially the target_loads the kernel looks for. I have also applied some other miscellaneous tweaks for the governor which all helped with performance while keeping battery life. Now, without further ado, I present you:
What you need to do (on Custom ROMs)
1) Make sure you are rooted and have Busybox installed.
2) Download a kernel manager app. There are loads of these in the play store, but I personally recommend this one.
3) Pop the following values in at the 'governor tunables' section, making sure you have the interactive governor selected.
above_hispeed_delay 20000 400000:60000 998400:30000
boostpulse_duration 80000
go_hispeed_load 99
hispeed_freq 1363200
max_freg_hysteresis 60000
min_sample_time 60000
target_loads 98 400000:68 533333:50 800000:25 998400:82 1094400:86 1152000:10 1209600:90
timer_rate 35000
timer_slack 80000
align_windows 1
4) TURN OFF TOUCH BOOST
5) (OPTIONAL) apply the other tweaks listed here
6) Make sure it's working correctly. Check if everything keeps running smoothly. If it doesn't, optimize your device more, or increase the min_sample_time by increments of 5000. If your CPU is going over the Idle speed often, adjust the timer_rate upwards by increments of 5000. If it stays at the Idle speed too much, adjust it downwards by increments of 5000.
7) ENJOY!
What you need to do (on Stock ROM)[Hit or miss for some]
1) Make sure you are rooted and have Busybox installed.
2) Download a kernel manager app. There are loads of these in the play store, but I personally recommend this one.
3) Pop the following values in at the 'governor tunables' section, making sure you have the interactive governor selected.
above_hispeed_delay 20000 400000:60000 998400:30000
boostpulse_duration 80000
go_hispeed_load 90
hispeed_freq 1363200
max_freg_hysteresis 60000
min_sample_time 60000
target_loads98 400000:68 533333:50 800000:25 998400:82 1094400:86 1152000:10 1209600:90 [These are not sticking for some, though we are looking for help as you read]
timer_rate 40000
timer_slack 80000
align_windows 1
4) TURN OFF TOUCH BOOST
5) (OPTIONAL) apply the other tweaks listed here
6) Make sure it's working correctly. Check if everything keeps running smoothly. If it doesn't, optimize your device more, or increase the min_sample_time by increments of 5000. If your CPU is going over the Idle speed often, adjust the timer_rate upwards by increments of 10000. If it stays at the Idle speed too much, adjust it downwards by increments of 10000.
7) ENJOY!
Conclusion
I have had lots of fun with observing and calculating the optimal speeds and settings. I hope these tweaks will help someone and if they do, please let everyone know by leaving a post in this thread. Good luck!
Thanks to:
@soniCron for making his amazing guide
@squid2 for making the kernel that inspired me to make this guide
@abhijeetc9762 for making the rooting guide
@==vj== for making the other tweaks-guide
@Tel864, @FalKoopa, @..::Matr!x::.. , @JackTheRipper1891, @hekomat, @mihaum and more for testing
Tested working on
Squid kernel
crDroid 6.0.1
DominionOS 6.0.1
X-Infinity kernel
crDroid 6.0.1
DominionOS 6.0.1
Stock kernel
crDroid 6.0.1
Resurrection Remix 6.0.1
DominionOS 6.0.1
Optimus kernel
crDroid 6.0.1

Trying out these settings for a while, but it definitely seems more responsive. Maybe that's just a placebo, though.

sticktornado said:
Trying out these settings for a while, but it definitely seems more responsive. Maybe that's just a placebo, though.
Click to expand...
Click to collapse
Great to see they seem to be working for you! Could you please let me know which ROM and/or Kernel you're using? I could use that information to make a 'working' or 'tested' list.

TVD1903 said:
Great to see they seem to be working for you! Could you please let me know which ROM and/or Kernel you're using? I could use that information to make a 'working' or 'tested' list.
Click to expand...
Click to collapse
I'm using the stock 6.0 ROM with Squid's Kernel, revision 14b. If it also helps, I'm on the 1GB version of XT1540.

With my XT1540 1gb on 6.0 and the stock kernel, the responsiveness seems better. I'm going to run it a day to check battery and if that's ok, I'll apply these settings on boot.
One question...on the target load settings I'm seeing a space between 400000: and 68. All the other values don't have a space after the colon so I assumed this one shouldn't either.

me also testing.... xt1541 2gb with stock 5.1.1 rom and squid kernel
for now with those settings and intelligplug enabled (hotplug driver) everything seems little bit smoother than before ... now testing battery....
from what i can see in kernel adiutor>>frequencies tab: some intermediate frequencies are disabled/unused....(533mhz, 800mhz, 1152mhz)... before only 200mhz was unused 'cause min freq was set to 400mhz....
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
Tel864 said:
With my XT1540 1gb on 6.0 and the stock kernel, the responsiveness seems better. I'm going to run it a day to check battery and if that's ok, I'll apply these settings on boot.
One question...on the target load settings I'm seeing a space between 400000: and 68. All the other values don't have a space after the colon so I assumed this one shouldn't either.
Click to expand...
Click to collapse
no space between 400000:68

Tel864 said:
One question...on the target load settings I'm seeing a space between 400000: and 68. All the other values don't have a space after the colon so I assumed this one shouldn't either.
Click to expand...
Click to collapse
Oh shoot! You're right on that, it's just a typo. Thanks for letting me know!
..::Matr!x::.. said:
me also testing.... xt1541 2gb with stock 5.1.1 rom and squid kernel
for now with those settings and intelligplug enabled (hotplug driver) everything seems little bit smoother than before ... now testing battery....
from what i can see in kernel adiutor>>frequencies tab: some intermediate frequencies are disabled/unused....(533mhz, 800mhz, 1152mhz)... before only 200mhz was unused 'cause min freq was set to 400mhz....
Click to expand...
Click to collapse
Yes, that is exactly the behavior we want to see. We don't like those frequencies because they are not the most efficient to be running at. The governor is now set to quickly scale up to the frequency we need to do a certain thing (browsing, app loading etc.). If you wanted to be running at those frequencies more, you could up the target_loads on them, but I do not recommend that.

Ok, this is strange, my target load settings aren't sticking. I've put them in twice and after a few minutes, that setting reverts back to 80. I can put them in, exit Kernel Adiutor and come right back and they're there. If I wait a little while and go back, they're gone.
XT1540 1gb
Stock rom
Marshmallow 6.0
Sent from my SM-T530NU using Tapatalk

Tel864 said:
Ok, this is strange, my target load settings aren't sticking. I've put them in twice and after a few minutes, that setting reverts back to 80. I can put them in, exit Kernel Adiutor and come right back and they're there. If I wait a little while and go back, they're gone.
XT1540 1gb
Stock rom
Marshmallow 6.0
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
Hmm that is odd indeed. Could you flash a custom kernel and try again?

TVD1903 said:
Hmm that is odd indeed. Could you flash a custom kernel and try again?
Click to expand...
Click to collapse
I'm going to have to wait on that, I'm on a soak test for a couple of apps so I need to stay stock kernel for now. For grins, I'm going to try another kernel app though I doubt that's it.
I just noticed that Greenify was closing Kernel Adiutor in the background. Although that wasn't affecting the other settings, I'm going to stop that and see if it works.

My target load settings aren't sticking either, I'm on stock 5.1.1. rom, stock kernel, also using Kernel Adiutor.

hekomat said:
My target load settings aren't sticking either, I'm on stock 5.1.1. rom, stock kernel, also using Kernel Adiutor.
Click to expand...
Click to collapse
It must be something with the stock, since you're on Lollipop and I'm on Marshmallow.

Okay. Thank you all for testing. I will add a message to the OP saying it doesn't work with the combination of stock Moto kernel and ROM. I'm not entirely sure why this is happening, but I feel it might be because of the hotplug. We can be sure that it is not due to the stock ROM, right? Someone's tested it on stock with Squid Kernel.

@TVD1903, I've just tried setting it on stock 5.1.1 with Squid kernel, and target loads won't save.

Welp. There must be something with the Stock ROM that's preventing us from changing the governor settings. It does work here, on crDroid. I do not have the technological knowledge to fix this issue to be fair. If there is any dev reading this, could you please let us know what the problem is?

here with stock 5.1.1 rom, squid kernel and kernel adiutor app everything working....
{
"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"
}

@..::Matr!x::.., does the setting stick? Try rebooting.

mihaum said:
@..::Matr!x::.., does the setting stick? Try rebooting.
Click to expand...
Click to collapse
yes... i'm 2 days with this setting... check in kernel adiutor >> cpu >> apply at boot

I have checked apply at boot, nevertheless taget_loads won't be saved. What is your device (i.e. XT1541)?

mihaum said:
I have checked apply at boot, nevertheless taget_loads won't be saved. What is your device (i.e. XT1541)?
Click to expand...
Click to collapse
xt1541 2gb
... try pasting this code linear in target_load...
Code:
98 400000:68 533333:50 800000:25 998400:82 1094400:86 1152000:10 1209600:90