The MobileXPRT 3 Community Preview is now available to BenchmarkXPRT Development Community members! If you are not familiar with the updates and changes we implemented in the newest version of MobileXPRT, you can read more in the XPRT blog.
Members can access the MobileXPRT 3 Community Preview APK on the MobileXPRT tab in the Members’ Area. We also posted an installation guide that provides a general overview of the app and walks users through each step. The entire process takes about five minutes on most devices.
If you have any questions about MobileXPRT 3 or joining the community, please let us know. Happy testing!
We appreciate everyone’s patience and feedback during the MobileXPRT 3 development process. We’re in the process of wrapping up some final testing and expect to release the Community Preview (CP) within the next week.
The first thing testers will notice about the CP is a new UI/UX experience. The aesthetic is completely different than MobileXPRT 2015. We’ve made it easy to select and deselect individual workloads by tapping the workload name, and we’ve consolidated common menu items into an Android-style task bar at the bottom of the screen to improve navigation.
Fundamentally, we rebuilt MobileXPRT with Android Studio SDK 27 to bring it up to date with contemporary Android development standards. While we kept the five workloads from MobileXPRT 2015, we gave one a major overhaul, updated the test content in the remaining four, and added a sixth workload: Optical Character Recognition. You can find more details about these changes in our earlier discussion about MobileXPRT 3 development in the blog.
The screenshots below show the MobileXPRT 3 main screen, how the screen looks when users customize the combination of workloads, the end-of-test results screen, and the archived results page with one test result view expanded. Note that the archived results page also displays the median of all overall test scores completed to date.
We’ll announce the CP in a community message and here on the blog when it goes live. As with all community previews, the MobileXPRT 3 CP will be available only to BenchmarkXPRT Development Community members. If you have any questions about MobileXPRT 3 or joining the community, please let us know. Happy testing!
The next couple of months will be very busy with XPRT activity, so we want to update readers on what to expect. Depending on a number of factors, we expect to release HDXPRT 4 and MobileXPRT 3 community previews (CPs) within the next four to six weeks. We’re also hoping to publish an early AIXPRT request-for-comment (RFC) build on GitHub within the same time frame. Here’s a little more detail about each of these developments.
HDXPRT 4: We originally planned to release the HDXPRT 4 CP several weeks ago. As we recently discussed in the blog, a lot has changed in the Windows 10 development world within a short period of time, and Microsoft has released a number of new Redstone 5/October 2018 Update builds in quick succession. While our HDXPRT 4 CP candidate testing went well overall, we observed some inconsistent workload scores when testing on some of the new Windows builds. Since then, we believe we’ve narrowed down the list of possible causes to a few specific graphics driver versions, but we’re still testing to make sure there are no other immediate issues. As soon as we’re confident in that assessment, we’ll release the CP along with any relevant information about the affected graphics drivers.
MobileXPRT 3: MobileXPRT 3 development is progressing nicely, and we’re close to completing a CP candidate build. We’ll test that build extensively on our library of Android phones and tablets, and barring any unforeseen issues, we plan to release the CP in the next few weeks.
AIXPRT: AIXPRT is the umbrella name for a set of tools we’re developing to help evaluate machine learning performance. After a great deal of research, we’re getting closer to releasing a build – tentatively called the AIXPRT RFC – for community members and other interested parties to download and review. For a number of reasons, the AIXPRT RFC process will be a little different than our normal XPRT RFC and CP process. We’ll be offering more information on the AIXPRT RFC build over the next several weeks.
We’re grateful to everyone who’s contributed in any way to each of these projects, and we look forward to sharing the benchmarks with the world. If you have any questions about the XPRTs, please don’t hesitate to ask!
In last week’s blog, we discussed why we now consider full BatteryXPRT rundown tests to be the most accurate and why we’re releasing a new build (v110) that increases the default BatteryXPRT test from 5.25 hours (seven iterations) to 45 hours (60 iterations). We also built v110 using Android Studio SDK 27, in order to bring BatteryXPRT up to date with current Android standards. Today, we’ve posted the new build on BatteryXPRT.com and in the Google Play Store, and we’ve also published an updated user manual. Please contact us if you have any questions about BatteryXPRT testing.
Last fall, we published the WebXPRT 2015 Processor Comparison Chart, a tool that makes it easier to access hundreds of PT-curated, real-world performance scores from a wide range of devices including everything from TVs to phones to tablets to PCs. Today, we’re happy to announce that we’ve added a WebXPRT 3 Processor Comparison Chart.
The WebXPRT 3 chart follows the same format as the WebXPRT 2015 chart, letting you click the average score of each processor to view all the WebXPRT 3 results we currently have for that processor. You can change the number of results the chart displays on each page, and as the screenshot below shows, a new drop-down menu lets you toggle back and forth between the WebXPRT 3 and WebXPRT 2015 charts. W plan to add additional capabilities on a regular basis, so if you have ideas for features and types of data you’d like to see, let us know!
If you’d like to submit results for us to consider for publication in the chart, follow the detailed instructions here. The submission process is quick and easy. We look forward to seeing your results!
Some time ago, we started to see unusual BatteryXPRT battery life estimates and high variance on some devices when running tests at the default length of 5.25 hours (seven 45-minute iterations). We suspected that the problem resulted from changes in how new OS versions report battery life on certain devices (e.g., charging past a reported level of 100 percent). In addition, the progress of battery technology in general means that the average phone battery lasts much longer than it did a few years ago. Together, these factors sometimes led to BatteryXPRT runs where the OS reported little to no battery decrease during the first few iterations of a test. We concluded that 5.25 hours wasn’t long enough to produce an accurate battery life estimate.
After extensive experimentation and testing, we’ve decided to release a new build that increases the default BatteryXPRT test length from 5.25 hours (seven iterations) to 45 hours (60 iterations) to allow enough time for a full rundown on most phones. Based on our testing, we consider full rundown tests to be the most accurate and will use those exclusively in our Spotlight testing and elsewhere. Testers will still have the option of choosing shorter test durations, but BatteryXPRT will flag the results with a qualifier that recommends performing a full rundown.
We plan to release the updated build by the end of next week and update BatteryXPRT documentation to reflect the changes. We have not changed any of the workloads and both performance results and full-rundown battery life estimates will be comparable to results from earlier builds.
BatteryXPRT continues to be a useful tool for gauging the performance and expected battery life of Android devices while simulating real-world tasks. If you have any questions about BatteryXPRT, please feel free to ask!