A Look At The Changes In The Android M Previewby Brandon Chester on May 29, 2015 8:00 AM EST
- Posted in
- Google IO
- Android M
Today during Google I/O 2015's opening keynote Google announced the latest release of their Android operating system. The new version of Android is using the code name Android M, much like how Lollipop was initially referred to as Android L. While Android Lollipop was a major release with many new features and a comprehensive redesign, Android M goes back to basics, and focuses on polishing what Google introduced with Lollipop. That isn't to say that there are no new features or design tweaks, but they are not on the same scale as Lollipop's changes. It may be best to think of Android M being to Lollipop what Jellybean was to Ice Cream Sandwich.
When Google originally announced Android L at Google I/O last year, they released a developer preview so developers could prepare their apps for the new operating system, as well as for both developers and Android enthusiasts to provide feedback about the changes that were being made. Google has done the same thing with Android M, and they have committed to releasing over-the-air updates to the developer preview on a monthly basis.
While I'm hopeful that the final name of this next Android release will be Android Muffin, we won't know details about the name of the new OS for quite some time. Opening the Android M Easter egg in the About phone section of Settings shows you the new Android M logo which you can see in the cover image of this article. Long pressing on that logo kicks you out of that section and presents you with the increasingly common Tsu (ツ) emoji. Google clearly enjoys the speculation from users and the press about what the final name will be.
While we don't know the full name of Android M, we can look at some of the changes that are included in the developer preview build that Google has released. All of these features are obviously subject to change, and some will most certainly change as users and developers give feedback on them in the coming months. I'm just taking a look at what changes have been made so far to see where Google is headed, and to cover some of the changes that were too small to be mentioned during Google's keynote.
Android Lollipop on the left, Android M on the right
The first thing you're likely to notice after installing the Android M preview is that Google has included a new wallpaper which is set as the default option. They've also made some notable tweaks to the lock screen. The most obvious is the change to the clock and date. Not only is the text more bold, but the altered spacing between characters may mean that we're looking at a font other than Roboto, or at some special version of Roboto. I've never been very good with identifying fonts so I couldn't say for sure, but I personally prefer the thinner look of the original clock.
On top of the new font, Google has also replaced the phone dialer shortcut with a voice search shortcut. I would love to know if this is the result of data showing that people rarely used the phone shortcut. The phone part of a smartphone now seems more like an additional app on what is really a computer in your pocket.
Android Lollipop on the left, Android M on the right
Not much is tweaked with the home screens of the Google Now Launcher in Android M. You still get the same grid of icons, with the leftmost home screen being Google Now. Once you enter the app drawer you'll see that Google has made some significant changes after all. The big change is a switch from having pages of apps that you scroll horizontally between to having a continuously scrolling vertical list of apps. From a functional standpoint, this layout is similar to how the app drawer was designed in older versions of Android from Gingerbread and prior.
There are also some changes at the top and on the side of the new app drawer. Based on some quick testing, I believe that the row of four icons on the very top are your four most commonly used applications. Above those is a search bar for those users who have so many applications that scrolling to them becomes a chore. Since the drawer is organized alphabetically, Google has made finding apps easier by putting letters on the left side which indicate the first letter of the app names that you're currently viewing.
Something I've desired for a long time is a revamp of the permissions system on Android. Quite frankly, I feel like the system prior to Android M was a complete and utter disaster. The reason is that if there was a single permission that you didn't want an app to have, then you were barred from installing that application. Permissions were also grouped poorly, and sometimes apps would have to ask for permissions that made them seem malicious but for some obscure reason were required for part of that app to function. In Android M, Google has resolved both of my concerns by changing the system to ask permission at the time a function of the phone needs to be used rather than at the time of install.
Since the permissions system is a key part of Android, it wasn't possible for Google to bring their new system to older applications. Because of this, the screen above with a list of permissions that you need to accept at the time of install won't be going away any time soon. However, Google has been able to implement part of their new permissions system, and if you take the time to use it you can control which permissions an application has access to. This can be done by going to the Apps menu in Settings, selecting the app, and then selecting permissions. This brings up the list you see in the right image above, and you can enable to disable permissions at will. I think this is a huge win for users and their privacy, and it will be even better when developers update their applications so that users can just accept or deny permissions as they are needed.
Copy and Paste
One of the smaller improvements that Google noted during the keynote was a new system for copy and paste. Rather than having a group of unlabeled options appear at the top of the phone, a floating menu would appear over the text that was selected with the available options. It's basically the same way iOS and Windows Phone handle copy and paste, and it's not surprising to see all the operating systems converge on this way of doing it as it really does seem like the best way to handle it.
Unfortunately, as of right now it doesn't seem to work properly in every application. Above you can see Docs, Gmail, and Chrome, and each of them present a different menu for copy and paste. Docs supports the new floating menu, Gmail now uses text instead of unlabeled icons but still has it at the top, and Chrome is unchanged in its behavior. The new feature where words would be selected in chunks surprisingly only worked in Gmail which doesn't even support the new menu properly.
Thankfully, the feature worked perfectly in third party apps like Skype and Twitter just fine. I was concerned when Google's own applications weren't cooperating with the new feature, but it appears that they are the exception rather than the rule.
Android Lollipop Volume Menu
Another smaller change in Android M that Google made note of is a change in the behavior of volume controls. Google was clearly aware of the user confusion caused by the new system they introduced in Android Lollipop for handling when the phone was muted, as they made a point of asking how many members in the Google I/O audience didn't like the changes. The problem was fairly simple. In older versions of Android, hitting your volume down button at the lowest volume level would enable a vibration only mode, and hitting it once more would enable silent mode. Android Lollipop made some strange changes that made it seem like silent mode was removed, and instead added three options which defined what notifications would be allow to trigger a vibration. While this was actually a nice feature for allowing only certain contacts to trigger notifications, it was implemented in a clumsy manner that confused users.
In Android M, the volume options have been greatly simplified. When hitting volume down while vibration only mode is enabled, all sounds and vibrations are completely disabled, with the exception of alarms. This still poses a problem for users who want to have their phone be completely silent no matter what the circumstance is. For that, users will need to take a look at the new Do Not Disturb toggle in the Quick Toggles section of the Notification Drawer.
To me, the new system in M is better, but it's still not perfect. I don't understand why Google feels like Do Not Disturb needs to take the place of silent mode by allowing you to block all sounds, with the volume mode accessible via the volume buttons limited to still allowing alarms to be triggered. iOS has had a Do Not Disturb feature for years now, and it coexists perfectly with the ability to have a silent mode that blocks all alerts or vibrations.
The Developer options section of the Settings app also has a couple interesting new feature additions. The first is a Theme option which allows you to select a Light or Dark theme, much like the ones that you can select for the keyboard. At present it only changes the appearance of the Settings app, and it's unclear if this will ever be extended to other applications or parts of the operating system.
The second interesting new feature in the SystemUI Tuner. The design of the menu makes it clear that Google plans to add more options here in the future, but right now it allows you to tweak the toggles that are available in the Quick Toggles part of the Notification Drawer. After removing the rotation lock toggle, the SystemUI Tuner began to crash upon opening for me, so I would recommend not altering any toggles that you use frequently.
The last change that I've noticed during my time using the Android M preview is this new menu for choosing what you want your USB connection to do. Google showed this off during their keynote, but with a different purpose. At the moment, it allows you to choose whether you want to just charge your device, or whether you want to connect via MTP or PTP to transfer files. This is probably to defend against attack vectors like hacked USB chargers, but the menu will also be very useful when USB Type C becomes common among devices as it will allow you to negotiate which device is going to charge the other. This means you could potentially recharge your phone from your tablet's larger battery.
These impressions all relate to the user-facing changes in Android M. Because this is a release that focuses on polish and bug fixes, there are a lot of changes under the hood that are hard to easily examine and evaluate, and some of the most amazing ones such as the new Now on Tap feature are yet to be implemented. However, what I've seen so far is very promising. As both Android and iOS are reaching a point of maturity after their respective redesigns and feature additions, I openly welcome a focus on polish and under the hood changes that will improve the user experience in ways that the user will not directly see. That's clearly the philosophy Google has adopted with Android M, and it will be very interesting to see how it evolves in the next few months as Google releases more developer previews to show us where they're headed.
Post Your CommentPlease log in or sign up to comment.
View All Comments
Murphs_Law - Tuesday, June 16, 2015 - linkExcept that security has been blown up to such a huge deal when its not really a big deal... When was the last time you actually had been affected by by mobile security issues? I'll be honest in my experience.. NEVER.
"Security" seems like such a buzzword these days when it was never something that impacted the majority of users. Sure if you are a high level target who may be targeted by malicious software or viruses then its a concern, but thats not the case with the majority of users.
Gadgety - Sunday, May 31, 2015 - link@Chillin1248 My kid's got the Nexus 4. It's running the latest version of Lollipop, and the updates have been totally timely. We haven't encountered any instability. This of course is vanilla Android.
kpxgq - Sunday, May 31, 2015 - linkyoure obviously doing something wrong then... the nexus4 (as with with all nexus phones) has vanilla android from the factory you shouldnt have to mess with Roms... if you jailbreak iOS and start adding features it will have the same issues. The G2 already has one of the highest rated battery life of all phones (higher than most of the iphone models) so once again i think you messing with the roms and installing rogue apps is the issue (which once again can happen with iphone if you jailbreak and install rogue apps)
i use an android phone (LG G3) and an ipad mini3 and i have no issues with both... i dont mess with roms, xposed, and i dont jailbreak so thats probably where you issues are
you cant cherry pick instances where you caused your phone to be more unstable and then blame android for it... its like add nitrous an aftermaket parts to you car and saying that the car is unstable and has bad gas mileage and blaming the car manufacturer.
patrioteagle07 - Friday, June 5, 2015 - linkYou should probably read this... http://www.nextpowerup.com/news/17955/my-first-tim...
Aka, iphones are even more buggy and crash prone, they just cost more and are more liable to break.
Shizuma - Friday, May 29, 2015 - linkIt is Google's problem though because they allow it to happen, really Google needs to take stricter control over Android like Apple does. Now I don't mean insanely locking down Android like iOS is, simply that they need to require all manufacturers to use the vanilla Android ROM and the need to add a robust built in skinning support, so then the manufacturer customizations are separated from the OS itself and Android updates can be pushed out to all phones in a timely manner and manufacturers can update their skins as required. Also Google or the Manufactures need to outright ban carrier customization like Apple does as the carriers being in the process of updates makes it way worse.
johnnycanadian - Friday, May 29, 2015 - linkPrecisely -- this level of abstraction was already common in systems development 20+ years ago.
Apropos of nothing, it's nice to see that after Apple cribbed from Android for iOS 7 and 8 that Google is cribbing from Apple again (Google Pay and permissions). Turnabout is fair play!
mrochester - Friday, May 29, 2015 - linkThis. I don't know why people say it's not Google's fault when it was Google's choice to make Android open source and therefore let Android turn into the mess that it is in. If Google had simply kept Android closed source and properly controlled the platform, it would be so much better.
tuxRoller - Sunday, May 31, 2015 - linkIt has nothing to do with the evils of open source (it's probably the preferred way for "younger" devs to work and even microsoft is jumping onto the open source train) and everything to do with the specifics of licensing. As others have said, they could have easily attached more requirements to use of the code as they have done with use of gapps.
Murphs_Law - Tuesday, June 16, 2015 - linkThen it would be no different than Apple. There would be no high level customization short of "jailbreaking". Many manufactures would not agree to produce hardware to have the software match the competition. You can't simply say if Google kept Android closed things would be better... you wouldnt have the rich world of android we have today.
phoenix_rizzen - Friday, May 29, 2015 - linkSony and Motorola started doing things along these lines. They use an almost stock Android install, and push all their customisations into apps that can be installed (and upgraded) separately via the Play Store. They also push a lot of their changes back into the Android repos, and are very developer-friendly when it comes to the custom ROM scene.
It's just too bad their marketing departments are so lean. They have some great hardware that no one has heard of or is able to use outside of certain countries.