Database Info

Mini Overclocking Guide

Mini Overclocking Guide​
NOTE: The Steps Below were Tested on Froyo Roms. I have found different and perhaps better ways to test stability with CM7 Roms so I added a section for that too.
You can still use Stability Test but I don't use it too often anymore for CM7.
Programs Required for testing:
#1 Stability Test
#2 Neocore (please note that some kernels are not FPS unlocked meaning that the frame rate will not go over 56fps so make sure to compare apples to apples when testing different kernels).
For overclocking/undervolting you can use either Pimp My CPU or Voltage Control
Intro:
I posted this Guide in ROM thread but decided it might help someone trying to get a head start overclocking...just a reference not a bible.
First of all, please realize that no two CPUs are created equal. Just like with PC Overclocking, there is the luck of the draw involved here so just because one person can do 1.4Ghz it does not mean you will be able to do so nor it means that my UV settings will work for you.
Achieving 1.2Ghz should be feasible for almost all users since most of the code for it was already done by Samsung themselves. After that point though, it is a matter of luck. Many users can do 1.3Ghz but getting into 1.4Ghz the chances of stability drop dramatically.
Please note that with CM7 Roms it seems a LOT more people is able to hit 1.4Ghz and even 1.5Ghz fully stable. 1.6Ghz is also working although not as common. It is easier to use it if you select 1.6Ghz as the ONLY frequency but of course battery life will be affected.
So, start at 1.2Ghz and try to achieve stability with the lowest possible UV settings you can get to improve your battery life then when fully stable, go for a bit more speed if you like until you find your limit.
Process:
The following is the process I use to get 100% stability. Of course, you can use your own or tweak as you like as this is hardly the ONLY TRUTH of overclocking…I just hope it gives you a good idea on how to achieve stability.
I normally use these settings for 1200Mhz:
1200Mhz @ -100
1120Mhz @ -100
1000Mhz @ -100
900Mhz @ -100
800Mhz @ -100
400Mhz @ -100
200Mhz @ -100
100Mhz @ -100
After setting those up , click the Apply Now button but do not save to the Boot settings until you are sure they are stable for you.
To check stability I first run the Stability Test program and let it loop about 30 times or at least 20 of the CORE (not the RAM).
If it fails give it another shot if it fails again then it is time to adjust the voltages for 1200Mhz.
My experience has been that Stability Test crashes to the home screen when it needs more voltage so if it crashes for you change the UV to -75 and test again.
When you are able to pass that test , you can go to Neocore and try looping Neocore and let it running for about 5 to 10 minutes.
If Neocore freezes, at least for my phone, it means that voltage is too high so I need to drop the UV.
Right there is where the whole trick is. Trying to find what UV voltage is enough for Stability Test to pass but still low enough so that Neocore does not freeze.
This takes a lot of trial and error specially when going for 1.4Ghz!
Another thing is that the UV setting for the frequency below the one you are going for, like 1120 and 1000 for example, do have an effect on the stability you are trying to achieve on 1200Mhz because the phone does not seem to like big voltage jumps .
Some times changing the voltage for the frequency below the one you are adjusting is a good way of achieving stability.
This becomes more important when for example you find out that changing 1.2Ghz to -50 gives you stability for Stability Test but then you need -75 in order to pass Neocore test. What do you do then? What I have done with relative success is , use -75 but then increase the voltage to the frequencies below 1200.
For example if I had
1200Mhz @ -75
1120Mhz @ -100
1000Mhz @ -100
I would change it to:
1200Mhz @ -75
1120Mhz @ -75
1000Mhz @ -75
then test Stability Test to see if those changes help you pass it without having to increase the voltage for 1.2Ghz directly thus avoiding the Neocore freezing issue.
Another process some users are doing is just run Neocore for about 30 minutes and it seems to be a good alternative for some. Guess it all depends on your particular phone.
So, as you can image, this means a LOT of trial and error and restarts of your phone. For 1.2Ghz it should be painless but if you want to go higher, prepare to do a lot of the steps above.
Another thing to consider is that some phones seem to work better with kernels that only have one top speed after 1Ghz as opposed to kernels that offer multiple speed options so this is yet another variable to work with.
Also, remember that to restart your phone, there is no need to pull out the battery. Just press and hold the Volume Up and Power button and it will restart.
I am sure this guide can be done a lot better and will be glad to add or edit with any recommendations you can offer.
I hope this helps some of you trying to push your phones to the limits and have fun!
UPDATE for CM7 Users
With CM7 what we considered THE holly grail of speeds, 1.4Ghz with Froyo Roms suddenly became a VERY common thing.
I have no explanation as to why but a LOT of users are able to get 1.4Ghz and even 1.5Ghz perfectly stable on CM7 and the phones just fly at those speeds. Some are also able to get 1.6Ghz stable but that is harder.
Setting only one speed like 1.6Ghz dramatically increased the stability as well. Just a hint for you guys wanting to do some benchmarks.
You can use a program like Pimp My CPU or Voltage Control to set the voltages and the Maximum and Minimum speed.
Now while the Steps at the beginning of the guide (for Froyo roms) should be fine for CM7 as well ...I have noticed, at least with my phone , that a video player called Moboplayer is VERY good for stability testing CM7. In fact, I do not even use Stability Test any more since I moved to CM7.
When the voltage is a bit low on my screen it creates some artifacts, usually green spots that come up and go in random areas until it freezes.
My actual favorite player for CM7 is Dice Player because for me it plays 720p files better but I like moboplayer a lot as well specially because of the artifacts it shows when I am not stable so it is a quick way to tell the settings are not going to work.
Another thing I love to use if the Riptide Game (tegra 2 game) with Chainfire 3D plugin to make it work on our phones. That game will just close without warning when my speed is unstable. So I just let it running the demo on its own for about 10 minutes.
So basically, I use Moboplayer and Riptide to test my stability and with those tests my system is ready to go and takes less time than the steps I used to do.
Of course you can come up with your own preferred tools since our phones are quite unique and seem to have their own personalities.
It seems some users are having luck with my settings so here are my settings for 1.6Ghz This is for GLITCH kernel (V10C VC). Remember that each kernel has different voltages so instead of giving you a minus value like -100 I will give you the actual voltage I am using for each speed.
1.6Ghz - 1425mV
1.5Ghz - 1400
1.44 - 1325
1.4Ghz - 1325
1.3Ghz - 1275
1.2Ghz - 1275
1.0Ghz - 1200
800Mhz - 1100
400Mhz - 950
200Mhz - 850
100Mhz - 850
For Governor I normally just have Smartass and the Scheduler is NOOP.
Not that while for 1.6Ghz my current setting is either -50 or -75, if I were to select only 1.6Ghz as my max and minimum speed, I am then able to lower the voltage to -100 perfectly stable. Just an interesting thing for you to play with.
Important Note for CM7 users getting many FCs like google service or android service.
CM7 has a much smaller data space for application installs and every time I get to that limit my phone gets crazy with FCs. You can check that by going to your applications and launching the TERMINAL application then type df (in lower case) and pressing Enter.
Look at the top table listed for /datadata and make sure you have some available space.
As long as I keep that from filling up (in fact I prefer to keep it around 60% max to give me some room) my phone works like a charm.
You can use an app like APP2SD to move application data to the SD card to free up space.
Have fun and enjoy your pumped up phone!
UPDATE 12/30/2011
CyanogenMod 9 (ICS) users with Glitch kernel using LiveOC you can use my settings as a starting point.
This is what I use for 1603Mhz
Voltages:
ARM voltage
from 1500 to 1200 = 1.5V ; 1000 = 1.375V ; 800 = 1.250V ; 400=1.100V ; 200=950mV ; 100=900mV
Int from 1400 to 1200 = 1.2V ; 1000 = 1.15V ; 800 = 1.125V ; 400=1.100V ; 200=1.100V ; 100=1.000V
Then 123% LiveOC using 1300MHz step (giving you 1.6GHz)
Governor I am still testing but usually Smartass V2
You can of course use it as a starting point for lower speeds if you like.

Nice man. Saves alot of frustration with this.

Awesome! Thank you!

You are the OC master, Shaolin.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

I wish I was a master indeed but I just have a lot of patience I guess to test ..and test...and crash..an test some more

I think I saw a post that said that any temperature below 56 degrees Celcius is fine for the captivate. I still start to worry though if it reaches 50 during a stability test, what's your opinion?

I noticed that mine when it its 50C or so for any reason (battery temp IIRC) it stops charging so that is where I normally draw the line. If I cannot keep it under that I dont feel comfortable.

That 50 is pretty high, at least for me. Even with stability test going for an hour or so at 1400, I only hit 46. Haven't seen anything higher
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Depends on ambient temp of course...you cannot compared devices temps without knowing the ambient temp. In any case, I saw that when I was using the first Trident kernel. That one even made my screen feel very hot...kinda scary lol
Right now, the only app I have that makes my phone stop charging, even when temp is low, is the Justin TV viewing app....weird. I even ran the phone at 600Mhz only to make sure.

AReynante said:
That 50 is pretty high, at least for me. Even with stability test going for an hour or so at 1400, I only hit 46. Haven't seen anything higher
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
I was testing out 1500 1400 is fine for me with -100 for each value. 1500 is a different story since I haven't managed to find a stable combination yet (that doesn't reach 50 degrees Celcius).

Sweet. Are you getting to 50C with a specific app? I only get there with some streaming apps but I really only use 1.5 for fpse emulator for example.

I don't have an app that tells me the temperature so the only time I know is if I do a stability test. I'm not sure if I really have a need for 1500MHz since I don't use emulators much but it's more of a "yea my phone can do it" kind of accomplishment - unless I'm missing out on some other benefits of 1500Mhz over 1400Mhz besides possibly more smoothness.

zuN! said:
I don't have an app that tells me the temperature so the only time I know is if I do a stability test. I'm not sure if I really have a need for 1500GHz since I don't use emulators much but it's more of a "yea my phone can do it" kind of accomplishment - unless I'm missing out on some other benefits of 1500Ghz over 1400Ghz besides possibly more smoothness.
Click to expand...
Click to collapse
Lol 1.5 terahertz I want that phone!

studacris said:
Lol 1.5 terahertz I want that phone!
Click to expand...
Click to collapse
Wow didnt notice that....thats Fing awesome!

Stability Test question
Hey Shaolin,
Just a quick question here, when you mention running stability test through 30/50 runs, are you referencing the RAM runs or the core runs? Just checking, since the RAM runs complete within a few minutes whereas the core runs take closer to half an hour, etc.
Thanks for posting the guide, much appreciated!!!

Since the new version I am only doing 30 of the core runs since it seems to take longer than before.
You are welcome amigo

shaolin95 said:
Since the new version I am only doing 30 of the core runs since it seems to take longer than before.
You are welcome amigo
Click to expand...
Click to collapse
Hey mate, maybe you can add this to your guide as I thought before that stability test and several runs of new core, nenamark, etc...that after passing those tests you're probably stable but what I found out that I can pass those tests without problems and just recently those test are not enough for you to be sure if you are really stable what I have found is to run or record in your phone video cam in its highest resolution about 720p for 200mb worth of data if your phone won't freeze then it's pretty stable you can delete those files afterwards.

Indeed each phone and user can find specific things that work for them, for example with my phone I can just use mobo player and play some videos and I get artifacts when voltage is low or I had a game that with low voltage will always freeze at the same spot yet some user do not have the same effect.
I guess I can add a small list of other possible quick tests like that video one you mentioned as alternatives

I found out another way to test stability which is to do a batch operation of backing up apps with TiBu. I'm not sure what it implies if it crashes though

Hi shaolin95, can I link this post in my VoltageControl thread? (with credits ofc)

[Q] Overclocking and battery life

This is a question for those who have overclocked their Xoom. How much is overclocking to 1.5Ghz affecting battery life?
Overclocking would be the only reason I would root right now, and I am trying to make up my mind on whether to do it.

My battery life is better after using setcpu to overclock. The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom) with setCPU you are extending the top end of how fast the CPU can go. The clever bit is you can also tell your xoom to slow itself down and go very efficient when the screen is off or if the chipset gets too hot (which it never has). If you do go for it I recommend using setcpu using interactive scaling (prioritising the user interface) and whack the max speed up to 1500 and the min speed down to 217 mhz

I wouldn't recommend setting screen-off profiles at the moment. It seems to lead to some strange issues once in a while.
That said, because you're only going to 1.5 GHz when needed, battery life doesn't really suffer. Additionally, at least in my usage, my screen uses ~70-85% of my battery. This is even during heaving gaming, where the Tegra 2 really has to work hard.
I wouldn't worry about its effects, personally.

MrGinger said:
The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom)
Click to expand...
Click to collapse
All CPUs do this, not just Tegras.

Re scaling, never said otherwise I've never had a problem with screen off profile. Maybe just lucky

About CPU

Hi. My question us what CPU speed can I use before the desire s takes damage? Thanks
Sent from my HTC Desire S using XDA Premium App

Would not go over 1200mhz for general use but in the end it comes down to heat and chip quality. Some chips will run faster and produce less heat then others, you'll have to test yours! Don't over volt even if it is possible?
That's about all I can give you on the matter.
Sent from my HTC Desire S using XDA App

um... just a quick question... why do You need more power? I mean what for??
n64 and psx emulators - full speed, gameloft's dungeon hunter 2 and rainbow six - smooth as my wifes ass, all the flash movies on web or divx offline - no problem, general use - as good as gingerbread can deliver.
I was thinking about which dual core beast shall I buy and ended up with this pocketable and powerful beauty.
... back to the topic - I wouldn't overclock it over 1.5 ghz, even then only for demanding tasks. battery life would decrease as well and I wouldn't trade that for a bit more fps.

Okay. Thank you guys
Sent from my HTC Desire S using XDA Premium App

bronx said:
um... just a quick question... why do You need more power? I mean what for??
n64 and psx emulators - full speed, gameloft's dungeon hunter 2 and rainbow six - smooth as my wifes ass, all the flash movies on web or divx offline - no problem, general use - as good as gingerbread can deliver.
I was thinking about which dual core beast shall I buy and ended up with this pocketable and powerful beauty.
... back to the topic - I wouldn't overclock it over 1.5 ghz, even then only for demanding tasks. battery life would decrease as well and I wouldn't trade that for a bit more fps.
Click to expand...
Click to collapse
Good response, I bought a Desire S recently too and feared the "single core" 1 GHz CPU wouldn't be much faster than my Legend clocked at 768 MHz, after all it is only 232 MHz difference. Couldn't have been more wrong. The phone is a beast.

1.2 ghz is a good speed if you wanna overclock (& also this speed is more than enough)
1.4-1.5 ghz is the limit, anything more than that is very unstable and can cause damage to your cpu

Hey guys. I have a Desire HD. Although they're different phones, i'm sure the internals are almost exactly the same, bar few differences. As such, the cpu should also be the same. I tried out different cpu speeds. I kept my phone at 1.72ghz for a couple of weeks. The phone got pretty hot when using Wifi and such, but didn't get too hot. I'd say the safe point is 1.5ghz but at the stock voltage. Works for me, should work for you guys too I can get 1.7ghz at 1325mv, which is good enough for me I didn't get random crashes etc. My persona highest on this phone was around 2.1 ghz, which was insanely high, the phone was super fast, but got hot blazing hot and the phone started flashing orange led lights and then shut down for like 10 minutes straight. I thought it was gone but...nope, was lucky thank god LOL
Always be careful. If you have insurance, then go ahead and by all means clock the hell out of it if you don't mind a decrease in battery life. But if you have no insurance, and bought it sim-free...i'd suggest 1.3ghz...better be safe than sorry, wouldn't you agree?

the phone started flashing orange led lights and then shut down for like 10 minutes straight. I thought it was gone but...nope, was lucky thank god LOL
Click to expand...
Click to collapse
Haha, bet that was a ball-shrinking moment. Made me laugh reading it.
But seriously, considering the potential damage & the native performance of the DS you wouldn't want to go crazy really.
Sent from my HTC Desire S

Hi!
I succesfully overclocked my DS to 1,5GHz(first to 1,3GHz, than to 1,4GHz), and it's fully stable with stock voltages. I use virtuous unity 1.29.0, and tweaked the built in OC daemon. Tested with stability test v1.5, and no problems after 30 minutes. Temperature is around 40 C(plugged in, charging, and running stability test).
What do you think, can I use it for 24/7? The temperatures are not high, and the phone is rock stable, so is it safe?
Thanks for answer.

ffodi said:
Hi!
I succesfully overclocked my DS to 1,5GHz(first to 1,3GHz, than to 1,4GHz), and it's fully stable with stock voltages. I use virtuous unity 1.29.0, and tweaked the built in OC daemon. Tested with stability test v1.5, and no problems after 30 minutes. Temperature is around 40 C(plugged in, charging, and running stability test).
What do you think, can I use it for 24/7? The temperatures are not high, and the phone is rock stable, so is it safe?
Thanks for answer.
Click to expand...
Click to collapse
why do you need to run it on 1.5ghz? it is very fast at 1.2ghz
& also 1.5ghz will consume more battery & if you put some load on the cpu like a little gaming or a lot of browsing it can get heated up
overclocking more than necessary isnt good as there can be hidden damage to the chip(even if the processor doesn't get heated up)
read post #3 here
so always go easy on the overclocking

kartkk said:
why do you need to run it on 1.5ghz? it is very fast at 1.2ghz
& also 1.5ghz will consume more battery & if you put some load on the cpu like a little gaming or a lot of browsing it can get heated up
overclocking more than necessary isnt good as there can be hidden damage to the chip(even if the processor doesn't get heated up)
read post #3 here
so always go easy on the overclocking
Click to expand...
Click to collapse
Thanks for the answer! I overclocked it to 1,5GHz becouse I like it if everything is fast as lightning.
I know it can consume more battery, but it's not a problem for me.
I've read that post, it's useful thanks, but i think if everything is on stock voltage it cant hurt the cpu. I overclock my desktop rig also since ~15 years, and never had problems with that. I know that it's not the same, but I hope there will be no problems with that.

Thoughts on OverClocking Sensation

Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt

I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.

I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt

I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.

mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App

Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707

I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...

So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt

I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?

i think at LeeDroid 1.2 you must not use setcpu but Demon control?

BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.

Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.

Linpack Scores Relatively Low

I am just wondering why the Sensation is only hitting around 80MFlops at most in Linpack @ 1.5GHz. It seems that this phone should be getting 100+ every time. I have also noticed that the single core may score 55MFlops while the multicore will only raise that to 60MFlops.
Does it have something to do with the Java libraries? I also saw something about NEON libraries?
I think the highest I've ever scored with my Sensation is 91MFlops.
Thanks for any input on this guys. I know it's just a benchmark, but I'm just curious.
EDIT: Just scored a 27. I'm just gonna uninstall this app and use AnTuTu. How does this CPU ACTUALLY perform against other high end CPUs?

snelan said:
I am just wondering why the Sensation is only hitting around 80MFlops at most in Linpack @ 1.5GHz. It seems that this phone should be getting 100+ every time. I have also noticed that the single core may score 55MFlops while the multicore will only raise that to 60MFlops.
Does it have something to do with the Java libraries? I also saw something about NEON libraries?
I think the highest I've ever scored with my Sensation is 91MFlops.
Thanks for any input on this guys. I know it's just a benchmark, but I'm just curious.
EDIT: Just scored a 27. I'm just gonna uninstall this app and use AnTuTu. How does this CPU ACTUALLY perform against other high end CPUs?
Click to expand...
Click to collapse
Qualcomm actually has better floating point calculations than others, it's one of the benefits of the dragons. If you're using Sense, try linpack on Vanilla and it will be higher. Sense & benches don't go together b/c of something HTC screwed up.
http://www.nordichardware.com/news/...lcomm-demonstrates-new-msm8660-processor.html

what exactly is a floating point calculation?

Awesome, thanks!
By Vanilla, do you just mean a stock ROM without Sense? Would CM7 work? I just installed CM7 and set my min max to 1620/1620 and topped out at 101MFlops, but that was only out of 3 runs.
Does this also mean that Sense has slower real-world performance? Or just for benchmarks?

snelan said:
Awesome, thanks!
By Vanilla, do you just mean a stock ROM without Sense? Would CM7 work? I just installed CM7 and set my min max to 1620/1620 and topped out at 101MFlops, but that was only out of 3 runs.
Does this also mean that Sense has slower real-world performance? Or just for benchmarks?
Click to expand...
Click to collapse
Yeah cm or aosp, sense has always been slow with benches since the HTC hero. It doesn't play nice with any bench really, compare the same phone on sense and vanilla and scores are different. I don't know much about floating points but its probably related to how fast things are calculated. The hummingbird had a lower linpack than the scorpions of that time. And this doesn't mean sense is slower but it rapes the phone's ram excessively. When ics is out benches should be done to see how this phone really performs, most of the 1 core is sleep anyway or not at max.
Sent from my T-Mobile Sensation 4G using XDA App

One important thing:
When you score in multi-thread is just about 10 points above the single-thread score, it's because your second core (CPU1) didn't go online, or simply too late, so multi-thread was just using one core
Try this: with root explorer, go to sys/devices/system/CPU/CPU1/online
in this file replace 0 by one, then save. Immediatly set the permissions to read only (on "write" is ticked by default, untick it)
Now your both cores are always online, ready to scale up, and multi-thread scores will always be far superior to single-thread.
(it's not sticky, everything we go back as it was after a reboot)
Also my very best score with Linpak was 115, at 1.782ghz, CPU1 forced online, I posted a screenshot somewhere in Bricked kernel thread. This is a real battery drain and hot device to get this score
In real life, 90 or 95 at 1.5ghz is pretty good

i900frenchaddict said:
One important thing:
When you score in multi-thread is just about 10 points above the single-thread score, it's because your second core (CPU1) didn't go online, or simply too late, so multi-thread was just using one core
Try this: with root explorer, go to sys/devices/system/CPU/CPU1/online
in this file replace 0 by one, then save. Immediatly set the permissions to read only (on "write" is ticked by default, untick it)
Now your both cores are always online, ready to scale up, and multi-thread scores will always be far superior to single-thread.
(it's not sticky, everything we go back as it was after a reboot)
Also my very best score with Linpak was 115, at 1.782ghz, CPU1 forced online, I posted a screenshot somewhere in Bricked kernel thread. This is a real battery drain and hot device to get this score
In real life, 90 or 95 at 1.5ghz is pretty good
Click to expand...
Click to collapse
Wow! Never knew about that, I just assumed that the second core's clocks were off or something. Thank you very much good sir!