Develop Bugs

[Q] Quadrant Standered

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.

[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] What is an average quadrant score?

Please forgive me if this s somewhere else, but the search function is down I think.
I feel like my brand new evo is pretty laggy compared to what Ive seen. I have rooted and am running the newest stock kernel.
Ive tried Mik's rom and Myn's rom, they both net me an average score of 1100 on quadrant.
Am I way below where I should be? Seems like my menus are much "jerkier" than what Ive seen around.
Also, if anyone knows, what does wipe SD-EXT in recovery do?

EricSS619 said:
Please forgive me if this s somewhere else, but the search function is down I think.
I feel like my brand new evo is pretty laggy compared to what Ive seen. I have rooted and am running the newest stock kernel.
Ive tried Mik's rom and Myn's rom, they both net me an average score of 1100 on quadrant.
Am I way below where I should be? Seems like my menus are much "jerkier" than what Ive seen around.
Also, if anyone knows, what does wipe SD-EXT in recovery do?
Click to expand...
Click to collapse
I would agree that 1100 is average, but you could make your phone so much faster. Download Spare parts from the market and set you transitions and windows animations too fast. This should increase your quadrant score, thought it may take two test to show a boost. Also how long gave you had your evo on its current rom. The evo is like a person, it needs time to adapt to its kernel. So when you flash a rom, be patient and give your phone a couple day (3 or 4) to get used to the kernel. Then if performance and/or battery is bad, you can pm and i can recommend the kernel i use as well as others. With my current set up, which is Myn's RLS 5 and net 4.3 cfs, but don't worry just sit on your current set up. Good luck

redsoxfan320 said:
I would agree that 1100 is average, but you could make your phone so much faster. Download Spare parts from the market and set you transitions and windows animations too fast. This should increase your quadrant score, thought it may take two test to show a boost. Also how long gave you had your evo on its current rom. The evo is like a person, it needs time to adapt to its kernel. So when you flash a rom, be patient and give your phone a couple day (3 or 4) to get used to the kernel. Then if performance and/or battery is bad, you can pm and i can recommend the kernel i use as well as others. With my current set up, which is Myn's RLS 5 and net 4.3 cfs, but don't worry just sit on your current set up. Good luck
Click to expand...
Click to collapse
Thanks, I just flashed Myn's RLS 5 a few hours ago and I have been flashing like every day since I rooted. Ill give it a few days and see what happens. My girlfriend jsut got an EVO slide and I guess I just have envy since it seems so much snappier straight out of the box.
Not to mention my battery seems to die in a matter of a couple hours and hers has gone down only 30% in the last 16 hours.

EricSS619 said:
Thanks, I just flashed Myn's RLS 5 a few hours ago and I have been flashing like every day since I rooted. Ill give it a few days and see what happens. My girlfriend jsut got an EVO slide and I guess I just have envy since it seems so much snappier straight out of the box.
Not to mention my battery seems to die in a matter of a couple hours and hers has gone down only 30% in the last 16 hours.
Click to expand...
Click to collapse
I recommend just leaving it on the same kernel for the weekend. Also do you use sense as in the clock and different widgets. Because i removed sense from my phone and get about 19 hours on a single charge with regular use.

redsoxfan320 said:
I recommend just leaving it on the same kernel for the weekend. Also do you use sense as in the clock and different widgets. Because i removed sense from my phone and get about 19 hours on a single charge with regular use.
Click to expand...
Click to collapse
Yeah I do use sense. Not sure if Im ready to give it up yet though ><

1100 seems like an average score for an relatively "stock" rooted Evo with a custom rom. I've had my quadrant score range from 1100 to 1300 from just a custom rom. Flashing different kernels with net you different scores also. With just netarchy's 4.1.9 no havs, Fresh 3.5, no overclock netted me a score ranging from 1300-1400. Overclocking to 1.2 ghz got to 1450-1650. I'm sure I can tweak some more to squeeze more performance out of my Evo. But usually I keep my phone at stock speed with Fresh rom and I'm satisfied with its performance.
Sent from my PC36100 using XDA App

EricSS619 said:
Yeah I do use sense. Not sure if Im ready to give it up yet though ><
Click to expand...
Click to collapse
Okay because my bro has the same set up as me but gets about 4 hours less battery, because sense sucks battery life.

can anyone tell me if my numbers seem off i get about 1200-1300 quadrant and 32-33 on linpack with stock kernel and myns rls5...

EricSS619 said:
Please forgive me if this s somewhere else, but the search function is down I think.
I feel like my brand new evo is pretty laggy compared to what Ive seen. I have rooted and am running the newest stock kernel.
Ive tried Mik's rom and Myn's rom, they both net me an average score of 1100 on quadrant.
Am I way below where I should be? Seems like my menus are much "jerkier" than what Ive seen around.
Also, if anyone knows, what does wipe SD-EXT in recovery do?
Click to expand...
Click to collapse
I use MIUI and average around 1600-1700 on quadrant oc'd to 1150. The ROM itself is much smoother running than pretty much every sense rom I've tried but still not perfect. That "jerkiness" is a limitation of the EVO, no matter what ROM or kernel you use it still won't be iPhone smooth.
SD-EXT is where your apps are stored when using apps2sd. So wipe SD-EXT will wipe that partition.

I went from using stock sense with a score of 1100ish... To runnin CM6 with the stock kernel and a score of 1400 ish... My 3g speed went from an average of 450kbps to above 700... Go figure
Sent from my PC36100 using XDA App

[Q] Overclocking the Evo past 1.19

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.

So is it just my epic?

So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?

NissanNick said:
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
Are these freezes ONLY happening when running o/c? If so, then your hardware might not like o/c speeds. Please clarify that it is not an o/c issue due to the information you provided above.
If you're stable and having no locking issues on stock, then flash ROMS/kernels and of the bat start boosting to o/c speeds then seeing instability, how/why are you ruling out it's not a o/c or hardware limitation?
NissanNick said:
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
I don't think sprint will swap your phone out just because you can't manage stable o/c speeds on your phone. LOL

Sounds like you need to do the classic Wipe 3X before flashing.

Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.

NissanNick said:
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
Click to expand...
Click to collapse
It's not the overclocking that causes your phone to go into sleep of death, it is the low end. 100 Mhz causes sleep of death on a lot of phones on a custom ROM. Set your minimum frequency to 200 Mhz and you will be fine. Don't change any of the stoick voltages.

Try using stock speeds (400-1000). Then work your way incrementally in both directions to see which frequency(ies) cause your issues. Each phone is unique, so find the sweet spot.
I get the black screen of death about twice a month running twilight 1.1.1. My phone runs 200-1000 with no undervolting and set on conservative. I'm just too lazy to bother playing with settings since I'm holding out for SRF 1.3 to release.