Diving into Android M: Memory manager and revoking/adding permissions

Last week we brought you quick looks at a number of new changes that are heading to Android M. We’re at the point where most of the big changes have since been discussed thoroughly, but today let’s take a look at two fairly interesting changes that we’ve yet to talk much about.

Want to dive even deeper? Check out our full “Diving into M” series by clicking here.

First up, the new Memory manager. With Android Lollipop you can going into the “Running” section of the Apps menu to see how much RAM each app, and the system itself, is using. This was already a pretty great option for power users, but with Android M you can now get an even deeper look at your device’s RAM utilization.

The Memory section in M tells you how good of a job your device is doing when it comes to RAM usage, how much each app is using on average, and the maximum that each app has used recently. Bottom-line, it makes easy to see which apps historically are the worst offenders when it comes to memory consumption. Tapping on any of the apps in the list will give you even more info, such as currently running processes and what processes were running recently. You can even force stop a process if you so choose.

To open the Memory manager, you’ll want to go to the Apps menu, hit the hamburger menu, choose Advanced, and from there select Memory.

The other area we want to focus on is permissions. A big part of the Android M announcement surrounded permissions, and how apps designed for Android M will give users deeper control over what permissions apps have access to. Right now much of this isn’t up and running, as this is still a developer preview and no apps have been optimized for the new permissions system. In the final build of Android M, apps optimized for the new permission system will actually ask you to authorize individual permissions as you run into them (like first time using the camera in an app), instead of requiring you to grant all permissions in bulk when you first install them.

Beyond that, you’ll also be able to go in and grant/deny app permissions for apps even after you’ve already authorized or denied them in the past. So let’s take a look at how that will work.

Going into Settings > Apps, you’ll have two ways to mess with permissions here. First, you can click on any app individually. A new window will open up, and you’ll then click on the Permissions option. From here you’ll see any permissions an app currently has access to — or is denied. Turning them off/on is as easy as hitting the slider.

That’s not the only way to do this, though. From the Apps menu, you can also click on the hamburger menu and go to Advanced. This is the same screen you’ll access the Memory manager, but this time we will click on App permissions. This will bring up a list of permission groups (Calendar, Camera, Phone, etc).

Clicking on any of these permissions will bring a new list showcasing what apps have access to this permission. You can turn them off/on from here. Keep in mind that revoking permissions in Android M Developer Preview doesn’t actually seem to be working, but this is a preview and so we aren’t surprised.

What do you think of the new Memory Manager? The Permissions system? Let us know in the comments.

Three backtracks on mid-contract price hikes

With all-you-can-eat data tariffs, 4G connectivity as standard and free roaming in popular travel destinations, Three’s often applauded for being a carrier of the people. Whenever a new service is announced or a new country added to the free roaming roster, you can bet Three’s going to make sure everyone knows about it. One thing you can also count on, however, is the network provider keeping mum when something might damage its pro-consumer reputation. Case in point: Three’s stance on mid-contract price increases.

Last year, Ofcom introduced new rules to stop carriers increasing the price of mobile contracts during the agreed term. Anyone stung by rising costs could exit their contract without penalty: a decree that effectively killed mid-term price hikes. One slight loophole to the new regulation was that providers could up the cost of contracts in line with inflation, as long as all relevant paperwork mentioned this explicitly. EE and O2 took advantage of this by adding the appropriate clauses to their contracts, but at the time, Vodafone and Three committed to completely static pricing models.

A few days ago, however, Three quietly changed its terms and conditions to include the inflation clause — any contract signed on or after May 29th 2015 will be subject to a small yearly price increase in line with inflation, with the first bump occurring this time next year. It’s not like this makes Three any different from O2 or EE, of course, but it does make us question the provider’s definition of “commitment.” Meanwhile, Vodafone’s sticking to its guns, at least for now. A couple of months ago, the carrier took to its blog to yet again reaffirm its promise to keep contract pricing completely fixed, thereby “keeping with the spirit of the regulations.”

Filed under: Wireless, Mobile

Comments

Via: ISPreview