Develop Bugs

How do I overclock my HTC Touch Pro 2?

Hy,
I saw on the internet that someone has clocked his HTC Touch to 800mHz. But I wanna know how I can do that two! A small increase of the total mHz is also welcome. (600+mHz). I hope that someone can help me
Thanks
regards,
Sami

I second this
Greatly appreciated if someone can help.

Someone on the internet posted a screen of his Touch Pro 2 (clocked to 800mHz) nuerom.com/BlogEngine/post/2009/09/06/Touch-Pro-running-at-800MHZ.aspx
But there is no tutorial how to do it....

That link you provided is for Touch Pro (Rapahel) not for Touch pro 2 (Rhodium)
As far as I know there is no way to overclock the Rdodium processor...
(hope I´m wrong)
{
"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"
}
Some updates, Touch Pro 2 Stuff
by no2chem
17. septiembre 2009 14:25
On Overclocking
I still haven’t been able to identify how to control the PLL properly. I need to look into Linux/Android code, where they apparently have the Kaiser running at 528MHz just fine. Again, once I figure this out, the tool will be updated.
On The Touch Pro 2
I got the Touch Pro 2 from Sprint, finally – and can begin working on it. I’ll have a version of the battery driver with FastCharge, Temperature Override and 1% soon, I’ve already disassembled/reassembled it, it’s just awaiting my patches. I’ll probably post a review soon, but the best part of this phone is the screen. If you haven’t seen one, go and look at one. I’d say some of the major cons are the price (on Sprint), the missing tab button and the lack of a flashlight. It is definitely faster according to my reference benchmarks on stock. This will be my target device for a CE6/CE7 BSP as well now.
Click to expand...
Click to collapse
More info:
http://nuerom.com/BlogEngine/post/2009/09/10/Why-we-cane28099t-do-7e600MHz-yet.aspx

orb3000 said:
That link you provided is for Touch Pro (Rapahel) not for Touch pro 2 (Rhodium)
As far as I know there is no way to overclock the Rdodium processor...
(hope I´m wrong)
More info:
http://nuerom.com/BlogEngine/post/2009/09/10/Why-we-cane28099t-do-7e600MHz-yet.aspx
Click to expand...
Click to collapse
It's the same internal chipset (MSM7xxx series), so theoretically it should work. IIRC the OMAP overclocker works on almost all the OMAP-based phones on XDA. If anyone's interested in trying it, you can download the overclocker here.

DaveTheTytnIIGuy said:
It's the same internal chipset (MSM7xxx series), so theoretically it should work. IIRC the OMAP overclocker works on almost all the OMAP-based phones on XDA. If anyone's interested in trying it, you can download the overclocker here.
Click to expand...
Click to collapse
Yeah, that is true, but to this date I haven´t heard of anyone who has tested with successful results
Anyone?

orb3000 said:
Yeah, that is true, but to this date I haven´t heard of anyone who has tested with successful results
Anyone?
Click to expand...
Click to collapse
I am fixing to test this in a few minutes.
Wish me luck!

Good luck! Let us know what happens and you might want to be out in the cold just in case it overheats.

For some odd reason, it doesn't show the 700+ MHZ Clock..
I can underclock easily though if that helps anyone with battery life.
Hmmm..

I´ve read that they (nuesoft) are working on it
Hopefully soon we see some tool that works with Rhodium!
let´s keep this thread alive so soon as anybody has an update will post it here
-----
And don´t forget to vote!

rossle12 said:
I can underclock easily though if that helps anyone with battery life.
Click to expand...
Click to collapse
Really? How much of a boost do you get? If underclocking is stable, that'd be a huge bonus. Most of my mobile tasks don't require running a full clock.
I've checked nuerom pretty regularly since September to see if there's any news, but I had no idea it worked at all on TP2. My impression was that, despite sharing a processor with TP1, this item wasn't compatible for some reason. Maybe I was just reading too much into the errors people were getting due to it being early in development.

It would be great if the TP2 can get some more mHz. Thanks for the replies. Lets hope there will be soon a app that will clock the TP2 to a higher level Would like it!
So keep us updated if you've heard something or if you need someone to test a app
Regards,
Sami

fortunz said:
Really? How much of a boost do you get? If underclocking is stable, that'd be a huge bonus. Most of my mobile tasks don't require running a full clock.
Click to expand...
Click to collapse
It worked stable, even at 19.20mhz, but it was extremely [email protected][email protected]
Haha, do NOT run it lower then 100, it will kill you. Easy to fix though, just soft reset.
Works great when I'm out without a charger
Edit: It gave me another 2-3 hours at 384mhz I believe

rossle12 said:
It worked stable, even at 19.20mhz, but it was extremely [email protected][email protected]
Haha, do NOT run it lower then 100, it will kill you. Easy to fix though, just soft reset.
Works great when I'm out without a charger
Edit: It gave me another 2-3 hours at 384mhz I believe
Click to expand...
Click to collapse
2-3 hours of USE, or just standby?
(thanks for responding )

Nothing new on the overclock development on the touch pro 2 yet???

you can try racing stripes or flame decals. maybe even a spoiler. everyone knows that makes things go faster.

fortunz said:
2-3 hours of USE, or just standby?
(thanks for responding )
Click to expand...
Click to collapse
Only for texting mostly, but yes usage.

The Jack of Clubs said:
you can try racing stripes or flame decals. maybe even a spoiler. everyone knows that makes things go faster.
Click to expand...
Click to collapse
hahah maybe I should try that

Ooo im waiting for this too!

It's Not there Yet.
I am also waiting for that.

[Benchmark] 3D/OpenGL Performance Across ROMs [28/07/10]

Hi.
I'm have now rewritten the Spreadsheet and will shortly be integrating my CPU benchmarks and GPU benchmarks into the same sheet (not really that interesting or anything but it's there if you want to see exactly how things are worked out) but it explains why the progress has been slow recently. I have now taken this thread over from Arkymedes - and a HUGE thanks to him for creating the spreadsheet and doing most of the benchmarks which are still being referenced in them. He has done a brilliant job!
This page will continue to keep the tests strictly to GPU performance. CPU performance can be viewed here.
(like Arkymedes) I will take in consideration the clock used in each ROM and try to use the maximum allowed by the kernel using SetCPU. HOWEVER, all rom's will be tested at 691 MHz for consistency and any other frequencies will be detailed.
About JIT, unfortunately, all Arkmedes tests show that it doesn't affect 3D performance YET, since all this apps are not properly optimized and didn't take JIT into account. However, this may change with Froyo builds so keep an eye out.
All the ROM's clocked @ 691MHz "Performance" under SetCPU, unless specified otherwise. All tests are conducted 5 times and an average is taken. The tests are carried out in Aeroplane mode with no widgets running on the desktop. No apps are installed aside from the benchmark apps and Apps2SD is used (if enabled by the ROM). The latest version of the benchmark software is always used (they usually only add support for new phones in updates rather than changing benchmark parameters).
Benchmark apps:
Neocore - Qualcomm's own benchmark tool for 3D performance. Measured in FPS
Benchmark - Softweg's test suite for benchmarking. Only the GPU test done here to account for 2D performance. Measured by an internal score.
An3DBench - Tests based on jPCT, a free 3D engine for Java. 7 tests showing the capabilities of the engine. Measured by an internal score.
Note that all the tests mean: The higher the score, the better.
Anyway, here it goes
{
"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"
}

A little suggestion: you should specify wether whe rom is sense or vanilla, and also the CPU clock used for the tests.

Can't wait!

that's a long couple of hours.......

Are you going to do VillainROM 10.2 with Sense + JIT enabled? If not I can try and do a benchmark.

Thread updated

Please Note:
I believe in the EzHero 2.7 stats, that jit is not enabled, with jit EzHero 2.7 is equal or greater than EzHero 2.0

maybe link each of the roms in the first thread for people to easily find...being quite new here i cant fins the Androbin-cr2-5.0.7...what ever that one is...

Your efforts are highly appreciated, good job.
But there is a problem: you didn't say which ROM is JIT enabled and which is not, because as you see CPU benchmarks have better results on JIT enabled ROMs, even though, as you can see, 3D is not affected.

My bench marks
My benchmarks with EzHero 2.7+ JIT:
Linpack- 4.886
Neocore w/ sound- 30.2FPS
Neocore w/o sound- 33.2FPS
Quadrant Standard- 280
Benchmark Pi- 7222 milliseconds
Very good job on the post, well done keeping us informed!

Hello!
What I'm trying to do here is to benchmark any version that I can find in these forums WITHOUT any further optmization. The benchmarkings are done OUT OF THE BOX
So, if I have to MANUALLY enable JIT or any OC AFTER the flashing, it will NOT show in these graphics!
I didn't do that because it is just impossible for me to keep track of every single optmization that can be done to every single one of this ROM's. I just don't have the time and resources for that.
So again, all this tests are done straight after the flashing of the downloaded ROM (logically, after some reboots and bla bla bla).
I really hope that you guys understand that. It's not a way to show which ROM is better, since there are MANY more factors that dictate that, like BT calls, GPS and so on. It's just a way to measure mostly 3D performance out of the box with the ROM's you provide.

sheridan2000 said:
maybe link each of the roms in the first thread for people to easily find...being quite new here i cant fins the Androbin-cr2-5.0.7...what ever that one is...
Click to expand...
Click to collapse
That's a good idea, but I guess the WIKI sticked in the first page should have done the job. It will be redundant but I can try to keep track of them.

Man sad day, all you have to do in EzHero to enable jit is go to the terminal app and type jit-on.
Still, job well done! Kudos!

xenoside said:
Man sad day, all you have to do in EzHero to enable jit is go to the terminal app and type jit-on.
Still, job well done! Kudos!
Click to expand...
Click to collapse
I will add EZHero 2.7 with JIT enabled after Italy x Paraguay

Arkymedes said:
I will add EZHero 2.7 with JIT enabled after Italy x Paraguay
Click to expand...
Click to collapse
World Cup always comes first my friend lol

its raining pretty hard in the game...
anyways, so 2.0 is JIT enabled and 2.7 is not in your graph? because huge difference in linpack scores with the older having a better score.
you should also mention Benchmark Pi - lower the score, the better.

-2y2k- said:
its raining pretty hard in the game...
anyways, so 2.0 is JIT enabled and 2.7 is not in your graph? because huge difference in linpack scores with the older having a better score.
you should also mention Benchmark Pi - lower the score, the better.
Click to expand...
Click to collapse
Yeah, 2.0 is jit enabled, but now 2.7 is optional due to complaints and split decisions. I posted the benchmarks with jit on the last post of the front page

im a Sense guy but its been awhile since I tried a non-sense one, your ROM is rrreally tempting right now lol

-2y2k- said:
im a Sense guy but its been awhile since I tried a non-sense one, your ROM is rrreally tempting right now lol
Click to expand...
Click to collapse
Well vanilla Eclair and EzHero are both great roms, heck even Androbin is tied with those two.

In the Quadrant Graph, androbin doesn't have his bar.

Quadrant Scores:

lets post scores and what we are running to get their to help compare the different options available now for our Droid Incredible 2's
1649 gingerbread (.3.) for another week or so

CM7 Nightly 2. Stock kernel, not overlocked:
{
"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"
}

Cm7 overlocked to 1497
30 minutes or so later...and yes my crappy digital cameras clock is wrong

Cyanogen 1.8ghz

Underclocked and still better than stock. Runs great at 768mhz. No complaints.

Maximum overclock on stock CM7 kernel (~1.5ghz).

I did some tests with the CM7 Nightly 3. I got some amazing scores:
Stock cpu speed:
1.2GHz:
1.45GHz:
1.6GHz:
1.7 and 1.8GHz gave me lower scores than 1.6GHz, so I guess its safe to say 1.6Ghz is the max stable speed.

can't wait to hit cm7 and push it now !!!

Running miui at 1.49ghtz.
Sent from my Incredible 2 using XDA Premium App

Im running cm7 nightly 3 at 1.8 (and tested at 1.6) I am only around 2800 how are y'all getting up to 3500?
Sent from my Incredible 2 using XDA App

Interestingly, after some tweaking, messing around, and other stuff, I managed to score over 2200 at 768mhz. I'm getting some nice smooth performance out of it while underclocked, and getting it to do things quicker means it'll save that much more battery.

nimdae said:
Interestingly, after some tweaking, messing around, and other stuff, I managed to score over 2200 at 768mhz. I'm getting some nice smooth performance out of it while underclocked, and getting it to do things quicker means it'll save that much more battery.
Click to expand...
Click to collapse
What exactly did you tweak and mess around with? Cause that's sounds pretty nice.

melgibson666 said:
What exactly did you tweak and mess around with? Cause that's sounds pretty nice.
Click to expand...
Click to collapse
I'm not really sure, to be honest. I was mostly tweaking personal preferences, then messing with governors on the CPU. While comparing governors, the number kept climbing until it broke 2200 then fell back to just under 2200. I double checked my CPU clock settings to make sure I was still at 768mhz. I haven't really done any further testing. I suspect part of it may be JIT optimizations, but I'm not sure.

nimdae said:
I'm not really sure, to be honest. I was mostly tweaking personal preferences, then messing with governors on the CPU. While comparing governors, the number kept climbing until it broke 2200 then fell back to just under 2200. I double checked my CPU clock settings to make sure I was still at 768mhz. I haven't really done any further testing. I suspect part of it may be JIT optimizations, but I'm not sure.
Click to expand...
Click to collapse
Yea I was messing around with the different govenors after reading your post and I noticed a big difference between the power saver and ONdemand. Power saver makes the transitions a little sluggish but I guess that's to be expected for what it's trying to do. lol All in all though the battery life on ondemand is leaps and bounds ahead of the stock ROM I'm running a 1.1ghz clock right now and it is like butter with battery life to boot.

Quad Standard
mine came in at 2924 thats awesome!

tragedy , mine is between 1250-1500

zozor said:
tragedy , mine is between 1250-1500
Click to expand...
Click to collapse
What Rom
Sent from my Incredible 2 using XDA Premium App

zozor said:
tragedy , mine is between 1250-1500
Click to expand...
Click to collapse
Stock ROM? Mine wasn't even that low stock. Did you run it more than once?
Sent from my Incredible 2 using XDA App

am running this rom
[ROM] Offical Gingerbread 2.3.4 ROM is out via OTA by ChinaTelcom

zozor said:
am running this rom
[ROM] Offical Gingerbread 2.3.4 ROM is out via OTA by ChinaTelcom
Click to expand...
Click to collapse
Damn sorry bro I got a 2900 while on the phone lol
Sent from my Incredible 2 using XDA Premium App

benchmarked ROMS: stock GB v. leaked ICS v. CM9 v. CM9+HO!NO! kernel

I wanted to see how each current rom stacks up in a comparison, all roms were installed fresh- data wiped and all. i could not get the test to run with the HO!NO! kernel at full clock, even though my phone handles everything else fine at full clock.
each test was run 2x on each rom.
{
"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"
}

were you using antutu? this is what i got with it. All i did was kill all processes. running nightly from 6.11 and also using HO!NO! (thank you) v2 OC to 1.84Ghz

Hmm.. LG's ICS looks very promising for future custom ROMs/Kernals. Nice comparison.

yes, antutu. i think it's OK, benchmarks are what they are but I figure it should provide a generally good comparison. the only app installed on each rom was antutu and for cm9, gapps 3/17.

osmosizzz said:
were you using antutu? this is what i got with it. All i did was kill all processes. running nightly from 6.11 and also using HO!NO! (thank you) v2 OC to 1.84Ghz
Click to expand...
Click to collapse
this comparison is not a speedy demon test, i've done that and posted that previously, I can achieve those results you posted with the stock gb killing processes and much more to get the phone in drag strip mode.
this is simply an attempt to compare ROMS on a generally = footing.

updated

dangit Os, now you've got me curious how this cm9/HO!NO! can perform but i'm maxed at 1782 mHz! i'd bet this phone could tap 8000 fully set to race

scott0 said:
dangit Os, now you've got me curious how this cm9/HO!NO! can perform but i'm maxed at 1782 mHz! i'd bet this phone could tap 8000 fully set to race
Click to expand...
Click to collapse
The speed is very promising hands down. you cant go any higher than that speed? i know that every processor has its own share of DNA, but i would assume most would stop at 1.8

osmosizzz said:
The speed is very promising hands down. you cant go any higher than that speed? i know that every processor has its own share of DNA, but i would assume most would stop at 1.8
Click to expand...
Click to collapse
mine rebootw when i run antutu at that speed.

6.21 build?
Sent from my LG-P930 using XDA

even andasa's nitrogen rom should be added to the chart as he's back with a new nitro and an update !

I'm running stock Bell ROM and OC to 1836MHz with HO!NO! kernel & I get 7605 in Antutu without killing anything. So what's the point of running ICS?

noemtfj said:
I'm running stock Bell ROM and OC to 1836MHz with HO!NO! kernel & I get 7605 in Antutu without killing anything. So what's the point of running ICS?
Click to expand...
Click to collapse
1. Benchmarks are not everything. 2. ICS improvements mainly come from its ui hardware acceleration and if you used it you would see the point of running ics. Its significantly smoother than gb ever was and it manages memory better.

kalel90 said:
1. Benchmarks are not everything. 2. ICS improvements mainly come from its ui hardware acceleration and if you used it you would see the point of running ics. Its significantly smoother than gb ever was and it manages memory better.
Click to expand...
Click to collapse
Correct for smoother, I experienced ICS for 2 days b4 went back to GB. For memory, I don't know about it's management mechanism but I saw it used more memory.

funny that my nitro hd in stock2.3.5 scores 5647 total but get 1522 on gpu what is a lot.But i dont know why i get really bad I/O (430) i think its cuz the sd card is class 2 16 gb wich is slow.

Overclock - 1802mhz CPU, 512mhz GPU

I ran Quadrant Pro at 1802mhz on the CPU and 512mhz on the GPU (Franco Kernel & Jelly Belly ROM)
This was the result.
{
"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"
}

Did your phone explode? Because I don't see a picture.

And you posted this here..... Why?

Slemhelge said:
I ran Quadrant Pro at 1802mhz on the CPU and 512mhz on the GPU (Franco Kernel & Jelly Belly ROM)
This was the result.
Click to expand...
Click to collapse
thats lousy! id be embarrassed to show that off to people. i suggest a kernel change. anyways, that post does not belong here in development, nor anywhere near development heres trinity at 1728mhz..

simms22 said:
thats lousy! id be embarrassed to show that off to people. i suggest a kernel change heres trinity at 1728mhz..
Click to expand...
Click to collapse
LMAO! Damn you simms

can't beat simms at his own game =P

First off, that's embarrassingly low. I've gotten 4,000+ at 1.6GHz. Second why the hell did you post that in this section? I thought you needed 10 posts to post in a dev forum. Mods please close and OP read the damn rules.

irizwan said:
can't beat simms at his own game =P
Click to expand...
Click to collapse
lol, unfortunately not true though. there are a few that know how.
i just think that anybody running at 1802mhz should know how to propery use it or not be allowed to run that high of an oc. i mean, the op isnt getting any benefit from it unless you call a higher rate of battery loss a benefit. learn how to benefit from a high oc like this, or dont use it. its pointless to show off that youre using a high oc if a slightly oc'd(1344mhz kernel) can run laps around your phone. dont get me wrong, i know that franco kernel is capable, but this does it no justice.

simms22 said:
thats lousy! id be embarrassed to show that off to people. i suggest a kernel change. anyways, that post does not belong here in development, nor anywhere near development heres trinity at 1728mhz..
Click to expand...
Click to collapse
trinity FTW!

Then someone do tell me a good kernel and how to do a proper OC thats stable, efficient etc etc.. Im **** at OC'ing.. i just put franco kernel 512mhz and was allowed the option to go 1802mhz, which ive never seen before..

What development are you doing here?
None? Then why is it posted in development?!!
Thread moved
FNM

Slemhelge said:
Then someone do tell me a good kernel and how to do a proper OC thats stable, efficient etc etc.. Im **** at OC'ing.. i just put franco kernel 512mhz and was allowed the option to go 1802mhz, which ive never seen before..
Click to expand...
Click to collapse
Franco Kernel is a great kernel, yo must be doing wrong. I have achieved that score with franco's at 1.3 OC and Stock JB ROM...

Slemhelge said:
Then someone do tell me a good kernel and how to do a proper OC thats stable, efficient etc etc.. Im **** at OC'ing.. i just put franco kernel 512mhz and was allowed the option to go 1802mhz, which ive never seen before..
Click to expand...
Click to collapse
try them all, or a few different kernels at least. every phone is different, and will react differently to different kernels. also, just because you can oc to 1802, doesnt mean that your phone will properly handle it. at this point, it looks like you arent getting any of the gain from this high oc(some loss actually), but are going through your battery like you are. first off, at that high oc, turn off thermal throttling if you are going to benchmark. play with adjusting voltages until you find your sweet spot at that oc. try ocing less too, your phone might not like 1802, or 1700, or 1600.. not many phones do. also, when you benchmark, benchmark with your hiest cpu speed/highest cpu speed(1802/1802) so that you dont scale and actually bench 1802mhz.

simms22 said:
turn off thermal throttling if you are going to benchmark.
Click to expand...
Click to collapse
This is the key point that I believe the OP forgot to do.

IAmAN00bie said:
This is the key point that I believe the OP forgot to do.
Click to expand...
Click to collapse
very likely youre right.

Not even worth overclocking honestly.
Only for benchmark scores, your phone most likely doesn't run that much faster.

I Am Marino said:
Not even worth overclocking honestly.
Only for benchmark scores, your phone most likely doesn't run that much faster.
Click to expand...
Click to collapse
funny, only people that dont overclock say that, i guess they really do believe it for themselves. but in reality, there is a difference. if its a slight overclock, its not that different. when its a big overclock, the difference can be dramatic.

simms22 said:
funny, only people that dont overclock say that, i guess they really do believe it for themselves. but in reality, there is a difference. if its a slight overclock, its not that different. when its a big overclock, the difference can be dramatic.
Click to expand...
Click to collapse
I have overclocked before, I've done it before on the GNex as well.
I mean it was a huge increase of ability to a single core phone and early dual cores but for a phone already seemingly perfect on the software side, the phone already screams as stock clock speeds.
Besides, is it worth the probable loss of battery life? A marginally higher benchmark score? Things opening 1 or 2ms faster?
This is all just my opinion, I have no hard facts behind all this, but at least in my own personal testing and experimenting, there was no obvious benefit.
Provided you might be right, I've never OC'ed past 1.5, but beyond that, what's the effect on the health of the hardware, and like I said, battery life?
I could be totally wrong and I'm not against admitting being wrong.
Just personal preference I guess.

I Am Marino said:
I have overclocked before, I've done it before on the GNex as well.
I mean it was a huge increase of ability to a single core phone and early dual cores but for a phone already seemingly perfect on the software side, the phone already screams as stock clock speeds.
Besides, is it worth the probable loss of battery life? A marginally higher benchmark score? Things opening 1 or 2ms faster?
This is all just my opinion, I have no hard facts behind all this, but at least in my own personal testing and experimenting, there was no obvious benefit.
Provided you might be right, I've never OC'ed past 1.5, but beyond that, what's the effect on the health of the hardware, and like I said, battery life?
I could be totally wrong and I'm not against admitting being wrong.
Just personal preference I guess.
Click to expand...
Click to collapse
agreed. i myself use stock frequencies on franco kernel i've used almost all kernels and roms possible but now i've stuck with aokp n franco smooth even when under-clocked to 1 Ghz. i find no point of oc'ing other than just benchmarking usually get 3.4-3.3K on quadrant with normal freq.

simms22 said:
funny, only people that dont overclock say that, i guess they really do believe it for themselves. but in reality, there is a difference. if its a slight overclock, its not that different. when its a big overclock, the difference can be dramatic.
Click to expand...
Click to collapse
Your phone spends most of its life in the 350/700mhz range.
Signed,
An Overclocker