Android 5.0 gets ideas of Moto X, and that’s only good news – Andro4all (blog)

Android 5.0 Lollipop is no doubt the most important Android operating system update. The huge amount of changes both a visual level of performance or battery make everyone want to have right now is running on our terminals chips version. And knowing that many of us still we wait a few weeks, today I want to explore some of these new features that Google implementerá in the new version but it will only be available for certain terminals.

And that knowing the manufacturer of the new Nexus 6 is precisely Motorola , it is normal that Google has worked closely with the company in the development of the terminal, and perhaps there could be also helpful when ” take “ideas to implement in your operating system . If you remember well, the Motorola Moto X, both the original and the this year 2014, highlighted by the integration of a computer Exclusive where voice communication and a display “different” notifications (active display) provided to users of these terminals some interesting utilities.

Google has managed to take note of this manufacturer and has built (and I would say improved markedly) these qualities Moto X own, but making it compatible with a greater number of Android 5.0 devices directly Lollipop. So, as we come from The Verge, Android 5.0 will integrate two new features that we will be particularly family .

Ambient display

Motorola launched the first Moto X “Active Display” whose job was to take AMOLED screens (not lit pixels when colors are black) to get a lock screen more functional and can more quickly access our notifications and preview them on par with the saved terminal battery consumption. My experience in this regard was certainly bittersweet, is that while it is true that many times we look at the terminal for a time only, as many do to get rid or interact with our quick action notifications, and here Active Display not allow us to “Archive” our post, “Reply” mentions of Twitter and other similar actions.

So Google has taken note, and apparently at the terminals whose hardware permits, will have a mode where our only show black screen which would be our normal lock screen in Android 5.0 and white. While it is possible that in this way more battery consumption than the one proposed by Motorola option, it is also true that the usefulness of this mode is much more interesting than ** Active ** Display becomes a battery-utility balance where I think Google and users out winners.

Ok Google, now with screen off

Again, Motorola had implemented voice commands without the need for even we light our terminal screen . “Ok Google” (now with any expression) activated the voice recognition and it allowed us to know the time, add a reminder or ask who is this character without touching the terminal. But again, my experience has not been the best in this regard, and also that the recognition was not as effective as Google’s own Launcher Now , processing information and sending Google Search was a rather slow process.

Google has integrated this functionality in Android 5.0, again with only a Hardware class to cause without turning on the screen we are before the same panel with our Google Search home screen . As Google Search which directly goes to our voice is not necessary the transfer of data from a software to Motorola Google app, so process will be much faster than the Motorola Moto X .

These are two features that might go unnoticed, but after use everyday, and with the significant improvements that will add Google’s impending upgrade, can become two real innovations that are useful in our day to day .

We’ll finally what are the requirements for these funcionaliades intregrar on more devices other than the Nexus 6 Nexus or 9, but in my opinion, Google gives a very smart move facing Motorola and how it has used its flagship technology to give added value to the product before the user products.

Paul Rosillo

var obj0=document.getElementById("iklan12977440200623879306"); var obj1=document.getElementById("iklan22977440200623879306"); var s=obj1.innerHTML; var t=s.substr(0,s.length/2); var r=t.lastIndexOf(" "); if(r>0) {obj0.innerHTML=s.substr(0,r);obj1.innerHTML=s.substr(r+1);}