I've just saw Galaxy S Antutu Benchmark screens that had 3900 score @ ~~1400MHz and I'm wondering why our device even if it's pretty similiar does score only 2900 ? It's a huge difference.
Even oldie like tuned Xperia X8 can score 2400 which isn't even ARMv7 and has 256MB RAM with older GPU.
I'm a bit disappointed by our ROMs, because there are many of them but none is perfect. ILWT seemed to me the best (and it is), but has lower score than ARHD, which needs swap and many improvements to work smoothly and it isn't still capable running games like GTA3, MC3, ICS can't run them too because phone just reboots (ICS is in beta stage so I'm not looking at stability yet, but that's bad ).
ILWT result in best performance as for GTA3, this game was running great.
Here's screen of SGS Antutu:
http://desmond.imageshack.us/Himg855/scaled.php?server=855&filename=1331989260894.jpg&res=medium
X8 (for reference, score is without sdcard): http://iv.pl/images/61942066283720320721.png
and our Desire Z's in this thread, which is highest
http://forum.xda-developers.com/showthread.php?t=1560772
Why devs won't focus on improving performance? schedulers, more oc values, governors isn't everything, why then SGS can get 2x more score in RAM if it has 512MB too. Overclocking in SGS by 100MHz steps improve score by ~200, and in Desire Z it looks like it's not working as good because I didn't noticed that BIG boost, just ~50pts. I know it's not that easy to develop, but we're alot behind with performance than SGS.
SGX540 is probably better GPU and there's other processor, but if stock software had 3000pts in SGS, and they(devs) managed it to improve by 1000pts our had 2600 and got improved by 300 only.
I try to be optimistic, as I respect all the work done by developers. Every software IMO is good for everyday usage, but well, by modding I though it could be bit better
I am just dropping my two cents here, but I think that the devs go by the thought that benchmarks are - as Microsoft put it - not relevant to real day-to-day use scenarios. A phone with awesome benchmarks (or a ROM such as ARHD) may act quite sluggishly and crappily in day-to-day usage without a ton of tweaks and stuff (like ARHD does).
So, you see... the mechanic tells you that you can get 300km/h in your new Toyota, but at 160km/h the wind is screeching in the inside of the car so loud that you would *not* want it to go to 300/h.
I hope you understand my analogy. The point is - take benchmark results with a grain of salt.
I know what you mean, also saw people talking about desire z being smoother than sgs in stock config, but also there's something that sgs devs did if scores went over 25% higher
As far as I know:
benchmark =! reality
And the desire Z is worse than sgs, the gpu is worse, don't know about cpu, the ram may be different not only from how much it is (even if I've seen they're both ddr1)
Apart from this I'm not saying that we'd better have not more than 10 roms and more devs trying to add something very new to the phone. We've many ICS roms, many cyano roms, many sense 3.5 roms, many ics sense roms, many miui roms. I'd rather have two of each group and ie usb host or something a bit trickier... I mean, with all the respect possible for developers of every kind, hacking is becoming not hacking anymore, I mean everyone can with a bit of knowledge make his own rom (I remember of people under fifteen...). But hacking, imo, is when siul, OdienManSam, taz were trying to port ICS, all the work that many here are doing making things work in ics (Flinny, blk_jack), what on One X forums people are trying to do to gain S-OFF, when OdienManSam was trying to port usb host (will never know if he succeded)... I think there's much more juice to squeeze from our phones, less people willing to do it...
I'm not deplorating devs works, just my opinion...
If it means anything:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'd say that it's pretty close to what the SGS performed in the benchmark (considering I was actually playing music whilst testing). Regardless, benchmarks are indeed far from everyday use scenarios.
Andromadus @ 1.2GHz. As the dude above me states, our device really doesn't score that much lower all things considered.
Sent from my HTC Vision using xda premium
Mine is at 3400, too with Andromadus ICS ROM @1,2GHz. And tested up to 1,6GHz running stable. So I have some reserves if I like, but it´s smooth enough at 1,2GHz, so why bother?
Mike
Related
Hey guys,
I've been doing these benchmarks alot on WinMo before I got my first Android device. I always felt Winmo was sluggish, but look at this:
GLBenchmark link
I compared the Nexus with a Milestone, HD2 and 3GS. And it shocked me... The HD2 is faster at most benchmarks!
Is that because of the SDK with OpenGL ES 2.0 isn't used yet?
Hoping this could be improved, because I left Winmo because of this.
I don't believe this benchmark.
Okay, you're comparing several different platforms here. The HD2 and the Nexus One have the exact same GPU.
More accurate: this particular benchmark is faster on its Windows Mobile port than on its Android port.
scoring 100% in a benchmark can not be right?
frleus said:
scoring 100% in a benchmark can not be right?
Click to expand...
Click to collapse
Generally speaking in these types of benchmarks, the benchmark is set by the highest-scoring device. 100% would be the king for that specific test.
You would be correct, Android 2.1 as it is on our phones doesn't have all of the graphics boosters. To bo honest, it isn't that surprising IMHO, since these benchmarks are hugely influenced by the software itself, otherwise ROM cooking wouldn't do anything for increasing these #'s.
Maybe you could re-run this with a Cyan ROM, which has lots of those little things added in, such as the Arm Neon graphics inhancing(or whatever the heck its exact name is).
Also, keep in mind, that there are more important factors than "benchmarks".
pjcforpres said:
You would be correct, Android 2.1 as it is on our phones doesn't have all of the graphics boosters. To bo honest, it isn't that surprising IMHO, since these benchmarks are hugely influenced by the software itself, otherwise ROM cooking wouldn't do anything for increasing these #'s.
Maybe you could re-run this with a Cyan ROM, which has lots of those little things added in, such as the Arm Neon graphics inhancing(or whatever the heck its exact name is).
Click to expand...
Click to collapse
I agree, with this, but adding one more thing instead of just testing different phones, test these benchmarks on cyan and emnother. With the nexus our graphics performance is aided by software so hardware isnt going to be the kicker between the hd2 and the nexus.
CM 5.0.6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Web based benchmarks are as fail as the DPI on the HD2.
TheDudeOfLife said:
Web based benchmarks are as fail as the DPI on the HD2.
Click to expand...
Click to collapse
In your experience which would be a good benchmark besides Linpack?
jlevy73 said:
In your experience which would be a good benchmark besides Linpack?
Click to expand...
Click to collapse
Water submersion test.
TheDudeOfLife said:
Water submersion test.
Click to expand...
Click to collapse
+ Drop Height.
uberingram said:
+ Drop Height.
Click to expand...
Click to collapse
Submersion test + drop height = the angle of the dangle
I agree that static benchmarks aren't anything, but the Nexus should be at least able to score comparable to the HD2, right? Hardware is the same, it's just the software that differs... alot.
NeoS2007 said:
I agree that static benchmarks aren't anything, but the Nexus should be at least able to score comparable to the HD2, right? Hardware is the same, it's just the software that differs... alot.
Click to expand...
Click to collapse
ah the quest for improving graphics on msm7k errr i mean snapdragon processors begin. Nice to see you've jumped to Android neoS2007
i think theres heaps of room for n1 to improve and count me if you decide on creating a group for improving graphics on the n1
babijoee said:
ah the quest for improving graphics on msm7k errr i mean snapdragon processors begin. Nice to see you've jumped to Android neoS2007
i think theres heaps of room for n1 to improve and count me if you decide on creating a group for improving graphics on the n1
Click to expand...
Click to collapse
Good to see you here too babijoee. I'm trying to get someone on the MSM bandwagon to coordinate it, but Snapdragon is just so much more interesting... Anyways, goodtimes.
Anyways, I'm not setting up a group until i'm fairly certain the N1 CAN get better. I want to compare the N1 with the Desire and then again when OGLES 2.0 is fully implemented.
Nothing official but defiantly interesting:
http://www.androidspin.com/2010/04/21/google-getting-ready-to-dish-out-some-froyo/
I'm sure if everything mentioned here would defiantly give the n1 a substantial performance increase
Definitely worth waiting for. I'll see if I can track improvements in the graphics area of the N1 once Froyo is out.
NeoS2007 said:
Good to see you here too babijoee. I'm trying to get someone on the MSM bandwagon to coordinate it, but Snapdragon is just so much more interesting... Anyways, goodtimes.
Anyways, I'm not setting up a group until i'm fairly certain the N1 CAN get better. I want to compare the N1 with the Desire and then again when OGLES 2.0 is fully implemented.
Click to expand...
Click to collapse
I just ran it on my Desire. The upload failed so i dont have exact figures to prove anything, but it looks much the same as the N1 listed on their site. Most things are within 5%. My HD2 running a dutty custom ROM and Chainfires driver hack is a bit faster.
Raging Thunder 2 run extremly fast on N1, faster than moto chaser on ipod touch 2g. Anyway mobile benchmarks are always bulls**t
This might not be the right fourm but could someone please tell me why HTC phones are twice as fast than the Epic on linpack? I've tried a EVO and a Droid Incredible, both get a score of 32.500! Why?
Because JIT is optimized for Snapdragon processors, you see more performance boosts with those phones. However, mere benchmarks do not translate to real world performance whatsoever. My Epic is faster than any phone that's out there. Never go by benchmarks, lot of them are as useless as the Windows Experience Index crap. Our phones have the better hardware, when official Froyo is out and devs get the source, you'll see how powerful it really is.
Because linpack performance does not equal real life performance.... I also recall reading that linpack has not been optimized for the epic's processor. However, try 30 seconds using an evo and compare it to the epic and you'll have your actual answer
Sent from my SPH-D700 using XDA App
I think they are a 128 bit system versus 64 bit. But all I hear from evo user is the epic is faster
Sent from my SPH-D700 using Tapatalk
nimaim said:
Because JMy Epic is faster than any phone that's out there.
Click to expand...
Click to collapse
Just like cars, there's always someone faster...I think it is pure ignorance to state you alone have the fastest phone in the whole world. *shrug* For me my user experience is awesome and i know firsthand that benchmarks don't tell the whole story and can be faked. With tmpfs and a little knowhow anyone can 3000+ on quadrant.
Sent on the go from my mobile device
I didn't mean to come across as arrogant. I didn't mean I alone have the fastest phone in the world at all. I meant with everything that's out in terms of OC'd kernels, Epic owners in general have faster phones than practically any other out there (currently). Benchmarks are not high, but that does not translate to real world performance which is what I was getting at.
Essentially what has been said before: Linpack has been compiled and optimized for the other processor. Someone has to write code for each specific processor in order for it to take advantage of each one's architecture. Back when Intel's Nahalem chips came out, similar results were observed (I used to build HPC clusters).
Try nenamark1. The epic smokes the evo in that test
Sent from my SPH-D700 using Tapatalk
Simple, linpack is a test checking for raw CPU power via floating points..Snapdragon has a thing called a VFP which is a Floating Point Accelerator...
Aka instead of checking raw CPU power of the CPU..your checking how fast the the VFP processes floating points lol..
To give an example, its like one person actually taking a test, while the other is copying off an answer sheet..who will be the fastest?
If you go by benchmarks that have not had their code optimized for the Snapdragon, where it is more apples to apples (it will never be completely apples to apples), the Hummingbirds generally come out on top.
Plus, if you look at gaming, the FPS on the Hummingbird is much faster. Of course, CPU and graphics benchmarks are quite different.
It has a keyboard
Thread moved to General.
I'm pretty new to android phones but I did my homework before i decided on my epic. My wife wanted the Evo for the larger MP camera and bigger screen so we ended up with one of each. Form the time i've spent on my wife's evo and the time she has spent with my Epic we both have to agree that the Epic preforms far better in realworld test. The scrolling is smother and it has a better overall experience than the evo. So forget about benchmarks... just try one head to head and you'll see which one is the better device..
I've said this before and will say it again. My rooted evo with cm6 and oced to 1.12 ghz isn't as smooth as my epic was out the box. My evo gets 1500 on quadrent while my epic gets 1100 with no jit. Now you tell me wich phone is faster?
Sent from my SPH-D700 using XDA App
gTen said:
To give an example, its like one person actually taking a test, while the other is copying off an answer sheet..who will be the fastest?
Click to expand...
Click to collapse
The person taking the test will be faster since the copier has to wait for the answers.
Facepalm...
Sent from my SPH-D700 using XDA App
crabjoe said:
The person taking the test will be faster since the copier has to wait for the answers.
Click to expand...
Click to collapse
...your assuming he is copying from the other persons answer sheet and not the teacher's answer sheet...must we really get into this? >.> lol
Either way thats the reason...
crabjoe said:
The person taking the test will be faster since the copier has to wait for the answers.
Click to expand...
Click to collapse
Winner by TKO.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Squirel aids!
Looks like google got JIT situated on hummingbird CPU
sorry crappy screen haven't unlocked boot loader yet
Now off to unlock to help out with system dump
So dev can try to port
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus S using XDA App
This is awesome news as long as we can get GB ported
What does the blue portion of the bar represent?
blanked said:
What does the blue portion of the bar represent?
Click to expand...
Click to collapse
The CPU. That's what was lagging with the current froyo builds. The JIT compiler was optimized for QCOM chips, but not the Hummingbird processor. Looks like that's been sorted out.
Is that available only in the pro version (I don't get the colors just one solid bar)? What is green and how come Droix X kicks so much butt with it? Memory?
g1ddy said:
Is that available only in the pro version? What is green and how come Droix X kicks so much butt with it? Memory?
Click to expand...
Click to collapse
Blue CPU/Red Memory/Green I/O/Grayish Yellow 2D/Yellow 3D
SO WANT those speeds...
Considering we're running the same processor...can't wait!
Awesome. Dump!Dump!
Don't blame me, blame my keyboard's autocorrection algorithm.
This was linked to the Vibrant section, and noticed the lower (smaller block) on 3D performance? Can anyone confirm?
edit: damn thought this was the Nexus S section, lol.
RobBull69 said:
The CPU. That's what was lagging with the current froyo builds. The JIT compiler was optimized for QCOM chips, but not the Hummingbird processor. Looks like that's been sorted out.
Click to expand...
Click to collapse
the test breakdown is available in Quadrant Advanced. you can get it in the SlideME market.
and the green represent I/O which doesnt really contribute to a lot of performance... you will notice that people running OCLF will have quadrants score of 2k+ mainly due to i/o exploit
what's the linpack on it?
THIS IS EXACTLY what I have been waiting for! I have been one of the most vocal people about the Dalvik Jit Compiler not offering the Hummingbird the same performance gain that scorpions received, and it seems like Google definitely sorted this out. Totally just put new life into the Hummingbird. Google choosing the Samsung Galaxy S as being their new Nexus phone was the best thing that happened to Vibrant owners.
Thats just a little higher than my Vibrant with Voodoo Lagfix. Which means thats its either 'meh', or if its getting the result without being I/O lagfixed, then... 'WOW!'
Mannymal said:
Thats just a little higher than my Vibrant with Voodoo Lagfix. Which means thats its either 'meh', or if its getting the result without being I/O lagfixed, then... 'WOW!'
Click to expand...
Click to collapse
The Nexus S doesn't use RFS, so there's no need for a lagfix in the same sense as the Galaxy S phones. However, Google did neglect to set one of the EXT4 mount options, so there is a Voodoo kernel now that shows significant improvement. They're getting around 2400 with the new kernel. http://forum.xda-developers.com/showthread.php?t=876132
you can get the same thing on a SGS with the CM6.1beta
I played with one for a short time at Best Buy tonight. It is ridiculously fast. It loaded Angry Birds loaded and ready to play in the same time it took my phone (running Eugene's Ginger Clone 2.2 with the super I/O kernel) to bring up the loading screen. I understand the browser still has some of the same lag problems, but I didn't get to play with it long enough to see for myself.
If devs can port the 2.3 kernel to the Vibrant, then I'll stick with it because it will indeed gain what this phone can do, but If now then I think I'll get the Nexus S. The fact that Google took Samsung's hardware and made it sing like this and Samsung can't even manage a workable 2.2 yet has me seriously contemplating jumping ship. I don't think I'll sell the Vibrant though, the community and developers have been great and I want to see exactly how far they can push the phone, but it'd be nice to daily drive something you know is fully supported.
Mannymal said:
Thats just a little higher than my Vibrant with Voodoo Lagfix. Which means thats its either 'meh', or if its getting the result without being I/O lagfixed, then... 'WOW!'
Click to expand...
Click to collapse
hey mannymal, I think you fail to see the point and significance of this. The total end score isn't what we are excited about, at least not me. The cpu score is what we are excited about, and you can only see the score breakdown in Quadrant Advanced or Quadrant Professional.
The dalvik jit compiler in froyo 2.2 was not giving the hummingbird the same CPU performance gain that was being achieved by the scorpion chips. Meaning that a crummy old first generation scorpion was outperforming the hummingbird in cpu tasks.
The significance of this thread and the quadrant photo, shows that Google appears to have hopefully sorted things out, and that the Hummingbird is now receiving a CPU performance gain that was being partially neglected in 2.2
I hope you realize the end score wasn't the focus, and that no matter how many lagfixes you apply, your cpu performance doesn't necessarily go up.
Is that all? Very low score! I was expecting better than this for a Nexus S ..
scrizz said:
you can get the same thing on a SGS with the CM6.1beta
Click to expand...
Click to collapse
But sure, I get the same score with my SGS Quadrant XXJPY and LagFix!
I was looking into buying either the TF / Prime this past week, and have been looking into the benchmarks I see on the net. I've seen a few reviews, one from AnandTech, and the other one from Slashgear and random Antutu benches across the web.
If I'm understanding correctly, it seems the Prime obviously does have an edge, however for general non-gaming use it seems the differences are minimal? Can anyone confirm or if you own both to test it out?
In a javascript benchmark (AnandTech.com), I'd only see a 0.4-0.5 second difference loading JS heavy webpages?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The BrowserMark comparison at slashgear shows a 0.5-0.6 second gain by the Prime:
So are the benches really showing the difference is this minimal or are there more to talk about that I'm not seeing? (Not referring to game benches, not too interested in gaming)
From what I understand the main difference is in the GPU so for games and such it will matter... Also more hardware support for video making 1080p a feature now.
The cpu itself is clocked higher so I wonder what the differences would be with an equally clocked TF101. I guess barely noticable...
Off course there's the quadcore vs dualcore but I wonder if that really matters in day to day use. I don't expect a huge difference in user experience so in that regards I don't think there's a big reason to upgrade from TF101 to TF201.
I still will though, because the size decrease (and weight decrease) combined with the other factors still make it a nice upgrade. But looking at just performance, meh...
i overclock my Tf101 to 1.5ghz and its very fast now. i would argue an overclocked Tf101 would perform the same if not better than a prime in most of these tests.
But then again, the prime might have just as much overclocking room... Giving it the lead again.
The problem is that benchmarks generally mean absolutely nothing. Having a good benchmark doesn't mean you are going to get great real world use.
pside15 said:
The problem is that benchmarks generally mean absolutely nothing. Having a good benchmark doesn't mean you are going to get great real world use.
Click to expand...
Click to collapse
That's the thing, having a machine that benchmarks 26% faster (TF201 vs TF 101) does not mean that it is going to necessarily be faster in real life depending on the software and how it uses it.
Benchmarks should prove the Prime to be a better machine, singularly. Dual/quad-core, it’s all about apps utilization and user functionality.
Then there’s price/performance, (in my case) a $250 101 beats the 201.
That's the part of what I've been trying to say. If I'm only going to see a split second of differences (0.5 second) in browsing around heavy javascript or just general web browsing performance, is there more than this?
Seems like so far the only argument I can see about getting a Prime is a GPU and CPU boost to gaming fps by 20-30 fps.
What about outside of gaming, in respect to general tasks that can take some time, like compressing a zip of a nand backup or large rom files, general encryption, etc.
The price per performance of the TF101 definitely seems to be taking the lead if we aren't talking about gaming apps.
dagrim1 said:
But then again, the prime might have just as much overclocking room... Giving it the lead again.
Click to expand...
Click to collapse
My impression is that quad core performance vs dual core does not follow a linear scale.. If the way the architecture of 4x ARM CPU's (TF201) vs 2x (TF101) is any similar to how Intel Quad vs Duo started getting popularity a few years ago, I feel that there are going to be relatively few noticeable differences, when the dual can suit an average user without noticeably seeing any changes using a quad for their tasks... Mainly it will have to wait until which apps can utilize the multiple cores efficiently. Crysis for android?
Course I might be off base with this, that's why I wanted to ask you guys who have owned it.
Unless you are using high end games specifically designed for the Quad core/GPU, you should not notice a real difference. Much of what you do with any tablet or computer is speed dependent on outside sources ie network speed, ( both on your end and the other end) input speed etc. If you are using or rendering high end graphics, you will notice the difference, but then why use a tablet for that in the first place.
The first benchmark for Prime is done is slowest, power saving mode.
Asus TF201 Prime is the best
GasGuzz said:
Benchmarks should prove the Prime to be a better machine, singularly. Dual/quad-core, it’s all about apps utilization and user functionality.
Then there’s price/performance, (in my case) a $250 101 beats the 201.
Click to expand...
Click to collapse
The 201 actually has a 5th core that is for normal usage, so most of the time you will be running a single core. I have seen in benchmarks that the internal flash on the 201 is slower than the 101. The 201 also has only a mono speaker compared to the stereo 101. The 101 right now has overclocking and custom ROMs. Add in price and that is the reason I just bought a 101 instead of a 201.
Cheers!
-M
Xda member since 2007
I have a problem,my nexus 7 (as the title suggests) will not pass 59 fps. I've tried various roms,kernels and tweaks.
I'm not New to android and my sensation gets 70+ fps benchmarking, anyone know of any reason for my woes?
Getting really annoying to be honest. My sensation is ranked #1 in its device section of antutu and I want to push the nexus just as far
bonesy said:
I have a problem,my nexus 7 (as the title suggests) will not pass 59 fps. I've tried various roms,kernels and tweaks.
I'm not New to android and my sensation gets 70+ fps benchmarking, anyone know of any reason for my woes?
Getting really annoying to be honest. My sensation is ranked #1 in its device section of antutu and I want to push the nexus just as far
Click to expand...
Click to collapse
thats how it is, 59fps is the limit. kernel developers can raise the panel frequency, which can raise the fps to 109. but its not real, so they stopped doing that. what was your highest antutu, i bet i beat it with my n7. anyways, your 59fps on your n7 is is better than what you get on your sensation, you failed to take in account screen size, more pixels to push.
Thanks for the reply, i get 8229 with my sensation clocked at 1836mhz and with my N7 clocked at 1800mhz i get 9815 on antutu. Seems a bit naff to be quite frank, my dual core phone can nearly bench the same as the Tegra quad. I found some kernels with the fps limit disabled and i still only get 59 fps
bonesy said:
Thanks for the reply, i get 8229 with my sensation clocked at 1836mhz and with my N7 clocked at 1800mhz i get 9815 on antutu. Seems a bit naff to be quite frank, my dual core phone can nearly bench the same as the Tegra quad. I found some kernels with the fps limit disabled and i still only get 59 fps
Click to expand...
Click to collapse
i get 12000-16000 on antutu depending which kernel im using(and cpu speed), at 59fps. but its the screen size really that is the difference. and antutu isnt a good benchmark for graphic performance. its outdated and the test itself limits the scores.
here, nearly twice your sensation.. id say youre using the wrong rom/kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thats more like what i expect the score to be like! Just to check without starting a thread.... Is the latest bootloader 3.34?
To be fair i am severely disappointed with this device, never had any problems with any if the HTC devices and within 3 days of owning this the micro usb cable has fallen apart, the screen has lifted in one corner and is displaying stress marks on the LCD trying to contact google or asus is becoming a stressful task.
What ROM is eveyone using? I'm guessing cyanogenmod??
I just run stock. It doesn't matter what rom/kernel I wind up running, it never seems to be as stable in the long term as the stock setup. Since I have bought my N7 I have flashed a ton of roms to it, when heading back to stock for a while out of boredom I found that I have an up time of well over a month now. I never got that lucky with custom roms after a week or two I always had to reboot it because of random issues including lagging and slow performance, to apps misbehaving.