Related
Maybe its just me but I feel like overclocking our phones is unnecessary. It seems like its just for boostin benchmark scores and it doesn't really affect real world performance. For me I used setcpu and it makes the phone slower and laggy when on conservative. Is that just setcpu not playing nice with my phone?
Tapatalkin it from my Epic 4G
Overclocking, for most part, is all about getting the most you can out of what you have. For some its a numbers game, for others it's just because you can. Personally, I like at least having the option open. However, my Epic doesn't like 1.2ghz.
Stock speeds are enough most of the time. I don't usually run the programs that use 100% of the cpu, so I really don't need to worry about it. Though, if I had the capability to OC.. I would.
As for setcpu, I've never experienced any overly excessive lag or anything brought about by its use. Though, by its nature it will be slightly slower to respond.
Coming from a hero, i can tell you overclocking is certainly not a gimmick! It may not be as necessary on these epic cause its crazy-awesome fast from the box, but it still helps. I keep mine at 1.6ghz on conservative, and performance when i play certain games. For me its about the multi-tasking improvment. Also i like to see my icons fade in smooth no matter what i have going on in the phone
But for me at least, its far more than just a benchmark score. However it is pretty sweet telling my iphone rocking coworkers to eat my ghz
jok3sta said:
Maybe its just me but I feel like overclocking our phones is unnecessary. It seems like its just for boostin benchmark scores and it doesn't really affect real world performance. For me I used setcpu and it makes the phone slower and laggy when on conservative. Is that just setcpu not playing nice with my phone?
Tapatalkin it from my Epic 4G
Click to expand...
Click to collapse
Well first it depends completely on your phone, all are different in terms of what they can handle, so each individual phone will respond differently to overclocking/undervolting. I can personally run 1.2, 1.3, and the 1.6 completely fine, while a lot of people can't run any of these. In terms of performance, it does make a difference with animation speeds, fps on games such as pocket legends or angry birds, and overall lagginess. But again, this is dependant on your phone.
Sent from my Xtremely Syndicated and Emotionless Epic 4G
I flashed the Xtreme kernel today but for some reason, I'm not getting the FPS unlock. Nenamark and Neocore are not getting the +70 I was expecting...
Eazail70x7 said:
I flashed the Xtreme kernel today but for some reason, I'm not getting the FPS unlock. Nenamark and Neocore are not getting the +70 I was expecting...
Click to expand...
Click to collapse
Are you running v1.2.0? If so, the fps cap is not fixed on this version because Devin removed the 1.6ghz step which allows the framerate to be raised. It works on some phones, but not all which is why he removed it.
Sent from my Xtremely Syndicated and Emotionless Epic 4G
That explains it
The same argument comes up every once in a while concerning PC overclocking. I admit the phone overclocking has yet less benefits and even more downsides, but oh well, it's still super neato.
AndrewZorn said:
The same argument comes up every once in a while concerning PC overclocking. I admit the phone overclocking has yet less benefits and even more downsides, but oh well, it's still super neato.
Click to expand...
Click to collapse
Exactly, you have to compare this to pc overclocking because it is the same exact thing. Two processors of the same make and model will overclock differently no matter what, it depends entirely on the die. Correct, the benefits are less noticeable, but it still makes a difference.
thomasskull666 said:
Exactly, you have to compare this to pc overclocking because it is the same exact thing. Two processors of the same make and model will overclock differently no matter what, it depends entirely on the die. Correct, the benefits are less noticeable, but it still makes a difference.
Click to expand...
Click to collapse
There is a notable difference with stock 1ghz and a 1.2ghz. 1.2 - 1.3 isn't worth it in real world that's bragging rights
Sent from my SPH-D700 using XDA App
Hey guys, can you use z4 root on this phone? All i want is to remove is the bloat and undervolt it for my battery.. Any ideas of this works?
Why don't you ask in the z4 root thread
Sent from my SPH-D700 using XDA App
Wtf there is a thread for everything here lmao.
Dj21o said:
Wtf there is a thread for everything here lmao.
Click to expand...
Click to collapse
Yea and the search button helps to find it.
Sent from my SPH-D700 using XDA App
Dude I know lol. I have a rooted hero, but im sick of all the custom bs. I want to underclock and thats it!
So I've been messing around with different roms and kernels for the past few weeks and finally settled on CM6 6.1.1, and the snap 7.6 bfs kernel, for stability and speed. I turned on the turbo mode with snap, OC'd to 1152mhz (freezes at 1192), killed all apps, and ran quadrant.
[Picture of a 2330 benchmark screencap was supposed to go here, but I don't have eight post haha]
I know thats pretty good, my scores average from 2100-2350, but I'm looking to make it even quicker. What can I do?
Thanks!
Move to gingerbread.
Sent from my PC36100 using Tapatalk
sultan.of.swing said:
Move to gingerbread.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Which ROM and which kernel?
weehooherod said:
Don't use Snap 7.6 on CM6.1.1, just use the stock kernel. The new kernel built in with CM6.1.1 is much better, Snap 7.6 is pretty old.
Click to expand...
Click to collapse
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC
xsaqzw said:
Which ROM and which kernel?
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC
Click to expand...
Click to collapse
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.
A benchmark does not actually show how fast your phone is....
Cyanogen himself stated this.
quadrant scores =/= to your phone being 'fast'.
But if you care about synthetic benchmarks then you could trick your file system into giving you quadrant scores in the 3000+ range.
by the way thanks for posting this in the relevant subsection of the evo forum dedicated to development this will absolutely further the development of android.
Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section
Lol okay then guys, so which gingerbread ROM and which kernel for the best efficiency and speed?
david279 said:
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.
Click to expand...
Click to collapse
I couldn't agree more, how instant can a phone get? Theres a point where speed wont be relevant anymore and its pretty damn close to it already. In my eyes efficiency is the future, doing more with less is something im looking forward to.
Sent from my Warm TwoPointTwo RLS5 Beta'd out Evo
lexusmike said:
Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section
Click to expand...
Click to collapse
**** man I'm sorry I'm new to this forum.
Mods: Please move to the correct section.
Thread moved to General.
Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.
Oddly enough, I'd rather have the transition animations that come with some of the custom ROMs, even if they take longer. They provide a much more "fluid" experience. I don't like the jarring, speed-driven, animation-free transitions that come with stock ROMs, because they lack polish. As soon as I saw videos of those animations, I was in love. LOL. Seriously though, lag and lack of animations (which consequently actually help hide lag and load times) are the two things I see holding back the polish of Android. Just as an example (not trying start a flame war here, people), look at the animation when going from portrait to landscape in iOS. Then look at Android's lack thereof. THAT is what Android needs-to actually FEEL faster, not necessarily BE faster. So try something like that if you want the phone to feel more fluid instead of just achieving raw benchmark speed. Again, just my opinion (kind of sad that I feel the need to put that disclaimer in every post lately).
Award Tour said:
Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.
Click to expand...
Click to collapse
that is interesting.. thanks for the info.
I hope it does open some more performance and maybe a way to overclock the GPU
Im not playing call of duty on my phone or anything. I want efficiency.[/QUOTE said:
Lmao
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Finally we have a fair test for the dual cores. Just been running it and i have the top 5 scores!!
Is that 1608mhz , your phone must be on fire
Now have 150.595. It was a bit warm. I expect it to fall as the number one soon, i m sure there are guys on here with over 1.7ghz. I cant seem to get that to stay stable.
Finally! My highest (1.2) was 122 although that was an inconsistent result. My average high is around 100. Wonder what the Sensation and Tegra devices are hitting.....
Regards.
Best i can do so far.
I'm getting wildly inconsistent results. Managed to get 120 at 1200mhz with a accuracy of 2.2 after a dozen runs.
Sent from my GT-I9100 using XDA Premium App
Yeah you just have to keep trying until you get a high score with a valid accuracy. It wont let you save unless its consistently accurate.
MaBlo said:
I'm getting wildly inconsistent results. Managed to get 120 at 1200mhz with a accuracy of 2.2 after a dozen runs.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
did you set both minimum speed and maximum speed to 1200?
152 is my new high, thats it for a while, battery flat, phone rather warm!
140 is my best stable score, running @1.425ghz using Tegrak
rovex said:
152 is my new high, thats it for a while, battery flat, phone rather warm!
Click to expand...
Click to collapse
the top 10 has only your results in it, lol
Its the Moto Zooms i worry about., Although the Tegra is slower the Zoom seems to be able to hit up to 2GHz. We need a 1.8Ghz SGS2 to keep them down..
I do wonder if the Atom powered tabs will beat us though.
ph00ny said:
did you set both minimum speed and maximum speed to 1200?
Click to expand...
Click to collapse
Yes I did.
Sent from my GT-I9100 using XDA Premium App
I got 155.597 MFLOPS with my Galaxy S II overcloked to 1.56 GHz at 1.375v on Core voltage.
The rest is default.
I can probably break 160 MFLOPS if i take the CPU speed up to 1.65 GHz if i can get it to run stable there.
rovex said:
Its the Moto Zooms i worry about., Although the Tegra is slower the Zoom seems to be able to hit up to 2GHz. We need a 1.8Ghz SGS2 to keep them down..
I do wonder if the Atom powered tabs will beat us though.
Click to expand...
Click to collapse
Let me get this straight, you're 'worried' about another phone putting in a better score than your phone on a benchmark program?
Sent from my GT-I9100 using Tapatalk
Pagnell said:
Let me get this straight, you're 'worried' about another phone putting in a better score than your phone on a benchmark program?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
LOL, my thoughts exactly reading this entire thread...
Pagnell said:
Let me get this straight, you're 'worried' about another phone putting in a better score than your phone on a benchmark program?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
He's not even talking about a phone, if I understood what he meant, he's talking about the Xoom tablet.
[Sarcasm] Yes im going to have sleepless nights for weeks about it..[/sarcasm]
I would have thought the context (competitive spirit) was obvious..
Anyway it seem the Sensation bunch have found the Linpack cheat. 200 on a 1.2ghz non overclocked Sensation.. Nah...
Ok, now i managed to get 170.027 MFLOPS in Linpack with the CPU at 1.58 GHz and the Core voltage on 1.375v .
So far the phone are 100% stable at this clock.
Tom-Helge said:
Ok, now i managed to get 170.027 MFLOPS in Linpack with the CPU at 1.58 GHz and the Core voltage on 1.375v .
[image]
So far the phone are 100% stable at this clock.
Click to expand...
Click to collapse
Precision: Inconsistent Result
It's been about a year since any benchmarking threads have been created for the A500, and I'm interested to see how people are getting better performance.
I'm running Flexreaper v5 and I score around 6200 in AnTuTu. One other ROMs and other kernels I'm getting around 4300. However, the AnTuTu comparison charts show quite a few people scoring 7500+ with the A500.
How are people getting such high results?
Overclocking maybe?
essevee said:
Overclocking maybe?
Click to expand...
Click to collapse
Hoping for something a bit more specific. Kernel, ROM, CPU Frequency...
BTW - Mine is OCed to 1.5 GHz
Think I found one of the ROMs that's getting such high performance. I got the JB ROM from he would cannot be named, and this thing flies! 5600 in AnTuTu with no OC. Set GPU to 400 MHz and OC'ed CPU to 1.6 GHz, and that clocked in at 7225.
elmerohueso said:
Think I found one of the ROMs that's getting such high performance. I got the JB ROM from he would cannot be named, and this thing flies! 5600 in AnTuTu with no OC. Set GPU to 400 MHz and OC'ed CPU to 1.6 GHz, and that clocked in at 7225.
Click to expand...
Click to collapse
I'd be a little careful at 1.6. Runs a little unstable, and is only for benchmarks.
Moscow Desire said:
I'd be a little careful at 1.6. Runs a little unstable, and is only for benchmarks.
Click to expand...
Click to collapse
It looks like the new kernel allows clocking up to 1.68, so I have just left it at an even 1.6. I haven't run into any major instability so far (knock on wood), and I really like how smooth it is. I've finally been able to play Asphalt 7 smoothly (good way to blow off steam at work). Thanks, though.
[First forum post!]
I recently flashed franco.kernel onto my 16GB Nexus 4 (rooted, PA3+) and I overclocked it, but I was wondering how far I can go. I heard about a possible 2GHZ overclock but I'm not sure what kernel that uses. Any suggestions?
Hordiyevych said:
[First forum post!]
I recently flashed franco.kernel onto my 16GB Nexus 4 (rooted, PA3+) and I overclocked it, but I was wondering how far I can go. I heard about a possible 2GHZ overclock but I'm not sure what kernel that uses. Any suggestions?
Click to expand...
Click to collapse
no one can run 2ghz on their nexus 4
nvm.
simms22 said:
no one can run 2ghz on their nexus 4
Click to expand...
Click to collapse
A test kernel someone made awhile back when the nexus first came out it ran fine at 2ghz was a little hot at times but it worked :laugh:
Well, what is the highest that I would be able to overclock my Nexus, anyway? franco goes up to 1.7, I'm wondering whether it's possible to go any higher. And if I could go any higher, what kernel would I have to use? I'm just quite curious.
Faux has one that goes to 1.9 i think
PouperPoups said:
Faux has one that goes to 1.9 i think
Click to expand...
Click to collapse
test it. it doesnt test as a 1.9 kernel no matter how hard you try, its not really 1.9ghz. a 1.9ghz clocked cpu, will test like a 1.9 ghz cpu, not a 1.7ghz cpu. there are other kernels that go to 1.944ghz also, they test like 1.944ghz. but that doesnt matter, most phones will not be able to run at a "real" 1.944ghz.
simms22 said:
test it. it doesnt test as a 1.9 kernel no matter how hard you try, its not really 1.9ghz. a 1.9ghz clocked cpu, will test like a 1.9 ghz cpu, not a 1.7ghz cpu. there are other kernels that go to 1.944ghz also, they test like 1.944ghz. but that doesnt matter, most phones will not be able to run at a "real" 1.944ghz.
Click to expand...
Click to collapse
Mine runs at 1.944 just fine, with an undervolt of 150 across the board
qwahchees said:
Mine runs at 1.944 just fine, with an undervolt of 150 across the board
Click to expand...
Click to collapse
bench it, show me that it benches like 1944mhz. just because it says 1.9ghz, doesnt mean it actually is. that can be faked. 1944mhz will bench like 1944mhz, 1836mhz will bench like 1836mhz, and so on. if it benches like 1.7, 1.6, 1.5ghz, then its not 1.9ghz. sure benchmarks dont show real world use, but they do show what speed you are testing by their results. we know what range each speed should test at. fauxs' 1.9ghz doesnt test where 1.9ghz should test at, and faux has been caught before, on other devices, showing that the device is running at a higher speed when actually isnt.
simms22 said:
bench it, show me that it benches like 1944mhz. just because it says 1.9ghz, doesnt mean it actually is. that can be faked. 1944mhz will bench like 1944mhz, 1836mhz will bench like 1836mhz, and so on. if it benches like 1.7, 1.6, 1.5ghz, then its not 1.9ghz. sure benchmarks dont show real world use, but they do show what speed you are testing by their results. we know what range each speed should test at. fauxs' 1.9ghz doesnt test where 1.9ghz should test at, and faux has been caught before, on other devices, showing that the device is running at a higher speed when actually isnt.
Click to expand...
Click to collapse
Its becuase it throttles down when benching, its cause the freq cant stay that high the whole time without risking damaging the board so it throttles down to lower "safer" freq. On real cpu on a computer it has fan speeds to go higher when the temp is to high but that solution is not possible for mobile soc.
franco probably belives that 1.7 is the best possible OC since the throttling wont be that high. I would say that he is right but i prefer the stock speed and never mess with OC on mobile soc. But thats just me
More than often to much OC gives the opposite effect and makes the phone slower because of all the throttling.
Skickat från min Nexus 4 med Tapatalk 4 Beta
Utacka said:
Its becuase it throttles down when benching, its cause the freq cant stay that high the whole time without risking damaging the board so it throttles down to lower "safer" freq. On real cpu on a computer it has fan speeds to go higher when the temp is to high but that solution is not possible for mobile soc.
franco probably belives that 1.7 is the best possible OC since the throttling wont be that high. I would say that he is right but i prefer the stock speed and never mess with OC on mobile soc. But thats just me
More than often to much OC gives the opposite effect and makes the phone slower because of all the throttling.
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
pm sent to you
simms22 said:
pm sent to you
Click to expand...
Click to collapse
Thanks, I see what you mean now.
Skickat från min Nexus 4 med Tapatalk 4 Beta
IMO Trinity is probably best for overclocking, but even it can only go up to 1836 MHz. Also, there are risks to OC as well--which ranges from overheating to red light of death to your phone spontaneously combusting. Just letting you know
Sent by carrier pigeon