Friday | September 30, 2016
Popular Links:
3DMark for Android

3DMark for Android Fine Art Phd Thesis Company Custom Essay Junior Research Paper Help

College Essays Recommended Length
The Android version of 3DMark includes a new test. Ice Storm Extreme raises the rendering resolution from 720p to 1080p and uses higher quality textures and post-processing effects to create a more demanding load for the latest smartphones and tablets. Ice Storm Extreme will soon be available in the Windows version of 3DMark too, giving you another way to compare the performance of Android and Windows tablets directly.

There are no separate Advanced or Professional Editions on Android. You will be using the same version of the benchmark that will be available worldwide, for free, from the Google Play store."

Paper On Fight Club Do My Homework Finance 3DMark for Android starts with a very simple screen:

3DMark for Android 3DMark for Android

3DMark for Android 3DMark for Android 3DMark for Android

3DMark for Android 3DMark for Android Book Reports Done For You

Buy Autodesk AutoCAD LT 2015 (32-bit) oem

On Windows, Ice Storm uses a DirectX 11 engine limited to Direct3D feature level 9 (9_3/9_1 depending on optional shadow filtering support). On Android and iOS, Ice Storm uses OpenGL ES 2.0 and content, settings and rendering resolution are the same on all platforms and scores can be compared across Windows, Windows RT, Android and iOS.

Ice Storm runs at 1280×720 with normal texture resolution and post-processing quality. Extreme ups the resolution to 1920×1080 and increases texture resolution and post-processing quality. Given that there are a number of resolutions around for phones and tablets after the rendered scene is created it is scaled to the native resolution of the display. This is commonly called "offsceen rendering" and Futuremark feel it is the best approach for ensuring that devices can be compared fairly.

Futuremark also note that no vendor specific OpenGL ES 2.0 extensions are used, that textures are compressed using ETC and textures that require alpha channel are loaded uncompressed.

3DMark for Android 3DMark for Android
3DMark for Android 3DMark for Android

In terms of specific engine features we have:

Traditional forward rendering using one pass per light.
Scene updating and visibility computations are multithreaded.
Draw calls are issued from a single thread.
Support for skinned and static geometries.
Surface lighting model is basic Blinn Phong.
Supported light types include unshadowed point light and optionally shadow mapped directional light as well as pre-computed environmental cube.
Support for transparent geometries and particle effects.
16-bit color formats are used internally in illumination buffers if supported by the hardware.

So what about performance?
Well here we have a selection of results from the last few generations of hardware for comparison. Our test devices all have 1GB of memory and are running their latest OS. (NOTE: These are Euro/UK versions of the devices):

Device Phd Thesis Umist CPU/GPU
Galaxy Note 10.1
Exynos 4412 Quad Core A9-1.4GHz / Mali-400MP
Galaxy S3
Exynos 4412 Quad Core A9-1.4GHz / Mali-400MP
HTC ONE X Tegra 3 – Quad Core A9- 1.5GHz / GeForce
NEXUS 7 Tegra 3 – Quad Core A9 -1.2GHz / GeForce
Xperia T Dual Core Krait 1.5GHz / Adreno 225
Sony Tablet S Tegra 2 – Dual Core A9 – 1GHz / GeForce

Thanks to Vodafone for their continued device support:
Vodafone UK

3DMark for Android Benchmark

3DMark for Android Benchmark

So there are some expected scores in the above tables, for example the Note 10.1 and Galaxy S3 scoring near identical results. Then there are some interesting figures such as the Tegra 3 scoring better than Exynos on gaming, but not physics. Then of course there are surprises such as the dual core Xperia T outperforming the rest of the devices in the graphics test which is more of a factor in the overall result and places it higher in the leader board.

So what are our thoughts on 3DMark for Android overall? Well so far it seems the app is off to a decent start. There are still a few stability kinks to be worked out, for example a few crashes on our S3 and there are mistakes in the spec/hardware database… even some missing mainstream devices such as the Note 10.1 but these are to be expected given the vast number of devices and configurations out there. The fact is that for some time now Android (and iOS etc) has needed a range of useful benchmarking applications and over time this may well become one of the key metrics when judging hardware for purchase.

Write Master Thesis Plan Let us know your thoughts and scores in the forum…

About Author

Stuart Davidson