On my APQ8064 / Adreno 320 phone at 720p and "power saving" mode (only 1 core turned on?), I got a 42.9 FPS average (was generally always at ~58 except for some outdoor scenes in the 30s).
With all cores on, the average FPS is 57.3. (I saw a low of 45 for a split second I believe)
Apparently that makes this APQ8064 / Adreno 320 phone is marginally better than the Nexus 4 :)
Strange, I don't seem to have a benchmarking mode on my Droid 3. When it starts up I'm taken straight into the environment, and I don't see any options or settings available. Am I just noob'n out, or is anyone else having this problem?
Swipe down from the top little banner thing, tap the gear on the right to go into Settings to adjust quality / resolution. Then when you're back in the engine, swipe down again to hit the Benchmark button.
There is no top little banner thing when I'm running around in the environment. This is the difference I was talking about between what I'm seeing on my Droid 3 and the screen shots posted above. I'm wondering if it's a problem specific to the Droid 3 (wouldn't surprise me), or if it has to do with Android 2.3. Is anyone else still running 2.3?
it's good that it is running close to vsync. means that once you start adding AI , gameplay elements, bots, objects etc the performance will remain good.
imagine if it were running <30fps without any elements or objects inside the gameworld, that would be a bad sign.
Even my now archaic Nexus S never dipped below 30FPS in this, and I think the average was just below 40. Most games look far worse than this, yet run worse as well. Granted this has no AI or characters on screen which would rob some performance, but it still looks like more geometry and shading work than the vast majority of mobile games.
Desire HD - 800x480 High Performance: 25.6fps Desire HD - 800x480 High Quality: 23.8fps Desire HD - 600x360 High Peformance: 16.5fps Desire HD - 600x360 High Quality: 15.6fps Desire HD - 400x240 High Performance: 18.1fps Desire HD - 400x240 High Quality: 17fps
Yes, reducing resolution dramatically reduced framerate on my device.
Hardware variants - something to do with the cell chip type and other wifi junk - but yeah the point is, it's irritating.
Got 45.3 on the Note 2 here, not 45.8 as the chart shows - US version, original android no hacks, has the quad and the mali 400, jellybean 4.1.1, cleared the ram first as well that helped a bit, also it came with split screen apps working.
960x540 (75% rez) high quality = 45.6
100% rez(1280x720), high performance = 47.4
lol - Kind of surprised I guess the mali400 is a bit weak / it does better in the bench suites Quadrant and Antutu vs the others in the charts.
Brain Klug mentioned it somewhere might be in this article about the chip doing LTE - so the dual core snapdragon version had to mesh with the no LTE radio chip as I understood it. Others elsewhere have stated there were shortages of quadcores due to demand so Samsung used alternate cores for regions and also for similar phones (changing nearly just the ARMs core and making a new phone model). So I guess there are several reasons.
I noticed on the Google Play store that it shows 134MB download for my Galaxy S3 and Transformer TF101, but only a 94MB download for my Galaxy Tab 2 7".
Is it the same benchmark being run on each device, or is it different versions of the "game"?
As long as it still runs on a HTC Desire / Nexus One, it's not worth any further investigation. Sure, it only runs at 11 FPS average according to the benchmark, but that's way too good for my 'ancient' smartphone. And rendering such static scenes is always less demanding than a moving character, or even several characters (battle) with lots of additional details and effects. So I don't really see a use in this except advertising for Epic, which, however, isn't an indicator for the quality of real games, because of the missing effects/characters/moving objects.
This just shows how old the Epic Citadel demo is. Most devices already reach 60 FPS at native resolution on max quality with it. I don't know why they even bother porting it at this point. They should've just worked on a new one based on Unreal 4, and then launch for both iOS and Android in the same time. This was pointless.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
Facebook
Twitter
RSS
52 Comments
Back to Article
Brian Klug - Wednesday, January 30, 2013 - link
I forgot to include Galaxy Nexus, that'll be up shortly.-Brian
Blindsay04 - Wednesday, January 30, 2013 - link
Should be pretty close to mine, I got an average of 40.5 FPSmmp121 - Thursday, January 31, 2013 - link
Got a 40.8 on my GNexmark29 - Thursday, January 31, 2013 - link
I just got a 51.0 average with high quality on minemark29 - Thursday, January 31, 2013 - link
then I ran with extended desktop to have a 1280x720 resolution and got 48.7 averagenoll - Thursday, January 31, 2013 - link
What ROM are you running?mark29 - Thursday, January 31, 2013 - link
Latest cm10.1 nightly plus latest franco kernelSouka - Friday, February 1, 2013 - link
I'd like to see rooted devices and their scores.Keep the CPU/GPU clocks the same... I'm just curios if theres a difference.
then overclock and see if it helps.
My $.02
santeana - Friday, February 1, 2013 - link
53.9 at 720p ;-)aokp 4.2.1, Franco kernel 364, 1405mhz, wheatly
louisotto - Saturday, March 23, 2013 - link
56.8 on Xperia Z on High Performance, 1080 resDrops to 56.0 on High Quality
Curious that it runs at 1794x1080 even though it fills the screen!
SquattingDog - Friday, February 8, 2013 - link
On my Samsung Google Nexus S (2nd generation Nexus):24.8 @ 800x480 (Native), High Performance
21.6 @ 800x480 (Native), High Quality
Specs: 1GHz Cortex A8 Single Core, 512MB RAM, PowerVR SGX540, Jellybean 4.1.2
Taemoor - Wednesday, January 30, 2013 - link
I just got 58.8. I want to confirm this score. Is there anyone else out there with a Kobo Arc? Please reply to this and post your score.thanks
Taemoor - Thursday, January 31, 2013 - link
it was on full res (1280X736) and ran it again with even astonishing 58.9.nagi603 - Thursday, January 31, 2013 - link
B&N NookColour with CM10: 13.whatever fps, regardless of resolution.neothe0ne - Thursday, January 31, 2013 - link
On my APQ8064 / Adreno 320 phone at 720p and "power saving" mode (only 1 core turned on?), I got a 42.9 FPS average (was generally always at ~58 except for some outdoor scenes in the 30s).With all cores on, the average FPS is 57.3. (I saw a low of 45 for a split second I believe)
Apparently that makes this APQ8064 / Adreno 320 phone is marginally better than the Nexus 4 :)
dragonsqrrl - Thursday, January 31, 2013 - link
Strange, I don't seem to have a benchmarking mode on my Droid 3. When it starts up I'm taken straight into the environment, and I don't see any options or settings available. Am I just noob'n out, or is anyone else having this problem?WeaselITB - Thursday, January 31, 2013 - link
Swipe down from the top little banner thing, tap the gear on the right to go into Settings to adjust quality / resolution. Then when you're back in the engine, swipe down again to hit the Benchmark button.dragonsqrrl - Thursday, January 31, 2013 - link
There is no top little banner thing when I'm running around in the environment. This is the difference I was talking about between what I'm seeing on my Droid 3 and the screen shots posted above. I'm wondering if it's a problem specific to the Droid 3 (wouldn't surprise me), or if it has to do with Android 2.3. Is anyone else still running 2.3?jmke - Thursday, January 31, 2013 - link
it's good that it is running close to vsync.means that once you start adding AI , gameplay elements, bots, objects etc the performance will remain good.
imagine if it were running <30fps without any elements or objects inside the gameworld, that would be a bad sign.
xaueious - Thursday, January 31, 2013 - link
Average was mid 30s for my T30 TF300. Anandtech should have one of these devices lying around. Would be curious to see your results.powerarmour - Thursday, January 31, 2013 - link
48.8fps with an Asus Transformer Prime :-http://img716.imageshack.us/img716/7978/screenshot...
fabarati - Thursday, January 31, 2013 - link
Just as a reference, my Optmius 2X (Tegra 2) @ 800x480 scores on High Quality.1st time, 48.7 FPS
2nd time 52.3 FPS
3rd time 51.3 FPS
tipoo - Thursday, January 31, 2013 - link
Even my now archaic Nexus S never dipped below 30FPS in this, and I think the average was just below 40. Most games look far worse than this, yet run worse as well. Granted this has no AI or characters on screen which would rob some performance, but it still looks like more geometry and shading work than the vast majority of mobile games.piroroadkill - Thursday, January 31, 2013 - link
I want Y-inversion..piroroadkill - Thursday, January 31, 2013 - link
That said, I get 23.8fps on my HTC Desire HD at maximum resolution (800x480) at High Quality.Looks even smooth, the quality is glorious.
piroroadkill - Thursday, January 31, 2013 - link
*looks even smoother [than that]Desire HD - 800x480 High Performance: 25.6fps
Desire HD - 800x480 High Quality: 23.8fps
Desire HD - 600x360 High Peformance: 16.5fps
Desire HD - 600x360 High Quality: 15.6fps
Desire HD - 400x240 High Performance: 18.1fps
Desire HD - 400x240 High Quality: 17fps
Yes, reducing resolution dramatically reduced framerate on my device.
piroroadkill - Thursday, January 31, 2013 - link
Not that it matters, but for completeness, this is running an old Gingerbread ROM, Android Revolution HD 5.1.11, Android 2.3.3, CPU clocked @ 1.2GHz.sheh - Thursday, January 31, 2013 - link
And would performance on the Exynos/Mali variant be better than the MSM/Adreno?sheh - Thursday, January 31, 2013 - link
I guess the Note 2 there should be pretty similar to the "other" S3.Kepe - Thursday, January 31, 2013 - link
A friend of mine ran the benchmark on his Exynos based S3, he got 41,3 fps.CeriseCogburn - Friday, February 1, 2013 - link
Hardware variants - something to do with the cell chip type and other wifi junk - but yeah the point is, it's irritating.Got 45.3 on the Note 2 here, not 45.8 as the chart shows - US version, original android no hacks, has the quad and the mali 400, jellybean 4.1.1, cleared the ram first as well that helped a bit, also it came with split screen apps working.
960x540 (75% rez) high quality = 45.6
100% rez(1280x720), high performance = 47.4
lol - Kind of surprised I guess the mali400 is a bit weak / it does better in the bench suites Quadrant and Antutu vs the others in the charts.
sheh - Friday, February 1, 2013 - link
But then, why should the RF radio affect the CPU and GPU choice? :)And I also don't get why they don't have unified RF hardware as well, maybe with the exception of antennas which take up physical space.
CeriseCogburn - Wednesday, February 6, 2013 - link
Brain Klug mentioned it somewhere might be in this article about the chip doing LTE - so the dual core snapdragon version had to mesh with the no LTE radio chip as I understood it.Others elsewhere have stated there were shortages of quadcores due to demand so Samsung used alternate cores for regions and also for similar phones (changing nearly just the ARMs core and making a new phone model).
So I guess there are several reasons.
sheh - Friday, February 1, 2013 - link
Strangely lower. I guess it's difficult to say like that if there are other factors than CPU and GPU.WeaselITB - Thursday, January 31, 2013 - link
Droid 4 (TI OMAP4430 1.2GHz / PowerVR SGX540 304MHz / 1GB RAM)Average FPS of three runs: 49.9
Resolution 960x540 qHD
High Quality
Kepe - Thursday, January 31, 2013 - link
HTC Sensation (qHD) @ 1728 MHz CPU & 332 MHz GPU and set to High Quality1st run 42,1 fps
2nd run 41,1 fps
3rd run 41,5 fps
hammer256 - Thursday, January 31, 2013 - link
Resolution: 1024x720Average FPS: 29.3
Ok so Adreno 220 might be showing its age at this point....
randomhkkid - Thursday, January 31, 2013 - link
Strange that the s2 scores lower than the Galaxy nexus even though the GNex is a higher res and has a slower gpu.powerarmour - Thursday, January 31, 2013 - link
I think it's quite well optimized for PowerVR hardware, especially if it's an iOS port.Then again Tegra 3 seems to do quite well, I wonder what excuse the Nvidia haters will have for this one... ;)
CeriseCogburn - Friday, February 1, 2013 - link
None.I'm thrilled, it's utter silence...
Wait, the tegra3 won, top o the chart ... why one would think they'd retract all the months of whining about tegra3.
Not thrilled, I take it back.
lmcd - Friday, February 1, 2013 - link
Mali 400's deficiencies have been thoroughly noted and addressed in the T-seriesSilverEyes - Thursday, January 31, 2013 - link
Device: Samsung SGS I9000 @ stock CPU, running 4.2.1 by pawitpbuild.props set to Nexus S for install from app store
Resolution: 800x480 (100%)
High Performance (just one run):
Average FPS: 33.7
High Quality:
1st Run: 23.3 fps
2nd Run: 20.5 fps
3rd Run: 18.4 fps
Qualitatively: I'm surprised how well this ran. Far smoother than Splice for instance, which is choppy on my phone at best.
Great framerate given the age of the hardware, only occasional stuttering.
Lonyo - Thursday, January 31, 2013 - link
I noticed on the Google Play store that it shows 134MB download for my Galaxy S3 and Transformer TF101, but only a 94MB download for my Galaxy Tab 2 7".Is it the same benchmark being run on each device, or is it different versions of the "game"?
CeriseCogburn - Friday, February 1, 2013 - link
Good question - shows 41.07 mb on my Galaxy Note 2 from the google play store once installed...If I go full webpage I get 153mb download from google play.
UpSpin - Thursday, January 31, 2013 - link
As long as it still runs on a HTC Desire / Nexus One, it's not worth any further investigation.Sure, it only runs at 11 FPS average according to the benchmark, but that's way too good for my 'ancient' smartphone.
And rendering such static scenes is always less demanding than a moving character, or even several characters (battle) with lots of additional details and effects. So I don't really see a use in this except advertising for Epic, which, however, isn't an indicator for the quality of real games, because of the missing effects/characters/moving objects.
nathanddrews - Thursday, January 31, 2013 - link
Average of three runs:T-Mobile Samsung Galaxy S3 (100% resolution 1280x720)
Quality 42.3fps
Performance 46.2fps
Acer Iconia A100 (100% resolution 1024x552)
Quality 32.5
Performance 36.8
rs2 - Thursday, January 31, 2013 - link
The app crashes for me whenever I try to access the 'Settings' section. Device is a Sony Xperia S.Any ideas?
felipetga - Friday, February 1, 2013 - link
My Acer Iconia scored 33.7 fps, High Quality @ 1024x552. Running regular Android 4.03. Tegra 2 still hanging on its own... sort of...RaistlinZ - Friday, February 1, 2013 - link
Sprint HTC EVO 4G LTEAvg: 45.4
High Quality
1028x720
Krysto - Friday, February 1, 2013 - link
This just shows how old the Epic Citadel demo is. Most devices already reach 60 FPS at native resolution on max quality with it. I don't know why they even bother porting it at this point. They should've just worked on a new one based on Unreal 4, and then launch for both iOS and Android in the same time. This was pointless.DesktopMan - Saturday, February 2, 2013 - link
An option to turn off vsync (if possible) would make it more useful for comparisons. It would also still let Epic brag about how well it runs.shubham412302 - Saturday, February 16, 2013 - link
my atrix 2 scored 53.3 with stock