Develop Bugs

[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!

[KERNEL]1.28Ghz?!

Just wondering if anybody has tried this kernel yet? Found it over on AndroidMobileJunkie.com (Followed a link in somebody's sig here n XDA that said 1.28Ghz so naturally I was curious lol) Anyways, here's the link for the post over on AMJ. http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-22-oct.11/

yea ziggy's kernel. It's been in discussion in both of the Desire rom port threads. 1.28 is very rough on the processor though, and mostly unstable for a lot of people's phones (mine included), even ziggy admits it's a risky business, but he has proven it is possible.

I am so tempted to try this, but I'm afraid to fry my phone. My go big or go home mentality may make me give in. Wish there was someone who posted on the thread link

I ran it. No problems a 1.28 but really didn't use it long. Here's my Quadrant post in the Desire Z port thread:
http://forum.xda-developers.com/showpost.php?p=8775977&postcount=168
X

I'd imagine that clocking the processor that high wouldn't make much difference than say, 1.19GHz.
In fact, in plenty of ROMs I've tried, anything clocking over 1152mhz actually gives me a decrease in my quadrant scores. Not to say its not a stability issue - I'd assume that most Snapdragons actually clock higher than 998mhz, but then are reduced because that's baseline performance, anything less than 998mhz would get kicked.
I've never had a ROM crash, even running at 1.19GHz, but didn't notice any performance gains, plus, unless you just happen to get a chip that is capable of 1.28GHz no problem, it's probably near bottle-neck anyway.
And Quadrant has several variables way outside of clock speed that can pull 1800's, including just your flavor ROM.
Bottom Line: It's not worth frying your phone just for a barely-existent performance gain. If you happen to have a processor that is incapable of stability at 1.28GHz, you might fry out some transistors, then get stuck with something that freezes if you clock it over 700, let alone the 998 stock.

For me personally 1.28 is no improvement over 1.152. In fact, it gives me worse benchmarks.

sorry for repost

I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.

I tried this kernal and my camera stopped working...

HeyItsLou said:
I gave this kernel a try and I actually prefer the newest HTC 2.6.32.17 charging time has significantly decreased battery life has increased and the performance is really responsive and smooth. My quadrant scores are nothing impressive pretty average but I would rather all of the above than a high quadrant.
Click to expand...
Click to collapse
Lou hit the nail on the head. I love the .17 kernel. Im using the new guy with great performance, battery life, charging, and neat transitions. its like a new phone.

I'm using this with a vanilla froyo ROM and my battery life is amazing. Haven't noticed any freezing or any program not working.

Wow!
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol

dimebagdan65 said:
Thanks for all the replies guys, I think for now I'm gonna stick with the stock kernel also, I just remember back when I used to run KxK's kernels seeing great benchmarks and battery life I was always wondering if there were any faster out there lol
Click to expand...
Click to collapse
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z

Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?

Nevermind...found it!

ziggy471 said:
There's always faster, the question is will they work. lol
When I'm running the newer Sense ports, HD or Z, I can only run 1.113, no matter how much or little voltage I give it. When I'm running an older one, I can go all the way up.
As for stability at 1.28G, I need to work on the voltage more, to find the sweet spot, I just did it 'cause Jugs said one of his Bravo buds had it working, so I had to try.
I'll keep playing with it if people are still interested, otherwise, I'll just keep at the lower speeds.
Z
Click to expand...
Click to collapse
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy

hajabooja said:
Just loaded up your AOSP on Ruby 1.1.4. Running great, 1600 in Quad at 1ghz. Everything seems really smooth. Are the voltages undervolted at 1ghz? Maybe you could start your own thread?
Click to expand...
Click to collapse
What AOSP kernel??? I only see one kernel, and it references skyraider, which leads me to believe it is a sense kernel
edit: I am dumb. It is a different thread on the same site as listed above
http://forum.androidmobilejunkie.com/threads/kernel-ziggy471-droid-incredible-aosp-23-oct.24/

rmaccamr said:
By the way, my post wasn't meant to disrespect your efforts to 1.28GHz, I'm just giving fair warning that someone could possibly burn out their phone if they jack it up all the way. When I'm ready for an upgrade, I'll probably put this thing to the max.
Thanks Ziggy
Click to expand...
Click to collapse
I didn't take it as such, and I agree with you fully. I prefer somewhere between 1.113 and 1.15. That's the reason I included the init script to set the max at 1.113, which I find very stable and fast, hell I'd say 1865 quad with ID's Z port isn't too shabby at 1.13.
I should be able to get 1.28 more stable with playing with the voltages, it's just that takes time, and I wasted too much this morning doing both AOSP INC and Evo kernels, so I'm worn out for awhile on kernels. I still need to fix the Evo for puertoblack, since it appears I left the debug port out, so no adb for it. lol
Z

[Q] Benchmark questions!

First off I'm fairly aware of the fact that benchmarks are not accurate representations of the day to day real life usefulness of the handset.
That said, I used both linpack and quadrant standard edition for the first time tonight while testing another kernel with my current rom (which is cm7, ggingerbread-6).
At the conclusion of my testing it was very obvious that one kernel completely outclassed the other in a benchmarking situation, however something else became apparent that leads to this post.
If I follow and believe everyone else's benchmark scores, even those posted an hour earlier in the same kernel thread, then I might have the slowest Evo on planet earth.
I see other users of the same rom and kernal posting scores which are never below 1500 in quadrant, I saw one instance of 1300 but nonetheless, even overclocking to 1075 I can barely break 1100 and usually fall just below that. Sadly enough on the "slower" of the 2 kernals I was barely surpassing 900.
Now on the linpack side of things I don't have any comparative scores to judge against, but ill post what I received anyhow for information's sake. On the "faster" of the two kernels (the one that came prebuilt into the rom) I was getting between 33-34, on the new kernel I was testing I was getting between 19 and 22, these are all "mflops" of course, whatever that may be.
Someone give me some information or advice here! Do I just happen to have a slow evolution, or are others either exaggerating or using some trick/mod/tweak I'm royalty unaware of??
Thanks in advance!

some people brag, some people cheat, most have low scores, few have high, there isn't a very good baseline and the benchmark programs dont scale very well at all, I have run 1800 scores and I have run 600 scores, guess what. both roms were smooth and you wouldn't have been able to tell a difference, what does that mean? do we believe the benchmark programs? are they spitting a random number at us? who knows! dont believe them, be satisfied with how your evo is running and if it's not running very well then try a different kernel or rom, keep trying new ones until your satisfied, only then will some benchmark program output not mean a thing

Most of my Quadrant benchmarks with aftermarket ROMS+kernels have been in the 1100-1400 range, using VaelPak and various kernels to get most of the better scores there. The highest I've had was CM7RC1 with the SnapTurbo kernel, got an 1821. It was unusable, though.
I've come to the conclusion that the benchmarks aren't as important as battery life, especially with the Evo.

Biggest reason for the huge difference in numbers? Different versions of the app. The dev changed how it rates phones.
Sent from my PC36100 using XDA App

Thanks!
Explained. I knew they were totally not concurrent with the outward performance and usability of the device, and for what its worth while I've only ever flashed a total of 3 roms, this one is perfect for me and I seem to be one of the rare few with no problems whatsoever, everything works exactly as I would expect it to. So yes, l never feared my device was suddenly slower now that I knew the all knowing superultrabenchmark number.

Is it worth overclocking and undervolting Sprints galaxy s 2?

Running EL29 Odexed Blue Rom with EL26 stock kernal.
Just came from eVo 4G and have no idea if its worth it and if so what setting.
Any advice would be appreciated.
Sent from my SPH-D710 using XDA App

I've not done the undervolting yet but I'm thinking about it just still reading on what I want to do. I did however do the overclocks for a few days and imo only I really saw no need for it from the stock settings so I just went back to normal. The phone is fast enough for me even playing games that extra 1-2-3-400 mhz really didn't show that much of a difference.
Again this is my opinion others see the need for it I just didn't.

cidica said:
I've not done the undervolting yet but I'm thinking about it just still reading on what I want to do. I did however do the overclocks for a few days and imo only I really saw no need for it from the stock settings so I just went back to normal. The phone is fast enough for me even playing games that extra 1-2-3-400 mhz really didn't show that much of a difference.
Again this is my opinion others see the need for it I just didn't.
Click to expand...
Click to collapse
Thanks for you're opinion. Let me know how the undervolting goes if you decide to do it.. I wonder if vipermod would work with this device. I had it with my evo and it was pretty easy to use.

feelingnerdi said:
Thanks for you're opinion. Let me know how the undervolting goes if you decide to do it.. I wonder if vipermod would work with this device. I had it with my evo and it was pretty easy to use.
Click to expand...
Click to collapse
I think viper mad some stuff for the phone. I know he has a rom out for the phone already so maybe his tweaks are there you could always check the dev section.

My phone had freezing issues at anything higher than 1.4ghz, but even then the only real difference I saw was quadrant scores. Games ran the same, in fact I think the UI actually was choppier when OC'ed. Never really looked into it much though.
I don't even know why I tried it in the first place, I never said to myself "gee, this could be faster.." I guess coming from an HTC Hero it was a habit.

this phone does NOT need to be over clocked; it is so much faster than your Evo, that you won't believe it!
Undervolting and under clocking can give you extra battery life; do a search on the Dev thread, and you will learn lots about it..

High benchmark, what set up?

I eventually ran a benchmark on my CarbonROM install on my Sprint Galaxy Nexus, clocked at a max of 1.6
But, I saw that my device compared to others is just super super low, I don't have the numbers on me as I don't have my phone, but if you're one of those people who have a high benchmark score, what's your setup?
I know it's said that benchmarks aren't important, but they at least have to mean something with performance.
So, what are you running?

Try flashing franco.Kernel. Makes a huge difference!
Before franco: 2204
After franco: 2932 (Quadrant Standard)
ROM: PACman ROM, 1.2 GHz

Seriously, there should be a thread stickied for the bench freaks, all in the same place. *sigh*
Sent from my Nexus

bk201doesntexist said:
Seriously, there should be a thread stickied for the bench freaks, all in the same place. *sigh*
Sent from my Nexus
Click to expand...
Click to collapse
There is one. Just needs sticky-ing.

Beauenheim said:
I know it's said that benchmarks aren't important, but they at least have to mean something with performance.
So, what are you running?
Click to expand...
Click to collapse
See, the thing is, benchmarks really do mean nothing. Benchmarks don't affect how well your device performs. If it runs fast, it runs fast-- you don't need the benchmark to know that.
Sent from my Mahjong Nexus

Beauenheim said:
I know it's said that benchmarks aren't important, but they at least have to mean something with performance.
So, what are you running?
Click to expand...
Click to collapse
Yeah. Because being able to crunch 110,000,000 triangles vs 90,000,000 has real world implications.

Yay! It's been a while since we've had a thread to remind us how useless benchmarks are and offer us all an opportunity to debate about it, yet again.:good:

I make my words what Chainfire said, but globaly.
If you trust benchmark results, you'll know that running naked in the garden for 5mins will affects performance by 20%

Neat, alright.
So absolutely nothing?
That really doesn't make any sense to me. Those 90,000,000 triangles being processed will at least show me how well it will do in a game, to a degree, right?

Not in any way you could actually notice. That was also an extreme hyperbole as far as differences go. To be totally honest, the only real value of benchmarks is stress testing an OC but even then there are better ways.

063_XOBX said:
Not in any way you could actually notice. That was also an extreme hyperbole as far as differences go. To be totally honest, the only real value of benchmarks is stress testing an OC but even then there are better ways.
Click to expand...
Click to collapse
Well alright, thanks for your insight. I've been in the android game for awhile but I don't know a lot of these things.