Why is it so incredibly fast the Nexus 6 with Android 5.1? – Hypertext

Why is it so incredibly fast the Nexus 6 with Android 5.1? – Hypertext

Wear it according to Francisco Franco since I had the Galaxy Nexus (what a horrible screen had) as it was and is one of the best developers of kernel panorama, gained fame in the XDA forums, where users “cook” their own ROMs and kernels for mobile devices.

Android 5.0 Lollipop has not been the best version of Android as I’ve read in various online communities, but was first. Android 5.1 is raging unlike the draft, especially for its performance . Those with Android 5.1 Nexus 6 are praising the performance of your terminal after upgrade but in reality, it is not only the new version of the operating system and improvements in ART. It is the kernel

A word of Francisco Franco learned from his profile on Google +:.

Android 5.1, plus all the improvements in ART and the possibility that they have been cleaned and improved throughout the framework code has a very important change in the Nexus 6: now has four cores running forever, which helps tremendously to task scheduler to distribute the workload across all cores processor, giving the user the perception of not having a device waits, or slow to respond

This is very important and is something that my impression is unknown. A processor, albeit of 4, 8 or 32 cores not always use all at once , depends on how you manage the kernel and operating system. So there are two processors infinitely better than 8-core (which in truth are two of four cores) cores. But of course, you’ll probably wonder if that extra performance dramatically affect the battery, continue

Google has disabled routines boost migration to another thread -. If you do not know what is one driver developed by Qualcomm. Inc, which to receive notification of task scheduler when a thread migrates from one processor core to another, minimizing the lag that the user can perceive increasing the frequency of the target nucleus at the same or faster than the core which originally workload developed.

1. Passing the execution thread core (CPU0) to the core (CPU2). (Eg)
2. The driver is notified of what happened.
3. This driver read the actual frequency that works (cpu0).
4. If the current frequency (cpu2) is less than the frequency (cpu0) at that moment, increases the frequency of (cpu2) at that frequency. If the frequency is lower than the frequency threshold (1.7Ghz), increases the rate at that frequency.

These migrations of yarn to different cores dozens of times per second occur. One of the changes I made in my kernel, Franco Kernel, was disable this driver to conserve battery because the chip Nexus 6 I do not think it’s necessary. I’m sure Google has made consumption calculations and determined that the benefits of driver do not offset the losses in autonomy, so they have decided to disable it and I applaud them for it.

• The appointments have been retouched slightly to make them more didactic without altering its message.

As we see, both changes improve performance and do not increase battery consumption, since should be balanced profit and loss of each . Moreover, users are reporting a better autonomy and a great improvement in performance.

As if that were not enough, the changes are not unique Nexus 6 and all processors high-end Qualcomm should get these improvements in the relevant updates. In addition, several users report that has fixed the serious failure “memory leak” affecting Android 5.0 although not confirmed because it only takes a few hours in distributing this new build of Android.