AnTuTu results, especially 2D graphics, are coming back with huge and consistent (multiple tests) variances between devices. 3D is off but not as widely. Since the phones being tested were all built within weeks of each other and running the same (stock) s/w, what could be causing such deviations in performance? 2D graphics scores swing from 147 to 286 which is almost a 50% variance. Hardware? Drivers? And could there be any correlation between this and the display flickering and other graphics issues?
And if we can limit the arm chair quarterbacking from those that aren't deep in to the code that would be great. There's enough layperson speculation in the general section.
{
"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 made similar experiences in different networks, especially with the stock rom. When i´m in wifi the results differ from them in bad network. If i have played a game before it shows other results, as when my One X didn´t use the graphic drivers...Try it. At this time - with ARHD Rom - i have most around 11500 and 11900 in AnTuTu, only one time 10600.
Benchmarks are more a game than really good guides... if your phone runs smooth, don´t worry about the results.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
BarryH_GEG said:
AnTuTu results, especially 2D graphics, are coming back with huge and consistent (multiple tests) variances between devices. 3D is off but not as widely. Since the phones being tested were all built within weeks of each other and running the same (stock) s/w, what could be causing such deviations in performance? 2D graphics scores swing from 147 to 286 which is almost a 50% variance. Hardware? Drivers? And could there be any correlation between this and the display flickering and other graphics issues?
And if we can limit the arm chair quarterbacking from those that aren't deep in to the code that would be great. There's enough layperson speculation in the general section.
Click to expand...
Click to collapse
Pretty sure this has to do with the crappy gfx drivers. The same thing that cause the camera to have issues and the notification bar. While I had the international one x, the phone benched really well while those problems weren't happening, but as soon as I was able to reproduce them and ran the tests again, score was reduced by a lot.
I could reboot the phone and the problems would go away, only to come back after some use.
designgears said:
Pretty sure this has to do with the crappy gfx drivers. The same thing that cause the camera to have issues and the notification bar. While I had the international one x, the phone benched really well while those problems weren't happening, but as soon as I was able to reproduce them and ran the tests again, score was reduced by a lot.
I could reboot the phone and the problems would go away, only to come back after some use.
Click to expand...
Click to collapse
Hey designgears, everyone with a low result gets a normal result just like you referenced after rebooting. So it seems the graphics crap is drivers. There's rumors of an end-of-month update to fix them and HTC's supposedly issuing a statement in the UK shortly. I hope they nail Nvidia, this is the second device to have Teg3 related issues at launch.
BarryH_GEG said:
Hey designgears, everyone with a low result gets a normal result just like you referenced after rebooting. So it seems the graphics crap is drivers. There's rumors of an end-of-month update to fix them and HTC's supposedly issuing a statement in the UK shortly. I hope they nail Nvidia, this is the second device to have Teg3 related issues at launch.
Click to expand...
Click to collapse
ya, last time I buy a Tegra product... lol
Related
Engadget
HTC Mondarian on the AT&T network
Perhaps a 1.3 ghz CPU?
Snapdragon QSD8650A processor
4.3" screen
I believe an aluminum casing?
If all that is true, then T-mobile can have their HD7. I'd be much happy with this.
More pictures!
Nothing breathtaking but maybe the best looking WP7 device by HTC so far.
Lets hope the rumors of a 1.3GHz Snapdragon processor and a 1400mAh battery is true.
{
"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"
}
http://pocketnow.com/windows-phone/htc-mondrian-renders-for-the-press-surface-1#comments
nizzon said:
Lets hope the rumors of a 1.3GHz Snapdragon processor and a 1400mAh battery is true.
Click to expand...
Click to collapse
It's funny how people build up unrealistic expectations and then get disappointed.
As Nietzsche once said, hope dies last, I would kill it first.
Thats unrealistic?
Looks like the Samsung Cetus has a 1500mAh battery.
But hey... lets hope it has the same specs as all the others, so we won't get disappointed.
Oh wait!... I have a better idea, lets don't care at all.
I wish I could quote some fancy philosopher here... or do I?
Samsung Cetus i8700 is prob the best looking so far and with really good specs. I just hope a 16GB flavour is offered for that model.
nizzon said:
But hey... lets hope it has the same specs as all the others, so we won't get disappointed.
Click to expand...
Click to collapse
What's the point in hoping when you know already that it'll have the same specs. Don't know about the battery though.
vangrieg said:
What's the point in hoping when you know already that it'll have the same specs. Don't know about the battery though.
Click to expand...
Click to collapse
hoping? there are multiple reports out claiming that it will be 1.3, no one is blindly speculating.some people see the cup half full, but I guess you see it as wheats the point of looking?
Whatever. Microsoft said all devices will use the same chip. You can fantasize about those "multiple reports" as much as you like. There have been multiple "leaks" reposting Photoshop renders made by xda members just for fun, with big blogs copypasting things without thinking. Most of these "reports" had the same source.
Of course many of the blogs out there are wrong and start chirping what the one before them said. But no one is blindly predicting or "hoping" something out of reach like a phone with a 3.0 ghz quad core with 1 gb graphics either. Regardless of what microsoft said it is very possible that there will be a phone with more than 1 ghz, possibly even a 1.3 ghz, within the next year.
Next year, sure. Just not at launch. If this Mondrian is launched this "holiday season" it's getting the same chip as others. Easy as that.
If only it had a qwerty keyboard =(
..........
Bezzletine said:
If only it had a qwerty keyboard =(
Click to expand...
Click to collapse
Relax, there will be phones with qwertys.
Hey Guys, I have One X almost month and I was the one who was glad to have device without any issues. Everything was great but now my screen starts to flicker. So I want to ask WTF is it possible to start to have issues when it was OK and not faulty device?
I know it's tedious to have to plod through long threads but this has been asked and answered about a dozen times. The flickering is random. So devices that weren't flickering can start days or weeks later. HTC said on May 2 they identified the issue so I'd imagine we're getting closer to an update that'll correct it.
So it is software issue?
I really believe its in every HOX device.
enyaj said:
I really believe its in every HOX device.
Click to expand...
Click to collapse
after reading dozens of topics I agree, that + htc statement that it is a software problem and it will be fixed via OTA kept me from replacing it with a new one because there is a very big chance it will flicker as well
enyaj said:
I really believe its in every HOX device.
Click to expand...
Click to collapse
It's not. Mine's never flickered. The Asus Prime which is also Teg3 had the same problems at launch. It's illogical that devices using identical h/w and s/w that were built at the same time should perform differently but they do. Some Prime's had graphics issues and some didn't; just like the One X. The general consensus is that it has to do with variations in the Teg3 chip with some of them being at the low or high end of tolerances. When the s/w receives a response outside the range it's expecting it borks. It also explains why this might not have come up in testing if all of the early chips supplied to HTC by Nvidia were carefully screened and had very tight tolerances. Not defending HTC, but this is an Nvidia issue. The XL has none of these issues and uses a different CPU/GPU. Since Nvidia’s code and drivers are proprietary they’re also the ones that have to come up with the fix. Asus rushed out updates but they actually made things worse. Hopefully the delay is HTC being more methodical and trying to get it right the first time.
the flickering is not as random as you guys think, its happening at high temperature for devices that are flicker free out of box (45 degree and over)
clearly has to do with the health of the chip you are getting (chips differ in thermal room ahead based on yields) and clearly has to do with the backlight power management thing in Tegra3 (PRISM)
BarryH_GEG said:
It's not. Mine's never flickered. The Asus Prime which is also Teg3 had the same problems at launch. It's illogical that devices using identical h/w and s/w that were built at the same time should perform differently but they do. Some Prime's had graphics issues and some didn't; just like the One X. The general consensus is that it has to do with variations in the Teg3 chip with some of them being at the low or high end of tolerances. When the s/w receives a response outside the range it's expecting it borks. It also explains why this might not have come up in testing if all of the early chips supplied to HTC by Nvidia were carefully screened and had very tight tolerances. Not defending HTC, but this is an Nvidia issue. The XL has none of these issues and uses a different CPU/GPU. Since Nvidia’s code and drivers are proprietary they’re also the ones that have to come up with the fix. Asus rushed out updates but they actually made things worse. Hopefully the delay is HTC being more methodical and trying to get it right the first time.
Click to expand...
Click to collapse
First read my topic again. Your device never flickered have absolutely no value because it doesn't mean that it wont flicker tomorrow or week later..
Another one of these threads? Sigh. :banghead:
Sent from my HTC One X using xda premium
Castellano2 said:
First read my topic again. Your device never flickered have absolutely no value because it doesn't mean that it wont flicker tomorrow or week later..
Click to expand...
Click to collapse
Read my response. By telling you it could happen at any time doesn't mean I'm in any way excluded. Because it's random anyone could be affected at any time.
http://forum.xda-developers.com/showthread.php?t=1597448
{
"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 noticed alot of people on the forums posting benchmarks after installing different ROM. I decided to download Quadrant just to see what I was pulling. I scored low in comparison to what I've seen, so I just completely wiped my phone back to stock (data wiped and then ODIN) and tried it, and pulled a 4678. Flashed CleanROM SE 1.2, and it went up to 4706. I've seen some people between 5k and 7k. A few videos I watched, people claiming to be completely stock were getting 5600+. Any clue what's wrong here? Is there anyone else out there that is stock that can benchmark and tell me what they get?
Thanks in Advance,
emoti0n
Read through the benchmark threads and you'll come to understand a few things:
- benchmarks are useless as an ongoing measurement. They merely show capability potential.
- your benchmarks will vary not only based on the rom and kernel, but what other apps you have running as services, what specific device configuration you have set at the time of running.
Does your phone perform amazingly doing what you want it to do? That's the only relevant and important measurement.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
spycedtx said:
Read through the benchmark threads and you'll come to understand a few things:
- benchmarks are useless as an ongoing measurement. They merely show capability potential.
- your benchmarks will vary not only based on the rom and kernel, but what other apps you have running as services, what specific device configuration you have set at the time of running.
Does your phone perform amazingly doing what you want it to do? That's the only relevant and important measurement.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Click to expand...
Click to collapse
Right. I understand what you're saying and that software environment can change the results, but two out-of-box state phones should score somewhat close to each other, yes or no? In comparison to what I've seen, my CPU is where I'm lacking. I also understand that I can OC and hit higher scores, but just comparing it to other phones that claim to out-of-box / stock - I'm scoring low in comparison.
Spy is probably right. But benchmarks should be somewhat similar
This is running DAGr8's AOKP Bullet build.
{
"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 GT-N7105 using Tapatalk 2
emoti0n said:
I noticed alot of people on the forums posting benchmarks after installing different ROM. I decided to download Quadrant just to see what I was pulling. I scored low in comparison to what I've seen, so I just completely wiped my phone back to stock (data wiped and then ODIN) and tried it, and pulled a 4678. Flashed CleanROM SE 1.2, and it went up to 4706. I've seen some people between 5k and 7k. A few videos I watched, people claiming to be completely stock were getting 5600+. Any clue what's wrong here? Is there anyone else out there that is stock that can benchmark and tell me what they get?
Thanks in Advance,
emoti0n
Click to expand...
Click to collapse
I've been following the saber kernal for a while and seen that some guys are running the saber kernel on clean rom OC'd. Not sure if that what your looking for but that would put you right up there along the 7k mark.
I don't try to squeeze out numbers on the quadrant thing but I have ran a few times just to see. I score right about 6900. Note 2, CleanRom 4.0.5 with the kernal from that rom and no other tweaks that I know of that would increase the score. I am not over clocked or anything. Seems fine to me
Sorry to bother you guys with that silly question. Total user error. I had power-saving mode on, and it didn't even occur to me. I pretty much turn it on first thing anytime I reset my phone, and do it without thinking anymore. However, after resetting back to pure stock one more time, without power-saving mode, I actually hit 7168. Basically, I was trying to see the difference myself of stock performance verses a different ROM / kernel. I would also like to see the battery life difference for myself.
Anyhow, thanks to everyone for their responses.
I'd like to see benchmark performance results of phones stock out of the box and after debloating with root. There tons of posts about perceived performance but no real data.
If no one has done it by the time I get home around 8 eastern time, I'll do it. Performance seems a little better, but for me was the battery life improvement
Here you go, I saved everyone the time. I just visited a well known benchmark site and conducted three tests for you.
Stock - 31,137
All bloat removed - 30,389 (This was lower than I was expecting)
All bloat and Google apps removed - 37,991 (Not a bad score)
The site is easy to use, I just set the lower limit as 30,000 and the upper as 39,000. It produced three benchmark scores for me. I didn't even need to turn my phone on.
Remember, like all benchmarking, YMMV.
nobnut said:
Here you go, I saved everyone the time. I just visited a well known benchmark site and conducted three tests for you.
Stock - 31,137
All bloat removed - 30,389 (This was lower than I was expecting)
All bloat and Google apps removed - 37,991 (Not a bad score)
The site is easy to use, I just set the lower limit as 30,000 and the upper as 39,000. It produced three benchmark scores for me. I didn't even need to turn my phone on.
Remember, like all benchmarking, YMMV.
Click to expand...
Click to collapse
Too bad too many people will take this post seriously. [emoji23]
nobnut said:
Here you go, I saved everyone the time. I just visited a well known benchmark site and conducted three tests for you.
Stock - 31,137
All bloat removed - 30,389 (This was lower than I was expecting)
All bloat and Google apps removed - 37,991 (Not a bad score)
The site is easy to use, I just set the lower limit as 30,000 and the upper as 39,000. It produced three benchmark scores for me. I didn't even need to turn my phone on.
Remember, like all benchmarking, YMMV.
Click to expand...
Click to collapse
Surprising Results.
:angel:
I did it. Out of the box was 33000 and after root and flash sphinx rom got 30500 on antutu. Phone still smooth so i don't worry about it.
On Dalvik:
Antutu: 35000
Quadrant: 25000
On ART:
Antutu: 27000
Quadrant: 12700
Disappointed with the performance under ART!
Anyone knows why the discrepancy?
Using stock UK 10e on model D855 - 16Gb
Sent from my LG-D855 using Tapatalk
Widget21 said:
Disappointed with the performance under ART!
Anyone knows why the discrepancy?
Click to expand...
Click to collapse
Yes, your random number generator benchmark app is useless.
nobnut said:
Yes, your random number generator benchmark app is useless.
Click to expand...
Click to collapse
What a useless piece of post... Please go and play with traffic if you have nothing positive to contribute... Stay clear of my posts!! You've been warned!
Sent from my GT-I9300 using Tapatalk
Widget21 said:
Stay clear of my posts!! You've been warned!
Click to expand...
Click to collapse
*** Shivers! *+*
Widget21 said:
What a useless piece of post... Please go and play with traffic if you have nothing positive to contribute... Stay clear of my posts!! You've been warned!
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
{
"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"
}
My wife has a P7 Pro and I've got a P6 Pro. I decided to run a Geekbench test on them and was shocked to see the P6 Pro scored about 5% higher than the 7 Pro. Anyone have an idea what would cause that? Is there such thing as an underperforming CPU?
{
"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"
}
PuffDaddy_d said:
My wife has a P7 Pro and I've got a P6 Pro. I decided to run a Geekbench test on them and was shocked to see the P6 Pro scored about 5% higher than the 7 Pro. Anyone have an idea what would cause that? Is there such thing as an underperforming CPU?
View attachment 5936341
View attachment 5936343
Click to expand...
Click to collapse
Well there's a ton of variables that could affect those scores but yes, it's VERY possible to underclock a CPU, just as you can overclock it. I'm not saying that happened, but simply answering the question, as I have no idea the differences between them. OS can definitely affect this score just as much as CPU. So, what operating system (ROM) are both using, and kernels, ROOT magisk, ETC.? There's so many things that can cause this to happen that we will need a LOT more information to even begin to figure this out.
What I see here is your Pixel 6 performing better than average, I've seen scores from 2800 to 3200, but not higher, higher than that are rare, my highest score is 970/2843, can you tell which rom(beta, stable...), kernel, mods or modules and so are you using? Did you disable any app too?
Try using 3D Mark Wild Life Extreme or so to test 3D performance, or try antutu so you can have more info, thanks!
Thanks for the quick replies. I certainly understand that benchmark values can change from device to device or even day to day on the same device. I just never thought SoC's from 2 different generations would yield results showing the older device with higher performance.
Both phones are fully stock, not rooted or modified in any way with the latest Android 13 stable build. I only made this comparison because my wife's P7 Pro was having trouble taking more than 2 or 3 pictures in a row without temporarily locking out the camera shutter until the system resources cleared up. My P6 Pro in the same conditions had no trouble firing off 5 or 6 shots in a row without said issue.
PuffDaddy_d said:
Thanks for the quick replies. I certainly understand that benchmark values can change from device to device or even day to day on the same device. I just never thought SoC's from 2 different generations would yield results showing the older device with higher performance.
Both phones are fully stock, not rooted or modified in any way with the latest Android 13 stable build. I only made this comparison because my wife's P7 Pro was having trouble taking more than 2 or 3 pictures in a row without temporarily locking out the camera shutter until the system resources cleared up. My P6 Pro in the same conditions had no trouble firing off 5 or 6 shots in a row without said issue.
Click to expand...
Click to collapse
Your Pixel is a 1% one, her Pixel has an issue probably, factory resetting one day should fix it, I'll avoid restoring a backup of settings and so to make sure it works as it should.
Make sure to clean caches and checking background apps, try also better battery stats to check what's eating up resources, it is probably an easy fix, but finding it will need some work, thanks for sharing
Well, If you spend time to read previous news and you will know it's normally because both chips are made by the same technology from Samsung. And the chip used by your P6P may be luckily packaged from the best performance of specific position of the wafers(Center dies or near center dies ...) ... So it's within the reasonable variation.