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

[app] (update 31/07, v 0.0.4.1) avsMon for thalamus kernel / Oxygen 2

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.

[ROM][AOSP] 4.0.4 ICS | Evervolv | 2.2.0b1 | 5/20/12

This ROM is built from source and is incorporated s custom Evervolv look and feel to the stock ICS experience. This started as a collaborative effort to port ICS to the eris, heroc, and hero. We will continue to work together to try and get the best functionality, speed, and enjoyment possible. I've had a lot of fun working on ICS since source was released back in November and it's been great to work with many other devs across a multitude of devices and backgrounds.
A ton of credit for how functional this ROM is must go to jaybob413 who always amazes me with both his ability to fix anything & everything, and also his willingness to share, teach, & work together. We all know workshed of course who has given me lots of help & advice, not to mention that GSB is what got me into messing around with ROMs. Then there's the master of all that is Evervolv, preludedrew. When not sabotaging my builds or giving me a hard time, he puts up with my questions and has taught me a lot along the way. Many thanks to those that open source their work and fixes like CyanogenMod and plenty of others. And now on to what you are here for...ICS on the Eris.
--------
* Downloads *
You flash this BETA build at your own risk! Be sure to make a nand backup and do a full wipe before flashing. The first boot takes awhile so give it some time.
ROM - 2.2.0b1
MD5sum: 3b2e097212eec7187f32109846c3fad8
Gapps are NOT included so be sure to flash this zip if you want them!
GAPPS - 5.20
MD5sum: fba8c84a2f370cd2c47743465c51731b
--------
WIP 2.6.35 kernel - Optional for those that want to try it out
Flashable zip
List of known Issues: here
--------
Keep in mind that this is a WIP so not everything will be completely stable or working perfectly. Progress is being made though...
Working
touchscreen
physical & capacitive buttons
data
sms & mms
camera - pictures
built-in screenshot feature
wifi
gps
calls
audio
microphone
sdcard
usb mass storage
sensors
vibration
trackball navigation, selection, light
notification / charging LED
Not Working
camera - video & panorama modes
bluetooth(still can't figure out why)
wallpapers - offset from center
wifi signal strength icon display
gpu hw acceleration / opengl
mic mute in call
google music app
voice search app
Click to expand...
Click to collapse
Changelog
2.2.0 Beta 1:
* Coming Soon...
2.1.0 Beta 2:
* ability to take pics with camera but no preview and loads slowly(rapmv78, zbwu86, CAF)
* browser/gmail/etc fixed (arcee)
* revamped notification toolbox - new layout, use EVToolbox app to select widgets/# per row/default on pulldown (settings icon switches views, long-press to enter settings app)
* fixed bug where selecting silent in power popup menu(on long-press) first went to vibrate instead
* fixed signal strength reporting in Settings->About phone->Status
* other misc fixes/tweaks/options
2.1.0 Beta 1:
* AOSP 4.0.3 source
* full audio (jaybob413)
* usb mass storage
* trackball functionality
* cache2cache updated and included
* notification toolbox - cycle through notifs/widgets/media/batt by pressing settings icon(long-press for settings)
* EVToolbox app - lockscreen(style, custom mapping), choose notif toolbox widgets, 6bar/stock signal strength icon toggle, vol btn lockscreen music control toggle, vol btn wake toggle
* initial launcher settings(press menu while on home screen) - Homescreen->search bar toggle, other options are just placeholders for now
* latest gapps, terminal emulator, file expert, quickpic, and opera mini included in ROM
* misc fixes/improvements
Alpha 5 / Preview 2:
* working gps
* fixed some background crashes of libdvm (jaybob413)
* bluetooth now turns on and "sees" devices but I was unable to pair successfully
* hot reboot added to reboot options menu
* now includes the optimized galaxy nexus boot animation (workshed & snowjumpstump)
* added terminal emulator app to build
* replaced stock gallery app with quickpic for the time being
* updated maps to v6.0.1 in the tiny gapps zip
Alpha 4 / Preview 1:
* fixed keyboard prediction - english only for now
* fixed keyboard layout so bottom row is no longer cut off (jaybob413)
* mic works after a delay of 2 - 10s
* audio: speaker plays stereo sounds only, at times has a delay, and sometimes too quietly
* reboot options added: recovery, bootloader, normal
* File Expert app included
* built with most apps/framework in ODEX format
Alpha 3.5:
* fixed touchscreen for the older melfas type
* fixed wifi
* fixed sdcard mounting
* fixed sensors
Alpha 3:
* button mapping fixed (no more needing adb to reboot!)
* added ICS gapps base & ICS gmail
* added superuser app and su binary for root privileges
* disabled flashing red border(visual StrictMode)
* removed a few uneeded/incompatible apps along with foreign fonts & tts to save space on /system
Alpha 2:
* touchscreen fixed(synaptics only)
Click to expand...
Click to collapse
--------
* Recommended Flashing Instructions *
1 - full wipe: data + cache + dalvik cache
2 - flash the ROM zip
3 - flash Gapps
4 - reboot: the first boot will take awhile
5 - ensure everything is loaded and settled by letting the screen timeout and waiting a minute or so before waking it up and proceeding
6 - skip or go through the google setup wizard and then wait another couple mintes to allow the rest of the ROM to load up and any google data to sync
7 - reboot and allow things to load up again (optional)
8 - everything should now be ready to go
--------
* Tips *
* switching between the Evervolv notification toolbox and the stock notification view is achieved by swiping either left or right
* can open a running apps list by long-pressing the home button & swipe(or long-press) to clear (useful if an app won't open or system slows down to clear out some memory)
* disabling an app is very easy in ICS: either through the manage app screen or by dragging a particular app from the drawer to the "app info" section displayed at the top of the screen, you'll find a button to disable that app
* the ICS launcher makes it simple to create & use folders: just drag one icon on top of another, let go, and they will now be in a folder together which you can name whatever you like
--------
* Sources *
Evervolv: GitHub & Gerrit
Conap's Kernel: GitHub
WIP 2.6.35 Kernel: GitHub

Screenshots
A video showing off the touchscreen in alpha2 thanks to workshed:
These screenshots are of the first alpha where the touchscreen was acting like a trackpad/pointer:
{
"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"
}

* reserved *

Just wanted to say thanks for your work and time working on this, awesome job!

Congrats on being the first to make an ICS rom on the eris, MH!!

Congrats lix! Nice work my man, I'm proud of you. (I know that sounds stupid, but I am) please feel free to contact me, I'm sure I could help with some of the button mapping. Maybe we could team up some, just msg me if you're down, no worries if not.
You can email or add me to gtalk, anyone can! [email protected]
p.s. the email address is a long story lmao
Again, good work Mon! (I can't figure out what I want to call you in short) lix or mon hahaha

This is sexy!

Awesome work goose ! Congrats bro
Sent from my ADR6300 using xda premium

great work bro,, i have one aso,, just trying to fix a few things,,sounds like ut haven the same issues

Good ol' Eris. What a trooper.

Way to go, Mongoose (and the crew)! Thanks for your development effort!

Awesome, not sure if I want to wait until this is more stable or not to play around with it, probably once the buttons are mapped I'll play with this

one word. simply awesome. this is why my eris remains in use as my bedside clock/mp3 player. it just never seems to give up thanks to the amazing developers we have here.

Thanks. Something to really look forward. keep it G

Knowing how far this device has come and being here since day one of the launch, all I have to say is holy ****, pardon my language

Just wondering if anyone has given this a spin yet or maybe everyone's waiting until it's more functional which makes sense

MongooseHelix said:
Just wondering if anyone has given this a spin yet or maybe everyone's waiting until it's more functional which makes sense
Click to expand...
Click to collapse
i plan to give it a spin soon

This is unbelievable. I upgraded from the good ol' Eris a few months ago, and the progress on this far surpasses Thunderbolt development. It's a shame really, that development on the tbolt is so fragmented.
I still keep my Eris around just to load up projects like these, and marvel at how far it has come. It's a long way from the Cupcake that it launched with.

i havent released my ics rom yet and not sure if this one has the ics boot ani i noticed some dont have it so here it is
http://www.multiupload.com/KQIKUWS75U
also if i read this thread right, the screen goes black and doesnt turn back on without battery pull,,,,try pluggin usb cord in if not then unpluggg it should turn back on

Just incase anyone's curious about gapps with this; tried yesterday, no worky! Touch screen doesn't work to run the setup... in all, though, killer job mongoose!

AK Kernel Profile - Synapse

As the title suggests, this thread is for people to post their profiles with each other in an effort to not clog up the development thread. Synapse is a great tool with a ton of variations. Feel free to share what worked and what didn't.

jlevy73 said:
As the title suggests, this thread is for people to post their profiles with each other in an effort to not clog up the development thread. Synapse is a great tool with a ton of variations. Feel free to share what worked and what didn't.
Click to expand...
Click to collapse
now that's a good and wise idea
hope that Profile Save/Restore gets fixed for Synapse and we'll find here some interesting presets to test on from more experienced users
Thanks

I'll just list the things that I changed. Cause Synapse won't let me save profiles. Heard it's still being worked on So that's good news
CPU max frequency - 1574MHz
CPU Governor - interactive_pro
Intelliplug enabled with performance profile active. CPU max screen off at 729MHz. No undervolting yet
I/O -ROW with 1024 KB read-ahead.
Laptop mode enabled
There's way more stuff to tune and I'll play around with them when I have more time which will be in a week
I tried 1.2 GHz for a day and it was still smooth even on Facebook which is quite a surprise
{
"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"
}
Screenshot proves it all.
Cheers everyone and lets light up this thread with profiles and all
Sent from a Device codenamed Bacon!

funCrash93 said:
now that's a good and wise idea
hope that Profile Save/Restore gets fixed for Synapse and we'll find here some interesting presets to test on from more experienced users
Thanks
Click to expand...
Click to collapse
For me works like a charm...
Select your Profile then on the top press the checkmark. Then press the "Resore Selected Profile" Button. Now you will get a Toast with success loaded and "Restart Synapse".

Test was done with - CrDroid 5.5 ART.
CPU max frequency - 1574MHz
COU Multicore - Agressive
CPU Governor - Smartmax_eps
Intelliplug enabled with balanced profile active. CPU max screen off at 729MHz. 50 mV undervolting +-
I/O -Deadline with 1024 KB read-ahead.
GPU - 389MHz with Conservative
Laptop mode enabled
TCP Congestion - hybla
Fist half of the day, was heavy usage (playing Leo's Fortune), however I noticed a slighty higher battery drain, when my phone got hot (at earpiece, back&front) after 2hours +- ?.
Anyway, school day was over & I went home and did the usual light stuff, checking Facebook, Snapchat, writing messages on phone and over MightyText.
I'm satisfied so far. Going to try the interactive_pro next.
Idle: 5-7mV

now running @sien1996 's profile (except Max Screen Off Freq. : haven't set that one)
so far ok, will update later w/ Gaming Experience

Where can I find intelliplug option? I only see mpdecision under hotplug...

Chaplan said:
Where can I find intelliplug option? I only see mpdecision under hotplug...
Click to expand...
Click to collapse
It's in the hotplug tab right under mpdecision

sien1996 said:
It's in the hotplug tab right under mpdecision
Click to expand...
Click to collapse
Can't find it... Really can't. Does it say intelliplug?

Chaplan said:
Can't find it... Really can't. Does it say intelliplug?
Click to expand...
Click to collapse
Yeah. It's the one with the 'balanced' 'eco-performance' stuff. And the hysteris value and touch boost stuff. Don't even need to scroll, it's right there when you click hotplug.

Where can I find the Laptop mode option?

depends
Chaplan said:
Can't find it... Really can't. Does it say intelliplug?
Click to expand...
Click to collapse
sien1996 said:
Yeah. It's the one with the 'balanced' 'eco-performance' stuff. And the hysteris value and touch boost stuff. Don't even need to scroll, it's right there when you click hotplug.
Click to expand...
Click to collapse
i'm using synapse on several devices and kernels and thus have to bring to your attention that what you see there depends on the kernel while the kernel you can use and it's tunables depend partly on the device. that's one of the goals of synapse that it adapts to the available tunables, depending.
so i would suggest that you (finally) mention your config, kernel (probably AK ) and device and perhaps post a screenshot of the hotplug tab so we can see what's there and not and help further.
http://forum.xda-developers.com/attachment.php?attachmentid=2912743&stc=1&d=1409049574

Nexus 5 with uber sabermod faux...

that's it
Chaplan said:
Nexus 5 with uber sabermod faux...
Click to expand...
Click to collapse
looks like if this config simply does not provide the option to use intelliplug.
most people here are using AK-Kernel on OnePlus One so this config is not widely spread and thus, including myself, i cannot
not provide you with a lot of quality input but certainly you do not have that option. i think (read somethin in git) @ak will
sooner or later make a kernel for the hammerhead, perhaps @ak you would confirm or deny this assumption quickly
however, if that will be the case i recommend to use that kernel or elementalX which i'm currently using on my Nexus 5, which i'm using for 9 months now
with a few never lasting sidesteps to try others. by the way came from franco in late november 2013.

Faux sound problem for UKM is fixed ... Now all work like a champ ... And its free [emoji7][emoji7][emoji7][emoji7]
[email protected]

ak said:
Faux sound problem for UKM is fixed ... Now all work like a champ ... And its free [emoji7][emoji7][emoji7][emoji7]
[email protected]
Click to expand...
Click to collapse
How do I enable faux sound? Or is it already done?
Sent from my A0001 using Tapatalk

cashyftw said:
How do I enable faux sound? Or is it already done?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Enabled under sound tab.
[email protected]

best i found for touch response
this profile is the best i found till now "WIP" to optimize the lack of responsiveness of the touchscreen, especially when double tapping to wake but in general as well.
battery consumption with these settings is around 2% in 9h 30' in idle, SOT is around 7h ( +/-30' ) depending on apps and radios mostly used.
as usual battery performance is relative to config, usage, radio signals etc. so the above serves as a clue. only tells what happens on my device.
[URL="https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0"]https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0
[/URL]
IMPORTANT NOTICE:
In the process of copying profile files from Dropbox and probably from other sources it occurs that the file name is changed to xxxx.tgz.gtar while to correct name MUST be xxxx.tgz, in this case that would be 888.tgz. if the file does not have this correct name before you try to restore it in synapse it will say: Invalid File further you have to check the "√" sign on top each time it appears, while upon restarting the app "Synapse" which you have to do from within the app not closing and re-opening the app. when the app has opened you have to non-intuitively hit "X" not "√"

magnamentis said:
this profile is the best i found till now "WIP" to optimize the lack of responsiveness of the touchscreen, especially when double tapping to wake but in general as well.
battery consumption with these settings is around 2% in 9h 30' in idle, SOT is around 7h ( +/-30' ) depending on apps and radios mostly used.
as usual battery performance is relative to config, usage, radio signals etc. so the above serves as a clue. only tells what happens on my device.
https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0
IMPORTANT NOTICE:
In the process of copying profile files from Dropbox and probably from other sources it occurs that the file name is changed to xxxx.tgz.gtar while to correct name MUST be xxxx.tgz, in this case that would be 888.tgz. if the file does not have this correct name before you try to restore it in synapse it will say: Invalid File further you have to check the "√" sign on top each time it appears, while upon restarting the app "Synapse" which you have to do from within the app not closing and re-opening the app. when the app has opened you have to non-intuitively hit "X" not "√"
Click to expand...
Click to collapse
Thanks, will give this a try with the new 0.33 build that just got posted.

magnamentis said:
this profile is the best i found till now "WIP" to optimize the lack of responsiveness of the touchscreen, especially when double tapping to wake but in general as well.
battery consumption with these settings is around 2% in 9h 30' in idle, SOT is around 7h ( +/-30' ) depending on apps and radios mostly used.
as usual battery performance is relative to config, usage, radio signals etc. so the above serves as a clue. only tells what happens on my device.
https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0
IMPORTANT NOTICE:
In the process of copying profile files from Dropbox and probably from other sources it occurs that the file name is changed to xxxx.tgz.gtar while to correct name MUST be xxxx.tgz, in this case that would be 888.tgz. if the file does not have this correct name before you try to restore it in synapse it will say: Invalid File further you have to check the "√" sign on top each time it appears, while upon restarting the app "Synapse" which you have to do from within the app not closing and re-opening the app. when the app has opened you have to non-intuitively hit "X" not "√"
Click to expand...
Click to collapse
Running this profile now, downloaded properly without the need to change the file name. Proper feedback soon.
Oneplus one/PA 4.5 beta 3/AK

[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