Develop Bugs

[Q] Have we hit the limi (true overclockin?)

I know we can dynamically scale our CPUs and have unlocked the frequencies it is allowed to scale to...
But when [and how] are we going to get cracking at really OCing? Im sure we can hit 1.4 or so? Any thought?
I don't want any 'omg blow up im an idiot' posts. Serious ****

Not saying we can't...but 1.4 would be a 40% increase in power... I doubt we can reach those numbers in a safe daily use way.

Being that half the Evos can't run 1.19 stable..... Good luck
Sent from hell using XDA App

surrealmethod said:
Not saying we can't...but 1.4 would be a 40% increase in power... I doubt we can reach those numbers in a safe daily use way.
Click to expand...
Click to collapse
I ran 768 on occasion and 710 all day every day on my Hero.. 710 is roughly a 34.5% increase so I would bet we (by we I mean they, the people who are smart enough to understand kernel dev) could get close to 1.4..

I run my palm pre at 1ghz that's 50% more, im sure one day it will happen
Sent from my PC36100 using XDA App

Doesn't the extra heat generated hurt with no way to add cooling? (I'm talking if you go 40-50% OC)

surrealmethod said:
Not saying we can't...but 1.4 would be a 40% increase in power... I doubt we can reach those numbers in a safe daily use way.
Click to expand...
Click to collapse
1.4 is not a 40% increase in power. You have to bump voltages to reach that kind of speed, which means even more power consumed.

Unless I'm wrong, doesn't 1000×1.4 (40%) = 1400MHz (1.4GHz)?
AzN1337c0d3r said:
1.4 is not a 40% increase in power. You have to bump voltages to reach that kind of speed, which means even more power consumed.
Click to expand...
Click to collapse

oskinosmee said:
I run my palm pre at 1ghz that's 50% more, im sure one day it will happen
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Pre is 600 MHz stock so thats not a 50% increase, its more like 64%, and the Pre hit 1.2 GHz, which is double. Be nice to see some ridiculous kernels for the people (not me) who have 3 extended batteries and just want to show off, but I'm satisfied running at 1.19 GHz daily, I'm sure if i left it at 1 GHz i wouldn't even notice the difference.

I was running 1.3 on the Droid full time with no problem.

Tilde88 said:
I know we can dynamically scale our CPUs and have unlocked the frequencies it is allowed to scale to...
But when [and how] are we going to get cracking at really OCing? Im sure we can hit 1.4 or so? Any thought?
I don't want any 'omg blow up im an idiot' posts. Serious ****
Click to expand...
Click to collapse
right about now it's looking like 1.19 is the max where you will still see performance boost with it being detrimental to the system. i'm not so much worried about cooling. i recently threw a hdd in a fire that exceeded 1000ºf and the chips didn't burn. so i really dont think he have to worry too much about frying the circuit board. it's just what they can be increased to and still increase real performance

[Q] Quadrant Benchmark Frequency changes 400, 600, 800mhz but never 1Ghz?

Hey all,
Noob here, i noticed under "current frequencies" in the Quadrant Benchmark that it jumps between 400 and 800mhz but ive never seen it at 1000mhz. Is this normal or should i bring it to the sprint store to get it checked out?
Thanks!

Quadrant probably doesn't need the whole 1000 mhz to complete its tasks. You should instal set cpu and set it to performance mode and then try it
Sent from my SPH-D700 using XDA App

hmm im currently running stock, i need to be rooted inorder to use setCPU right?

Joeway124 said:
hmm im currently running stock, i need to be rooted inorder to use setCPU right?
Click to expand...
Click to collapse
that's right.

News flash: Quadrant sucks and is woefully inaccurate, use SmartBench 2010 or GLBenchmark.

Yes quadrant sucks. About your question... It shows the frequency that it's running at that time. It's not made yo run at 1000 all the time for battery purposes. When u start quadrant, since it's an intensive on your CPU, I'm sure it scales to 1000. Mine didn't used to show 1000 either until I starting using CPU tuner.

yeh, i know watcha guys mean, thanks!

(Q)I have a og evo and cant overclock it 1.2ghz.

I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium

Each Evo is different. Some of them can't handle that high overclock, or can't be undervolted very low. Each one is different, each has its limits.
I don't understand the big deal with overclocking. It burns your battery faster. I personally underclock, with little to no lag and is good enough for my casual gaming needs

Mine doesn't like a clock much at all. I can get about 1.1 before it starts locking up but even then it hangs a lot. I honestly don't see a difference from 1.0 to 1.2. Get a decent rom, good kernel and try out the v6 script an I almost guarantee you will like that better.

beaumontcali48 said:
I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium
Click to expand...
Click to collapse
Well for us to be able to help you, you would need to provide us with more details on how you are trying to accomplish this.

I use no frils cpu but have also tried setcpu and viperMOD I know that's the best way to overclock but is very confusing. Have any step by step instructions to of to 1.2 I know having higher voltages helps as well.
Sent from my Nocturnal 4G using xda premium
Sent from my Nocturnal 4G using xda premium

Overclocking is overrated. If you need to overclock for every day usage, then something is wrong - at least in my opinion. Resource intensive gaming is different, but you shouldn't need to overclock for browsing, texting, casual games, etc.
Try out the V6 Supercharger script. I'm not currently using it, but have in the past and it seemed to make my phone more snappy. A lot of people swear by it and it's a great script, definitely worth a shot. There are other things you can do to speed up your phone without overclocking. I'd try other options first since overclocking will chew through your battery. Increase the dalvik vm heap size, there are plenty of free apps on the market to help with this task. Uninstall apps you don't use, I'll bet that you never use some of the apps on your phone. Back them up with Titanium Backup and you can restore them if you ever need them again.
In case you didn't already know, the Evo can't overclock past 1.2, I'm not 100% sure why - it has something to do with the processor.
Supersonic Evo 4G | MIUI | Tapatalk

I never oc over 1075 and only when plugged in if i play a game I need to oc.for I just activate my charging profile and plug up and play 1.2 ghz is a good chance of doing serious.damage as these older scorpion processors get very very hot at that clock speed so they lock up to try and protect themselves from heat damage or they shut down the phone 1075 is as high as you should need to go for any games the evo can handle on the subpar gpu
Sent from my Classic-EViLizED-ToMAToFiED-EVo4g-

beaumontcali48 said:
...also tried setcpu and viperMOD I know that's the best way to overclock.
..
Click to expand...
Click to collapse
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!

shift
Get a shift. Mine runs fine at 1.9. But usually run it art 254-1200 on demand.

{ParanoiA} said:
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!
Click to expand...
Click to collapse
You can overclock and undervolt together just fine. You just need to ensure that every frequency has a high enough voltage to run the processor at that step. My Evo is overclocked and undervolted just fine, although IIRC I can only push it up to 1.1 GHz . My tablet is 1ghz to 1.6ghz and is undervolted as well, though.

merge rls 2.0, iron monkey, Droid overclock because of the profiles options. I set up four profiles including one for temp. sometimes i'm underclocking and sometimes overclocking but only up to 1.19 to prevent freeze and boot loops. Only downside is right at open Droid overclock needs su permission but that is my choice since profile changes at open.
Very snappy afterwards.
Sent from my PC36100 using XDA Premium App

When I had the 4G, I was never able to go above 1118, or somewhere around that. It would have freezing issues.
On my evo shift, I was able to do 1.7 gHz (compared to stock 800 mhz) ok. 1.6 pretty reliabily, and I could run 1.5 all day long. Some guys could do 1.9. It just depends on the phone.

Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium

tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Shoot the brutha a link
TrevE Supporter!

tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101

Yea shot me the link too bro.
Sent from my PC36100 using xda premium

First let me say I don't use viper mod or any voltage controlling mod.
On sense 3.0 roms such as mikg I over clock to 1152 and set the minimum to 384 and its smooth as butter. No problem and battery lasts all day.
On aosp however such as decks (I'm on it now) I underclock to 499 and leave the min at 254. Smooth as always and battery lasts forever.
Anything past 1152 is going to cause problems (at least in my experience) also the rom/kernel can effect how much you can overclock.
Sent from my PC36100 using xda premium

Gary13579 said:
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Its counter productive because it is giving less to something that needs more. (Don't take this post as me trying to be a ****. Just voicing how someone explained it to me a while ago)
Think of this as cars.
Lets say you have a nice fancy v8 mustang. Stock, everything is well, balanced.
If you start adding parts and get it pushing out 1000 horsepower (overclock) your most likely gonna need more feul (voltage) or at least stock amount flowing into the engine just to keep it running.
Now lets say you got that same 1000 horsepower gas destroying mustang and you start to lower the amount of gas flowing into the engine (undervolt (done in vipermod)) cylinders (CPU) wont get enough gas, it wont work, and your stuck going no where.
So if that made sense (did to me) then you can see why they are counter productive. Unless your using vipermod to overvolt (which idk if you can since I don't use it) then you can disregard this whole post
Sent from my PC36100 using xda premium

Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101

Gary13579 said:
Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Hmm, *interesting*. I believe the best answer to the OP was covered rather well earlier. It's all about your rom/kernel/hardware combination. With all the variables to consider as relevant, your best bet is to experiment and find what works for your device. Don't check set on boot untill you are confident the set-up is stable. Higher is not always better with overclocking. My device runs blazingly well underclocked @768max. Gets insanely great battery @499max. However my quadrants are better @ 1036 than at 1190.
Great thing about android is you can experiment and learn through trial and error.
Sent from my PC36100 using xda premium

[Q] How low can we go? (Undervoltage)

Okay I have tried searching, but it is a bit hard from my phone, so I'm sorry if I missed a post answering this.
Does anyone know how low UV this phone normally goes? In miui I could go as low as it allowed (750?) at the slowest CPU setting, but I wonder how low others go. I know it differs from one phone to another, but still..
Sent from my HTC Vision using XDA App

Our phone can usually only go down to about 850 but what you'll have to do is test each voltage for each clock speed, so what you would do is set the voltage (TEMPORARILY!!! THIS IS VERY IMPORTANT!) then set your clock speed to be only this speed to see if it is stable. IE: Set ~200 to 850, set clock speed to only ~200 (whatever it is for miui kernel, they are all different by a little bit) and then go around the ROM and look for any HARD lockups (lockups that require a battery pull, lots of lag and lag spikes are to be expected) and then turn screen off for like 30 secs and back on to check it. Do this for all clock speeds (if you want to change them all) For the record, AFAIK if a clock speed has a certain voltage, all clock speeds below it will be stable at that voltage. Once you get up to ~700 MHz also test it with some video. This should work if you want to be SUPER thorough but make sure you always TEMP first (because if it cause's a hard lockup, that will cause major problems...) also do a nandroid first just in case.
For the record, undervolting can be risky, so I am not responsible if you cause damage, just giving you a means of doing it

The lowest I've gone was 750 and works perfect. I don't want to go any lower though, phone's still eating up 32maH with screen off.

Thanks for the explanation. I already know how it works though and I'm being super careful. I was more interested in finding out what settings others use. So what are you at at other CPU speeds?
I test stability with Stability Test (I think its called) and some benchmark apps. Then try different stuff like movies, flash (like in a browser, not flashing anything) and turning the screen on and off. With temp settings in oc/uv beater.
--------------------
Sent from my HTC Desire Z using XDA premium

Does anyone know what scenario causes the most voltage drain from the CPU? Playing HD video? Crunching numbers (pi?)? Shooting pigeons?
Hmm, let me rephrase that
Name the 3 best ways to test stability when tweaking undervoltage

theres an app i found yesterday to test the stability of my SG2 its call "stability test" just set your core at that fixed clock and let it go...i just let it run 3-4 times after that if its good then i move on, but sometimes i feel the phone sluggish, i just increase the voltage on that and its fine again.
too much voltage burn the thing/ kill the battery, not enough voltage it starting to freeze up.

Yes I know the app and it's great! But I'm playing around with my own little app project so I was interested in what everyone use to test stability. That would be +1 to number crunching so far

Although I am starting to feel like I'm talking to myself I'll still post my (hopefully stable) undervoltage results if anyone should be interested:
Code:
245760: 750
368640: 750
576000: 900
768000: 900
806400: 925
902400: 925
1017600: 975
1113600: 1000
1209600: 1050
1305600: 1100
1401600: 1150
1507200: 1225
1574400: 1300
I'm testing a small app I'm coding, to learn more about Android, so the numbers will probably change as I learn more and get better at coding and testing the stability of my phone.
Also please remember your phone is going to be different than mine, even if the hardware is exactly the same, so this is only a rough guide.
Sent from my HTC Desire Z using xda premium

How do you undervolt with the default CM7 kernel?

[Q] CPU Throttling on JB 4.1

I recently installed Houstonn's JB port on an Optimus E973 and find the CPU throttling to be really aggressive compared to stock ICS. The port works perfectly for me (no wifi issues, etc), but the CPU will spend very very little time at 1.5 Ghz and will throttle down to 1.1 almost immediately. Its actually so severe that in terms of user experience, JB seems slower when you use the phone for more than a few minutes.
There was some discussion/consensus that the throttling on ICS was dependent on battery temp, but in JB it seems to depend on CPU temp now (throttling will still occur when battery is < 30C). Just wondering if anyone has a similar experience or can shed some light on this change? Thanks.

I am experiencing the same thing. Not noticing performance issues but noticing the throttling.
Sent from my LG-E973 using xda app-developers app

lunde20b said:
I am experiencing the same thing. Not noticing performance issues but noticing the throttling.
Sent from my LG-E973 using xda app-developers app
Click to expand...
Click to collapse
The throttling will happen no matter what - its to keep the cpu, battery, etc cool enough to prevent damage. I had throttling on ICS but it wasnt noticeable either. Most of the time the CPU would ramp up to 1.5 and get the job done quickly. Since I have upgraded it will only ramp up to 1.1 ghz for the most part (sometimes it will increase to 1.5, but that is uncommon).
I know that Quadrant is next to useless for comparing between phones, but I like to use it for monitoring changes in the performance of a single unit. On ICS, my LGOG would routinely get scores of 7300+ until the phone got quite warm and then it throttled down. On JB I have never seen a score above 6700 and the loss is entirely due to CPU score. Checking CPU Spy shows me that the CPU never hits 1.5ghz throughout the test, even when run on a cool phone.

Aha... found something of interest here.
The odd frequencies of this JB rom have been reported elsewhere.