Slashdot Mirror


Google Begins Rolling Out Android 7.0 Nougat (venturebeat.com)

An anonymous reader writes: Google today started rolling out Android 7.0 Nougat to existing Nexus devices via an over-the-air software update. This is a gradual rollout: The Nexus 6, Nexus 5X, Nexus 6P, Nexus 9, Nexus Player, Pixel C, and General Mobile 4G (Android One) will all be updated, but " it may take several weeks" before everyone gets the latest and greatest, a Google spokesperson told VentureBeat.The Nexus 5 (2013), which packs in a Snapdragon 800 SoC coupled with 2GB of RAM and 5-inch full-HD display, won't be receiving Android Nougat update -- despite having all the hardware capabilities required for a phone to receive Google's latest OS update. The truth of the matter is if Google wanted to update the Nexus 5 with the latest Android software, it could have. It just chose not to. It's very likely that same will be the case for the Nexus 6, a phone that has 3GB of RAM, and Snapdragon 805 SoC, next year when the company releases Android O update.

9 of 164 comments (clear)

  1. Re:No problem by LichtSpektren · · Score: 2, Informative

    Older Android versions still get security releases.

  2. Re:Google's management quality is degrading rapidl by LichtSpektren · · Score: 3, Informative

    That line seemed to be the submitter's personal opinion and not backed up by anything in the linked article.

    We don't know why Google didn't push an update for the Nexus 5.

  3. Re:Damn you Google by LichtSpektren · · Score: 4, Informative

    Who says the Nexus 5 isn't getting updates anymore? It's not getting Android 7, but Google updates older OS releases, just like Apple still gives security updates for macOS 10.9.

  4. Re:No problem by LichtSpektren · · Score: 3, Informative

    Android 4.4 and 5.1 got security updates a month ago: https://android.googlesource.c...

    Granted, OEMs and carriers are probably blocking those from getting to 99% of peoples' phones, but that's not Google's fault.

  5. Re:No problem by LichtSpektren · · Score: 4, Informative

    Sorry, you're going to need to back up "99% of people are now running pwned phones" with some facts (which are to be distinguished from the refuse coming from your ass).

    Google patches their OS. OEMs and carriers don't send them downstream, and there's nothing Google can do about it because Android is FOSS and you can do whatever you like with it. The fact that iOS is restricted and closed gives the illusion that iPhones have better security, but if anybody could sell iOS devices beside Apple, their ecosystem would look just as bad.

  6. Re:No problem by LichtSpektren · · Score: 3, Informative

    Compare this to desktop machines though. Microsoft of Ubuntu or whoever makes your OS can issue updates. As soon as those updates are made available, you can update your desktop computer. You don't have to wait for HP, Dell, or anybody else to allow you to make that update to your desktop computer. Why can't phones work the same way? When Google updates Android, I should be able to apply that update, and the manufacturer of the device should have no control over whether or not that update is applied.

    Well, if you bought a phone with an unlockable bootloader, you can flash whatever OS you want on it. As I wrote elsewhere, even the original Galaxy Nexus from 2011 can get the Cyanogenmod equivalent of Android Marshmallow this way.

    But the main "problem" (if you want to consider it so) with Android is that it's a FOSS platform. Apple and Microsoft heavily strangle their respective closed platforms so that OEMs and carriers can't do anything to interfere with Apple's and Microsoft's business (aside from, in the case of Windows, pre-installing bloatware). But since anybody can legally install Android on anything, Google can't use the same kind of leverage. Well, that's a good thing, I say. It means I'm not on Google's leash.

  7. My question is: by nightfire-unique · · Score: 3, Informative

    Have they fixed the rather major defect they introduced by forcing an unconfigurable doze on us all?

    Any application which requires the device to remain active (ie. safety applications like marine anchor and AIS alarms) are not functional on Android 6.0+. Even if you add applications to the exception list, they'll still be suspended, and woken only every 15 minutes while dozing.

    A simple "do not EVER interfere with this process under any circumstances" option would resolve it, and to be honest it's quite shocking it was ommitted.

    --
    A government is a body of people notably ungoverned - AC
  8. Re:Do we nned it? by gTsiros · · Score: 3, Informative

    yeah, that's what it says on my device, too. 21%

    however, the total doesn't reach 100%. More like 40%

    the simplest conclusion from that is that the indicated percentage is untrustworthy

    --
    Looking for people to chat about multicopters, coding, music. skype: gtsiros
  9. Re:Users mostly part of the "used phone" market? by perpenso · · Score: 4, Informative

    Why are you defending google so much? Do you have google stock or some shit? Google is a corporation. Their decisions are based on money nowdays. The original guys are long gone.

    I'm defending Google because right now Nexus devices are the only phones that reasonably respect their users' right to unlock the bootloader. I dread living in a world dominated by Samsung, Apple, and Microsoft.

    Your secure boot theory sort of undermines your user rights argument. So in your scenario of why the limitation might be justified you can add Google to that domination list. :-)

    I have no idea what you're talking about. Android 7 has a new secure booting mechanism, but it's not the same as Intel's SecureBoot that (theoretically) locks the bootloader. You can still unlock the bootloader on Nexus phones. Indeed, Google even advertises that as a benefit.

    Then you need to edit your list as Microsoft allows the unlocking of the boot loader as well. Also while Samsung will void your warranty they don't really prevent you from changing the boot loader so they don't really belong on the list either. Only Apple aggressively locks down the boot process and works to prevent user modification.