Results: Web Tests
Our test methodology for this section aims to mitigate the impact of browser versions and ensure consistent results across the respective platforms, hence we chose to use a standard version of the Chromium-based Opera 16 browser for all Android devices. Since iOS limits our choice to Safari and we are unable to easily force versioning on that platform, the iPhone 5s is included as a reality check or sorts, not as a direct CPU-to-CPU comparison to the Android devices.
The Apple iPhone 5s comfortably takes the lead in this test. The Find 5, which previously performed less-than-optimally due to its Android 4.1.1 OS and FHD resolution, improves in this test, appearing just behind the more powerful Sony Xperia Z1. As for the HTC One, the device continues to suffer from its HTC Sense ROM.
Unsurprisingly, the iPhone 5s absolutely dominates the JSBench test as a result of both its 64-bit ARM A7 SoC and iOS' native thread boosting for the HTML engine (also a likely reason why the OS is restricted to Safari). Moving onto the Android platform, the Xperia Z1 tops the chart with a resounding margin over the HTC One. Although it's easy to point to the phone's powerful Snapdragon 800 SoC as the explanation for its performance, Sony was one of the first to optimize for the Krait architecture with its first-generation Xperia smartphones, so it’s likely these optimizations carry forward into the company's current device line-up.
The Find 5's poor performance in this test can once again be attributed to its Android 4.1.1 operating system and substantial quantity of "live" content that is simply not present in the Galaxy S3's version of Android 4.0.4.
We commence our range of HTML5 tests with the Impact HTML5 Benchmark, which is essentially a time demo of the Impact HTML5 game engine. This test should provide an indication of each device's performance in most HTML5-based platformers.
The Impact HTML5 test also provides another indication of the HTC One's relative lack of memory due to HTC Sense. The device comes in last place in spite of its Snapdragon 600 being the third most powerful SoC on paper.
Finally, we have Principled Technologies' WebXPRT, an HTML5-based Web app benchmark. This test simulates common productivity tasks that are traditionally handled by locally-installed applications, including photo editing, financial charting, and offline note-taking.
Although WebXPRT seems significantly more focused on math throughput and consequently allows the Snapdragon 600 to perform much better, the test essentially duplicates Impact HTML5. Consequently, we continue to see the dominance of the iPhone 5s and the excellent performance from the Xperia Z1 and its Snapdragon 800 SoC.
btw The audio and storage rows in the first page are mixed up.
SOftware is where it lacks, though. I got this because Oppo promised frequent updates to the OS, and TBH the Android-based variant it came with was not too bad of an experience. Then it became clear that the development team does not really know what they're doing (same minor but annoying bugs with every release, now barely coming through with 4.2, etc). They could have given CyanogenMod the kernel and drivers and let them pick up the development. CM-based ROMs are functional, but still plagued by bugs that come from lack of access to proprietary code.
Basically, their approach (at one point there were 2 or 3 versions of ROMs in development, none out of a beta state) stretched them way too thin, and it shows.
Last but not least, ignoring many requests of just embracing AOSP and let the plethora of apps do the rest was not a smart move on Oppo's part.
With this phone, however, I doubt Apple will stick it inside their own chassis and call it ther own. It is mildly interesting, but as is often the case, forays into new market segments by otherwise high quality manufacturers are often precarious.
By all means, get an Oppo Blu-Ray player. As far as the phone, they need to get through their growing pains.
It seemed a bit biased and not truly giving a comparison with current market phones.