- Added a battery test for Android, iOS.
- Added a brief summary to “Share Results” email on iOS.
- Addressed 64-bit code generation issues on Android/AArch64.
- Fixed a crash that occurred on Windows 10.
- Fixed a crash that could occur on 32-core systems.
- Reduced the memory footprint of the BlackScholes workload.
The biggest new feature in Geekbench 3.3 is the battery test. The new battery test is designed to measure the battery life of a device when running processor-intensive applications (such as games).
The test is meant to completely discharge a completely charged battery. While it’s possible to run the test with a partially discharged battery (e.g., a battery with 75% charge) the test results will not be as accurate.
The recommended steps for running the test are as follows:
- Plug in your device.
- Launch Geekbench 3.
- Launch the battery test.
- Wait for your device to completely charge.
- Unplug your device. The battery test will start automatically. The test can take several hours to complete, especially on newer devices with larger batteries.
- Wait for your device to completely discharge and turn off.
- Plug in your device and wait for it to turn on.
- Launch Geekbench 3. The battery test result will display automatically.
The test result includes the battery test runtime, the battery test score, and the battery level at the beginning and at the end of the test.
Here’s what the different numbers mean:
Battery Runtime is the battery test runtime. If the test started with the battery completely charged and ended with the battery completely discharged then the test runtime is also the battery lifetime.
Battery Score is a combination of the runtime and the work completed during the battery test. If two phones have the same runtime but different scores, then the phone with the higher score completed more work. As with Geekbench scores, higher battery scores are better.
Battery Level is the battery level at the start and the end of the test.
We hope you find the new battery test useful. Please let us know if you have any questions, comments, or suggestions regarding the test (or the release).