LightBlog

dimanche 6 novembre 2016

Huawei Mate 9/Kirin 960 Early Testing & Comparison with Pixel XL/Snapdragon 821

Huawei has ambitious plans for itself, as the Chinese giant that aims to eventually beat Apple also wants to be the second largest smartphone maker within the next two years. At the heart of this mammoth effort is Huawei's flagship lineup, which now includes the Huawei Mate 9.

The following article covers the theoretical maximum performance of the Kirin 960 compared to the Snapdragon 821 by looking at various benchmark results; none of these findings should be confused with indicators of actual real-world performance, which we will cover in future articles.

Despite all of the technology that the Mate 9 packs inside, the SoC is one of the most alluring aspects for performance junkies, and the Kirin 960 has a lot to live up to in the world of ever-increasing competition. So, the question is: how does the Kirin 960 compare to the Snapdragon 821? We took the Huawei Mate 9 through an early set of benchmarks to get a feel for the SoC's CPU and GPU performance, although we still have a lot of testing to do regarding real-world UI performance, thermal throttling, thermals, and real-world gaming performance. But those are topics for another day, so let's look at what we've found so far.


Huawei's HiSilicon Kirin 960

The Kirin 960 inside the Huawei Mate 9 is the latest flagship-grade SoC to debut in a device in 2016. Manufactured by Huawei's semiconductor subsidiary, HiSilicon, the Kirin 960 employs a big.LITTLE octa-core configuration: four Cortex-A73 cores operating at a peak frequency of 2.36GHz and four Cortex-A53 cores operating at a peak frequency of 1.84GHz. The GPU on the Kirin 960 is handled by the newest ARM Mali-G71MP8 GPU clocked at 900MHz and based on the 'Bifrost' architecture.

When compared to the Kirin 950, the Kirin 960 offers a few notable improvements. While the Kirin 950 employed four Cortex-A72 cores for its performance cluster, the Kirin 960 bumps this cluster to four Cortex-A73 cores. Despite the similarity in their nomenclature, the design used in the A73 is more similar to the Cortex-A17 Sophia µarch family while the A72 is closer in design to the A57 and A15 Austin µarch family. ARM claims that the new architecture is faster (by up to 30%), smaller, and more efficient (by up to 30%) than the A72, making the A73 a definite improvement in the performance department.

The GPU, though, is a different ball game altogether. The Mali-G71 is the first GPU from ARM built on the newest 'Bifrost' architecture. When compared to the Mali T880, the Mali-G71MP8 doubles the number of shader cores (from a maximum of 16 to 32). Couple this with the move to the new architecture, and you get a GPU that is more powerful and more efficient than the GPU in the predecessor, while still remaining scalable. Over the T880, ARM claims that the G71 offers 20% better energy efficiency, 40% better performance density, and 20% external memory bandwidth savings.

To put all of this in context, let us remember how the 2015 HiSilicon Kirin 950 performed. In our review of the Honor 8, we found that the Kirin 950 had great performance while demonstrating decent thermal efficiency, especially during sustained performance. However, the GPU was the weakest link in the Kirin 950, so Huawei had to step up their efforts this year. The Kirin 950 was the first flagship SoC to employ CPU cores based on the Cortex-A72 architecture when it was deployed in the Huawei Mate 8 in late 2015, but while other SoCs began utilizing Cortex-A72 cores this year, Huawei had to introduce something better to remain ahead of the curve. And they did just that with the Kirin 960 which improves the peak and sustained CPU and GPU performance.


Hands On

While the HiSilicon Kirin 960 is expected to be better than the Kirin 950, how does it fare against the Qualcomm Snapdragon 821, the SoC used in some recently released flagships? To compare, we put the Kirin 960 in the new Huawei Mate 9 to the test against the Snapdragon 821 Pro-AB found in the Google Pixel XL and ran both devices through a few benchmarks. Keep in mind that the Pixel Xl's Snapdragon 821 runs at the same clock speeds as the regular Snapdragon 820, but we'll update our findings as soon as we get our hands on a device running on a different variant of the Snapdragon 821 within the next few weeks. Each benchmark below was performed three times to weed out outlier results, and the three results for each benchmark were averaged to provide a more accurate score for each device. In addition, to reduce the effects of thermal throttling on our peak performance testing, we allowed each device to cool down between each testing iteration before proceeding with the next benchmark. With that being said, keep in mind that again these results are only representative of theoretical peak performance and not sustained performance, which we will be testing in the future.

Starting off with GeekBench 4, a benchmark that mainly tests the CPU's prowess (single and multi core) we find the following results:

geekbench-4-scores

 

In single core performance, the Kirin 960 on the Mate 9 performs better than the Snapdragon 821 on the Google Pixel XL. The multi core performance is where the dual-cluster octa-core setup and the A73's on the Kirin 960 shine against the dual-cluster quad-core Kyro setup on the Snapdragon 821, offering around 30% better results. The margin of theoretical difference is significant, albeit applications would need to properly utilize multi-threading to make the best use of the CPU superiority, and the scheduling solution that Huawei implements will greatly affect real-world results as well.

Even the Kirin 950 on the Honor 8 with the CPU profile set to "performance" outperforms the Snapdragon 821, despite the significant generational gap between the two. The Mate 9 widens the gap further by healthily building upon the Kirin 950's lead, but arguably not as much as could be expected out of a full-year improvement.

Moving on to AnTuTu, a benchmark that holistically tests all major SoC keypoints (as well as other components), we find:

antutu-score

 

The Huawei Mate 9 loses out to the Google Pixel XL in 3D performance, but remains marginally ahead across UX and CPU performance. RAM is where the score of the Mate 9 is about double that of the Pixel XL. Due to the deficit in 3D performance, the Pixel XL just about comes out on top of the Mate 9. Keep in mind we aren't fond of AnTuTu and we usually abstain from showcasing its results in our in-depth performance analysis, but we also recognize it's one of the most popular benchmarks out there for quick and easy testing, so we thought these numbers would be relevant to some readers.

BaseMark OS II, another holistic benchmark that tests overall performance in key areas paints a similar picture:

basemark-os-ii-graph

 

In this benchmark, the Mate 9 and the Pixel XL run neck-to-neck in system performance, while we see the same deficit where memory is concerned, with the Mate 9 outputting a score more than double that of the Pixel XL. However, the Pixel XL is superior in graphical performance. Since Basemark OS II weighs each score differently than AnTuTu's simple sum of scores, the Mate 9 comes ahead of the Pixel XL in this benchmark by a healthy margin.

The Adreno 530 in the Pixel XL is still notably faster than the Mali-G71 BiFrost GPU on the Kirin 960, and GFXBench confirms the same story. GFXBench 4.0 focuses mainly on 3D Graphics performance across various tests, so the results from this benchmark help shed some light on the differences in GPU prowess of the devices.

gfxbench-data

 

Next up is PCMark, another holistic benchmark that tests system performance by putting it through simulations of common tasks such as web-browsing and video editing:

pcmark-data

 

Finally, we'll move on to 3DMark, which we feel gives a better perspective of a device's gaming performance by testing the SoC with both high-level graphics and physics tests:

3d-mark-data

Here, too, we see that the Adreno 530 offers superior graphical performance compared to the Mali-G71.

 


Conclusion

While we should keep in mind that these are just a few benchmarks and we haven't put the Kirin 960 through more rigorous tests, we can already begin seeing trends and inferring some results. First, we see that there is indeed a noticeable CPU performance bump: Geekbench 4 scores have gone up by a healthy amount over what we measured with the Kirin 950 on the Honor 8, which itself was already outperforming the Snapdragon 820 (and the Pixel XL's 821) with its Cortex-A72 core setup. The biggest leap forward is in the GPU department, however: while the late-2015 Kirin 950 and its Mali-T880 MP4 offered graphical performance similar to that of the Snapdragon 805's Adreno 420 (a late 2014 GPU), the results from the Mali-G71 are notably closer to what we see in the Mali-T880 MP12 of the Exynos Galaxy Note 7 and the Adreno 530 in the Snapdragon 820 and 821.

Overall, our first run through the standard benchmarks gives us an early but promising look at the Huawei Mate 9's peak performance and what the Kirin 960 is capable of. We'll be testing the chipset and the real-world performance in the coming days to offer better insight into aspects such as performance over time (which is reportedly one of the A73 cores' key improvements) as well as gaming performance (which is an aspect Huawei has allegedly prioritized with the Kirin 960). While the improvements to the Kirin 960 does put it ahead of other 2016 chipsets in many aspects, its lead is not substantial enough for the SoC to hold its ground once the next generation of flagship SoCs arrive. The next wave of processors from Qualcomm and Samsung will most certainly up the ante, but for now and in its own regard, the HiSilicon Kirin 960 found in the Huawei Mate 9 is a more than capable chipset.



from xda-developers http://ift.tt/2esQOiP
via IFTTT

Hidden “Partial Screenshots” Demoed on Android 7.1 Nougat

Screenshots have been around in Android ever since 4.0 Ice Cream Sandwich (and even back to 2.3 Gingerbread if you were on Touchwiz). However, the functionality that was added back in the day has remained stationary despite the evolved needs in the past 5+ years. Stock Android started off with simple screenshots, and stock Android has remained with simple screenshots.

While other OEM skins add in features like scrolling screenshots and more, there is hidden screenshot functionality that can be found on stock Android now: partial screenshots. This is "hidden" in the sense that this functionality was added in the latest Android version, but it still needs a small edit to activate it.

XDA Senior Member MrWasdennoch, known in the forums for his Android N-ify Xposed Module, found out that Android 7.1 Nougat on the AOSP master branch contains a commit named "Partial Screenshot", which seemingly allows users to select a size and grid position on the screen to take a screenshot. This results in a screenshot of that particular selection, rather than the full screen, which will help constricting the information displayed to narrower focus points.

XDA Recognized Developer Maxr1998 managed to enable the functionality by modifying line 53 of TakeScreenshotService to takeScreenshotPartial(). The feature would be available in his upcoming ROM build for the Nexus 4, but he was kind enough to demo the functionality for all of us to see without needing to flash a whole ROM:

As demoed, the screenshot functionality allows you to quickly select a focus area, without needing a gallery app to crop the image for you. While a very small addition by itself, this does show that functionality as basic as a screenshot is still open to evolution.

We hope more such smaller additions, like perhaps scrolling screenshots, are made part of stock Android in the future.



from xda-developers http://ift.tt/2fvb8B3
via IFTTT

Rovo89 Gives Update on Current Status of Xposed for Android Nougat

It's been a few months since Android 7.0 Nougat, and subsequently Android 7.1 Nougat, were released. While we do love the new feature additions that an Android version brings to our beloved devices, it does bring a lot of changes under the hood that changes things up for developers.

Every new Android version usually means that a lot of community based efforts and modifications end up needing an update, and a lot of times, a full overhaul and thorough rethinking.

Xposed is one such modification framework that requires a lot of maintenance to and effort to get it running running on new Android versions. XDA Senior Recognized Developer rovo89 is hard at work bringing the Xposed framework up and running on the newest version(s) of Android. Here is a quick update from him on the current status of the framework on Nougat:

Current status for Nougat: Hooks are generally working now. However, they're still unreliable for inlined methods and when JIT is used (which is often the case). I had given a few technical insights here. I'm currently thinking about the different situations that need to be handled and I create unit tests for them. Then I need to fix those which are failing or even crashing the device – ideally without recompiling the whole ROM like in previous versions. Not sure if the latter is possible though.

The good news starts off on the first sentence, although the "but"s follow it soon after. It is reassuring to know that Xposed still remains a possibility on Android 7.x Nougat and is not ruled out on account of any drastically insurmountable change.

We will still have to wait on the developer to find workarounds to issue, test, retest, polish and package all of it before average forum dwellers can install it on their devices. Let's hope for the best!



from xda-developers http://ift.tt/2fQSwjn
via IFTTT

samedi 5 novembre 2016

Plasma Mobile is a Fully Open-Source Smartphone OS from KDE e.V.

If you've dabbled with Linux distros in the past, then you've likely heard of KDE before. KDE stands for K Desktop Environment and it's one of the main desktop environment options (next to GNOME) that can be used on Linux distros. KDE e.V. is a registered non-profit organization that represents the KDE community when in legal and financial matters. The team behind this organization has just announced a new, open source smartphone OS called Plasma Mobile.

The team describes Plasma Mobile as a way to turn your smartphone into a "fully open hacking device, just like a PC." Those of you who have used KDE in the past might be familiar with the Plasma workspace by the name "KDE Plasma". KDE Plasma is available for desktops, netbooks, media centers for TVs, tablets and now mobile devices. If offers an adaptable user interface and in the future it will also offer a rapidly-maturing software system that is developed with an open life cycle.

The software has built the Plasma workspace into it, and offers KWIN/Wayland and Voicecall/Ofono while also integrating Plasma Apps, Plasma Widgets, Ubuntu Touch Apps and the possibility of installing Sailfish and Nemo Apps. Plasma Mobile's development team will be aiming to run many Qt/GTK/X11-based applications on the OS, and hope to implement package installation via the "apt-get install packagename" command. The platform will utilize libhybris on ARM devices while opting for DRM (Direct Rendering Manager) on Intel devices.

As of right now, Plasma Mobile only supports the Nexus 5 and the OnePlus One, along with some Intel-based devices. If you want to try this out on the Nexus 5, Plasma Mobile can be installed as a secondary ROM on your device thanks to MultiROM support. The team describes the state of MultiROM support for the Nexus 5 as "Solid" (so while it isn't perfect, it's past the 'Experimental' state).

Be sure to check out their forums if you are interested in trying out the software.

Source: Plasma Mobile



from xda-developers http://ift.tt/2fc3Jaq
via IFTTT

[SPONSORED] A look at the RhinoShield CrashGuard for Pixel XL

CrashGuard is superior to the bumpers of the past because it has been engineered to absorb impact. This is done by utilizing a proprietary polymer material that is far more shock-absorbent than plastic, and it also has a protective honeycomb structure within the bumper to disperse impact properly. In fact, within the honeycombs are compartments of pressurized air that act as airbags and deflect impact energy. If that sounds really elaborate, it is, and the net result is that you can drop your phone from a variety of heights (up to 11 feet) and if you have a CrashGuard bumper on the phone, you're going to have a completely unmarked phone.

https-%2f%2fimg-xda-cdn-com%2f_5bazhtzbvuyq2jx6ncb-m-klvk%2fhttp%3a%2f%2fi-imgur-com%2frcyrbkd

Not only are CrashGuard bumpers durable, but they're lightweight (with most of their bumpers coming in under 14 grams). They're also pretty grippy thanks to the matte finish, and they come in a variety of colors. Another thing we really like about the CrashGuard line is the pricing: the Pixel XL is priced at $24.99, and you can grab one from CrashGuard for the Pixel/Pixel XL.

https-%2f%2fimg-xda-cdn-com%2feaoleztmqknwsmi2xiywxi5jb70%2fhttp%3a%2f%2fi-imgur-com%2fohtqfdg

If you have one of the many other phones that are supported by RhinoShield, you can check out their Amazon page to see all of their available options.

Thanks to RhinoShield for sponsoring this post.



from xda-developers http://ift.tt/2fo34FL
via IFTTT

vendredi 4 novembre 2016

What Improved the Most in This Year’s Flagships?

The year is just about coming to an end, and we've seen most of what major OEMs have to offer. The flagship battle was hotly contested this year, with many phones offering many choices to suit many needs — just in the spirit of Android. Smartphones in general got smarter and better, and we are not complaining.

But all areas of a smartphone did not improve to the same degree. Some hardware features in smartphones evolved at a faster rate, and in some cases, minuscule improvements seemed drastic because the preceding flagship lacked oomph in that particular regard. Of course, subjective opinion and diminishing returns also change our perception of what was the biggest improvement in the flagships of 2016. So we ask you,

Which aspects of flagships saw the most improvement compared to the previous year? Which feature on a flagship gave you the most noticeable positive change compared to its predecessor? Was it the processor, the display, the build quality or the battery? Are there any areas where smartphones still need to improve on?

Let us know your thoughts in the comments below!



from xda-developers http://ift.tt/2f23UHH
via IFTTT

PSA: Android 7.1 Circular Icon Support is Determined by the OEM

Design consistency has been one of the major hurdles for Google since Android started becoming massively popular. Initially, Google's philosophy was to let OEMs have full control over their design philosophy. At first, this level of openness enticed OEMs to invest large amounts of resources into making Android smartphones and tablets.

However, the wide variety of OEM skins stood in stark contrast to the tightly controlled Apple iPhone experience. Starting with Android Lollipop, Google made major design changes (the Material Design UX, headed by at-the-time lead Android designer Matias Duarte) and hoped that app developers and OEMs would follow suit. While some OEMs such as Motorola and Sony were content with following Google's lead, others such as Samsung and Huawei still sport a design language that is largely non-Material.

Google hasn't given up on enforcing consistent design across various Android devices, and one of their latest efforts is the inclusion of circular icon support in Android 7.1 Nougat. Circular icons are intended to solve the issue with inconsistent icon size, but this approach has a set of issues that I'll let designer Liam Spradlin over at Android Police describe. Android 7.1 has barely made its way to Nexus devices, and it'll take quite a bit of time for OEMs to start rolling out Nougat, so it's unclear what impact circular icon support will have on design consistency. But what is clear is the fact that circular icons could die before they even have a chance to thrive: because Google has thus far made it totally up to the OEM whether or not they want their users to see circular icons.


circularicon1 Circular Icon Support on the Pixel XL circularicon3

Circular Icon Support is Determined by the Framework

Nearly every single one of the Google Pixel's features was leaked ahead of time by various blogs. Even the circular icon support was heavily hinted at as the leaked Pixel Launcher indicated support for circular icons, and other Google apps were slowly being updated with circular icon assets embedded in the APK. However, at the time the bloggers made an erroneous assumption: that circular icon support would be tied to the launcher. It's hard to blame them, though, as even Google's official announcement of the feature is bereft of any detail.

Fortunately, veteran Android developer Commonsware delved into more detail about how circular icon support would be implemented in Android 7.1 Nougat. Rather than app developer's exposing their round icon via PackageManager (allowing for launchers to decide whether or not to display round icons), the system framework decides whether or not to return either the regular icon or the round icon to the launcher.

When a launcher requests an app icon, the framework returns either android:icon or android:roundIcon, depending on the device build configuration.

What this essentially means is that the OEM can decide whether or not circular icons will be shown on your device. If Samsung, Huawei, LG, or any other OEM decides to forego circular icons, then your device will not see any round icon assets no matter what third-party launcher you install. Strike one for Google's design consistency push.

Commonsware has also discovered that the framework decides whether or not to return a circular or regular icon for ANY process that requests an app icon. In other words, developers need to be cautious that their circular icons look great not only in certain device/launcher configurations, but anywhere it may be requested.

Circular app icons are a nice visual change, but it's clear that there's an issue with their implementation. In all likelihood, we might see that only some devices like the Google Pixel and maybe some Motorola phones will implement circular icon support, while other OEMs will opt to continue using regular icons. If this scenario plays out, then Pixel owners may find themselves with a bunch of non-circular apps from app developers who don't bother to update their icon assets to accommodate only the few devices that would support round icons. And in that case, the entire consistency argument for round icons would be moot.

Thanks to Commonsware for discovering this!



from xda-developers http://ift.tt/2fmCBGD
via IFTTT