Develop Bugs

How do I use SetCPU?

Probably a dumb question from a noob,
But nonetheless a vital one.
I recently rooted my DHD and installed SetCPU - but what next? Do I set the overclock and undervolt values myself, or are they already set?
Sorry that this seems to stupid and trivial, but at the moment I'm not sure if it's actually DOING anything.
Thanks in advance!

You have to use a custom kernel if you want to OC your phone because HTCs stock kernels uave a 'feature' called Perf Lock which doesn't allow you to OC your phone.( underclocking should work, tho)
With custom kernels you can OC up to 2ghz (depends on which kernel you use).
Sent from my Desire HD using Tapatalk

How would I underclock then? I really only downloaded it to save myself battery - I just don't want to stuff anything up.

1) Make sure you enable "set on boot"
2) Under profile tab, enable it and then customize the profile.
For maximizing the battery, I'm currently using this profile. Start from there and personalize it.
charging
- 1152 max
- 307 min
- performance
- priority 100
screen off
- 460 max
- 307 min
- conservative
- priority 90
temp > 35
- 460 max
- 307 min
- smartass
- priority 80
battery <25
- 537 max
- 230 min
- smartass
- priority 70
battery < 50
- 768 max
- 230 min
- smartass
- priority 60
battery <75
- 921 max
- 230 min
- smartass
- priority 50

noodlesfordaddy said:
How would I underclock then? I really only downloaded it to save myself battery - I just don't want to stuff anything up.
Click to expand...
Click to collapse
Same way you over-clock with ONE minor difference... That's right, you lower the numbers!
Create profiles similar to post above but I would put screen off as top priority otherwise if it's plugged in and screen off, especially with performance setting, it will sit there at high clocks when it doesn't need to.
Out of curiosity, when you looked at the setcpu threads, what about them was in any way unclear? Let me know and I'll see if we can get them edited.

vsel values for cm9/cm10

Can we get a thread together for battery values. I am looking to maximize my battery life and wanted to know what governor values to set for cm9 particularly
Format of the thread should be
battery uptime: 22 hours per charge
main usage: wifi/music/email vs heavy data useage
vsel values
1. 33 300
2. 48 600
3. 58 800
Why is it even in the bootloader when I set VSEL 4 that the max CPU in the CM10 menu is set to VSEL3? How can I enable VSEL 4?

zetsui said:
Why is it even in the bootloader when I set VSEL 4 that the max CPU in the CM10 menu is set to VSEL3? How can I enable VSEL 4?
Click to expand...
Click to collapse
This doesn't need to be in the development forum. But to answer your question, utilizing CLK 4/VSEL 4 requires the GB kernel.

zetsui said:
Can we get a thread together for battery values. I am looking to maximize my battery life and wanted to know what governor values to set for cm9 particularly
Format of the thread should be
battery uptime: 22 hours per charge
main usage: wifi/music/email vs heavy data useage
vsel values
1. 33 300
2. 48 600
3. 58 800
Why is it even in the bootloader when I set VSEL 4 that the max CPU in the CM10 menu is set to VSEL3? How can I enable VSEL 4?
Click to expand...
Click to collapse
My settings for all roms. I get usually get 24 hours plus no matter what rom I use, and that's with using live wallpapers as well. The only time I get less is when I'm using a ton of bandwidth online or playing games. I get better battery with the values in parentheses since 700mhz handles mid lever activity much better than stock 600mhz and doesn't need to jump up to vsel3 near as much.
1. [email protected] (or 18)
2. [email protected] (or [email protected])
3. [email protected] (or [email protected])
Governor is Boosted (You can also mirror these settings with Smartass or SmartassV2 -preferred- for similar results)
Settings Are:
bst_awake_ideal_freq 600000 or 700000 (whatever vsel2 is set at)
bst_debug_mask 0
bst_down_rate_us 60000
bst_max_cpu_load 88
bst_min_cpu_load 40
bst_ramp_down_step 300000
bst_ramp_up_step 150000
bst_sample_rate_jiffies 2
bst_sleep_ideal_freq 300000 (whatever vsel1 is)
bst_sleep_wakeup_freq 300000 (whatever vsel1 is)
bst_up_rate_us 80000
You can also get good battery with conservative with these values. If you get lag, either deal with it or lower con_up_threshold. If you don't mind slight lag, the set con_up_threshold to 100.
con_up_threshold 95
con_down_threshold 40
con_freq_step 8
con_sampling_rate 160000
You can't use vsel4 since that requires a gingerbread kernel, which requires you to be on a Defy; preferably a red lens so you can use the camera. Motorola never updated the Bravo past Froyo, so were stuck with the Froyo kernel and all the limitations because of that.

syllogyking said:
This doesn't need to be in the development forum. But to answer your question, utilizing CLK 4/VSEL 4 requires the GB kernel.
Click to expand...
Click to collapse
Completely missed that post yesterday....There already is a vsel\cpu governor thread for the Bravo here. You'll notice my settings have changed quite a bit from that post\thread, but the roms have gotten better so they work better with lower vsels now. I was in a hurry and didn't even think of linking to the other thread

Check this out http://androidunderground.blogspot.com.ar/2011/05/setvsel-overclock-and-undervolt-your.html

BravoMotorola said:
Check this out http://androidunderground.blogspot.com.ar/2011/05/setvsel-overclock-and-undervolt-your.html
Click to expand...
Click to collapse
Good link for the newbs. My only issue with it is I've never had good vsel2 time with ondemand's stock 86 threshold value. That may be due to the page being written for Eclair and Froyo Defy while I've done most of my tests on CM7, a few on CM9, and a few on GB MIUI.
With minor\no tweaking, anything is better than ondemand 86 to save battery life. IMHO it goes boosted\smartassV2 > conservative > interactive > everything else. Those 4 governors are the only one's I'd bother with since they work (no bugs; smartass), have noticeable changes in behavior when tweaked, and can be tuned to use vsel2 more than 3. Also, boosted/smartassV2 are based on both conservative and interactive and take features from both.

Overclocking Instability

Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?

some CPUs have a higher tolerance than others for overclocking. looks like you got one of the super low tolerance ones.

I hope that's not the case :-/

brando56894 said:
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
Click to expand...
Click to collapse
you need to disable smart reflex mpu if you want to overclock. smart reflex doesnt know overclocking, so it sets your voltages to low for an overclocked cpu. thus, instant instability.
to disable smart reflex manually, use a terminal emulator. type su(press enter) then type these 3 lines and press enter after each..
*
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
0 to disable, 1 to enable.
btw, some cpu control apps give you options to disable/enable smart reflex.

What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.

the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that

brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
Click to expand...
Click to collapse
The 3 lines would be:
Code:
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_core/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_iva/autocomp
Frankly, though, don't expect 1.8GHz to be stable.

Your particular device's components might not hold it together with that oc.
Sent from my i9250

Darunion said:
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
Click to expand...
Click to collapse
Yea I know (I used to OC the CPU on my PC), I just wanted to go for something big to see if it could handle it.
Edit: seems to be stable at 1.4 GHz, I'm going to keep increasing it to see what the limit is. I'm assuming i'd have to turn off smartreflex on each boot so I should probably put it in a script in /etc/init.d correct?

brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
Click to expand...
Click to collapse
the trinity kernel toolbox lets you disable/enable smart reflex. plus, extremely few gnex will oc to 1.8ghz. and on top of that, to oc even to 1.4 or 1.5ghz, youll need to adjust your voltages to get yourself stable. every device likes different voltages.

I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
i can oc my gnex(using trinity kernel) to 1.803ghz.. but to use stable for every day, 1.689ghz is a good speed for my device. a majority of devices wont even oc that high and stable. stable being the key word.

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
Is she impressed by your turbo-nerd status?! :silly:

Haha she was an iSheep but I made her get an SGS3 and I turned her into an Android geek, now she flashes ROMs on her own lol
Cilraaz said:
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
Click to expand...
Click to collapse
Yea it wasn't stable in the true sense of the word, I meant it just didn't freeze every minute or so.
Sent from my Galaxy Nexus using Tapatalk 2

I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.

brando56894 said:
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
Click to expand...
Click to collapse
dont use PA cpu settings. do you have any other cpu control apps installed? make sure theres nothing enabled in PA cpu settings, nothing. then reboot. wait 2-3 after bootup then open tkt and try using it. is the problem still there?

It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.

brando56894 said:
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
Click to expand...
Click to collapse
sweet.
if you were checking before 3 minutes after bootup, then that was the issue. whatever it was, lets hope it doesnt come back.

I was setting the values after the phone had been up for hours, idk what the problem was :-\q

[KERNEL][AOSP4.4/5.1/6.0/7.1] dkp - d2tmo - 2/4/18

Welcome to decimalman's kernel playground!​
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.

Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.

Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode

Look promising

kruse1944 said:
Look promising
Click to expand...
Click to collapse
Wow you're quick!
Let me know how it works for you. Happy flashing!

Thanks for your work:good:

Is it just me or is the voltage table backwards, higher voltages for lower cpu speeds?
Sent from my SGH-T999 using xda app-developers app

Am I missing something? Where do I dl d2tmo?
Sent from my Wicked fast SGS3!

akapaul26 said:
Am I missing something? Where do I dl d2tmo?
Sent from my Wicked fast SGS3!
Click to expand...
Click to collapse
You download the att one. Works for tmo.
Sent from my SGH-T999 using Tapatalk 2

robertd0619 said:
You download the att one. Works for tmo.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for helping out. :good: I'll change the file name to be more obvious shortly.
darjama said:
Is it just me or is the voltage table backwards, higher voltages for lower cpu speeds?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Bizarre. The tables are all correct and should display correctly, but your app is probably expecting a slightly different format. What app are you using? I'll try to figure out what's going on.

This kernel works great thanks I'm on pac rom. Thanks
aaaaaaaaahhhhhhhhhhhhhhh help me

decimalman said:
Thanks for helping out. :good: I'll change the file name to be more obvious shortly.
Bizarre. The tables are all correct and should display correctly, but your app is probably expecting a slightly different format. What app are you using? I'll try to figure out what's going on.
Click to expand...
Click to collapse
just took a look at your acpuclock tables, the first table uv to 1400000 but others don't match. nomal and fast should match up with one another from my experience. The multipliers seem good tho

ayysir said:
just took a look at your acpuclock tables, the first table uv to 1400000 but others don't match. nomal and fast should match up with one another from my experience. The multipliers seem good tho
Click to expand...
Click to collapse
The tables I'm using are the stock tables from CM & Samsung (obviously with extra frequencies added as well). I've deliberately kept the standard voltage setup (minimum voltage, different voltage tables for each PVS bin, etc.), although by default I disable the minimum voltage during boot.
On the other hand, at 2106 MHz, the PVS bin probably doesn't matter, and all three bins probably need the full 1.4 V. My processor undervolts nicely, so I don't have a good sense for what voltage is required when overclocking. If anyone provides me tables that work for them, I'll update the higher voltages.
LOL the multipliers should be fine except the ridiculous 2.5 GHz typo that should never have been committed.

decimalman said:
The tables I'm using are the stock tables from CM & Samsung (obviously with extra frequencies added as well). I've deliberately kept the standard voltage setup (minimum voltage, different voltage tables for each PVS bin, etc.), although by default I disable the minimum voltage during boot.
On the other hand, at 2106 MHz, the PVS bin probably doesn't matter, and all three bins probably need the full 1.4 V. My processor undervolts nicely, so I don't have a good sense for what voltage is required when overclocking. If anyone provides me tables that work for them, I'll update the higher voltages.
LOL the multipliers should be fine except the ridiculous 2.5 GHz typo that should never have been committed.
Click to expand...
Click to collapse
hmm your correct just took a quick gander at cm's tables. I say try increase the voltages accordingly and see if it makes a difference in readings

decimalman said:
Bizarre. The tables are all correct and should display correctly, but your app is probably expecting a slightly different format. What app are you using? I'll try to figure out what's going on.
Click to expand...
Click to collapse
I'm using set cpu. Thanks for looking into it.
Sent from my SGH-T999 using xda app-developers app

darjama said:
I'm using set cpu. Thanks for looking into it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm guessing this was an oversight on my part. I don't actually have the app, but I'm testing a bunch of fixes for a handful of different apps now. I'll push a test build (hopefully) later today that should get Voltage Control, Kernel Tuner, and maybe even SetCPU all working properly.

darjama said:
I'm using set cpu. Thanks for looking into it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
New test build should get SetCPU working properly. If you get a chance, will you try flashing this test build and letting me know if it works for you?

decimalman said:
New test build should get SetCPU working properly. If you get a chance, will you try flashing this test build and letting me know if it works for you?
Click to expand...
Click to collapse
That seemed to fix it, thanks!
Sent from my SGH-T999 using xda app-developers app

darjama said:
That seemed to fix it, thanks!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Great! If I don't run into any problems with the changes I made, I'll merge everything and it'll be in the next release.

robertd0619 said:
You download the att one. Works for tmo.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I figured as much. But was not 100% thanks
Sent from my Wicked fast SGS3!

Tutorial for Optimal Performance settings

[ROOT] Guide for increasing Performance significantly on One V
CPU-
The HTC One V processor (MSM8255) is designed* to be set at 1.4Ghz, it is safe to overclock to that range. Never under clock below 245Mhz. If your battery temp exceeds 114.3 degrees Fahrenheit (45.7 degrees Celsius) then you will need to revert to a lower clock rate, but that shouldn't happen
I/O Scheduler/Governor-
Best settings is Deadline in combination with SmartAssv2/LionHeart.
General-
-Its recommended animations in developer settings are turned off or turned down to 0.5x speed
-Turning off vibrate sounds/feedback will help with processor load in heavy situations (minor differences)
-Setting the launcher to 3 screens instead of 5
-Crossbreeder Mod contains a large amount of tweaks, if you use this mod you will see major performance improvements, Kernel Same Page Merging may be turned on with this device in settings, dont worry about extra CPU cycles or battery life drop, corssbreeder does it all. Just reboot into recovery and flash the .zip file on top of your existing ROM
-Enable KSM (Kernel same page merging) for better gaming experience and RAM utilization, compliments well with crossbreeder
Quick Summary-
-Overclock to 1.4Ghz (CPU is designed for this clockrate)
-Install Crossbreeder
-Reduce Launcher homescreens to 3
-Turn off haptic feedback
-Change I/O scheduler to Deadline
-Change CPU Governor to SmartAssV2
-Turn animations off or to 0.5x
Results
Antutu Benchmark (3 consecutive tests on each ROM, stock is control)
Stock- 2,515
RythmicRom w/o optimizations-3456
RythmicRom with optimizations-5143 (48.9% increase in performance from stock with CM 10.1 based ROM)

I'm on RC3.5 rom and just installed this script. It is really faster, the UI is more responsive now and makes internet connection smooth. However, it looks like will take a bit more time to boot up the system.
Remember to change the echo 256 > /proc/sys/kernel/random/write_wakeup_threshold to echo 16 > /proc/sys/kernel/random/write_wakeup_threshold, it is located in /etc/CrossBreeder/zzCrossBreeder
16 or 64 is recommended in the Crossbreeder thread now, the default 256 will introduce lag. Personally, I've changed it to 16.

Thanks for this ! Very helpful!

TheEndHK said:
I'm on RC3.5 rom and just installed this script. It is really faster, the UI is more responsive now and makes internet connection smooth. However, it looks like will take a bit more time to boot up the system.
Remember to change the echo 256 > /proc/sys/kernel/random/write_wakeup_threshold to echo 16 > /proc/sys/kernel/random/write_wakeup_threshold, it is located in /etc/CrossBreeder/zzCrossBreeder
16 or 64 is recommended in the Crossbreeder thread now, the default 256 will introduce lag. Personally, I've changed it to 16.
Click to expand...
Click to collapse
Hi, thanks for this. How do you open the file in an editable form? I can open (in Jota) it, but it refuses to save the change - presumably because I haven't opened it as a root user.
Oli.

zcacogp said:
Hi, thanks for this. How do you open the file in an editable form? I can open (in Jota) it, but it refuses to save the change - presumably because I haven't opened it as a root user.
Oli.
Click to expand...
Click to collapse
I'm still on 5.21.13, the new ver drains more battery and more buggy but it might be more faster. You can edit it so you already got root access right, you forgot to mount the /etc as writeable in root explorer so it won't save.
As the OP guide, I use sio as I/O scheduler. I don't suggest to use Deadline because it has the read priority 2X over write which is too slow for our microSD. It's only good when you use internal flash memory all the times like One X/One S/One, or else you never write somethings into microSD.

thanks I updated a few things and fixed that link

I get the score 6543 on antutu benchmark with mysense rc3.5 rom at 1.7ghz clock speed and governor - performance....i/o scheduler - bfq
Smooth as awesome
Sent from my HTC One V using xda premium

Here's my latest test I know this thread is old but I'm excited
I'm on Curtis slim bean ROM min freq 300 max 1.7 GHz tweaked with team kernelizers operation killjoy tweak script
My governor is set to smart...v2 I/o is set to deadline
As a oh heck if I need it I have set CPU to under clock automatically if my temp reaches roughly 115f which I believe is 44 or 45 celcius.
Sent from my immorality and my HTC One V using Tapatalk 2 sponsored by the letter mmm donuts... DOH!