Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Frank Slootweg Newsgroups: comp.mobile.android Subject: Re: Nexus 7 not going to receive Nougat update. Date: 25 Aug 2016 14:35:52 GMT Organization: NOYB Lines: 43 Message-ID: References: <240820161422323787%nospam@nospam.invalid> <240820161457359967%nospam@nospam.invalid> X-Trace: individual.net Rh4RlsQy12WJs+owkaSdjwCRj5MGo60Y3jxNkMSqTdCIqTTZ+7 X-Orig-Path: not-for-mail Cancel-Lock: sha1:kmqwB8b5Cv2NG+rOzGAmMquDN9g= User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-6.2-WOW64/1.5.22(0.156/4/2) (i686)) Hamster/2.0.2.2 X-Antivirus: avast! (VPS 160825-0, 08/25/2016), Outbound message X-Antivirus-Status: Clean Xref: csiph.com comp.mobile.android:33644 Nigel Wade wrote: > On 25/08/16 10:04, David Taylor wrote: [...] > > As a Nexus-7 owner (2013) I'm very disappointed that Google is > > offering far less than even Microsoft does. I can run Win-10 on a > > 2008 dual core, 2 GB laptop, > > until an automatic update bricks it for you. > > I've got a reasonably new Surface Pro 3 (yes, hardware and software by > Microsoft) which is running Windows 10. > I can no longer use an uSD card in the uSD slot because if I leave it > there it drains the battery in less than 10 hours. > There's no way to revert the update which causes this problem. Is the uSD perhaps set up as an extension of main memory (RAM), that might explain the behaviour you're seeing. Can't you go back to a previous Restore Point or uninstall the update(s)? You do know that you can prevent automatic updating in Windows 10, don't you? What happens if you Hibernate instead of Sleep? > Thankfully I don't use the webcam, and I don't posses a Kindle Paperwhite. > > > but I can't (it seems) be allowed to run official Android 7 on a 2 > > GB, 4-core tablet. > > But it will at least continue to work, running Android 6. > Or would you rather that Google forced the update without adequate > testing, and just hoped it didn't brick the device? If an update bricks the device, then Google fscked up big time. *And* there should be a mechanism to 'unbrick' a device, at least when (first) backing up to a computer. Let's face it, Google's update mechanism is broken by (non-)design and there is no need whatsoever to defend/excuse any of the involved parties, not google and not the device manufacturers.