Since receiving my A700 ten days ago, I have been eagerly awaiting the update to Jelly Bean. My main concern was lowering the heat generated by the tablet on the back lower left,
but I also was looking forward to all the other improvements JB brings.
I've been manually checking for the firmware update dozens (if not hundreds!) of times a day and the tab has always reported that it was "Up to date".
The tab came with (what I have been told is) a really old version of ICS installed (1.017), so the system was obviously NOT up to date.
Decided to check one more time this morning before attempting to force the available update(s) to my A700.
To my surprise there was an update available!
Actually there were 3 updates in total:
1) This update was just under 340MB and updated my A700 to version 1.029.
2) This second update was 35MB - I forgot to write down the firmware version for this one - DOH!
3) Third and final update was ~ 240MB and brought my tablet firmware 1.034 and Android version 4.1.1 - Woo-Hoo!!!
Now to see if the back still gets uncomfortably hot...
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
When will the international S7 receive the July update over the air? And any news about what this new update contains? (aside from the google security patches), any improvements to software?
thanks
I have the UK version of the G930F and I just got the 1-July-2016 update OTA today (12th July).
asifanwaruk said:
I have the UK version of the G930F and I just got the 1-July-2016 update OTA today (12th July).
Click to expand...
Click to collapse
Any improvements or anything new ?!
Well I only switched to the S7 from an iPhone6 a few days ago so I probably wouldnt notice anything new yet, but I doubt there is as it is really a security patch AFAIK. I had felt some 'stickiness' in Candy Crush earlier, which now seems better but maybe that was due to a phone reboot anyway? Either way, doesn't seem a huge end user change.
My phone model is SMG970W. I got the OTA update for the June security patch around the end of June. Because I wasn't on WiFi at the time, I swiped away the update to get back to it at a later time. But when I searched for an update later, it kept saying I was already on the latest update. And it has been like this since. July's almost ending, I'm still on the May Security patch, no update in sight. Did everyone else get their updates?
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
T-Mobile I'd imagine. Just use Pixel Flasher or https://flash.android.com
I joined the beta program
BladeRunner said:
I joined the beta program
Click to expand...
Click to collapse
How is it? Stable enough to daily drive? I was stuck on the Nov. 22 patch as well until I sideloaded via ADB last night.
Nov 1 is the latest Play System Update afaik, at least thats what the QPR shows....
Google is having problems
This is one of those moments where it's not you it's them is actually true and not gaslighting . Play Updates are not rolling out properly
BladeRunner said:
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
Click to expand...
Click to collapse
Seems you are not alone.
T-Mobile is running way behind on Google Pixel security updates
Timely updates are supposed to be a prime Pixel perk
www.androidpolice.com
Yeah I am on December update very annoyed with Google nothing has changed
Deleted
That sucks and should not be the Pixel experience. I would call T-Mobile and ask them why you are on an old update?
I have had decent updates so far but would be rather upset if I had a security update that was older than other OEM as that is part of the reason for getting a Pixel.
Sign up for Beta and you'll get QPR2 Beta 2. In my experience, it is much more fluid and responsive than previous builds. It fixes the scrolling issues and seems to have improved battery compared to the December update.
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Colchiro said:
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Click to expand...
Click to collapse
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
EtherealRemnant said:
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
Click to expand...
Click to collapse
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Colchiro said:
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Click to expand...
Click to collapse
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Also mine show November as last play service update (I'm on the beta). Italian unlocked phone
Nov is the latest still for play system. There wasn't a Dec and Jan hasn't rolled out yet
EtherealRemnant said:
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Click to expand...
Click to collapse
There's also the indeterminate minutes, if/when something goes sideways...
This is being delayed for un-branded devices as well, such as mine purchased G-Store direct, based on some sort of carrier-block. I'm tempted to go dig through some dev-docs, to see if I can find this (could be an section not published for most, I suppose), but I figure to what end, mostly.
As you mention, easy side-load, but without knowing why this is being blocked for non-TMo (branded, so not gated by their release of their OTA) devices, it's a gamble of sorts...
I just posted in another thread that I think this is an odd situation. I use an MVNO Boost Mobile that uses T-Mobile and I got the update on the 5th. Maybe I got it before they pulled it? Why would they hold the update back to T-Mobile customers but not the MVNO?