Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Android Cellphones Chrome Handhelds Power Security Upgrades

Android M Arrives In Q3: Native Fingerprint Support, Android Pay, 'Doze' Mode 83

Posted by timothy from the sleep-beats-death dept.
MojoKid writes with yet more news from the ongoing Google IO conference: Google I/O kicked off this afternoon and the first topic of discussion was of course Google's next generation mobile operating system. For those that were hoping for a huge UI overhaul or a ton of whiz-bang features, this is not the Android release for you. Instead, Android M is more of a maintenance released focused mainly on squashing bugs and improving stability/performance across the board. Even though Android M is about making Android a more stable platform, there are a few features that have been improved upon or introduced for this release: App Permissions, Chrome Custom Tabs for apps, App Links (instead of asking you which app to choose when clicking a link, Android M's new Intent System can allow apps to verify that they are rightfully in possession of a link), NFC-based Android Pay, standardized fingerprint scanning support, and a new "doze" mode that supposedly offers 2X longer battery life when idle.
This discussion has been archived. No new comments can be posted.

Android M Arrives In Q3: Native Fingerprint Support, Android Pay, 'Doze' Mode More

Android M Arrives In Q3: Native Fingerprint Support, Android Pay, 'Doze' Mode

Comments Filter:

  • Laugh (Score:2)

    by koan ( 80826 )

    "these aren't the droids you're looking for"

  • useless without updates (Score:5, Insightful)

    by Anonymous Coward on Thursday May 28, 2015 @04:08PM (#49793759)

    The most common Android version in the wild is still.. Jelly Bean.

    Android has dropped the ball on OS updates. Apple didn't do it perfect, but they are much better and mostly you can update devices to at least one or two more versions before it beomes obsolete.

    Google needs to up their game around OS updates or it doesn't matter what they put in it, if nobody is running it.

    • Re: (Score:2)

      by afgam28 ( 48611 )

      Among the changes are bug fixes and improved battery life, which are immediately useful to anyone who installs M, regardless of how many others don't.

      • Well, thank you very much, telling me that I'd get better battery life if I installed the new Android version. As far as I can tell (at least with all previous Android versions), Google's instructions for installing the new software are "What? You don't have one of these three Google-brand phones? Then wait for your carrier!".

        That's bad enough for my phone (which has a carrier, and Samsung's a reasonably major brand, though my previous HTC phone never got upgraded), but my tablet's Wifi-only, so there's n

    • I thought from what I read that because there's so much customization by each manufacturer for each model that updates or whole version upgrades (i.e. Ice Cream Sandwich to Jelly Bean or Jelly Bean to Kitkat) have to come from the manufacturer? That you can't just install a generic version from Google and have all features work?

      • Assuming that's true, it shouldn't be. Manufacturers shouldn't do proprietary customizations. Why they even want to do this and incur the expense is beyond me.

        • I'm just repeating what I read, I can't find that specific article but this one provides similar details: http://www.howtogeek.com/12927... [howtogeek.com] so in actuality it is true.

        • Re: (Score:2)

          by tlhIngan ( 30335 )

          Assuming that's true, it shouldn't be. Manufacturers shouldn't do proprietary customizations. Why they even want to do this and incur the expense is beyond me.

          It's called differentiation. Manufacturers want to make their phones unique, distinct and more desirable on the shelves. So if you're deciding between two phones with otherwise identical specs (same processor, RAM, flash), you'd look to their customizations as the differentiating factor. Because there's only so much a manufacturer can do - processor c

    • Re: (Score:1)

      by Anonymous Coward

      I would blame the manufacturers and carriers about as much as Google themselves for this update mess we have ourselves in. The Droid Turbo was supposed to get the latest OS a while back but Verizon and Motorola keep delaying the update.

      • Verizon finally updated my Ellipsis 7 to KitKat after a while - but now, I have lost the ability to save files to my 32GB SD card. I was told that for this device, KitKat only supports up to 16GB. But it took a while to upgrade. They had the same issues qualifying Windows 8.1 for Microsoft, and now, Verizon no longer offers the Lumia Ikon.

        In the above case, doesn't Motorola == Google itself? If Google has certified an OS, why wouldn't it be available on every Google device that meets the hardware requ

    • Re:useless without updates (Score:4, Informative)

      by rasmusbr ( 2186518 ) on Thursday May 28, 2015 @07:19PM (#49794913)

      The most common version is now KitKat with 39.8%. Jelly Bean is second with 39.2% and Lollipop has just under 10%.

      https://developer.android.com/... [android.com]

      Keep in mind that a lot of Android users have low incomes and/or live in countries where an over the air OS update would be a significant cost to the average person. We might think that a smartphone is useless without at least a 1GB per month data plan, but hundreds of millions of users in the developing world think otherwise.

      • Comment removed based on user account deletion

        • True, but if you're not visiting the Play Store you're probably either not using your phone for anything that would benefit from an OS update, or you're using Cyanogen or some other custom build.

          If you look at the distribution of people who actually download your app from Google Play it will be even more skewed towards newer versions of Android, because people download a lot more apps in the days and weeks after they buy a new phone.

          I have an app that currently sees about 20% Lollipop and 45% KitKat in new

    • Re: (Score:2)

      by DrXym ( 126579 )
      I've been developing Android since 1.x and there is a pie chart in the dev console which shows market share. The majority platform always lags behind the cutting edge but it changes over time. New versions of Android start as tiny slices and then grow to be the majority until the next version takes over. It's hardly surprising if a version from a year or so back is dominant. It's always like that.

      I don't see it being a big deal though since the general rule of thumb of developing on Android is you choose

  • but is it Bernard, Judi, or Ralph?

  • Large change with app permissions (Score:5, Insightful)

    by SuperKendall ( 25149 ) on Thursday May 28, 2015 @04:15PM (#49793791)

    They talk about how it's a stability release, but if you are going to compile your application with the newer dev tools you are going to have to do some work adapting to the iOS style permission model.

    I'm really glad to see Android adopted this model, the previous model made no sense from any standpoint - it was worse for the users, and worse for security. Now that Android will ask for permission when you actually want to use some protected resource, they can make a way more informed choice if they should allow it or not - and on the fly decide an app can access some things and not others (say allowing Contacts but not location).

    It's just a shame the older style permission model will be supported for some time to come, as it greatly eases the ability of spyware to operate on Android.

    • Re:Large change with app permissions (Score:5, Informative)

      by robmv ( 855035 ) on Thursday May 28, 2015 @05:08PM (#49794173)

      Older applications not targeting M, will show permissions at install time and be granted by default, but the user will be able to revoke them, the platform will just give empty data or fail. From the preview documentation [android.com]

      Note: On devices running the M Developer Preview, a user can turn off permissions for any app (including legacy apps) from the app's Settings screen. If a user turns off permissions for a legacy app, the system silently disables the appropriate functionality. When the app attempts to perform an operation that requires that permission, the operation will not necessarily cause an exception. Instead, it might return an empty data set, signal an error, or otherwise exhibit unexpected behavior. For example, if you query a calendar without permission, the method returns an empty data set.

      If you are worried that old applications can use the permissions immediately after installation, before you have time to disable the permissions, take into account that applications are installed on a stopped state, there is no programmatic way for it to auto start itself. Start on boot may work but it is not precisely immediately. So I think the best action is to go to those old applications just after install and remove every permission you don't want to grant before starting it.

      • Re:Large change with app permissions (Score:5, Informative)

        by c ( 8461 ) <beauregardcp@gmail.com> on Thursday May 28, 2015 @06:50PM (#49794753)

        Older applications not targeting M, will show permissions at install time and be granted by default, but the user will be able to revoke them, the platform will just give empty data or fail.

        ... and for those concerned about old apps failing under those conditions, Cyanogenmod's privacy guard has been doing this for quite some time and I've never heard of an app failing because of it. So it's possible to do it in a safe fashion. Whether that's how Google has actually implemented it remains to be seen.

  • The preview doesn't say it will run on Nexus 4, hopefully the final version will run because it's powerful hardware, 2GB RAM and Quadcore. Forced obsolescence of good hardware is annoying and hope Google is not bad as other OEMs.

  • wat? (Score:5, Informative)

    by sootman ( 158191 ) on Thursday May 28, 2015 @04:34PM (#49793913) Homepage Journal

    "For those that were hoping for a huge UI overhaul..."

    Yeah, because we haven't had one of those in a whole year. [wikipedia.org]

    • Re: (Score:1)

      by Anonymous Coward

      A year ago? That's practically prehistoric for the "UX designers" of the world.

    • Some people may not want a new UI every year, some are unhappy with which UI was left when the music stopped.

  • App Permissions ring hollow (Score:5, Informative)

    by Voyager529 ( 1363959 ) <voyager529@ya[ ].com ['hoo' in gap]> on Thursday May 28, 2015 @04:44PM (#49793977)

    The App Permissions seem to be missing the crucial ability to deny internet access to an app. There are apps where network data connectivity is the problem. Similarly, I wonder if Google will have this permission setting capability on its internal applications. I know that I have a rather tightly worn tin foil hat when it comes to Google and the information they get, but the Xprivacy 'deny' list on my phone is a mile long, and that's with most of their apps frozen or forcibly pulled out, I find that Google's data access on the platform demands a tight leash, leading the 'privacy' and 'permissions' charge to ring of hypocrisy - "we'll make sure that only we have your location" doesn't mean much to me :/

    • Uh, are you aware that Google owns AdMob, the main mobile ad provider?

      They would probably not want to make it easy for users to block ads by turning on and off internet access on a per app basis.

    • Re: (Score:2)

      by rdnetto ( 955205 )

      The App Permissions seem to be missing the crucial ability to deny internet access to an app. There are apps where network data connectivity is the problem. Similarly, I wonder if Google will have this permission setting capability on its internal applications. I know that I have a rather tightly worn tin foil hat when it comes to Google and the information they get, but the Xprivacy 'deny' list on my phone is a mile long, and that's with most of their apps frozen or forcibly pulled out, I find that Google's data access on the platform demands a tight leash, leading the 'privacy' and 'permissions' charge to ring of hypocrisy - "we'll make sure that only we have your location" doesn't mean much to me :/

      The ability to block internet access would effectively block ads. On the plus side, there are plenty of firewall apps in the Play store (though they do require you to have a rooted device).

  • Can't really complain... want more encryption (Score:5, Interesting)

    by mlts ( 1038732 ) on Thursday May 28, 2015 @04:52PM (#49794045)

    Lots of evolutionary fixes. The privacy stuff is better than nothing... but still all of nothing with legacy apps. The fingerprint standardization is good, because it allows an app that keeps keys to have an easy way to validate that the user is authorized.

    Mobile payment - works with credit cards, as opposed to ACH debits, so thumbs up there. This means there is some way of rolling back fraudulent charges should something happen. With ACH based mechanisms, once the crook sucks the money out, there is little or nothing one can do.

    Of course, there is one thing missing -- a standardized way to encrypt data on SD cards. Yes, /data is protected, but each device maker has their own way of securing SD card data. What is needed is protection similar to Blackberries in the past:

    1: Offer compatibility with vfat and exFAT filesystems, by using loopback encryption (EncFS), as well as adding UNIX permissions via UMSDOSFS to keep apps separated. UMSDOSFS hasn't been used in ages... but is ideal for enforcing basic UNIX permissions while allowing for MS-DOS based filesystems to be used underneath.

    2: Encrypt the entire SD card's partitions entirely similar to how /data is encrypted. This is the ideal choice, but it keeps the card from being able to be popped out and used with other devices.

  • I've clearly been on Slashdot for far too long. I read 'Doze Mode in the title and thought, 'Goddammit, if you're going to talk about Windows Mode, just fucking call it "Windows"!'

    And then I realised that it actually is 'Doze Mode'. Because 'Naptime' was taken, I guess.

    • Which is quite a coincidence, because my new Windows phone is actually quite good at not draining the battery when I'm not doing anything. The other day I was still at 95% battery by the end of the day because I was too busy to use my phone. My old Android phone on the other hand would easily go through 25-50% of it's battery in a day, even if I didn't use it for much. Most of the time I would plug it in at the office because if I didn't, it would be below 20% by the end of the day.

  • Are they finally going to implement a global "Undo" function?
  • I'm also sure many Google apps could reside happily on the SD card instead of taking up space on the built-in memory.

  • Lollipop is to Android what Windows Vista was to Windows: Nice looking, but slow and buggy. It lags a lot, sometimes to the point of entirely freezing up. If they speed it up and clean it up, I'll be very happy.

  • I can't wait to get...
    oh, yeah... Verizon.

    • We'll be lucky to see the first device running Android "M" on Verizon by Q2 next year.

      Nexus 6 launched on November 3, 2014 as the first Lollipop device. Seven months later in May 2015, my Note 4 is updated to 5.0.1.

Slashdot Top Deals

Love may laugh at locksmiths, but he has a profound respect for money bags. -- Sidney Paternoster, "The Folly of the Wise"

Close