3DMark fails with a black screen. Help?
There appears to be a rare issue when updating from older 3DMark to latest version that can cause this. Workaround is to uninstall, then reinstall 3DMark. We've made sure that this should not happen with future 3DMark updates.
3DMark fails to load on my phone - it just stops during loading or loads the first test and then exits. Why?
The most likely cause is lack of memory. First, verify that your device has 1 GB (1024 MB) memory to meet the minimum requirements. Second, note that any applications that are running in the background also consume memory. We recommend closing all background apps before running the tests as such programs always consume some resources and may influence your benchmark score negatively.
3DMark for Android v1.0.1 update includes changes that should resolve this issue for any 1 GB device models. Verify that you have the updated version. Devices with less than 1 GB are officially unsupported but may be able to run the tests if you untick "run demo" in the settings.
3DMark crashes on my Android device. Help!
We've tried to flag all the incompatible devices on the Google Play store but as there are so many devices and variants, we may have missed some. Please help us improve our list by telling us about your incompatible device.
The most common compatibility problem is with devices, such as the Samsung Galaxy Nexus or Samsung Galaxy Tab 2, that have the TI OMAP 4430 or TI OMAP 4460 chipset. We don't currently have a workaround, unfortunately, but now that 3DMark is publicly available we hope that the manufacturers and operators offering devices with these chips will notice the compatibility issues and work with us to fix them. Note that unticking "run demo" in the settings may allow you to complete a run on OMAP-based devices but there will be graphics corruption in the physics test.
For all other devices and any other crash issues, please post on our support pages including as much detail about the problem and your device as possible.
The benchmark stopped running in the middle of the test. Why?
If you are using a compatible device, make sure that all other apps running in the background have been closed. You may also want to temporarily disable notifications as the benchmark run will end prematurely if it is interrupted by an external application.
3DMark Android Edition FAQ
Which 3DMark benchmark should I use to test my device?
3DMark recommends the best test for your device on the Home screen. You can find more benchmark tests on the Benchmarks screen. Some tests might not be compatible with your device.
In general, you should use:
- Sling Shot Extreme for high-end smartphones and tablets that support OpenGL ES 3.1 or Vulkan.
- Sling Shot for mainstream devices that support OpenGL ES 3.0.
- Ice Storm Extreme for low-cost smartphones and tablets.
- Ice Storm for older devices.
The API Overhead feature test is a specialized test for comparing the performance of APIs.
What are the hardware requirements for 3DMark Android benchmarks?
3DMark Sling Shot Extreme
- Android 5.0 or later, 1.5 GB memory, OpenGL ES 3.1 compatible, 203 MB of free storage space.
3DMark Sling Shot
- Android 5.0 or later, 1 GB memory, OpenGL ES 3.0 compatible, 203 MB of free storage space.
3DMark Ice Storm Extreme and Ice Storm
- Android 4.0 or later, 1 GB memory, OpenGL ES 2.0 compatible, 235 MB of free storage space.
3DMark API Overhead feature test
- For the OpenGL ES 3.0 part: Android 5.0 or later, 1.0 GB memory, OpenGL ES 3.0 compatible.
- For the Vulkan part: Android 7.0 or later, 1 GB memory, Vulkan compatible.
- 113 MB of free storage space.
Can I compare my results with scores from Apple devices?
Yes, scores from benchmarks with the same name can be compared across platforms.
Scores from tests with different names are not comparable. For instance, Sling Shot scores should not be compared with scores from Sling Shot Extreme. Even though the tests appear to be similar, they use different rendering resolutions and post-processing techniques.
When comparing scores across platforms, please note that the results reflect the performance of both hardware and software. APIs with low overhead, such as Metal and Vulkan, can deliver more performance than OpenGL ES even on devices with similar hardware.
Why can't I see my result in the Best Devices list?
The Best Devices list is not a "Hall of Fame". The scores are averages of results from users with the same device, with unusually high or low results excluded. For popular models, the average is calculated from thousands of individual results. The aim of the Best Devices list is to show how devices typically perform with stock settings.
You can find your own personal best scores on the "My Device" screen in the app.
My 3DMark scores seem to vary wildly between runs. Can I trust these results?
Some high-performance devices use aggressive thermal throttling to control the temperatures of the processors inside the device. As the device heats up it intentionally slows the processor to avoid overheating, which in turn leads to lower performance scores on successive runs. Measuring the effects of thermal throttling is another interesting way of using 3DMark to compare the performance of different devices.
To reduce this effect, we recommended waiting 15 minutes between runs to allow the device to cool down. You should also unplug the device during testing as the battery charging circuitry also generates heat. Try running the test in a cool environment. Don't run the benchmark in direct sunlight or near sources of heat, for example. For more tips on getting the best results from your device, please see our How to Benchmark page.
3DMark says I have a 'Mystery Machine.' What does that mean?
This message simply means that we haven't mapped your device in our database yet. There are thousands of compatible Android devices, and we are working hard to map and verify them all. You can get the latest list by completely closing the 3DMark app on your device, then restarting it. We refresh the database every hour.
If you have a brand new device model, please feel free to report the problem and include a link to a website detailing the hardware specs of your device.
Even if your device is not identified, your benchmark score is still perfectly valid for making comparisons.
Some of the hardware details shown for my device are incorrect.
We do our best to verify all data. There is a button at the bottom of the "My Device" page where you can report errors you have spotted. Please describe what you believe is incorrect.
Do note that some popular phone models can have different hardware depending on where and when they were bought, even if they share the same model name. You may want to first verify your exact model so that you are absolutely certain the data is in error.
If you notice that we have mis-mapped a device (i.e. the data fits another model of the same device but not yours), do mention that when reporting the issue.
I'm have a custom ROM and my device isn't recognized. Why?
On mobile devices, 3DMark reads the manufacturer and model information supplied by the OS. Unfortunately, with many custom ROMs this information is not available, and the app cannot tell what kind of hardware you have.
3DMark will show incorrect information if your custom ROM has a fake device string. The most common case seems to be with some Chinese tablets with ROMs that claim to be "gt-i9300" which is the Samsung Galaxy S III (Exynos 4 Quad). The same is true for lookalike phones that may appear to be a well-known model but inside the actual hardware of the device is completely different. If it's not a genuine device, 3DMark most likely won't be able to identify it at all.
Currently, there is no workaround for this issue. If your device manufacturer and/or model information is incomplete or wrong, 3DMark can't identify it.
In all of these cases, however, the benchmark score is still valid. The benchmark does not know which device you are using and the performance measured is still accurate for the actual hardware.
Where can I find more technical detail about the tests?
Our 3DMark technical guide contains detailed descriptions of the tests and an explanation of how scores are calculated. The guide covers all platforms, including iOS.