Not sure if it's just me but Geekbench results for multi-core have dropped quite significantly after the final Nougat release.
With Marshmallow it scored around 4400, with Nougat it's around 3200 which is quite a big drop.
Anyone else getting the same?
i got 3039 for pixel c and my nexus 9 got 3340. both with interactive governor. i would guess if the govenor was some performance type it would register higher numbers.
dkryder said:
i got 3039 for pixel c and my nexus 9 got 3340. both with interactive governor. i would guess if the govenor was some performance type it would register higher numbers.
Click to expand...
Click to collapse
Most devices are set to interactive anyway, that wouldn't result in such a large drop in multi-core performance.
Good to know it's not just my PIxel C.
1408 single / 3138 multi here :/
I have stuttering when scrolling on Chrome, but i didnt have this problem on MM and Remix OS
gtaadicto92 said:
1408 single / 3138 multi here :/
I have stuttering when scrolling on Chrome, but i didnt have this problem on MM and Remix OS
Click to expand...
Click to collapse
Thanks for testing.
I'm assuming this isn't intentional from Google.
Same here
I'm on preview 5 and I have similar geekbench results. I am running a rooted pixel c and got similar results with the performance governor as well.
Shocky2 said:
Not sure if it's just me but Geekbench results for multi-core have dropped quite significantly after the final Nougat release.
With Marshmallow it scored around 4400, with Nougat it's around 3200 which is quite a big drop.
Anyone else getting the same?
Click to expand...
Click to collapse
Maybe GeekBench isn't tuned properly for Nougat.
brando56894 said:
Maybe GeekBench isn't tuned properly for Nougat.
Click to expand...
Click to collapse
Seeing the last update for it was in Feb 2016, I would say this ^ makes sense.
I just tried out photo mate r3, which has a benchmark function as well. That is a raw photo editing app. In Marshmallow the benchmark takes 33 seconds. In nougat it takes at least 45 seconds. Very similar to the drop in performance seen in Geekbench. Unless photo mate and Geekbench are doing the exact same things, this seems like a performance regression.
It got even worse with Geekbench 4. I am now clocking 1200 single core and 2400 multi-core on Nougat. The individual stats are pretty pathetic compared to other devices. I wonder what happened?
Shocky2 said:
Not sure if it's just me but Geekbench results for multi-core have dropped quite significantly after the final Nougat release.
With Marshmallow it scored around 4400, with Nougat it's around 3200 which is quite a big drop.
Anyone else getting the same?
Click to expand...
Click to collapse
Read the reviews. Other people are having the same issues with these benchmark apps showing lower scores that are inconsistent. I don't think the Pixel C is by itself in these crappy scores.
bluestang said:
Read the reviews. Other people are having the same issues with these benchmark apps showing lower scores that are inconsistent. I don't think the Pixel C is by itself in these crappy scores.
Click to expand...
Click to collapse
Yeah. But I still get a ten second difference between Marshmallow and nougat in photo mate. I now get the same result as I do on my LG G4 (with its significantly worse processor). Nothing has changed except nougat. That's at least two apps where nougat performance is significantly worse than Marshmallow on the pixel c.
tim.malone said:
Yeah. But I still get a ten second difference between Marshmallow and nougat in photo mate. I now get the same result as I do on my LG G4 (with its significantly worse processor). Nothing has changed except nougat. That's at least two apps where nougat performance is significantly worse than Marshmallow on the pixel c.
Click to expand...
Click to collapse
Load marshmallow.
Sent from my Pixel C using Tapatalk
Thanks for the constructive reply. Next time I experience a problem in Android I will be sure to ignore it.
I think he may be saying the benchmarks FUBARed and just enjoy Nougat???
hey, i run geekbench 4 with the cpu bench and i got a really good score.
but with the compute bench (graphics) i got a really worse result.
i got 1216 points, the nexus 9 with the older soc gets 3689 points.
I think the problem is the graphics driver. some news pages says, android nougat will use a new graphic interface with the latest opengl version.
maybe nvidia hat not yet released a new driver and the older one can´t be use with the full power.
I also noticed this. I found another renderscript (the API Google uses for running computations on the GPU) benchmark and it show similarly bad results on pixel c. I also found this issue https://code.google.com/p/android/issues/detail?id=204712
That indicates that the pixel c didn't ship with a Nvidia specific renderscript driver, which might be why the performance is bad. Just a guess, but I don't think it is even using the GPU. Which is a shame. The pixel c should fly in this test. I wonder if it's possible to load in the driver from the shield TV?
ravn83 said:
hey, i run geekbench 4 with the cpu bench and i got a really good score.
but with the compute bench (graphics) i got a really worse result.
i got 1216 points, the nexus 9 with the older soc gets 3689 points.
I think the problem is the graphics driver. some news pages says, android nougat will use a new graphic interface with the latest opengl version.
maybe nvidia hat not yet released a new driver and the older one can´t be use with the full power.
Click to expand...
Click to collapse
Related
I've recently upgraded to the ARHD 5.0.0 Rom and my Quadrant score has dropped from an average of 4800 down to an average of 3800.
I realise quadrant is not the most reliable benchmark for realworld performance but that seems like a pretty big drop.
Anyone else know what could have happened?
Thanks.
What has happened is that it's meaningless Quadrant score has dropped. I'd just ignore it altogether.
Solaris81 said:
I've recently upgraded to the ARHD 5.0.0 Rom and my Quadrant score has dropped from an average of 4800 down to an average of 3800.
I realise quadrant is not the most reliable benchmark for realworld performance but that seems like a pretty big drop.
Anyone else know what could have happened?
Thanks.
Click to expand...
Click to collapse
People are reporting lower AnTuTu scores after 1.29 so if the ROM you're using is 1.29 based what you're observing could be a result of the update. Since Nvidia's code and drivers are proprietary the devs use it pretty much as-is.
Read this...
http://forum.xda-developers.com/showpost.php?p=25601709&postcount=626
And this...
http://forum.xda-developers.com/showthread.php?t=1632354
As Nvidia plays around with low-level code and drivers to address battery life and fix the graphics issues they'll be tweaking the behaviour of the CPU. There were some pretty odd changes to the CPU code in the Prime while Nvidia was tackling its launch issues.
You have to do quadrant in stock rom.
On 1.26 and 1.28 stock rom it's easily around 4,600 to 4,800. Should be around the same for stock 1.29. I'll see it when I get the Asia ota.
I've tried most roms around and some of their versions are low and some after their update becomes on par with stock in terms of quadrant. It's due to the fact that they are doing heavy tweaking on the rom thus affecting performance a bit (whether for better or worse) . Good thing is they can easily rectify the problem on their next releases.
Although benchmark is not a clear indication of real world performance but it's always nice to get high scores nonetheless. Lol.
Sent from my HTC One X using xda premium
Why does the pixel xl benchmark so much lower then other devices even with the newer snapdragon 821. It's single core and muticore scores are quite a bit lower then say a device with the same ram and snapdragon 820.
I think google is playing it ultra-ultra safe on this phone and underclocking it.
If they start having serious issues like the Note7, on their very first Pixel phone, it would destroy the product line.
My theory anyways.
Sent from my KIW-L24 using Tapatalk
dermotti said:
I think google is playing it ultra-ultra safe on this phone and underclocking it.
If they start having serious issues like the Note7, on their very first Pixel phone, it would destroy the product line.
My theory anyways.
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing hopefully they will update the kernel later down the line. Or once we can root and flash a different kernel and reclock it hopefully will see an improvement.
Kombat wombat said:
I was thinking the same thing hopefully they will update the kernel later down the line. Or once we can root and flash a different kernel and reclock it hopefully will see an improvement.
Click to expand...
Click to collapse
You do know there's 2 kernels out already just need to flash with adb
jaythenut said:
You do know there's 2 kernels out already just need to flash with adb
Click to expand...
Click to collapse
I've seen one but I didn't know there were two. I was going to wait until a recovery and root were available for it before I start flashing kernels.
There's 2 different versions of the SD821. There's a performance version which is what you'll see in the new Xiaomi phones, Asus Zen Deluxe phones, and the Leco. They have 2 cores clocked at 2.4ghz and 2 cores clocked at 2.2ghz. There is then the efficiency version, which powers the Pixel phones. Their clusters are clocked exactly at the same speed as the SD820.
According to Qualcomm, on version gives you 5-10% more performance and the other gives you 5-10% efficiency. Google has chosen the efficiency version. However after seeing a few Pixel battery tests, it lasts one hour more than the Nexus 6P which is great, but it's still not in the league of phones like the Samsung S7, S7E, and the dearly departed Note 7. Those 3 phones had the regular SD820 and last much longer than the Pixels.
TransportedMan said:
There's 2 different versions of the SD821. There's a performance version which is what you'll see in the new Xiaomi phones, Asus Zen Deluxe phones, and the Leco. They have 2 cores clocked at 2.4ghz and 2 cores clocked at 2.2ghz. There is then the efficiency version, which powers the Pixel phones. Their clusters are clocked exactly at the same speed as the SD820.
According to Qualcomm, on version gives you 5-10% more performance and the other gives you 5-10% efficiency. Google has chosen the efficiency version. However after seeing a few Pixel battery tests, it lasts one hour more than the Nexus 6P which is great, but it's still not in the league of phones like the Samsung S7, S7E, and the dearly departed Note 7. Those 3 phones had the regular SD820 and last much longer than the Pixels.
Click to expand...
Click to collapse
Did you see my battery results? I got 5hr sot using Waze and streaming Alex Jones app the whole time. I did this test driving from Chicago to St Louis. Not only that my reception was garbage and I got those results.
Sent from my Pixel XL using Tapatalk
TransportedMan said:
There's 2 different versions of the SD821. There's a performance version which is what you'll see in the new Xiaomi phones, Asus Zen Deluxe phones, and the Leco. They have 2 cores clocked at 2.4ghz and 2 cores clocked at 2.2ghz. There is then the efficiency version, which powers the Pixel phones. Their clusters are clocked exactly at the same speed as the SD820.
According to Qualcomm, on version gives you 5-10% more performance and the other gives you 5-10% efficiency. Google has chosen the efficiency version. However after seeing a few Pixel battery tests, it lasts one hour more than the Nexus 6P which is great, but it's still not in the league of phones like the Samsung S7, S7E, and the dearly departed Note 7. Those 3 phones had the regular SD820 and last much longer than the Pixels.
Click to expand...
Click to collapse
I thought it was the same processor just clocked at different speeds out the box, I could be wrong though.
Kombat wombat said:
I thought it was the same processor just clocked at different speeds out the box, I could be wrong though.
Click to expand...
Click to collapse
Many people did and thought Google was just underclocking the chip but it was revealed there's two versions of the chip, Google has the efficiency version. In fact, XDA wrote an article about it about a week ago go check.
TransportedMan said:
Many people did and thought Google was just underclocking the chip but it was revealed there's two versions of the chip, Google has the efficiency version. In fact, XDA wrote an article about it about a week ago go check.
Click to expand...
Click to collapse
So basically we are stuck with a under clocked version that really sucks.
TransportedMan said:
Many people did and thought Google was just underclocking the chip but it was revealed there's two versions of the chip, Google has the efficiency version. In fact, XDA wrote an article about it about a week ago go check.
Click to expand...
Click to collapse
I can't seem to find the XDA article can you link it please.
Kombat wombat said:
I can't seem to find the XDA article can you link it please.
Click to expand...
Click to collapse
http://www.xda-developers.com/a-loo...he-snapdragon-821-in-the-google-pixel-phones/
TransportedMan said:
http://www.xda-developers.com/a-loo...he-snapdragon-821-in-the-google-pixel-phones/
Click to expand...
Click to collapse
Many thanks.
Kombat wombat said:
So basically we are stuck with a under clocked version that really sucks.
Click to expand...
Click to collapse
It is not underclocked. It is just more energy efficient at the same clock as the 820. If it bothers you, just wait a little bit and I promise you that you will be able to OC it with a custom kernel. Then you can enjoy faster battery drain with absolutely no perceivable difference in performance.
Irrelevant number. This is the smoothest Android phone I've ever owned. That number can't tell you what the experience is like. Other phones have a higher score but run like crap. The phone was created to be an all-round performer. Not blow up in your hand like the Samsung M80.
Sent from my Google Pixel XL using XDA Labs
X10D3 said:
Irrelevant number. This is the smoothest Android phone I've ever owned. That number can't tell you what the experience is like. Other phones have a higher score but run like crap. The phone was created to be an all-round performer. Not blow up in your hand like the Samsung M80.
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
You know what your right, I can't fault the smoothness of the pixel, and true to form it is laggless and buttery smooth. I think I got carried away for a bit with benchmark scores and Numbers.
oRAirwolf said:
Then you can enjoy faster battery drain with absolutely no perceivable difference in performance.
Click to expand...
Click to collapse
lol. +1 for this point. I think people get too caught up in drag racing their phones with benchmarks. If it runs smooth I don't care what clock speed it is or what benchmark number is outputs.
I know, I'm sorry, benchmarks, who needs them? The reason I'm testing is because I bought this phone used and I want to make sure that it's not broken in some way. I have a friend who is flipping HTC 10's and he's been doing benchmarks on each one that comes across his desk, and it seems like they're quite a bit different than mine.
On the stock rom my Antutu score has ranged from 108,000 to 152,000. Each time there's up to a 20,000 point difference. In my experience, your benchmark scores shouldn't change much unless you change something, so why the 45K range in scores? Not only that, but in Lineage 14.1 my scores drop significantly, down to 72,000, with the highest at 98,000.
I performed a RUU today and my scores are still flexing between 108 and 118K.
GeekBench 4 is a similar issue, my multicore performance has ranged from 1700 to 4100, and my single core from 1100 to 1700.
On a regular basis my Droid turbo (from 2014, running Lineage 14.1) is beating my HTC One in both tests. Do I have a bad phone, or is this normal behavior for the Sprint 10?
My buddy gets about 4000/1700 in geekbench and about 118K in Antutu, and his scores don't seem to change very much. He's running Lineage 14.1.
thunder2132 said:
I know, I'm sorry, benchmarks, who needs them? The reason I'm testing is because I bought this phone used and I want to make sure that it's not broken in some way. I have a friend who is flipping HTC 10's and he's been doing benchmarks on each one that comes across his desk, and it seems like they're quite a bit different than mine.
On the stock rom my Antutu score has ranged from 108,000 to 152,000. Each time there's up to a 20,000 point difference. In my experience, your benchmark scores shouldn't change much unless you change something, so why the 45K range in scores? Not only that, but in Lineage 14.1 my scores drop significantly, down to 72,000, with the highest at 98,000.
I performed a RUU today and my scores are still flexing between 108 and 118K.
GeekBench 4 is a similar issue, my multicore performance has ranged from 1700 to 4100, and my single core from 1100 to 1700.
On a regular basis my Droid turbo (from 2014, running Lineage 14.1) is beating my HTC One in both tests. Do I have a bad phone, or is this normal behavior for the Sprint 10?
My buddy gets about 4000/1700 in geekbench and about 118K in Antutu, and his scores don't seem to change very much. He's running Lineage 14.1.
Click to expand...
Click to collapse
Perhaps it's thermal throttling?
Nougat update improved things on that front. Are you on Marshmallow? Also you can try going into developer option and setting High Performance mode and then doing your test to see if you get improved scores.
Tarima said:
Perhaps it's thermal throttling?
Nougat update improved things on that front. Are you on Marshmallow? Also you can try going into developer option and setting High Performance mode and then doing your test to see if you get improved scores.
Click to expand...
Click to collapse
I think you're probably right on the thermal throttling side of things. I'm on Lineage 14.1 now, and if I run a benchmark after the phone has been idle for a while it's in the 138K range where it's supposed to be. Overclocked on stock is where I'm getting closer to 145K. I think I was doing too many tests, and when they were bad, I'd flash to another ROM (while charging) which didn't help with the thermal side of things.
Thermal throttling also would explain why if you do one test, then immediately repeat it the phone will score worse, which happens every time I try it.
I'm not on MM, I did a RUU to the latest version of N and then unlocked from there.
Hi,
I have found that Honor 7X heats a lot during gaming or other tasks using high CPU and GPU use. As a result, it throttles and performance decreases.
So, I decided to do a CPU throttling test using this app
https://play.google.com/store/apps/details?id=skynet.cputhrottlingtest
I have the attached the result below. As you can see it is throttling a lot.
Can you guys download the app, do the throttle test and upload the results here?
PS: I did the test for 10 min and 20 threads setting.
I'm no expert in this area, but don't ** all ** phones overheat and throttle? Depending on usage?
The question is, to what extent are they being throttled? Which ones are the worse? And, did the oem design / manufacture the device in such a way that it doesn't result in damage (cracked solder == boot loop) if used in such a way often enough.
Do we have results from testing other phones doing the same things? Then we could compare, otherwise, only time will tell if the design holds up as it should.
AsItLies said:
I'm no expert in this area, but don't ** all ** phones overheat and throttle? Depending on usage?
The question is, to what extent are they being throttled? Which ones are the worse? And, did the oem design / manufacture the device in such a way that it doesn't result in damage (cracked solder == boot loop) if used in such a way often enough.
Do we have results from testing other phones doing the same things? Then we could compare, otherwise, only time will tell if the design holds up as it should.
Click to expand...
Click to collapse
Yes, all phones do throttle eventually, but my phone throttled to 78% performance in only 10 min. Also, I found that my phone was heating too much while gaming (SoC temperature would go above 65°C) . I wanted to see if others' Honor 7X was heating and throttling this much or is it only my device?
This is what I get on my device, your device may be suffering from bad thermal dissipation (if that's even the term for it), or, more likely, you live in an area with high temps
CriGiu said:
This is what I get on my device, your device may be suffering from bad thermal dissipation (if that's even the term for it), or, more likely, you live in an area with high temps
Click to expand...
Click to collapse
Thank you for testing it. It looks like your device throttles less than mine. Also the temperatures are lower. I think only my device has a fault in thermal performance.
I should have my phone on Monday and I'll run a test early next week for ya if still interested.
Men. Kirin processor are not best for gaming compare to Snapdragon because of there GPU problem. They will not perform well specially in gaming. It's universal fact.
seanpr123 said:
I should have my phone on Monday and I'll run a test early next week for ya if still interested.
Click to expand...
Click to collapse
OK. Thank you.
TabTapper said:
Men. Kirin processor are not best for gaming compare to Snapdragon because of there GPU problem. They will not perform well specially in gaming. It's universal fact.
Click to expand...
Click to collapse
Yes. You're right. Even the Snapdragon 450 has much better than GPU than Kirin 659.
Alrighty, here are the results from my Mate SE and I also had a Moto G5+ (Snap 625) to run against as a comparison. Looks like the first one is the Moto.
Thoughts?
seanpr123 said:
Alrighty, here are the results from my Mate SE and I also had a Moto G5+ (Snap 625) to run against as a comparison. Looks like the first one is the Moto.
Thoughts?
Click to expand...
Click to collapse
I don't think the processors \ GPU are much different. I think if we do feel a difference it's because of the overlay of EMUI. It has been well documented how much better stock Android runs in comparison to an overlay. Even super powerful Samsung devices have lag and jank because of the skin.
seanpr123 said:
Alrighty, here are the results from my Mate SE and I also had a Moto G5+ (Snap 625) to run against as a comparison. Looks like the first one is the Moto.
Thoughts?
Click to expand...
Click to collapse
The Snapdragon 625 throttles slightly lesser when compared to Kirin 659. This is because SD 625 is made on a 14nm Fab Process while 659 is made on 16nm. Also the Adreno 506 GPU in 625 is much more efficient (Also more powerful).
smokinjoe2122 said:
I don't think the processors \ GPU are much different. I think if we do feel a difference it's because of the overlay of EMUI. It has been well documented how much better stock Android runs in comparison to an overlay. Even super powerful Samsung devices have lag and jank because of the skin.
Click to expand...
Click to collapse
I agree that the processors are similar but the GPUs are very different. Adreno 506 is much more powerful and efficient than Mali T830 MP2. Also, the UI shouldn't have much effect on the throttling tests.
Geekbench Score Decreased a lot after Android 12 update,is this expected?, is everyone seeing the same issue? and what could be the reason?
Single Core: 275 and Multi thread: 1105
Thanks!
Did they fix the camera 2 api so GCcam can work? Asking for a friend.
Vishnuisgod said:
Did they fix the camera 2 api so GCcam can work? Asking for a friend.
Click to expand...
Click to collapse
Hardware Support level shows limited. So I dont think it will work.
I noticed my phone is working slower and some system apps are not responding sometimes now after i upgraded to android 12
I Avoid system updates as they generally tend to fix issues and reduce performance.
Seems like this is something related to heating.
When I am in a cold room(with AC turned) score returns to normal.
Single Core: 742 and Multi Core:1892
Shubham0779 said:
Geekbench Score Decreased a lot after Android 12 update,is this expected?, is everyone seeing the same issue? and what could be the reason?
Single Core: 275 and Multi thread: 1105
Thanks!
Click to expand...
Click to collapse
This happens very occasionally where all scores drop for some reason. Its mostly single core that drops in my case. Otherwise it's mostly around 750 single core and 1850 multi core
Newer isn't always better