Develop Bugs

overclocking

Hi,
Does over clocking the compact III give it more performance?
How does one overclock it in the first place?
i tried to search the artemis threads but could not find any information

Search for Battery Status Today Plugin

http://forum.xda-developers.com/showthread.php?t=282006&highlight=artemis+overclock

thanks for the response and the link
how did i miss that one ??

No problem. I had the same question a few days ago so knew what to look for. (For the record I have my P3300 at 260 using the Battery Status Today plugin and it is stable for everything including TomTom. The difference in performance is quite noticable when multitasking.)

thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?

xda_guy said:
thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?
Click to expand...
Click to collapse
Hi, not a very long term user, but my O2 Orbit runs fine at 273 with BatteryStatus. 289 seems not to be stable for me.

My P3300 runs max. at 273MHz. 286MHz makes device unstable, when it is full loaded.

xda_guy said:
thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?
Click to expand...
Click to collapse
The normal speed is 201, I believe. Overclocking creates more heat, takes more power, but seems to be stable when used in moderation (270ish max).
I had to take it off my phone because even overcloking to 210something caused me to not be able to stream video with WMP over wifi.

xda_guy said:
thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?
Click to expand...
Click to collapse
201 is the stock speed.
Overclocking could damage your device, especially if you push the edges of the chip's ability. Further continual over clocking might lessen the lifespan of the device.
That said there seem to be a good number of people overclocking to 250-260 without any obvious adverse effects. It may cause harm but for the most part seems safe as long as done in moderation. No one can say for certain though, it is a calculated risk.

Well BatteryStatus is your big friend here. The beta version (1.04) has an option called cpu scaler. I use it all the time. It works like this: you tell the program what you want to be the lowest cpu speed (for example 100Mhz) and you tell give in what the highest clockrate should be (for example 260Mhz). Depending on the load on you device BatteryStatus scales the clockspeed down or up. So when needed it gives you the extra power, and when not needed it will slow the device down, saving extra power and also saving the life of the processor.
I personally use the speeds mentioned above. But, when the speed is scaled down to 100Mhz the screen starts flickering a bit. If I were you I would not go down the 100Mhz.

Overclocking
I’ve Overclocked my XDA Orbit (O2) using Omapclock + OmapClockPlus successfully running at 264 speed anything above that doesn’t work on my phone, Reporting all programs running fine including Camera.

Dead Artemis...
JanetPanic said:
201 is the stock speed.
Overclocking could damage your device, especially if you push the edges of the chip's ability. Further continual over clocking might lessen the lifespan of the device.
That said there seem to be a good number of people overclocking to 250-260 without any obvious adverse effects. It may cause harm but for the most part seems safe as long as done in moderation. No one can say for certain though, it is a calculated risk.
Click to expand...
Click to collapse
Hi folks,
today my artemis is died.....
He only shows the start screen (T-Mobile Logo) and won´t to da any more... useing bootloader mode an flash the rom back to wm5 (WM6 was before) is successful but then is the same, only starting logo and nothing more.... (he fews me this for more than 5 hrs now....)
I used Battery Status with @ 260 MHZ...
Maybe this was the problem...
Regards,
Andy

mine's on constant 260 with xcpuscalar, no side effects, been like that for ages.

[Q] Percentage of well overclockable Desires?

Hi guys!
I haven't yet rooted my Desire(I would have but I was fool enough to install the 2.2 OTA).The main reason for me to root would be the ability to overclock my device.All this time that I have been around here on the Desire and Nexus One forums I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.However,to my great surprise,I noticed on OpenDesire ROM's thread that the Desire can be overclocked @1344MHz(which of course made me think a big HELL YEAH!).Is that number ok for all of us or for some select few?I remember from my Hero days that only some few,lucky guys like myself could overclock up to 768MHz,although there were cases of people,rare,yet not unheard of,that could overclock @844MHz.Is this the case here or are things different with the Snapdragon?
Many many thanks guys!

C'mon guys,no one?

tolis626 said:
I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.
Click to expand...
Click to collapse
I don't think overclocking to 1267MHz happens in rare cases. I had no problems oc-ing to 1267 and it seems that a lot of forum member were able to do this too.
Why don't you downgrade your HBoot to 0.80, root your phone and try it out?
Just make sure your phone does not become too hot if you try 1344MHz.

I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave

foxmeister said:
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
Click to expand...
Click to collapse
so this, its really not needed at all. a decent fast rom and 1ghz is more than enought for things to be super speedy. any decent kernal will provide more than enough speed.
overclocking(and lots of other things these days!) reminds me of that bit in jurassic park where they are all sat around the table and geoff goldblum says:
"Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should".
herein lies the lesson, just because you can do it doesnt mean you should do it.

Well,I have my reasons wanting to overclock...First off,I will check if I can see any difference in speed or smoothness.If there isn't,I will just revert the clock back to normal after some benchmarks.
I just am the kind of guy that wants to get the most out of his phone!

I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.

sbdags said:
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
Click to expand...
Click to collapse
That's what I'm talkin' about man!
And now that I think of it,it's not that much.I mean,the Hero could overclock @768,which is 45% overclocking.The Desire's 1267 is about 27% and 1344 is about 34,5%.Nothing too much!So why not?

Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.

Kinma said:
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Click to expand...
Click to collapse
Well my man,in this case the MSM7200A is no beast but rather a pooch that barks to no avail!Good pet however!
Joking aside,the Snapdragon is a beast for a mobile phone,but even beasts get beaten.Now,if I can somehow reach or even get close to the performance of the Galaxy S or the Droid X I'll be happy.Software wise I believe that HTC is far superior ,but it's hardware is a little out of date.Let's see what their new devices will do for us!
Btw,does anyone know if the so anticipated HTC Ace will be anything better than what we already have or if it will be the Evo for GSM users?
Thanks!

The desire is plenty fast as it is and I don't see the point of overclocking it. I've had it to 1267 in the past and it made no difference at all for usability. I'm also the type that overclocks all his computers...
Sent from my HTC Desire using Tapatalk

Personal preferences dude...What everyone does with their phone is their own business.I wish I could resist overclocking too!
However,I was watching a thread over at the N1 forums in which a dude named Storm9999(genius dude,not just a random one) stated that an overclock @1,3GHz could fry our phones.Is that so?I mean,I know overclocking reduces the CPU's lifetime,but is it THAT MUCH dangerous?

I think overclocking can kill your phone.. I use to overclock my own o2 orbit and it died after a year..

Friend of mine just burned his old HTC by overclocking it and as a consequence is going to buy a desire.
I had my phone overclocked at 1345Mhz for a moment, just to test it, and it made no real difference to when it was overclocked at around 1.2Ghz, which in turn has very very little difference to stock 1Ghz.
I think the only case where you see some small impact is in games.
I've tested HD recording at 1.345 Ghz and stock speed and there was no difference.
If anything, it's going to kill your battery and shorten its life for sure, going so high. If ever I will OC again I won't go over 1.1 and only if I find some tangible improvements.
As said, this phone is always fast, there is no real need to OC, other than for 'fun'.

The fun is what I want...Well,most probably I will have my phone overclocked at the maximum speed it can get for about a week or two and then go back to 1 or 1,1GHz...
Btw,your signature kicks ass andycted!

[Q] Overclock

Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:

Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.

thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.

How much is safe for overclocking?

I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.

ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
Any overclocking can be unsafe as it can shorten the lifespan of your memory and CPU. But with that said I run mine at 1200 with no issues. Most people don't go higher than 1600 but anything 1400 or lower is not going to burn it up too quick IMO. Everyones hardware will react differently though.
Sent from my Inspire 4G using xda app-developers app

They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G

ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
I run IceColdSandwich and have found 1459MHz to be the best combo of performance and stability on my phone. Every phone handles OCing a little differently, some can reportedly take over 1600 without a flinch and others will lock regularly with even a slight OC. Just experiment with the "set at boot" option turned off until you find something that works reliably on your phone.

Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2

asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think OC can affect battery drain only if you use an application which utilizes a full cpu load. But, if you're using this app in normal mode, economy will not be great also. So, when you using your phone for calling or general usage you will not see any problems with battery discharge.
I'm using DHD with Blackout v3.0 and I set 1200Mhz for maximum cpu value. I have no problems, phone is stable. Some time ago I used Leedroid ROM and set also 1200Mhz, but phone was rebooted by itself very often. More than twice a day.
You should try to use OC, as someone said above, without "set on boot" option. I think there is no danger for hardware up to 1600Mhz.

asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Click to expand...
Click to collapse
Not under normal use. There's a school of thought that says even though the increased speed requires more power, it can also finish tasks and go back to sleep faster, so it ends up being a wash. I've overclocked all three smartphones I've owned to date and haven't experienced any significant difference in battery life.

ai6908 said:
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
Click to expand...
Click to collapse
They say that as a precautionary measure just as they say flashing a custom ROM can be dangerous. For people who don't know what they're doing. But precaution aside, just like you said you can go up to 1600 MHz safely on this phone. I know every phone behaves differently but on average no one has issues upto that frequency. But above that frequency the phone might be unstable. The CPU will be drawing much more power at high frequencies and will heat up more. The CPU heating up too much and too frequently reduces the life of the CPU. So it's not a myth.
Sent from my Desire HD using xda premium

2ghz.... the phone is old now. Make it bleed.
Sent from my Desire HD

Don't try to Cross above 1600.

Does undervolting really save battery life?

Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
What part of "you won't save more than 2%" you didn't understand?

ilusi0n_ said:
What part of "you won't save more than 2%" you didn't understand?
Click to expand...
Click to collapse
Well, i don't really understand WHY it doesn't save more than 2% of the battery life. Afaik, EXUV does reduce heat and improve battery life by miles. But that's what I thought. In reality which is this, im not rly sure why that even with EXUV, it still cant save more than 2% of the battery life.
Sent from my S800 China Phone

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
I'm not technically expert with things like this but I have read an article/ blog before that undervolting may damage a phone since it was designed to work with that specific voltage. So, I actually didn't do that even UC or OC. Just saying.....

Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)

r25txe said:
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
Click to expand...
Click to collapse
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/samsung-kernel-msm7x30/commit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware

sir mordred said:
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/sa...mmit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
Click to expand...
Click to collapse
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.

So to sum all this up. We just have to leave the CPU & voltage tables alone since it damages hardware?
Via the Internet

It's not that you have to, but that chip designer recommends it.

r25txe said:
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
Click to expand...
Click to collapse
That was also the POST that I'm referring to that I've read :good: