[Q] Native Benchmark From SetCPU - G2 and Desire Z Q&A, Help & Troubleshooting

Can someone who has temporary root please post a "Native Bench" benchmark from SetCPU? I'm curious as to how the new processor performs in terms of raw power, without the JIT in 2.2 padding the numbers. I'm trying to compare it to my Vibrant (which doesn't have JIT) so this would be greatly appreciated.

Not sure which processor you mean but I'm averaging..
C:407-408
Neon:190-191
on my G2

By "new" I meant the MSM7230, which was new when the G2 was released... But I bought the G2 and answered the question for myself a while ago since apparently people couldn't be bothered to run a benchmark for 5 seconds
Thanks for taking the time to respond, though. I appreciate it, even if you are a bit late
BusinessSocks said:
Not sure which processor you mean but I'm averaging..
C:407-408
Neon:190-191
on my G2
Click to expand...
Click to collapse

Related

[DEV]_JIT Libs from XXJH3

For all users that have XXJP3 Froyo release installed. (i don't have Froyo installed) Here is libs from XXJH3 for JIT.
Maybe they are more optimized, only for users that understand what it is.
For instructions read this, you don't need to replace build.prop. The tutorial is for Android 2.1 but it's same for 2.2
vmlibs from XXJH3
Freshly installed Froyo : better run 14.19 MFLOPS
setenza01 said:
For all users that have XXJP3 Froyo release installed. (i don't have Froyo installed) Here is libs from XXJH3 for JIT.
Maybe they are more optimized, only for users that understand what it is.
For instructions read this, you don't need to replace build.prop. The tutorial is for Android 2.1 but it's same for 2.2
vmlibs from XXJH3
Freshly installed Froyo : better run 14.19 MFLOPS
Click to expand...
Click to collapse
have you tried this?
Does this speed up the phone or only the benchmarks?
Ok, I've just tried it.
Unfortunately, it gives me the same result.
Nearly, 14.5 MFLOPS with Linpack.
It was a nice try though.
No problems with these files as well.
I'm gonna have a look if it makes the phone be faster or not.
edit : With Quadrant advanced, it brings me ssssssslightly higher cpu score.
just about... 50 points more, I mean, in total score of 1900 or something (with ext2 fix)
Not really so much good but it's worth to have a try.
At least, we've found it out that we can get some files from Galaxy Tab.
Does it work on 2.1 ?
Sent from my GT-I9000 using XDA App
No, it doesn't. I'm using xxjp3 firmware ATM.
Sent from my GT-I9000 using Tapatalk
Mflops: 14.34
does anybody who tried this notice a difference in stability?
read: still so many FCs with this new JIT?
Maybe my question will sound too lame, but, did anyone try to use JIT libs from Nexus One? The procesor core is quite similar, and the instructions set is the same, so maybe it'll work?
I have. It ran at 15 mflops
Caused a LOT of fc's though
Sent from my GT-I9000 using XDA App
nm ignore my post
14M flops vs 3x Mflops the nexus one ... something goes wrong, do not you think?
braintheboss said:
14M flops vs 3x Mflops the nexus one ... something goes wrong, do not you think?
Click to expand...
Click to collapse
The first jit for nexus had similiar results. So wait for a proper release....
emelie said:
does anybody who tried this notice a difference in stability?
read: still so many FCs with this new JIT?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=736881&highlight=jit
DocRambone said:
http://forum.xda-developers.com/showthread.php?t=736881&highlight=jit
Click to expand...
Click to collapse
thx for the heads up, didn't notice that thread before.
so in a nutshell the JIT provided in the thread you referenced vs the JIT provided in this thread:
- still low results with benchmarks
i could care less about benchmark numbers. no offense and really thank you for pointing me to that thread!
what i'm looking for though, and this is mentionend in the thread you referenced, is stability of other apps which are used daily compared to benchmark apps.
emelie said:
thx for the heads up, didn't notice that thread before.
so in a nutshell the JIT provided in the thread you referenced vs the JIT provided in this thread:
- still low results with benchmarks
i could care less about benchmark numbers. no offense and really thank you for pointing me to that thread!
what i'm looking for though, and this is mentionend in the thread you referenced, is stability of other apps which are used daily compared to benchmark apps.
Click to expand...
Click to collapse
The current JIT is not stable for daily use. It was same for the first JIT implementations for Nexus and Desire.
Lets hope the will be a better froyo rom soon...
I am sure that linpack score will never be as high as we see today on N1. Maybe 20+ not higher.
If im wrong and with official 2.2 fw update score is 40+ then I will give away my phone for free
fua said:
I am sure that linpack score will never be as high as we see today on N1. Maybe 20+ not higher.
If im wrong and with official 2.2 fw update score is 40+ then I will give away my phone for free
Click to expand...
Click to collapse
My guess we see higher scores than 50+ in linpack
If samsung get their act together we will see 50 mflops. If not then 15 - 20
Sent from my GT-I9000 using XDA App
I'm starting to think the hummingbird might disappoint in performance with the JIT; Samsung might not be able to optimize the JIT as well as Google optimized it for the N1 (and all the other snapdragon-based devices). Look at Motorola, they just released the Droid 2 running a 45nm SoC not too different from the hummingbird and they only managed to get linpack up to 15Mflops with Froyo... I wouldn't think Motorola would do an official release of Froyo before optimizing it (but who knows, maybe pressure from Verizon to have a new device with Froyo before other carriers)
I doubt it, but there's also the possibility that there's something advantageous for the JIT in the Snapdragon architecture that is lacking in the OMAPs and Hummingbird architecture. I guess we'll see soon enough, we just have to hope for the best.

[Q] Percentage of well overclockable Desires?

Hi guys!
I haven't yet rooted my Desire(I would have but I was fool enough to install the 2.2 OTA).The main reason for me to root would be the ability to overclock my device.All this time that I have been around here on the Desire and Nexus One forums I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.However,to my great surprise,I noticed on OpenDesire ROM's thread that the Desire can be overclocked @1344MHz(which of course made me think a big HELL YEAH!).Is that number ok for all of us or for some select few?I remember from my Hero days that only some few,lucky guys like myself could overclock up to 768MHz,although there were cases of people,rare,yet not unheard of,that could overclock @844MHz.Is this the case here or are things different with the Snapdragon?
Many many thanks guys!
C'mon guys,no one?
tolis626 said:
I have been seeing that our devices are overclocked only up to 1113MHz and only in very rare cases 1267MHz.
Click to expand...
Click to collapse
I don't think overclocking to 1267MHz happens in rare cases. I had no problems oc-ing to 1267 and it seems that a lot of forum member were able to do this too.
Why don't you downgrade your HBoot to 0.80, root your phone and try it out?
Just make sure your phone does not become too hot if you try 1344MHz.
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
foxmeister said:
I have to ask the question, but does it really matter?
IMHO, the Desire is plenty fast enough that overclocking it simply isn't necessary.
I can understand underclocking to eek out more battery life, but other than gaining a few points on some benchmarks, I really don't see the point in overclocking.
Regards,
Dave
Click to expand...
Click to collapse
so this, its really not needed at all. a decent fast rom and 1ghz is more than enought for things to be super speedy. any decent kernal will provide more than enough speed.
overclocking(and lots of other things these days!) reminds me of that bit in jurassic park where they are all sat around the table and geoff goldblum says:
"Yeah, but your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should".
herein lies the lesson, just because you can do it doesnt mean you should do it.
Well,I have my reasons wanting to overclock...First off,I will check if I can see any difference in speed or smoothness.If there isn't,I will just revert the clock back to normal after some benchmarks.
I just am the kind of guy that wants to get the most out of his phone!
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
sbdags said:
I think ALL Desires can overclock to 1267Mhz. It's not that rare and I've not seen anyone having a problem with it.
It does make things a bit snappier as well.
Click to expand...
Click to collapse
That's what I'm talkin' about man!
And now that I think of it,it's not that much.I mean,the Hero could overclock @768,which is 45% overclocking.The Desire's 1267 is about 27% and 1344 is about 34,5%.Nothing too much!So why not?
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Kinma said:
Every CPU is different. The Qualcomm Snapdragon is a very different beast compared to the Qualcomm MSM 7200A.
We are just starting to learn what we can do with the Snapdragon without damaging it.
Click to expand...
Click to collapse
Well my man,in this case the MSM7200A is no beast but rather a pooch that barks to no avail!Good pet however!
Joking aside,the Snapdragon is a beast for a mobile phone,but even beasts get beaten.Now,if I can somehow reach or even get close to the performance of the Galaxy S or the Droid X I'll be happy.Software wise I believe that HTC is far superior ,but it's hardware is a little out of date.Let's see what their new devices will do for us!
Btw,does anyone know if the so anticipated HTC Ace will be anything better than what we already have or if it will be the Evo for GSM users?
Thanks!
The desire is plenty fast as it is and I don't see the point of overclocking it. I've had it to 1267 in the past and it made no difference at all for usability. I'm also the type that overclocks all his computers...
Sent from my HTC Desire using Tapatalk
Personal preferences dude...What everyone does with their phone is their own business.I wish I could resist overclocking too!
However,I was watching a thread over at the N1 forums in which a dude named Storm9999(genius dude,not just a random one) stated that an overclock @1,3GHz could fry our phones.Is that so?I mean,I know overclocking reduces the CPU's lifetime,but is it THAT MUCH dangerous?
I think overclocking can kill your phone.. I use to overclock my own o2 orbit and it died after a year..
Friend of mine just burned his old HTC by overclocking it and as a consequence is going to buy a desire.
I had my phone overclocked at 1345Mhz for a moment, just to test it, and it made no real difference to when it was overclocked at around 1.2Ghz, which in turn has very very little difference to stock 1Ghz.
I think the only case where you see some small impact is in games.
I've tested HD recording at 1.345 Ghz and stock speed and there was no difference.
If anything, it's going to kill your battery and shorten its life for sure, going so high. If ever I will OC again I won't go over 1.1 and only if I find some tangible improvements.
As said, this phone is always fast, there is no real need to OC, other than for 'fun'.
The fun is what I want...Well,most probably I will have my phone overclocked at the maximum speed it can get for about a week or two and then go back to 1 or 1,1GHz...
Btw,your signature kicks ass andycted!

[Q] overclocking issue

Now me and 4 of my friends have EVOs and I rooted all of them. Some of this EVOs are hardware verson 003 and one of them is 002. 2 are novatec and 3 are epson. We are all running fresh 3.1.0.2 with netarchy-toastmod-4.1.8 bfs, mine has 4.1.9 BETA, but my one friend is running CM6 RC2 because he loves it. Now all of these EVOs can overclock to 1.27 GHz but when we do it they freeze and crash. My one friend can go up to 1.22 just fine but the rest of us are stuck at 1.19. I want to know why this happens. If our phones cant take that much why have it. What's the point we have 5 EVOs here none can handle it. Im I doing something wrong is the a joke WTF!!
All the phones are different. Most can't oc past 1152 without causing reboots, mine included. Other than ridiculous benchmark numbers, I don't think you'll notice a huge difference in performance.
Sent from my FROYO'D EVO using xda app
dglowe343 said:
All the phones are different. Most can't oc past 1152 without causing reboots, mine included. Other than ridiculous benchmark numbers, I don't think you'll notice a huge difference in performance.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
andre104623 said:
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
Click to expand...
Click to collapse
Simple answer, not all chips are made the same. They are made to minimum standards. Your chip is rated to 1 ghz, and thats what the chip company delivered.
Some chips can handle more, but thats just luck.
As far as why do people strive for the high numbers, thats personal preference. Not everyone here cares about 30+ hours of battery life. Some just like the bragging rights.
Unfortunantly, all EVO's are not created equal. You can have the same hardware and version numbers on 2 devices, but one may be able to OC that high, and one may not. This is also why not everyone can run the superbattery kernel from the Baked Snack rom. There doesn't seem to be any rhyme or reason to it.
and c'mon, watch the language. There are rules around here, you know?
fachadick said:
and c'mon, watch the language. There are rules around here, you know?
Click to expand...
Click to collapse
Sorry, I thought we are all adults one swear now and again wont kill anyone
andre104623 said:
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
Click to expand...
Click to collapse
actually, cm snap 7.0 and 7.1 are extremely stable, have great battery life and have excellent benchmarks as well. i dont have a single problem with cm snap kernels and i run at 1228mhz when fully charged.
andre104623 said:
I dont really care about performance I just wanted to know why this happens and dont get me started on benchmark numbers its just and ****ing number who cares as long as the phone is running fast and sable and has good battery life then its fine some people go out of there way to make there benchmark the highest like CM-snap ver.7.0 kernel.
Click to expand...
Click to collapse
that's not going out of the way... it's making the phone as fast as possible. why do anything if you aren't gonna push the limit? how are you gonna develop if you don't push the limit?

GPU overclocking

Hi im running xdandroid on my rhod210 and i am very happy with it, one of the few annoying downsides to it is the ****ty fps of 17.5 which is quite choppy for most 3d games.
But iv heard that gpu overclock for rhodium is definatly possible with the right line added to startup.txt.
look at this thread:http://forum.xda-developers.com/showthread.php?t=697673
it says about overclocking the vogue with a line in startup.txt, with it the vogue achieved 36.5fps!!! which is brilliant, and the vogue is inferior to the tp2 harware wise.
So we know its possible and will give us great improvement, so all we need is someone with the know how to tell us how? it was sais that we would "need to talk to your kernel devs to add this functionality" so hopefully this will be a great update.
any comments, anyone willing to help? anyone working on the xdandroid project willing to implement this? it would be much appreciated.
tank you, please reply :]
Thus far I think we've only overclocked the main CPU, haven't touched the GPU. Looks promising tho.
ohhhhhhhh my god its really ?? i cant belief !! its co0o0o0o0o0o0ol
Jandyman said:
Hi im running xdandroid on my rhod210 and i am very happy with it, one of the few annoying downsides to it is the ****ty fps of 17.5 which is quite choppy for most 3d games.
But iv heard that gpu overclock for rhodium is definatly possible with the right line added to startup.txt.
look at this thread:http://forum.xda-developers.com/showthread.php?t=697673
it says about overclocking the vogue with a line in startup.txt, with it the vogue achieved 36.5fps!!! which is brilliant, and the vogue is inferior to the tp2 harware wise.
So we know its possible and will give us great improvement, so all we need is someone with the know how to tell us how? it was sais that we would "need to talk to your kernel devs to add this functionality" so hopefully this will be a great update.
any comments, anyone willing to help? anyone working on the xdandroid project willing to implement this? it would be much appreciated.
tank you, please reply :]
Click to expand...
Click to collapse
this would be awesome, would definitely raise its quadrant score
I'm not sure what is Vogue and what screen resolution it has, but I supppose as it's old phone with Qvga. Qvga means 1/4 of the pushing pixels that we have on screen. So if Rhodium had qvga screen we would have 4 times beter frame rate. 69 FPS. I wouldn't call 17,5 fps of WVGA 3D ****ty in phone that was presented almost 2 years ago with different operating system. And we should remember that it's Android, which isn't (for now) fully working.
I'm not sure what is Vogue and what screen resolution it has, but I supppose as it's old phone with Qvga. Qvga means 1/4 of the pushing pixels that we have on screen. So if Rhodium had qvga screen we would have 4 times beter frame rate. 69 FPS. I wouldn't call 17,5 fps of WVGA 3D ****ty in phone that was presented almost 2 years ago with different operating system. And we should remember that it's Android, which isn't (for now) fully working.
Click to expand...
Click to collapse
your right the htc vogue has a qvga screen, but it also has less processing power so this should somewhat balence things out. But i still think gpu overclocking would greatly improve the rhodiums performance and if i remember right neoseekers version of android recorded 24.1 fps, and that is without gpu overclock. so improvement is more than possible.
ohhhhhh god 24.1 fbs its brilliant beside 17.5 to the htc rhodium its co0o0o0o0ol
I tried the startup option they were talking about in the thread referenced... if the value is too low then maybe that is the issue, or it just doesn't work. Either way got 17.6fps on neocore before and AFTER changing the startup.txt and rebooting. Unless a dev wants to chime in I don't think that is the only step to overclocking.
Well those startup options are in the kernel. So we'd have to get the kernel enabled before we can ever dream of having the startup option work
Basically any option that's set in cmdline is being passed to the kernel - so if our kernel isn't enabled for that feature/option, it'll just get ignored.
arrgghh beat me to it
i dont kno how hard or easy it is to change the kernal to allow this but hopefully the devs will hear and implement this feature. Or if someone could contact them suggesting it would be great.
its actually simple to over-clock, but does anyone know what values to overclock to before burning up the phone?
If you guys want this done, id look for an existing winmo solution to do this on windows. Once we know what values to use on the clock regs, we can easily port it over on android.
a quick google search of 'overclocking gpu on htc touch pro 2' has lead me to nothing :/ im presuming this is because there is no need to overclock the gpu when running windows mobile because there are very few decent windows mobile games (as far as i kno) and havnt found any using 3d, specially not free.
But if we find the detailed specs of the touch pro 2, and then search for the safe frequesncy to overclock that power of gpu too wouldnt it be the same? thats probly our best bet unless someone can find evidence of overclocking gpu on a tp2 running windows mobile.
Jandyman said:
a quick google search of 'overclocking gpu on htc touch pro 2' has lead me to nothing :/ im presuming this is because there is no need to overclock the gpu when running windows mobile because there are very few decent windows mobile games (as far as i kno) and havnt found any using 3d, specially not free.
But if we find the detailed specs of the touch pro 2, and then search for the safe frequesncy to overclock that power of gpu too wouldnt it be the same? thats probly our best bet unless someone can find evidence of overclocking gpu on a tp2 running windows mobile.
Click to expand...
Click to collapse
Nahh.. don't work that way. Its not like 1 clock you can change to any frequency. All the clocks are derived from the plls and you would need to do some math to determine what pll to use and what to devide it by.
There are also other clocks involved with the display. mddi, mdp are other clocks that can also change. Vogue for example has the ability to over clock mddi.
But yea.. a winmo app would be very helpful.
[ACL] said:
Nahh.. don't work that way. Its not like 1 clock you can change to any frequency. All the clocks are derived from the plls and you would need to do some math to determine what pll to use and what to devide it by.
Click to expand...
Click to collapse
For those who are still unawares at this point, PLLs are crystals on the mainboard that resonate at different frequencies. Thus you would need to tear open the phone and figure out which PLLs are linked to the GPU and which are just ancillary, and then be able to put it back together. Whomever wants to take this upon themselves, I wish them luck.
Hamsteriel said:
For those who are still unawares at this point, PLLs are crystals on the mainboard that resonate at different frequencies. Thus you would need to tear open the phone and figure out which PLLs are linked to the GPU and which are just ancillary, and then be able to put it back together. Whomever wants to take this upon themselves, I wish them luck.
Click to expand...
Click to collapse
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
[ACL] said:
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
Click to expand...
Click to collapse
Yay, I can haz FPS?
[ACL] said:
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
Click to expand...
Click to collapse
Just curious if this work on GPU overclocking ever got anywhere or was determined to be possible in the future?
it's possible - but more than likely it would cause severe problems with battery life and stability. Considering the dismal state of our battery life already I doubt the work is worth it for an extra 4fps in angry birds.
Thread necromancy is bad mkay
randomblame said:
it's possible - but more than likely it would cause severe problems with battery life and stability. Considering the dismal state of our battery life already I doubt the work is worth it for an extra 4fps in angry birds.
Thread necromancy is bad mkay
Click to expand...
Click to collapse
If you're up to date on kernels, especially if you're on Wistilt's test branch, battery life is great. When sleeping, battery life is measured in days now. Anyway, just because the compromises involved don't interest you doesn't mean they wouldn't work for someone else.
Alternatively to overclocking the GPU, I wonder what sort of UI smoothness/framerates would be possible if the display driver were recoded to pixel double to our screen from 400x240 (same resolution as a Samsung Intercept).
I played around with the lcd density but that didn't seem to be able to create the same effect, as program's like Neocore still knew that my display was actually 800x480 and displayed as such.

[Q] Highest stable overclock on Touch Pro 2?

Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
reocej said:
Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
Click to expand...
Click to collapse
Depends on the device. Most seem to max out at 748,800khz, one guy claimed he hit 820mhz or smth outrageous.
Honestly the best way to establish what your device can handle is to push the OC in WinMo until it's not stable any longer. That should be a good indicator of how far you can push Android.
Honestly I found OCing Android to be way more trouble than it's worth - the phone seemed to lag even more, and it definitely made the device less stable. I'm not a big fan of overclocking my computer either, so I am a little biased.
Cool. Thanks arrrghh. I reprogrammed a USSC TP2 to use with PagePlus for my daughter and put Android on it for her. Just wanted to try and push it to its limits I guess and see what it would do. What class/size/brand card do you suggest I use? Right now it is using a Sandisk class 6 8 gig card, but I've heard some have gotten better performance from class 2 cards.
I'd start at around 600mhz and keep pushing it up 20mhz at a time. The clock driver only takes it in steps of 19.2mhz, but is smart enough to divide it correctly via mod. At 640 or so the bottom started to get noticeably warm, and I've set it at 660 right now.
Each device is different, some take overclocks easily than others.
-- Starfox
Thanks for the help guys, I'll keep tinkering with it.
I've a RHOD100 and have acpuclock.oc_freq_khz=692000 on FRX07 and all is well and does not seem to even get any way warm underneath.
Mind you, while I've set this, is there any way to check within Android as to what speed my TP2 thinks it's actually running at (in case it is ignoring the setting in the setup file) ?
However, it is possible that the speed may work differently with differing builds of the various components but maybe someone more knowledgable on here could confirm whether or not this is the case.
C
Hi,
i use the tool "CPU Master Free" to see the actually clock speed (i hope it shows the right values).
At this time its oc at 633,6 Mhz an no problems.
sebastian
Perfect - it says I'm running at 691.2Mhz
C
reocej said:
Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
Click to expand...
Click to collapse
Got my Tilt2 (most recent kernel + rootfs) maxed out at 768.000MHz, and I noticed smoother scrolling and window animations.
But for me, I noticed that the phone actually freezes at times.. even when the phone wasn't overclocked. I believe that's just bugs in the kernel, though, soo not much to do about that from my experience, OC performance relies heavily on the device and kernel version (if that wasn't obvious lol).
EDIT: Ehh, I've read that anywhere from 600-640MHz is the most stable. Currently I'm at 595.2MHz and am noticing an improvement in stability over 768MHz.. Hope this helps.

Categories

Resources