Related
hello all,
i was just curious, how come my quadrant scores are always so low (mid 1100s)? i know that's not terribly low, but it is not close to where the "evo benchers" site reports that they are. currently im using the new htc kernal, only becuase i have only seen minimal performance changes with kings or netarchy.
thank you!
when Evo first came out they were only mid 500's...
depends on rom you are running also i believe, i only got 1100-1200 running Sense roms with stock HTC Kernel.
With CM Nightlies + Snap7.6 + Turbo Mode + 1.2ghz setCPU .... math, lol, i have gone as high as 2600 on quadrant.
It's just a basic benchmark and unless you have the paid version that breaks down your score it isn't really a good thing to go by.
1100 is pretty standard with the new HTC kernel and a sense rom. I run VaelPak, trimmed some extra fat, and get 1350 with stock kernel, 1500 with kingx #10. So ill stick with the stock kernel, better battery life imo.
Hey... I think this thing makes phone calls too!
After alot of work and tweaking got my EVO to its highest quandrant yet..1585 and Linpack of 33.899 MFlops.
Always a great day when one has the full freedom to R&D something they purchased with their hard earned money without being shackled.
I use snap v7.6 w/turbo activated and just got 2483 , w/linpack 37.21
f10g44 said:
hello all,
i was just curious, how come my quadrant scores are always so low (mid 1100s)? i know that's not terribly low, but it is not close to where the "evo benchers" site reports that they are. currently im using the new htc kernal, only becuase i have only seen minimal performance changes with kings or netarchy.
thank you!
Click to expand...
Click to collapse
My scores are worse. I avg around 1000, usually 900something
Look a page or two down and the very helpful and patient peopele here gave my several suggestions. I haven't tried any of them yet, but I will when I have more time.
Ive gotten 2700's a few time with snap and Cyanogen 6.1 OC'd of course.
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
I'm running cr_mod w/ ota update, with dumfuq's cmkernel 4.0 flashed over it, and I ran a quadrant benchmark for the hell of it and it gave me a 400 and something, while clocked at 844 mhz. Cm6 gave me a 1200 and something. Now I know my phone isn't performing that low, because frankly, although not quite as snappy, has smoother animations and such. I can see it scoring as low as an 1100 or 1000 on the stock rom, but 800 points lower? A measley 400? I'm thinking of discrediting the score, since in my everyday use, I know it is not that bad. I just can't think of what would throw the score down THAT low. Might it have something to do with the kernel I flashed?
Sent from my T-Mobile myTouch 3G Slide using XDA App
MusicMan374 said:
I'm running cr_mod w/ ota update, with dumfuq's cmkernel 4.0 flashed over it, and I ran a quadrant benchmark for the hell of it and it gave me a 400 and something, while clocked at 844 mhz. Cm6 gave me a 1200 and something. Now I know my phone isn't performing that low, because frankly, although not quite as snappy, has smoother animations and such. I can see it scoring as low as an 1100 or 1000 on the stock rom, but 800 points lower? A measley 400? I'm thinking of discrediting the score, since in my everyday use, I know it is not that bad. I just can't think of what would throw the score down THAT low. Might it have something to do with the kernel I flashed?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
It doesn't have jit which and it's 2.1 as we have seen putting 2.2 on a phone dramatically increases scores mainly due to jit. Though you may not see too many differences in speed but they are there.
Sent from my T-Mobile myTouch 3G Slide using XDA App
acejoker25000 said:
It doesn't have jit which and it's 2.1 as we have seen putting 2.2 on a phone dramatically increases scores mainly due to jit. Though you may not see too many differences in speed but they are there.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Ah, yeah, in terms of user experience I feel no significant difference. I'll just ignore the scores until cm7 comes out.
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
Ah, yeah, in terms of user experience I feel no significant difference. I'll just ignore the scores until cm7 comes out.
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
Cm7 would be 2.3...But the score will always be lower on a sense rom than stock, Cm has perf features that cant be added to the stock rom...But if you use the jit mod for 2.1 you will get about 5xx w/ OC at max...Which is low, but you have to consider that this is meant as a mid-low range device...Have you seen some of the newest lowend androids out there? Like the optimus or whatever the LG phone is-it's nothing compared to the slide IMO.
Ace42 said:
Cm7 would be 2.3...But the score will always be lower on a sense rom than stock, Cm has perf features that cant be added to the stock rom...But if you use the jit mod for 2.1 you will get about 5xx w/ OC at max...Which is low, but you have to consider that this is meant as a mid-low range device...Have you seen some of the newest lowend androids out there? Like the optimus or whatever the LG phone is-it's nothing compared to the slide IMO.
Click to expand...
Click to collapse
I know cm7 is gingerbread, I don't like cm6, battery drain bug with cell radio. That's why I want to wait. I know its a midrange phone, still gets 1200 on cm6. Like I said, the user experience is fine I'll just leave it alone
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
I know cm7 is gingerbread, I don't like cm6, battery drain bug with cell radio. That's why I want to wait. I know its a midrange phone, still gets 1200 on cm6. Like I said, the user experience is fine I'll just leave it alone
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
The scores don't translate into better performance for me, in CM6 it's quick w/o OC-just like on stock where it's fast w/ def clocks. But I do like to see higher values just for the hell of it.
Ace42 said:
The scores don't translate into better performance for me, in CM6 it's quick w/o OC-just like on stock where it's fast w/ def clocks. But I do like to see higher values just for the hell of it.
Click to expand...
Click to collapse
Yeah, haha I actually studied the quadrant test as it was running, it seems to have HORRIBLE, and I mean REALLY REALLY bad file system write times. It took forever to get past those tests.
I flashed CM6.1 stable, because of a combination of my obsessive ROM flashing syndrome (according to r0man) and my desire to get the gingerbread Latin IME on my phone. Plus, I used what's-his-face's anyfirmware theme porter to port the green theme in miguel's theme port thread to cm6.1-stable, since miguel's is based off of a nightly. The font didn't get ported, but I was in it for the visual elements anyway, so no big issue there. cm6.1 is faster, but the 2d animations are more prone to lag than sense roms, for whatever reason. Someone once told me that it was because HTC puts their own window animations in and adds more frames to them to make them smoother.
Anyway, I guess the quadrant scores didn't matter too much, sense was awesome, but I'm happy where I am with cm6.1-stable themed. Quadrant scores are quite pleasing as well
So, Im sure this was answered somewhere, and I searched all over.
With that said, why cant the Evo be overclocked past the standard 1.19 or 1.2? I know stability is an issue, but there are other ARM processors that can OC almost double. Is the Evo ARM processor just not able to handle anything past that?
Does anyone know?
Thank you for the insite
You cannot compare the processor in teh Evo to other similar processors. Every single processor is different, and overclocking the evo past those speeds could brick it.
Why would you want to overclock that far? The Evo has no ventilation and crappy power management, even with an extended battery. You're taking an already unstable system and pushing it to the edge. Not only will your phone overheat and freeze, but you can permanently damage the hardware.
I know every processor is different and each one has their own limits.
There is always a risk of bricking and damaging the actual hardware, but what im asking is, in theory, and a practical test, can you push the evo processor past the 1.19 that seems to be the limit (im not talking about going huge, but is there a possibility of being able to hit the 1.5Ghz?). Because there are certain frequencies that are not stable, but ones slightly past that could be stable.
Just throwing it out there.
A car traveling at 120 MPH is not as easy to control as a car doing the speed limit.
try it out n see what happens n then report back ur findings for others that have the same question and cannot find an answer anywhere
Product F(RED) said:
A car traveling at 120 MPH is not as easy to control as a car doing the speed limit.
Click to expand...
Click to collapse
good analogy but that doesnt help anything.
{ParanoiA} said:
try it out n see what happens n then report back ur findings for others that have the same question and cannot find an answer anywhere
Click to expand...
Click to collapse
I would, but all the kernels that the Devs have developed have either a limit put on them, or they havent been able to allow it to OC that far
shagav said:
good analogy but that doesnt help anything.
I would, but all the kernels that the Devs have developed have either a limit put on them, or they havent been able to allow it to OC that far
Click to expand...
Click to collapse
I was wondering this too. It would be nice to have the option to push it over 1.19ghz, I'll be the test dummy.
My Evo can handle 1228 fairly well but can tell its not as stable as say 1190. 1190 MHz is no prob...1267 usually crashes after a run or 3 in quadrant. 1113 runs niiiice for me and my 0004 evo
stkiswr said:
My Evo can handle 1228 fairly well but can tell its not as stable as say 1190. 1190 MHz is no prob...1267 usually crashes after a run or 3 in quadrant. 1113 runs niiiice for me and my 0004 evo
Click to expand...
Click to collapse
I can run 1190 just fine. Can a Dev possibly create a kernel that allows us to go past 1.2whatever.
I can't go up to 1.19 stabley
Gimme a couple a days to come up with a new sig that is cool.
if I pass 1190 endless bootloop.... then ya gotta be fast and turn that damn thing down
I can go to 1228 MHz with Tiamat but it will crash and reboot once you do a couple of things.
shagav said:
So, Im sure this was answered somewhere, and I searched all over.
With that said, why cant the Evo be overclocked past the standard 1.19 or 1.2? I know stability is an issue, but there are other ARM processors that can OC almost double. Is the Evo ARM processor just not able to handle anything past that?
Does anyone know?
Thank you for the insite
Click to expand...
Click to collapse
despite the meriad of answers you have gotten, I have been running my Evo on Sprint lovers Rom, and KiNgxKernel-Evo-12-BFS357-2.6.32.25-Flashable.zip for kernal.
I have been overclocked at 1267 since the day the kernal came out. it is singularly the only kernal that has allowed me to do this without ever crashing. OH, and I'm using
SetCPU 1267 on both min and max and scaling set to performance.
shagav said:
I know every processor is different and each one has their own limits.
There is always a risk of bricking and damaging the actual hardware, but what im asking is, in theory, and a practical test, can you push the evo processor past the 1.19 that seems to be the limit (im not talking about going huge, but is there a possibility of being able to hit the 1.5Ghz?). Because there are certain frequencies that are not stable, but ones slightly past that could be stable.
Just throwing it out there.
Click to expand...
Click to collapse
Not going too big? Going from 1.0 ghz to 1.5ghz on a phone is like going from a civic to a v8. Alot of computer cpu's dont even overclock 500 mhz. I think you're expecting a little too much from a phone. If you want more, go buy a dual-core cpu atrix 4g or something. I'm a speed freak myself when it comes to cpu overclocking (mainly on computers) but 1.113 is plenty for a phone. It even runs fine at 600mhz. Dont get me wrong, it would be cool to get it that high, but your phone would hate you lol
Overclocking
Just flashed Netflix-AllianceROM-2.1-HybriD-3D-OTA-Themed-r7.3TCsigned.zip and was wondering if there is a safe compatible overclocking kernel. Anyone have an idea?
kdogg530 said:
Just flashed Netflix-AllianceROM-2.1-HybriD-3D-OTA-Themed-r7.3TCsigned.zip and was wondering if there is a safe compatible overclocking kernel. Anyone have an idea?
Click to expand...
Click to collapse
There are tons of kernals available in the Dev forum. I personally recommend Netarchy's kernals, but you are free to try any of them.
kdogg530 said:
Just flashed Netflix-AllianceROM-2.1-HybriD-3D-OTA-Themed-r7.3TCsigned.zip and was wondering if there is a safe compatible overclocking kernel. Anyone have an idea?
Click to expand...
Click to collapse
Until HTC drops source codes you will lose camera and other things.
How did you overclock the CPU? I have tried the setCPU and it does not work, I have my Phone rooted, installed the crazy UNleashed rom (since uninstalled) and could not get the setCPU to overclock. Even though UNleashed is made to do that, and I have read others getting over clocked. I am running Synergy now, which I do not think it can Overclock the EVO, but I would like to know how you fine folks are accomplishing this. I would love to go 1.1 right now.
AmericanAlien said:
How did you overclock the CPU? I have tried the setCPU and it does not work, I have my Phone rooted, installed the crazy UNleashed rom (since uninstalled) and could not get the setCPU to overclock. Even though UNleashed is made to do that, and I have read others getting over clocked. I am running Synergy now, which I do not think it can Overclock the EVO, but I would like to know how you fine folks are accomplishing this. I would love to go 1.1 right now.
Click to expand...
Click to collapse
If you're using a stock HTC kernel, hit menu inside SetCPU -> Perflock Disabler. Disable Perflock -> Set On Boot. Ta da.
Hi,
Im trying to get a bit of rock ´n roll out of my Defy+ thru serious overclocking,
im running MS2Ginger 3.0 at the moment that doesnt seem to be the perfect rom for getting great speeds, but it works.
Been running 1350Mhz for a while which seems to work rather good, going to 1400 makes my Defy more sluggish than a led slug. So that doesnt work, atleast not for what i can see.
The problem i see is when running Quadrant benchmarks, i only get numbers around 300 on the 2D test, is that normal?
Can someone tell me about a rom that could make me roll even faster and higher up in the result lists of Quadrant benchmark?
Regards.
So 214 views and nobody knows anything? Sounds impoosible on this forum
Don't know much about fast ROMs but everybody brags about CM7, of course. Also there are some people who claim Mokee os (CM7 Based) is the fastest. Check them out and let us know what you find out
Anyway, they say Quadrant isn't everything.
Sent from my Defy+ using xda premium (app needs update!)
fiskenigaten said:
Anyway, they say Quadrant isn't everything.
Sent from my Defy+ using xda premium (app needs update!)
Click to expand...
Click to collapse
exactly...
if you want fast delete all apps except for system ones...
& lob it off a tall building ^^ :chortle:
fiskenigaten said:
Don't know much about fast ROMs but everybody brags about CM7, of course. Also there are some people who claim Mokee os (CM7 Based) is the fastest. Check them out and let us know what you find out
Anyway, they say Quadrant isn't everything.
Sent from my Defy+ using xda premium (app needs update!)
Click to expand...
Click to collapse
Ok thanks for the advice, i'll check them out and post some kind of measurments
King_Rat said:
exactly...
if you want fast delete all apps except for system ones...
& lob it off a tall building ^^ :chortle:
Click to expand...
Click to collapse
Ok they say the Defy is a rugged phone but hell knows if that would be healthy for it. But as they say it aint the speed that kills its suddenly coming to a stop that kills so maybe i should go for a try
I recommend setting max and min to 1350 and also performance governor, on v6 supercharger before benching run an enginge flush and kill all apps using process manager except quadrant
DEFYing the Android planet with ICS
Ok i´ll try that V6 thingie but before that i thought i would tell what i have noticed so far.
MS2Ginger stayed around 1900 score on Quadrant with a top of 2100.
CyanogenMod seems to stay around 2400 with a peak of 2501 so far.
CyanogenMod seems to be better on the hardware tests except on the graphical parts where it seems to drop a couple of FPS, Anyone know any good
advice to maximize the graphical parts of CM?
A fun thing to notice is that with the original settings and MS2Ginger i achieved a score of 1350 and now riding around 2500, pretty nice.
One down thou with CM is that i woke up this morning without a statusbar and when the alarm went off i couldnt shut it off except for rebooting the phone.
mihovil13 said:
I recommend setting max and min to 1350 and also performance governor, on v6 supercharger before benching run an enginge flush and kill all apps using process manager except quadrant
DEFYing the Android planet with ICS
Click to expand...
Click to collapse
Ok now im un-supercharged again, either i did something very wrong or that script only worked in the wrong direction on my Defy+. Installed it and ended up running 1700 - 1800 scores on Quadrant, uninstalled it and is now back to 2300, dont know where the last 100 - 200 points ended up, will do some more tests before moving on to the Mokee OS rom.
Have a safe day/evening
I jujst wanted to say that im in no way is trying to put down the MS2Ginger developers work, this is just me and personal opinions in the hunt for a better performing Defy+
Cheers
in my opinion, oc-ing the defy to over 1.2ghz makes no sense and it only damages your cpu in the long run. i think that managing your ram gives a lot smoother experience than oc-ing your phone, because the only apps that dont run smooth on this little beauty are hd games, but they were never intended to. im using ram manager pro from market (play store), try it, maybe it helps!
sent from my cm7 defy...