This week, we
published an updated MobileXPRT 3 build, version 220.127.116.11, on MobileXPRT.com and in the Google Play Store. The new build addresses an issue we recently discovered, where
MobileXPRT was crashing after installation on some Android 11 phones.
Permissions requirements and a new storage strategy called scoped storage were causing the problem. By default, scoped storage restricts
an app’s storage access to app-specific directories and media, and prohibits
general access to external or public directories. It also prevents third-party
apps such as email clients or file managers from accessing MobileXPRT 3 results
files. This default setting requires an opt-in permissions prompt that
MobileXPRT 3 did not have prior to this week’s release.
MobileXPRT 18.104.22.168 points all of the benchmark’s file references to its private directory and allows users to zip results files and attach them to results submission emails. Neither change affects the testing process or test scores. If you have any questions or comments about the new MobileXPRT 3 build, please let us know!
As we discussed last week, we’ve learned that MobileXPRT 3 is crashing after installation
on some Android 11 phones. We now know what is causing this behavior: changes
to the storage strategy and permissions requirements in Android 11. The new file
storage strategy is called scoped storage. By default, scoped storage restricts an app’s storage access
to app-specific directories and media, and prohibits general access to external
or public directories. This default setting requires an opt-in permissions
prompt that MobileXPRT 3 does not currently have. It also prevents third-party
apps such as email clients or file managers from being accessing MobileXPRT 3
To fix this, we are
planning to rebuild MobileXPRT 3 to (1) point all of the benchmark’s file
references to its private directory, and (2) allow users to zip results files
and attach them to results submission emails. While we do not expect that either
of these changes will affect performance results, we’ll perform testing to
confirm this before we publish the new build.
We don’t expect these changes to take too long, and will keep you updated here in the blog. If you have any questions about the update process or MobileXPRT 3, please let us know!
We recently received a tech support inquiry about problems with new MobileXPRT 3 installations on some Android 11 phones. The tester installed MobileXPRT 3 on a selection of phones running Android 11, and the app crashed immediately upon opening. We were able to reproduce the issue on multiple phones in our lab, and currently know that the issue may happen on the Google Pixel 3, Google Pixel 4a 5G, Google Pixel 4XL, Google Pixel 5, and the OnePlus 8T (running Android 11 with an Oxygen OS skin).
MobileXPRT 3 continues
to run without issues on Android 9 and 10 phones. When we updated an Android 10
phone with an existing MobileXPRT 3 installation to Android 11, we found that
the benchmark ran successfully. This suggests a lack of fundamental
incompatibilities between MobileXPRT 3 and current versions of Android 11. Because
some of our lab techs experienced crashes immediately after the app asked for
permissions, we think it’s possible that new permissions-setting requirements
in Android 11 are causing the problem.
working to isolate the problem and identify a course of action. We’ll share
more information here in the blog as soon as possible. If you’ve encountered
this problem in your testing, we apologize for the inconvenience, and we’re
thankful for your patience as we work towards a solution.
If you have any information you’d like to share about running MobileXPRT 3 on Android 11, please let us know!
Today, we want to share quick
updates on a few XPRT topics.
In case you missed yesterday’s announcement, the CrXPRT 2 Community Preview (CP) is now available. BenchmarkXPRT Development Community members can access the preview using a direct link we’ve posted on the CrXPRT tab in the XPRT Members’ Area (login required). This tab also provides a link to the CrXPRT 2 CP user manual. You can find a summary of what’s new with CrXPRT 2 in last week’s blog. During the preview period, we allow testers to publish CP test scores. Note that CrXPRT 2 overall performance test scores and battery life measurements are not comparable to those from CrXPRT 2015.
We’ll soon be publishing our
first AIXPRT whitepaper,
Introduction to AIXPRT. It will summarize the AIXPRT toolkits and
workloads; how to adjust test parameters such as batch size, levels of
precision, and concurrent instances; how to use alternate test configuration
files; and how to understand test results. When the paper is available, we’ll
post it on the XPRT white papers
page and make an announcement here in the blog.
Finally, in response to decreased downloads and usage of BatteryXPRT, we have ended support for the benchmark. We’re always monitoring usage of the XPRTs so that we can better direct our resources to the current needs of users. We’ve removed BatteryXPRT from the Google Play Store, but it is still available for download on BatteryXPRT.com.
If you have any questions about CrXPRT
2, AIXPRT, or BatteryXPRT, please let us know!
We’re excited to announce that the MobileXPRT 3 source code is now available to BenchmarkXPRT Development Community members!
Download the MobileXPRT 3 source here (login required).
We’ve also posted a download link on the MobileXPRT tab in the Members’ Area, where you will find instructions for setting up and configuring a local instance of MobileXPRT 3.
As part of our community model for software development, source code for each of the XPRTs is available to anyone who joins the community. If you’d like to review XPRT source code, but haven’t yet joined the community, we encourage you to join! Registration is quick and easy, and if you work for a company or organization with an interest in benchmarking, you can join the community for free. Simply fill out the form with your company e-mail address and select the option to be considered for a free membership. We’ll contact you to verify the address and then activate your membership.
If you have any other questions about community membership or XPRT source code, feel free to contact us. We look forward to hearing from you!
Today, we published an updated MobileXPRT 3 build, version 22.214.171.124, on MobileXPRT.com and in the Google Play Store. The new build fixes an issue that was causing crashes on Xiaomi phones. Xiaomi holds significant market share in China, so we wanted to address the issue as soon as possible.
Xiaomi phones use a proprietary Android-based firmware called MIUI, which requires apps to communicate with the system in a specific way. When we originally built MobileXPRT 3, Android allowed an app’s code to send implicit messages calling certain classes of actions. In MIUI, the code must broadcast explicit messages that call the exact action necessary (e.g., waking from sleep). The requirement can improve security by allowing more granular levels of user control, and save power by restricting the number of unseen tasks that apps can run in the background without a user’s knowledge. The new MobileXPRT 3 build code complies with MIUI’s requirements. Other Android-based platforms will likely require explicit messages in the near future, so we’re hoping the new build will be relatively future proof.
We also fixed a few small UI bugs and improved the accuracy of the system hardware information that the app reports when a user submits a set of results. None of these changes affect performance, so scores from prior MobileXPRT 3 builds are comparable to those from the new build. If you have any questions or comments about MobileXPRT 3, please let us know.