Develop Bugs

How can i overlock my htc evo? Is it safe?

Sent from my PC36100 using XDA App

http://forum.xda-developers.com/forumdisplay.php?f=652

I've had my phone overclocked 15% for months now...I pre-ordered and picked it up on June 4th (the day they were released to the public) and it's never been replaced. I rooted it right away using the engineering hboot method, and I immediately went to a rooted stock rom with a kernel that'd allow overclocking the very first time I saw one posted on this forum. I've never been able to run it at anything higher than 1152 mhz, but I've also never had any stability issues at 1152 mhz. I also allow it to go as low as 128 mhz all the time.
Since then I've played with various roms, and various kernels, but the first thing I've done when changing any rom or kernel, is always set the min and max CPU speeds again, and decide which governor to use. I've also always played with the undervolting strategies, from static to HAVS, and I've always been able to get away with the most agressive stuff posted without any stability issues.
Your mileage may vary, but thats been my experience with an overclocked Evo. I will admit I can barely notice the performance difference from 998 mhz to 1152 mhz, but I actually notice a battery life improvement...get it done faster so the CPU can go back to idling at a low frequency as soon as possible mentality I guess.

please watch what you say here. its not going to get you any help to curse and swear at other members. last warning

@MikeOD, which governor and what governor parameters have you found to work best for you?
I think the whole overclock boils down to what you do with your phone. If nothing overly cpu intensive, then there's likely to be little gain in the amount of saved time.
I actually have mine under clocked at 921 Mhz (came that way in the rom initially). UI was fluid enough and everything still seemed to work well/responsive. I get slightly better battery life too. Noticeable in the rate the batt % declines during active tasks (web browsing).

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] franco.Kernel v141 Stock Voltages

So, I know we all have different phones, and after looking at a review of some voltages to try, I changed all the stock voltages to the ones I saw and saved them as default (don't ask me why, I do not know myself). Since this, I set my phone to hotplug and the phone has had multiple Sleep of Death cases. I think it has to do with the voltage but it could just be my phone not liking hotplug because it stops if I turn off hotplug. Or hell it could be that both together are causing it. So I was wondering could someone provide me with stock voltages at 384, 729, 1036, 1228 and 1344 mhz. Or better yet if you could provide me with the best voltages that help save a little battery life. Thank You! (Also I have been looking but have not found the stock voltage for the numbers I listed above)

stock voltages are 1025, 1203, 1317, 1380. 1350mhz is not a stock clock speed so theres no stock voltages. you can try these undervolt values, they are pretty conservative 850, 950, 1050, 1175 and 1250. remember to do nandroid backup first.
undervolt will not really gain you any noticeable difference in battery life, the cpu uses relatively little power to begin with so reducing it by a few hundred mv is not going to make a different with normal use. If you want to try it out just start from stock and go down 25-50mv at a time and test it with some games or stress test.

neotekz said:
stock voltages are 1025, 1203, 1317, 1380. 1350mhz is not a stock clock speed so theres no stock voltages. you can try these undervolt values, they are pretty conservative 850, 950, 1050, 1175 and 1250. remember to do nandroid backup first.
undervolt will not really gain you any noticeable difference in battery life, the cpu uses relatively little power to begin with so reducing it by a few hundred mv is not going to make a different with normal use. If you want to try it out just start from stock and go down 25-50mv at a time and test it with some games or stress test.
Click to expand...
Click to collapse
Thank you. If they really don't make a difference I will leave them be at stock. Any good value for 1350? Or should I just stick with 1250mV? Just really trying to get 2 days out of the phone, but I assume I cannot complain since I am already getting 4h of screen time with normal use on the 2000mah battery. I will look around here some more and see if I can find any more useful tips on better battery life. Thanks again!

neotekz said:
stock voltages are 1025, 1203, 1317, 1380. 1350mhz is not a stock clock speed so theres no stock voltages. you can try these undervolt values, they are pretty conservative 850, 950, 1050, 1175 and 1250. remember to do nandroid backup first.
undervolt will not really gain you any noticeable difference in battery life, the cpu uses relatively little power to begin with so reducing it by a few hundred mv is not going to make a different with normal use. If you want to try it out just start from stock and go down 25-50mv at a time and test it with some games or stress test.
Click to expand...
Click to collapse
I wish I would have read this post a few days ago prior to changing my voltage settings also. Only to learn that I wasn't doing my GNex a significant favor.

falconfan said:
I wish I would have read this post a few days ago prior to changing my voltage settings also. Only to learn that I wasn't doing my GNex a significant favor.
Click to expand...
Click to collapse
Ya thankfully read it, tried these voltages with hotplug on and screen off settings and the phone did not sleep of death this time, but it froze right after wakeup, so no hotplug for me, just conservative.

Also, be very careful with CORE and IVA undervolting. In my case, undervolting theese too much caused the exactly same issue you are dealing with. Same goes with profiles for SetCPU profiles which also causes the phone to behave like that in some cases

keem85 said:
Also, be very careful with CORE and IVA undervolting. In my case, undervolting theese too much caused the exactly same issue you are dealing with. Same goes with profiles for SetCPU profiles which also causes the phone to behave like that in some cases
Click to expand...
Click to collapse
So for what I can make out from your post, some reason its setcpu profiles not working, not the phones cpu itself not allowing it be put into hotplug mode? also, sorry for the noob question but what is the difference between CORE and IVA undervolting? Or should I say could you explain them to me.

If you are going to use profiles, your phone should be very stable. In other words undervolting makes it instable if you tweak it too much. Core and iva are very sensitive. Core is your graphic gpu. Let them stay at the normal settings. Use milestone franco stable build undervolting only the cpu. Rather 700 mhz at the lowest. Try it out
EDIT: "If you are going to use profiles, your phone should be very stable BEFORE setting profiles"
Sent from my Galaxy Nexus using xda premium

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

Setting CPU GOVERNORS

Guys im on slimbean im not aware of the governors thing its just increasing the cpu frequency for all i knw. Now,,,i had seen it on ma old galaxy y with hyperion 8 final build and now on ma grand with slim but as soon as i open the performance menu in advanced options it gives me a warning bout hardware is it really harmful for hardware setting cpu at its highest freq,,im in lve wid slim buh after setting d freq to highest m just addicted ma phone flies on performance does it harm ma cpu d hardware part pls help @iceyhotguy
May be u can
{
"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"
}
Sent from GT-I9505 using slimbean unofficial 20131115 the BEST rom

Sulaimanshariff said:
Guys im on slimbean im not aware of the governors thing its just increasing the cpu frequency for all i knw. Now,,,i had seen it on ma old galaxy y with hyperion 8 final build and now on ma grand with slim but as soon as i open the performance menu in advanced options it gives me a warning bout hardware is it really harmful for hardware setting cpu at its highest freq,,im in lve wid slim buh after setting d freq to highest m just addicted ma phone flies on performance does it harm ma cpu d hardware part pls help @iceyhotguy
May be u can
Sent from GT-I9505 using slimbean unofficial 20131115 the BEST rom
Click to expand...
Click to collapse
brother there is no big deal if you are not overclocking very much i mean to say that dont set max frequency too high also in performance even in low max frequency there is a observable change in phone performance so if you can dont use overclocking
but if you want do it within a safe zone i mean to say dont set max frequency too high cos setting max frequency too high gibe following problems
1 battery llife decreases cos it provides strenght for performance and in setting governor to performance you are killing it even more
2 sometimes phone becomes too hot from back
3 life of phone decreases
4 random reboots { not always }
remember brother all these points that i told you above are not always applicable to all devices on equal proportion as every device has different hardware and software interface so dont overclock your phone much
you should also wait for reply from @iceyhotguy i think he will also give you some help
good luck :good::good::good::good:

aditya rathee said:
brother there is no big deal if you are not overclocking very much i mean to say that dont set max frequency too high also in performance even in low max frequency there is a observable change in phone performance so if you can dont use overclocking
but if you want do it within a safe zone i mean to say dont set max frequency too high cos setting max frequency too high gibe following problems
1 battery llife decreases cos it provides strenght for performance and in setting governor to performance you are killing it even more
2 sometimes phone becomes too hot from back
3 life of phone decreases
4 random reboots { not always }
remember brother all these points that i told you above are not always applicable to all devices on equal proportion as every device has different hardware and software interface so dont overclock your phone much
you should also wait for reply from @iceyhotguy i think he will also give you some help
good luck :good::good::good::good:
Click to expand...
Click to collapse
Thanks for the reply bro for now i have set governors on performance and frequency is 1200mhz whichs d highest and my device is blazing fast i jist wanna know is it harmful using highest freq on a daily basis i really need a better battery backup should i set it to the default???and also is it harm for ma hardware in any way now or in future???
Sent from GT-I9505 using slimbean unofficial 20131115 the BEST rom

Sulaimanshariff said:
Thanks for the reply bro for now i have set governors on performance and frequency is 1200mhz whichs d highest and my device is blazing fast i jist wanna know is it harmful using highest freq on a daily basis i really need a better battery backup should i set it to the default???and also is it harm for ma hardware in any way now or in future???
Sent from GT-I9505 using slimbean unofficial 20131115 the BEST rom
Click to expand...
Click to collapse
yes brother yes it will be harmful please decrease max frequency to some extent
also if you want better battery life you should set cpu governor to ondemand or conservative

Ive done it tnx again
Sent from GT-I9505 using slimbean unofficial 20131115 the BEST rom

Sulaimanshariff said:
Thanks for the reply bro for now i have set governors on performance and frequency is 1200mhz whichs d highest and my device is blazing fast i jist wanna know is it harmful using highest freq on a daily basis i really need a better battery backup should i set it to the default???and also is it harm for ma hardware in any way now or in future???
Sent from GT-I9505 using slimbean unofficial 20131115 the BEST rom
Click to expand...
Click to collapse
Hey, ok to start with, you cannot overclock your grand. Overclocking needs a kernel that supports certain features and higher frequencies and sadly there is no stable custom kernel we can use right now. Overclocking would mean pushing the maximum frequency to about 1400-1500MHz.
Secondly, I'm almost sure 99.9% of grand are set to Max 1200 and Min 312 MHz because that's the default setting that comes with the phone and it makes sense to keep the minimum at minimum and maximum at maximum. And this is same for most phones, not just Samsung. OEMs put a max limit lower than the max power of the processor to avoid overheating and any damage it might cause if the processor reaches its full frequency too often, Overclocking unlocks the full potential your processor can reach. So basically it is more than safe to keep the maximum at 1200, but minimum should be set low, as that is the frequency your phone wakes up in each turn your screen on.
Only reason to lower the max frequency would be if your phone is heating up too often.
Now, regarding governors and I/O schedulers, these are the main things that are good about custom kernels.
Governors are are controllers of how your frequency scaling is handled, in other words, it controls how often and in how big steps your frequency jumps to a higher step (312 to 600 to 800 to 1200)
I/O schedulers is how your phone manages how to assign processing time to each task or app your phone runs. Depending on this your phone runs better for the process that is started first (noop scheduler) or focuses on multitasking, while giving all apps share of the processor (cfq scheduler)
I personally don't prefer Performance governor as it keeps the phone at max frequency, which is great for gaming but for day to day use it uses more battery and in long term could damage your processor
My preferences, Governor : Interactive and I/O : cfq
All Governors and I/O are explained here :http://forum.xda-developers.com/showthread.php?t=1989824
Once we get custom kernels going we can have more Governors and I/O
EDIT : Oh and make sure you arent using any third party apps to set your frequency, governor and i/o if you are using Settings>Advanced>Performance. Basically use just one thing apps or settings, otherwise it'll cause a conflict

So ultimately now i aint using the Governors roflol m afraid so i hve set it on demand one mre thing i would like to ask is slimbeans kernel not a complete custom kernel???
Sent from GT-I9505 HAPPY FLASHING^_^

Sulaimanshariff said:
So ultimately now i aint using the Governors roflol m afraid so i hve set it on demand one mre thing i would like to ask is slimbeans kernel not a complete custom kernel???
Sent from GT-I9505 HAPPY FLASHING^_^
Click to expand...
Click to collapse
Try around all governors, they are all safe and that's why I gave you the link, it's a 2 line review on all governors and I/O and you can use any of them without worrying . The damaging processor thing happens over very long periods of time. I have played with almost all processors on different phones, nothing bad will happen. My favorite one is smartassV2.
And no all custom ROMs have the basic kernel from CM10.1, that's why they have only the default features and governors.
We will have to wait for k2wl or another developer to create a custom kernel, preferably for CM10.2 when it is stable, because then all these ROMs will be upgraded to 4.3

iceyhotguy said:
Try around all governors, they are all safe and that's why I gave you the link, it's a 2 line review on all governors and I/O and you can use any of them without worrying . The damaging processor thing happens over very long periods of time. I have played with almost all processors on different phones, nothing bad will happen. My favorite one is smartassV2.
And no all custom ROMs have the basic kernel from CM10.1, that's why they have only the default features and governors.
We will have to wait for k2wl or another developer to create a custom kernel, preferably for CM10.2 when it is stable, because then all these ROMs will be upgraded to 4.3
Click to expand...
Click to collapse
Roflol ookie now will agn switch over to performance
Sent from GT-I9505 HAPPY FLASHING^_^

Sulaimanshariff said:
Roflol ookie now will agn switch over to performance
Sent from GT-I9505 HAPPY FLASHING^_^
Click to expand...
Click to collapse
Try interactive, it is good for both performance and battery backup. If you use performance, you might face reduced battery time.

iceyhotguy said:
Try interactive, it is good for both performance and battery backup. If you use performance, you might face reduced battery time.
Click to expand...
Click to collapse
thanks for giving abundant information