Develop Bugs

OverClocking on the HTC Incredible -

I've tried using, I'm not a slow learner. I just don't quite understand how to overclock it.
I'm curious if my profiles settings are correct -
1.113Mhz Max
275Mhz Min on Performance - Are those correct if your trying to run your HTC at its highest quality while sacrificing battery?
I had one -
1.113Mhz Max
1.113Mhz Min and performance. It seemed fast and kept my temperature down to 95.8° instead of being at 108.3° all day and it also saved battery life alot. The reason its normally that hot is because I'm constantly using my Droid. My screen is why my Droid mainly dies half the time.
But can anyone tell me if I'm working this right?
Sent from my ADR6300 using XDA App

The performance governor keep your processor at the highest clock speed, so unless your running benchmarks, I wouldn't recommed using it. What kernel are you using and which app are you using for overclocking?

{
"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"
}
Set CPU root user access.
Also what do you mean by Benchmarks? Like testing or running certain apps?
Sent from my ADR6300 using XDA App

withbloodskies said:
Set CPU root user access.
Also what do you mean by Benchmarks? Like testing or running certain apps?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Like testing with quadrant or linpack.
Sent from my Droid Incredible running a random CM7 nightly.

withbloodskies said:
I've tried using, I'm not a slow learner. I just don't quite understand how to overclock it.
I'm curious if my profiles settings are correct -
1.113Mhz Max
275Mhz Min on Performance - Are those correct if your trying to run your HTC at its highest quality while sacrificing battery?
I had one -
1.113Mhz Max
1.113Mhz Min and performance. It seemed fast and kept my temperature down to 95.8° instead of being at 108.3° all day and it also saved battery life alot. The reason its normally that hot is because I'm constantly using my Droid. My screen is why my Droid mainly dies half the time.
But can anyone tell me if I'm working this right?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
use 128-1113 smartass

withbloodskies said:
Set CPU root user access.
Also what do you mean by Benchmarks? Like testing or running certain apps?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Benchmark apps like linpack or quadrant measure the general amount of processing power the phone is capable of. People generally run these apps to test how fast their phone is. On another note; since it looks like you are using cyanogenmod why are you using setcpu and not the built in overclocking feature built into the rom?

N-Forced said:
Benchmark apps like linpack or quadrant measure the general amount of processing power the phone is capable of. People generally run these apps to test how fast their phone is. On another note; since it looks like you are using cyanogenmod why are you using setcpu and not the built in overclocking feature built into the rom?
Click to expand...
Click to collapse
Ahh, well with Set CPU it allows me to use a widget etc. Also by installing one of these CPU apps it controls cyanogens built in CPU.
I'd also like to ask about the updated Nightlies roms they come out with constantly, what do they do?
Improve performance, battery, more options etc?
Sorry I'm a bit new to the world of root.
EDIT-- I tested quadrant and hit the 1,381 mark. Weather that is good or not I don't know.
Sent from my ADR6300 using XDA App

With CM7 there's really no need for a separate CPU controlling app, and I've heard it can actually cause conflicts, so I'd recommend just using the built in performance settings in the CM settings menu.
If you're using the stock kernel, I'd set the governor to on demand (I'd recommend smartass but I don't think the stock kernel has it), and set you minimum speed to the lowest possible, max speed to 998mhz. I underclock a little bit (883mhz) and you can experiment with lower or higher max clock speeds if you want to. I've found that overclocking produces no difference in real world performance, everything is just as snappy at 883mhz as it is at 1113mhz and if you choose to underclock, you may notice slightly better battery life.
As for the nightlies, they're usually pretty small changes at this point. They've been perfectly stable and bug free for a while now. There are feature additions that go in to the nightlies, a few things they've added recently are built in screenshot, lockscreen wallpaper, and dBm in the status bar instead of signal bars.
So to answer your question, there isn't really any difference between the nightlies and stable release as far as performance and battery life, but there are more features and options. With the nightlies as stable and bug free as they are, I wouldn't think twice about recommending them.

N-Forced said:
Benchmark apps like linpack or quadrant measure the general amount of processing power the phone is capable of. People generally run these apps to test how fast their phone is. On another note; since it looks like you are using cyanogenmod why are you using setcpu and not the built in overclocking feature built into the rom?
Click to expand...
Click to collapse
Benchmarks only very remotely indicate processing power of the device. They mainly measure an abstract of what the ROM and kernel are able to do given certain parameters. I can set my Tbolt up to run in the 1900 on Quadrant or run AOSP and pull down 4000+ scores. CM kernels are good, but I think there are better ones. There's no way running a performance governor yields better life than smartass, ondemand, or interactive. The reason you might want to use performance is if you're using it for a screen off setting. Performance doesn't use clock cycles to constantly measure CPU load so its a good choice when you need the CPU to switch governors and ramp up quickly or when there is no need for the CPU to change speed. Every kernel has its own custom tweaked govs so they will all act differently. I currently run my dInc at 245-1.153 on a smartass gov and my Tbolt at 61MHz-1.49GHz on a modified ondemand gov. Running a setting that simply pulls good scores isn't even always indicative of the quickest, most useful setup. Plus, on many ROMs, running the SetCPU widget will cause serious lag issues regardless of how amazing your benchmark scores. There's a lot to be learned from playing and a lot to be learned from reading and benchmark scores are anything but a gold standard of performance measurement.

k_nivesout said:
With CM7 there's really no need for a separate CPU controlling app, and I've heard it can actually cause conflicts, so I'd recommend just using the built in performance settings in the CM settings menu.
If you're using the stock kernel, I'd set the governor to on demand (I'd recommend smartass but I don't think the stock kernel has it), and set you minimum speed to the lowest possible, max speed to 998mhz. I underclock a little bit (883mhz) and you can experiment with lower or higher max clock speeds if you want to. I've found that overclocking produces no difference in real world performance, everything is just as snappy at 883mhz as it is at 1113mhz and if you choose to underclock, you may notice slightly better battery life.
As for the nightlies, they're usually pretty small changes at this point. They've been perfectly stable and bug free for a while now. There are feature additions that go in to the nightlies, a few things they've added recently are built in screenshot, lockscreen wallpaper, and dBm in the status bar instead of signal bars.
So to answer your question, there isn't really any difference between the nightlies and stable release as far as performance and battery life, but there are more features and options. With the nightlies as stable and bug free as they are, I wouldn't think twice about recommending them.
Click to expand...
Click to collapse
I have to agree with him on the multiple clock setting apps. They work my running scripts and the scripts can conflict. If you're not running profiles, don't use SetCPU. If you are, ditch the other app.

Hmm, alright thanks. Well definitely learned alot from Over/Underclocking thank you.
Guess I'll get rid of the app? Should I use a different kernal though then the one I'm using depicted in that picture?
Sent from my ADR6300 using XDA App

withbloodskies said:
Hmm, alright thanks. Well definitely learned alot from Over/Underclocking thank you.
Guess I'll get rid of the app? Should I use a different kernal though then the one I'm using depicted in that picture?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
if you want. The cm kernel is just a generic kernel they port for each device so there isn't a lot of customization built into it. It's not a bad kernel, but there are certainly faster ones.

I just caught this thread and wanted to say Thanks for the input...
and ask for your recommendations on a few Kernels to try on a Dinc running CM7, and if you have the time what benefits they might provide?

I'd have to recommend Chad's incredikernel. It has the smartass governor, which tends to yield the best battery life as well as good performance. A feature it has that I find essential now is fast charge, as well as USB fast charge. There's also a flashable SD speed fix that remedies the slow transfer speeds on AOSP roms. It also goes hand in hand with the incredicontrol app, which allows for undervolting to extend your battery life even further.
I'd go to the incredikernel thread in the development forum, and also www.incredikernel.com to read up a bit on all the features and how to utilize them.

k_nivesout said:
I'd have to recommend Chad's incredikernel. It has the smartass governor, which tends to yield the best battery life as well as good performance. A feature it has that I find essential now is fast charge, as well as USB fast charge. There's also a flashable SD speed fix that remedies the slow transfer speeds on AOSP roms. It also goes hand in hand with the incredicontrol app, which allows for undervolting to extend your battery life even further.
I'd go to the incredikernel thread in the development forum, and also www.incredikernel.com to read up a bit on all the features and how to utilize them.
Click to expand...
Click to collapse
I installed the lastest, now you said I should get faster USB charge correct? Cause that would be absolutely wonderful, I broke my original cord and got this 1in cord that barely works and it works USB. If this is true this Guy is a God! Anyway so smartass is the best between saving battery and performance?
Sent from my ADR6300 using XDA App

Yes, I'd use recommend the smartass governor for the best combo of battery life and performance, and to enable USB fastcharge I use his incredicontrol app. Obviously the fast charge will only work if the USB port is putting out enough power to support it.

k_nivesout said:
Yes, I'd use recommend the smartass governor for the best combo of battery life and performance, and to enable USB fastcharge I use his incredicontrol app. Obviously the fast charge will only work if the USB port is putting out enough power to support it.
Click to expand...
Click to collapse
Dude seriously thank you! Is there a personal thread started from Chad declaring his awesome kernel? Ill join his alliance, this **** is literally the best thing my phone could have got.
- Before IncrediKernel, my phone died within 1-2 hours heavy use.
- After Installing, heavy use gives me 4-5 hours.
- Before IncrediKernel, my phone took 3-4 hours to fully charge.
- After installing, my phone charges within 1 hour and 30 mintues roughly upon heavy use. So estimated 40 minutes - 1 hour for full charge without use?
This kernel seriously did wonders. Thanks a ****ing alot chad! Best **** ever!
Sent from my ADR6300 using XDA App

[Q] How do you test your UV/OC setting?

The Galaxy Nexus has extremely poor battery life right out of the box. Now I'm using Modaco's ROM with UV/OC, and have been able to achieve some very decent battery life after undervolting.
How do you guys test the stability of your OC or UV settings? I'm using the following setting for now, which is relatively conservative seeing others' UV setting on the web (I'm not concerned with OCing, since I just want to get better battery life).
Mine:
1200MHz:1150mV
920MHz:1090mV
700MHz:950mV
350MHz:850mV
Default:
1200MHz:1380mV
920MHz:1317mV
700MHz:1203mV
350MHz:1025mV
The phone seems to be stable after a day of use. Right now I want to lower the voltage at 700 and 350 MHz as much as possible, since those are the frequencies that the phone stays at most of the time.
The way I test it is to use SetCPU to lock the frequency at, say 350MHz, and then set the desired voltage. Then run a series of benchmarks repeatedly, and if it crashed or rebooted, raised the voltage. So far the phone seems to be stable at 800mV for 350MHz and 925MHz. I'm going to lock down the max/min clock speed of the phone at 700/350MHz for the next few days and use it normally to see if it is stable or not.
Btw, the phone is surprisingly responsive even at 350MHz. Even Tiny Tower runs fine at that speed!
Is there any good CPU stress test apps that you guys can recommend?

tsekh501 said:
The Galaxy Nexus has extremely poor battery life right out of the box. Now I'm using Modaco's ROM with UV/OC, and have been able to achieve some very decent battery life after undervolting.
How do you guys test the stability of your OC or UV settings? I'm using the following setting for now, which is relatively conservative seeing others' UV setting on the web (I'm not concerned with OCing, since I just want to get better battery life).
Mine:
1200MHz:1150mV
920MHz:1090mV
700MHz:950mV
350MHz:850mV
Default:
1200MHz:1380mV
920MHz:1317mV
700MHz:1203mV
350MHz:1025mV
The phone seems to be stable after a day of use. Right now I want to lower the voltage at 700 and 350 MHz as much as possible, since those are the frequencies that the phone stays at most of the time.
The way I test it is to use SetCPU to lock the frequency at, say 350MHz, and then set the desired voltage. Then run a series of benchmarks repeatedly, and if it crashed or rebooted, raised the voltage. So far the phone seems to be stable at 800mV for 350MHz and 925MHz. I'm going to lock down the max/min clock speed of the phone at 700/350MHz for the next few days and use it normally to see if it is stable or not.
Btw, the phone is surprisingly responsive even at 350MHz. Even Tiny Tower runs fine at that speed!
Is there any good CPU stress test apps that you guys can recommend?
Click to expand...
Click to collapse
I've set the same voltages as you using Franco's nightly 6 (http://forum.xda-developers.com/showthread.php?t=1367341) and the Kang AOSP build for LTE (http://rootzwiki.com/topic/12451-rom-android-open-kang-project-toro-milestone-1-dec-27/), with minor changes:
1200MHz 1100mV
920MHz 1000mV
700MHz 900mV
350MHz 800mV
So far, stable for about 2 hours of doing everything I normally do, tried all of my games, web browsing, some YouTube, and Swype is running beautifully. I have been using "Stress Test" at the bottom of the Info tab in SetCPU to make sure it's stable running for a few minutes, then back).
Any ideas on Up threshold? I have kept it at 75% to make it snappier. Is that a reasonable value?

U could use the app stabilitytest , used it on my sgs2
Sent from my Galaxy Nexus using xda premium

I know SetCPU has a stress test function. But since it is not configurable, I'm not sure what it is doing.
Right now I'm using StabilityTest, which seems to work pretty well and have a number of configurable options.
I'm testing my phone by stress testing it at each frequency separately. For example, I'd use SetCPU to lock the frequency at, say, 350MHz, and then run classic stress test to see if my phone is table at that frequency at the specified voltage. I do this when I'm sitting on my desk at work not using my phone. I do this for every frequency and let it run for about an hour. If it is stable, I lower the voltage a tiny bit and then try again. And when I go to bed, and set min/max to 350/1200, and let the phone run scaling stability test overnight.
Currently my phone seems to be stable at:
1200MHz 1100mV
920MHz 1025mV
700MHz 900mV
350MHz 775mV
This is significantly lower than stock voltages and I'm getting much much better battery life.

I just lower by 25-50 until it locks up.. have had no problems doing it this way actually
Sent from my Galaxy Nexus using xda premium

tsekh501 said:
The Galaxy Nexus has extremely poor battery life right out of the box. Now I'm using Modaco's ROM with UV/OC, and have been able to achieve some very decent battery life after undervolting.
How do you guys test the stability of your OC or UV settings? I'm using the following setting for now, which is relatively conservative seeing others' UV setting on the web (I'm not concerned with OCing, since I just want to get better battery life).
Mine:
1200MHz:1150mV
920MHz:1090mV
700MHz:950mV
350MHz:850mV
Default:
1200MHz:1380mV
920MHz:1317mV
700MHz:1203mV
350MHz:1025mV
The phone seems to be stable after a day of use. Right now I want to lower the voltage at 700 and 350 MHz as much as possible, since those are the frequencies that the phone stays at most of the time.
The way I test it is to use SetCPU to lock the frequency at, say 350MHz, and then set the desired voltage. Then run a series of benchmarks repeatedly, and if it crashed or rebooted, raised the voltage. So far the phone seems to be stable at 800mV for 350MHz and 925MHz. I'm going to lock down the max/min clock speed of the phone at 700/350MHz for the next few days and use it normally to see if it is stable or not.
Btw, the phone is surprisingly responsive even at 350MHz. Even Tiny Tower runs fine at that speed!
Is there any good CPU stress test apps that you guys can recommend?
Click to expand...
Click to collapse
You might be able to get up to 50 more on 1200 mhz. I'm running at 1141 and when get time I will tweak that and 920 mhz. My 920 is 978. I can probably get 5-10 more there. My last bump was 15mv up because it was giving me problems. My last two are 877 and 757 respectively and those are tweaked out. Some ding dong was running 650, 750 850 and 950 and saying he was stable. He never got back to us to tell us if they were because I called him out on it. I've seen some tweaks that are close to ~1150, 1000, 950 and 850 or close to that looked close to maybe going lower. Everybody is different though. I havent seen anybody lower than my 920mhz and 350 mhz voltages and claimed rocked stable yet. I have had any reboots for a week now. I hope I can pull about 10mv lower on my higher frequencies when I get a chance. Uv won't help dramatically with battery as much as people like to think. They help with heat and longevity of phone more. You're only going to see maybe a 10% improvement or so with uv'ing. Need to see if voltage can be tweaked on gpu and screen. That would help more.
Sent from my Galaxy Nexus using xda premium

What kernel are you guys running? If you want a stable UV you need to check out LeanKernel, Imoseyon's kernels are the best out there imo. Here's what I've been running, stable.
{
"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"
}

I'm a fan of Leankernel. I was able to UV down to 650 for 350 MHz.

cvbcbcmv said:
I don't think there is a leankernel for GSM, I'm LTE though so, doesn't matter. Best way to test UV and OC, OC is just really if it works. If your CPU can't handle it you notice it immediately. UV, if your phone doesn't flip out, you're good. But never check set at boot until you run it for about a day, if all is good check it.
Click to expand...
Click to collapse
There is a lean kernel for GSM.. hand I'm pretty sure most kernels work with both.
Sent from my Galaxy Nexus using xda premium

1100
1000
875
775
Rock solid for two days now, very intensive usage and testing
Sent from my Galaxy Nexus using Tapatalk

Have you tried Franco's nightly? It's the only kernel other than stock I have tried and it's working very well. I'm down to the following now, no issues:
1200MHz 900mV
920MHz 800mV
700MHz 750mV
350MHz 700mV
Any reason to switch to the lean kernels?

OK, it seems that I was too conservative and I can try to lower the voltage somewhat lower. I'm using Modaco MCK kernel its custom ROM.
Is there any stress test/benchmark apps, beside StabilityTest and SetCPU that can loop continuously to stress my phone?
Sent from my Galaxy Nexus using XDA App

I doubt the UV interface works in Franco kernel, I am now supposedly running 1200 MHz at 600 mV Of course there are limits to uV, but it should still be possible to make the device hang.
Sent from my Galaxy Nexus using Tapatalk

Ktoonservative! Governor explained

In this thread we will discuss governors.
Primarily differences between ondemand and conservative based ones. This thread was created because ktoonsez made a hotpluging conservative governor. ... perhaps this needs explanation for the general community, that will imo prove the vast superiority of conservative based governors. First here is a link about governors in general it is sort of abridged but, covers allot of governors http://blog.g4team.com/?p=5519
As you can see it makes mention that most of these governors are similar to ondemand. So outlining the major differences. Ondemand scales to the highest frequency as soon as a load occurs. Conservative scales upward based on the frequency step variable which means for the most part will scale through every frequency to achieve the target load thresholds. What this practically means is ondemand is prone to wasting power on unneeded clock cycles. Ondemand also features something called a down differential, this variable determines how long the governor will remain at the given frequency before scaling down. Conservative does not have this, but instead relies on having a down threshold which insures that as soon as the load drops below a given variable it scales down as fast as the sampling rate allows. The result to this is a governor which attempts to keep the load level tolerable and save you battery! Now ! Ktoonservative Is that but in addition contains a hotpluging variable which determines when the second core comes online. The governor shuts the core off when it drops below the hotplug down threshold thus giving us a handle on the second performance factor in our CPUs behavior. While by default conservative is a poor performer it can be made to perform comparably to even performance governor. Here are some settings to discuss and start with. They are slightly less battery friendly under a load but very very well performing.
after realizing just everything mpdecision does i recommend turning it off for this govenor to work properly "stop mpdecision" in the terminal should do. it not only allows for things like benchmarks to lock frequency but generally will disturb these settings under a load, it will do something completely different. so when i turned it off i discovered the govenor behaving differently....more over exactly as you would expect this also meant with some ideas from mw86 that we dont really need touch booster. id recommend the first set of settings and use the last if you want mpdecision on. despite looking less aggressive for battery savings they usually will be with the absence of mpdecision
SAMPLING_RATE="15000"
UP_THRESHOLD="67"
DOWN_THRESHOLD="47"
FREQ_STEP="3"
SAMPLING_DOWN_FACTOR="1"
IGNORE_NICE_LOAD="0"
UP_THRESHOLD_HOTPLUG="85"
DOWN_THRESHOLD_HOTPLUG="33"
SAMPLING_RATE="40000"
UP_THRESHOLD="67"
DOWN_THRESHOLD="52"
FREQ_STEP="5"
SAMPLING_DOWN_FACTOR="1"
IGNORE_NICE_LOAD="0"
UP_THRESHOLD_HOTPLUG="68"
DOWN_THRESHOLD_HOTPLUG="40"
And here is the link for the kernel containing such http://forum.xda-developers.com/showthread.php?t=1800576
A further edit for jb builds most benchmarks are niced so you must turn off ignore nice load to test settings with them
Sent from my SPH-L710 using Tapatalk 2

The results
{
"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"
}
[/IMG]
Sent from my SPH-L710 using Tapatalk 2

Great post and discussion freecharlesmanson. I'm using your specs above and FREQ_STEP="5" I changed to 1, so it would be more like Lazy governor and save me extra power at the cost of a little lag since it must go through the full frequency scale instead of jumping to target frequency in a step or two. Watching cpu frequency in a graph shows this governor and your tweaks do great at being conservative but with power ready to be tapped. For frequency step at 1 im seeing stuff that ramped up in no time takes a half a sec more due to the frequency ladder it must climb... but I'm hoping it will mean it only uses high frequencies when its been under load for quite some time and not just from a basic background task I may care little about the speed in which its completed. Battery life is through the roof with this governor and Ktoonsez Kernel.
edit: if i set down threshold to 60 does it save more power without a lot of complications or does it cause large hiccups or uneeded frequency changing? would it be better to be near 50, stay at 45 or drop down under to 40-35? i was using your settings in other kernel thread but now using yours here and the rest as mentioned.

mw86 said:
Great post and discussion freecharlesmanson. I'm using your specs above and FREQ_STEP="5" I changed to 1, so it would be more like Lazy governor and save me extra power at the cost of a little lag since it must go through the full frequency scale instead of jumping to target frequency in a step or two. Watching cpu frequency in a graph shows this governor and your tweaks do great at being conservative but with power ready to be tapped. For frequency step at 1 im seeing stuff that ramped up in no time takes a half a sec more due to the frequency ladder it must climb... but I'm hoping it will mean it only uses high frequencies when its been under load for quite some time and not just from a basic background task I may care little about the speed in which its completed. Battery life is through the roof with this governor and Ktoonsez Kernel.
Click to expand...
Click to collapse
Yep if you can deal with the lag it will do the trick . You could try to slightly raise that number and just raise the up threshold and hot plug threshold allot like 85 up and 80 hotplug. Then raise the freq step to 2 or three maybe it might give a similar result by discouraging up scaling thru the demand end but would allow quicker scaling ever so slightly with less likelihood of jumping steps. By my math each freq step represents 4.3% total available scaling
Sent from my SPH-L710 using Tapatalk 2

Great work on this, appreciate you taking the time to explain it all!
Sent from my SPH-L710 using xda app-developers app

I can't stand any form of lag! Complete smoothness is the way to be
Sent from my SPH-L710

Lol if you're lagging using conservative with your shiny S4, you're doing it wrong.
I've used conservative exclusively over ondemand ever since root was achieved with my Epic4g which uses the 1ghz hummingbird processor and there's no lag...
I now use smartassv2...seems to give even faster performance and shuts things down quicker than conservative!
Sent from my SPH-D700 using xda app-developers app

A_Flying_Fox said:
Lol if you're lagging using conservative with your shiny S4, you're doing it wrong.
I've used conservative exclusively over ondemand ever since root was achieved with my Epic4g which uses the 1ghz hummingbird processor and there's no lag...
I now use smartassv2...seems to give even faster performance and shuts things down quicker than conservative!
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Smart ass is based on interactive my issue still falls with load regulation. Most of that it seems like it would race thru frequency more. Which may deliver good performance but if at all it would deliver the same but worse battery
This is how well it works for idle regulation and I should point out smart ass doesn't hotplug so in turn because it cannot regulate the second core most likely results in less efficient scaling and if the second core preempted scaling it offers more performance than scaling right off ,those screens are of it being used alittle before bed then alittle more after I woke up
Sent from my SPH-L710 using Tapatalk 2

Just applied values. So far so good. I was just curious, are you over clocking at all? Would it be safe to run this thing at 2106?
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
Just applied values. So far so good. I was just curious, are you over clocking at all? Would it be safe to run this thing at 2106?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Rofl. Anything over 1.5 is a waste.
Sent from my SPH-L710

drewmonge said:
Just applied values. So far so good. I was just curious, are you over clocking at all? Would it be safe to run this thing at 2106?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Its a governer not voltage settings so I can't see why you'd have a problem
Sent from my SPH-L710 using Tapatalk 2

Custodian said:
Rofl. Anything over 1.5 is a waste.
Sent from my SPH-L710
Click to expand...
Click to collapse
Fantastical.
Sent from my SPH-L710 using xda app-developers app

Freecharles manson I was tinkering more and decided to go in a different direction. can you tell me how this would act theoretically? it seems to do good at no lag and saves power still.
SAMPLING_RATE="13500"
UP_THRESHOLD="49"
DOWN_THRESHOLD="23"
FREQ_STEP="1"
SAMPLING_DOWN_FACTOR="4"
IGNORE_NICE_LOAD="1"
UP_THRESHOLD_HOTPLUG="24"
i chose these because I have a theory on single core load vs dual core load in our multi core setup. Since the governor can be multicore aware... I was thinking about what that means.
dual core cpu 100% load = 1 core 100% and the other. dual core 50% load can mean 1 core is at 100% load and second core 0% or anything in between to 50% on both the cores which is still the same... 50% load of a dual core cpu. So lets just say a rouge app pegs at 100% load regardless of 2nd core status. If we set up threshold or hotplug above 50% it means the load to up the frequency or amount of cores activated must be over the load of having 1 core fully loaded to 100% to activate.. ie one at 100% and the other a little over or vise versa both cores loaded to 51% total atleast. So I want my up threshold for frequency at 50% area so if one core ever loads to 100% it adds a frequency step. At the same time I want my second core to activate not while idle but at any load under the upthreshold. So to still save power i want down threshold just under the load required to activate core 2. So 25% seems like a good number. it is equivalent to a 50%load on one core alone or a balance of 25% load over both cores. So down threshold 1 percent under that so unless load is above that it lowers frequency as needed.
so to make sure its easier for the thresholds to jump in at right time i dropped each measurement 1% so it wouldn't literally need 100% load single core to up the frequency. so thats why i went 49%, 24% and 23%. this way the cpu doesnt often stay at a full load unless needed but ramps up when things take a few to calculate and hopefully finish faster saving juice by using the closest matched speed needed. To save power the frequency step is minumum but by the way thresholds are set it will ramp it up very quickly to whats needed even under light loads. battery life hasnt been too bad set like this over the day.
any thoughts on this and if it will work how I am hoping? I'm not sure the direction i took this for my personal use but my goal is a Conservative on demand governor with good hotplugging and to be sure it doesnt use speeds which are overkill for the task nor underpowered either. lazy Ktoonservative
i played around with the values differently and didn't like having hot plug kick in after frequency increase. i figure as load increases from zero it will stay at lowest speed till 23% then at 24% core 2 will kick in and if that doesn't lower cpu load by time it reaches 49% load it will stay in dual core and go up one cpu step... if load doesnt drop it will continue to add speed and stay in dual core. but as soon as load drops below 49% speed will stay same and then core two will shut off at 24% and either finish the work load at that speed in single core, drop to lowest cpu speed in single core or as needed renenable core two to start process all over and therefore either finishing work load or ramping again while in dual core up in frequency till load once again drops into the threshold ranges.
Custodian and Freecharlesmanson i respect your info and would love to know how accurate this is. I am new to Android as of this year but not new to cpus so if you have advice or feedback for this discussion Id be very appreciative.

So my issue atm is with ES explorer scrolling. It's super choppy.... I'm exploring more values in hopes of finding a sweet spot. I can confirm that the choppiness doesn't exist on ICS but does on asop ROMs. So I'm trying to see what's up now.
Sent from my SPH-L710

mw86 said:
Freecharles manson I was tinkering more and decided to go in a different direction. can you tell me how this would act theoretically? it seems to do good at no lag and saves power still.
SAMPLING_RATE="13500"
UP_THRESHOLD="49"
DOWN_THRESHOLD="23"
FREQ_STEP="1"
SAMPLING_DOWN_FACTOR="4"
IGNORE_NICE_LOAD="1"
UP_THRESHOLD_HOTPLUG="24"
i chose these because I have a theory on single core load vs dual core load in our multi core setup. Since the governor can be multicore aware... I was thinking about what that means.
dual core cpu 100% load = 1 core 100% and the other. dual core 50% load can mean 1 core is at 100% load and second core 0% or anything in between to 50% on both the cores which is still the same... 50% load of a dual core cpu. So lets just say a rouge app pegs at 100% load regardless of 2nd core status. If we set up threshold or hotplug above 50% it means the load to up the frequency or amount of cores activated must be over the load of having 1 core fully loaded to 100% to activate.. ie one at 100% and the other a little over or vise versa both cores loaded to 51% total atleast. So I want my up threshold for frequency at 50% area so if one core ever loads to 100% it adds a frequency step. At the same time I want my second core to activate not while idle but at any load under the upthreshold. So to still save power i want down threshold just under the load required to activate core 2. So 25% seems like a good number. it is equivalent to a 50%load on one core alone or a balance of 25% load over both cores. So down threshold 1 percent under that so unless load is above that it lowers frequency as needed.
so to make sure its easier for the thresholds to jump in at right time i dropped each measurement 1% so it wouldn't literally need 100% load single core to up the frequency. so thats why i went 49%, 24% and 23%. this way the cpu doesnt often stay at a full load unless needed but ramps up when things take a few to calculate and hopefully finish faster saving juice by using the closest matched speed needed. To save power the frequency step is minumum but by the way thresholds are set it will ramp it up very quickly to whats needed even under light loads. battery life hasnt been too bad set like this over the day.
any thoughts on this and if it will work how I am hoping? I'm not sure the direction i took this for my personal use but my goal is a Conservative on demand governor with good hotplugging and to be sure it doesnt use speeds which are overkill for the task nor underpowered either. lazy Ktoonservative
i played around with the values differently and didn't like having hot plug kick in after frequency increase. i figure as load increases from zero it will stay at lowest speed till 23% then at 24% core 2 will kick in and if that doesn't lower cpu load by time it reaches 49% load it will stay in dual core and go up one cpu step... if load doesnt drop it will continue to add speed and stay in dual core. but as soon as load drops below 49% speed will stay same and then core two will shut off at 24% and either finish the work load at that speed in single core, drop to lowest cpu speed in single core or as needed renenable core two to start process all over and therefore either finishing work load or ramping again while in dual core up in frequency till load once again drops into the threshold ranges.
Custodian and Freecharlesmanson i respect your info and would love to know how accurate this is. I am new to Android as of this year but not new to cpus so if you have advice or feedback for this discussion Id be very appreciative.
Click to expand...
Click to collapse
Well I'll explain it this way despite the freq step being low the issue is it will aim to unload the first CPU at 49% which won't take much after that while it will rest eventually because it is still so low on hotplug the second core will be constantly on. The second core offers more performance but much much more battery then slightly increases clock rate the issue is balancing that because so often you either end up with the clock rate racing up wards or the core staying on. . Personally don't take a shot in the dark. Take settings you know work and work towards your idea incrementally recording the changes the CPU time states record I think though not allowing the CPU to shift a full state up will be to major detriment to performance. Per CPU freq state is 4.3% I have found over 80% on available cores causes stuttering . I gave the settings a spin looks like the second core is on a bit much so you'd want to balance that out. But test test test test and let me know
Sent from my SPH-L710 using Tapatalk 2

Custodian said:
So my issue atm is with ES explorer scrolling. It's super choppy.... I'm exploring more values in hopes of finding a sweet spot. I can confirm that the choppiness doesn't exist on ICS but does on asop ROMs. So I'm trying to see what's up now.
Sent from my SPH-L710
Click to expand...
Click to collapse
Running es right now no issues . Sense it exist only on aosp I'm gonna guess it wasn't governor related? Can you confirm the same results running a different governor?
Sent from my SPH-L710 using Tapatalk 2

freecharlesmanson said:
Running es right now no issues . Sense it exist only on aosp I'm gonna guess it wasn't governor related? Can you confirm the same results running a different governor?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
It's not gov related. Tested with performance, ondemand, conservative
Sent from my SPH-L710
---------- Post added at 04:25 AM ---------- Previous post was at 04:20 AM ----------
Meh dunno wtf going on. It's only with ES rxplore.
vm.swappiness = 0
Testing. Just cause. Lol.
Sent from my SPH-L710

Yeah phones don't benefit from swappiness but I'd leave a slight amount just in case you ever approach oom if you have it turned off and you ever hit oom it will kill random possibly important apps or just plain lockup
Unless you go oom though it makes no difference
Swappiness is set to 15% on my desktop and its only using 200kb arbitrarily I might add
Sent from my SPH-L710 using Tapatalk 2

freecharlesmanson said:
Well I'll explain it this way despite the freq step being low the issue is it will aim to unload the first CPU at 49% which won't take much after that while it will rest eventually because it is still so low on hotplug the second core will be constantly on. The second core offers more performance but much much more battery then slightly increases clock rate the issue is balancing that because so often you either end up with the clock rate racing up wards or the core staying on. . Personally don't take a shot in the dark. Take settings you know work and work towards your idea incrementally recording the changes the CPU time states record I think though not allowing the CPU to shift a full state up will be to major detriment to performance. Per CPU freq state is 4.3% I have found over 80% on available cores causes stuttering . I gave the settings a spin looks like the second core is on a bit much so you'd want to balance that out. But test test test test and let me know
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
okay great explanation. It was a good read I'll go back to drawing board test test test and post back with more theory and results when i've come up with something that is working good for me. I'll keep in mind I need Hotplug to not kick in as often nor have cpu frequency shoot up to max so its a balancing act. I appreciate your info thank you. I'm reading as much as i can find on more governors and their adjustments to get ideas from them too like you said to base off an existing one and modify from there.

mw86 said:
okay great explanation. It was a good read I'll go back to drawing board test test test and post back with more theory and results when i've come up with something that is working good for me. I'll keep in mind I need Hotplug to not kick in as often nor have cpu frequency shoot up to max so its a balancing act. I appreciate your info thank you. I'm reading as much as i can find on more governors and their adjustments to get ideas from them too like you said to base off an existing one and modify from there.
Click to expand...
Click to collapse
What you are shooting for is the opposite end of the stick so. Getting the same results off a diametrically opposed idea is awesome keep it up
Sent from my SPH-L710 using Tapatalk 2

Gaming I/O and Governers Tweaks

I score 3028 after benchmarking with Quadrant after these small changes in CPU stuff and i thought i wanna share it ...
I tried all kinds of things to make gaming faster and after experimenting... I got 1950+ score for 3D perfomance and these are the overall results after changing the governor and I/O:
1st try: 3128 :laugh:
2nd try: 3209 :victory:
3rd try: 2977
4th try: 3028 :laugh:
Heres how...
You only need No-CPU frlls or CPU Master or any other APP capable of changing clock speeds eg. SetCpu... :good:
Set your devices Governor to smartassV2 and i/o scheduler to vr... Clock your CPU speed to the max frequency that is stable... Mine is 1.8GHz, but can OC to 2Ghz which can make my device boiling hot.... Minimum frequency you wanna set is 600 mhz and below... And thats about it...
DO NOTE! Only some kernels can use the SmartAssV2 Governor and vr I/O scheduler... if none of them is there, I recommend you use Ondemand Govern' and Noop I/O...
Again, not all kernels are gonna have that score..
If i made a great mistake, don't be afraid to correct me especially Pepoluan ...
BTW i'm using REMICS v1.7 by sparta20 and Forvivos kernel...

TiTAN-O-One said:
I score 3028 after benchmarking with Quadrant after these small changes in CPU stuff and i thought i wanna share it ...
I tried all kinds of things to make gaming faster and after experimenting... I got 1950+ score for 3D perfomance and these are the overall results after changing the governor and I/O:
1st try: 3128 :laugh:
2nd try: 3209 :victory:
3rd try: 2977
4th try: 3028 :laugh:
Heres how...
You only need No-CPU frlls or CPU Master or any other APP capable of changing clock speeds eg. SetCpu... :good:
Set your devices Governor to smartassV2 and i/o scheduler to vr... Clock your CPU speed to the max frequency that is stable... Mine is 1.8GHz, but can OC to 2Ghz which can make my device boiling hot.... Minimum frequency you wanna set is 600 mhz and below... And thats about it...
DO NOTE! Only some kernels can use the SmartAssV2 Governor and vr I/O scheduler... if none of them is there, I recommend you use Ondemand Govern' and Noop I/O...
Again, not all kernels are gonna have that score..
If i made a great mistake, don't be afraid to correct me especially Pepoluan ...
BTW i'm using REMICS v1.7 by sparta20 and Forvivos kernel...
Click to expand...
Click to collapse
AFAIK, governor's clock speed will be "locked" to the highest possible clock when you are running benchmark. let's take lulzactive as an example. look at this line
DEFAULT_INC_CPU_LOAD 70
Click to expand...
Click to collapse
, 70 means when processor's load is reaching 70% , the clock speed will be increased some steps. in benchmarking, cpu load is always high >>90%(i'm not sure so CMIIW) that means your clock speed will always be locked in that highest possible value no matter what your governor is (even conservative). the only difference is how long they need to get up to the next level of clock speed
so personal experience will be better to get your right value rather than benchmarking. every governor has difference time to reach higher level of clock speed which is not be able to be experienced in benchmarking. this is contrary to personal experience(daily use) which you can feel how your phone react toward a command. let's take example of the most battery saving(conservative) and highest performance(performance). you can feel that conservative is rather slow in executing command while performance will give nice personal experience. both of them didn't give any significant difference in benchmarking score but both of them can give significant difference in personal experience
i hope you get my point here
CMIIW

Thanks alot But according to personal experience, I nvr felt any lag whatsoever... In gaming like shadow gun, didn't feel that much lag compared to the stock kernel from Samsung...
Thanks for correcting me anyway! I appreciate it
Sent from my GT-I8150 using xda app-developers app

[Q] Do you overclock your Ace 2?

Hi,
given that now several ROMS support Overclocking, I wanted to ask what max frequency people use?
Also, do you REALLY feel an improved performance?
What governor are you using?
How does it affect battery life?
Just to start:
I use 1000MHz, ondemandq, battery life maybe 10% less, but to be honest, I cannot tell ANY speed difference.
What about you?

playagiron said:
Hi,
given that now several ROMS support Overclocking, I wanted to ask what max frequency people use?
Also, do you REALLY feel an improved performance?
What governor are you using?
How does it affect battery life?
Just to start:
I use 1000MHz, ondemandq, battery life maybe 10% less, but to be honest, I cannot tell ANY speed difference.
What about you?
Click to expand...
Click to collapse
U wont feel any difference cuz the OC is buggy and kernels on them let u do OC but in same time they slow ur ACE2 rly hard. Only OC on wchich u dont have any hard-bad-side effects is CM10.2 (22january). But to OC on it, u had to play with terminal. On cm10.2 OC was giving lot of performance, my ace on cm10.2 (22jan) with 1,2ghz, get awesome speed and responsibility. I reccomend u to not use roms which have build in OC (now), cuz kernels inside them are making ur ace slow and laggy.

I'm waiting for fully working Oc, so for now, 800mhz is enough.

i think its enough for 1000 mhz for good battery
sory for my bad english:laugh:

Still needs work
Overclock for our device still needs work.When I set it on 1228mhz with performance and deadline everything seems great at first but after a while the phone randomly reboots.Drastic which is basically the only app I use for games runs better with the original kernel than with the OC kernel.We have great developers,though,so I think that we'll get a stable OC really soon :laugh:

I never have problems with OC set to 1228mhz with performance. I also feel increased performance but battery drain is quite high and the phone gets quite hot.
Sent from my GT-I8160 using XDA Premium 4 mobile app

artur1131 said:
U wont feel any difference cuz the OC is buggy and kernels on them let u do OC but in same time they slow ur ACE2 rly hard. Only OC on wchich u dont have any hard-bad-side effects is CM10.2 (22january). But to OC on it, u had to play with terminal. On cm10.2 OC was giving lot of performance, my ace on cm10.2 (22jan) with 1,2ghz, get awesome speed and responsibility. I reccomend u to not use roms which have build in OC (now), cuz kernels inside them are making ur ace slow and laggy.
Click to expand...
Click to collapse
1,2 GHZ?!?!?! boy you sure do go above and beyond :good: does that not make your battery really bad? battery damage? side effects?
the highest ive gone is 1GHZ?

Speedtrix said:
1,2 GHZ?!?!?! boy you sure do go above and beyond :good: does that not make your battery really bad? battery damage? side effects?
the highest ive gone is 1GHZ?
Click to expand...
Click to collapse
Accidentally thanked
For side effects search google. And novathor said the safest, max freq is 1.2GHz
Sent from my GT-I8160 using Tapatalk

Speedtrix said:
1,2 GHZ?!?!?! boy you sure do go above and beyond :good: does that not make your battery really bad? battery damage? side effects?
the highest ive gone is 1GHZ?
Click to expand...
Click to collapse
Let me explain u:
U could do OC only with Performance+deadline.
The OC was rly working, i get higher benchmark scores (11200 antutu v4) and my ace get nexus-like responsibility (read: uber fast)
Buuut, Performance+deadline is combination which eats ur battery rly fast. Ur phone is using his max potential on this combo all the time, so battery is going down faster. I think that when we will get stable oc which will work with every governor+scheduler (for ex ondemandq+sioplus) it will work good. If the oc kernel will get optimized for inteligent governors (smartass etc.) which are giving u higher frequency only when u need it (when u get lagged, governor is setting ur frequency higher). it might work on battery just a little shorter than on stock.
Side effects? Processor will degrade a little bit faster, but if u arent going to use this phone for sth like 10 years then u shouldnt care about it. Screen will get burned out faster than our CPU on this OC.
As sb said 1,2ghz isnt rly high freq. STE said that 1,2 ghz is safe freq for this processor.
Battery damage? Ofc no. Ur battery wont get damaged dont worry. U can damage ur battery by charging it with ****ty noname charger or by setting ur wall charger currency too high (higher than 1Ah, when stock "safe" is 600 mAh).
Sb said in other thread that ace on 1,2 is overheating
.
.
IT ISNT!! 40-44 celcius degrees isnt high temperature. For many devices its normal temperature (galaxy s4 is hot like this when u play sth like angry birds/blocky roads). If u want to know what overheating is, then take from ur friend htc one x and run on it asphalt 8 on max setting. After 10-20 seconds u can easily fry eggs on it.
Ps. teddy, u can also hit "thanks" button "accidentally " for me too.

1200mhz
i run about mounth on 1200mhz govenor:interactive,CM11 unnoficial,battery is drain about 25-30% faster but is not problem OC down when i no need power :laugh::laugh:

artur1131 said:
Let me explain u:
U could do OC only with Performance+deadline.
The OC was rly working, i get higher benchmark scores (11200 antutu v4) and my ace get nexus-like responsibility (read: uber fast)
Buuut, Performance+deadline is combination which eats ur battery rly fast. Ur phone is using his max potential on this combo all the time, so battery is going down faster. I think that when we will get stable oc which will work with every governor+scheduler (for ex ondemandq+sioplus) it will work good. If the oc kernel will get optimized for inteligent governors (smartass etc.) which are giving u higher frequency only when u need it (when u get lagged, governor is setting ur frequency higher). it might work on battery just a little shorter than on stock.
Side effects? Processor will degrade a little bit faster, but if u arent going to use this phone for sth like 10 years then u shouldnt care about it. Screen will get burned out faster than our CPU on this OC.
As sb said 1,2ghz isnt rly high freq. STE said that 1,2 ghz is safe freq for this processor.
Battery damage? Ofc no. Ur battery wont get damaged dont worry. U can damage ur battery by charging it with ****ty noname charger or by setting ur wall charger currency too high (higher than 1Ah, when stock "safe" is 600 mAh).
Sb said in other thread that ace on 1,2 is overheating
.
.
IT ISNT!! 40-44 celcius degrees isnt high temperature. For many devices its normal temperature (galaxy s4 is hot like this when u play sth like angry birds/blocky roads). If u want to know what overheating is, then take from ur friend htc one x and run on it asphalt 8 on max setting. After 10-20 seconds u can easily fry eggs on it.
Ps. teddy, u can also hit "thanks" button "accidentally " for me too.
Click to expand...
Click to collapse
thanks get it now :good:

artur1131 said:
U wont feel any difference cuz the OC is buggy and kernels on them let u do OC but in same time they slow ur ACE2 rly hard. Only OC on wchich u dont have any hard-bad-side effects is CM10.2 (22january). But to OC on it, u had to play with terminal. On cm10.2 OC was giving lot of performance, my ace on cm10.2 (22jan) with 1,2ghz, get awesome speed and responsibility. I reccomend u to not use roms which have build in OC (now), cuz kernels inside them are making ur ace slow and laggy.
Click to expand...
Click to collapse
how to OC on cm10.2

@up
Terminal
Sent from my GT-I8160 using Tapatalk

OC on our phone have amazing effect, it feels like completely different device.
I use 1228 Mhz script, with performance/cfq, the battery on 4.4.2 Mahdi rom (btw TC 4.3.1 feels smoother) with ART is - 8-9 % for 12 hours standby. The battery obviously drains faster if you are using the phone extensively.
Here's a little bench ART + OC 4.4.2 ( can't wait for Cocafe's GPU OC kernel update :laugh: ) :
{
"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"
}

0.0 thats twice quadrant score i got before
Sent from my GT-I8160 using Tapatalk

how can i oc maclaw cm11?

No frills. Set max freq and set performance governor
Sent from my GT-I8160 using Tapatalk

No frills doesn't work for me. You can use this method to be 100 % that oc is applied :good: .
It works on all new TC source roms including maclaws builds.

avithohol said:
No frills doesn't work for me. You can use this method to be 100 % that oc is applied :good: .
It works on all new TC source roms including maclaws builds.
Click to expand...
Click to collapse
But there are only 3 available freqs there
Sent from my GT-I8160 using Tapatalk

Does your AOKP rom support latest cocafe's cocore 9 kernel GPU overclock options ?