First thing this morning, my phone insisted on a password instead of fingerprint for "first attempt after restart". But the Status page shows that the phone has been running for more than 600 hours, and I'm still on API2, Sept. 1 security update. But the Update page has a greyed-out "Continue update". When I click on Software Update, it says up-to-date and tells me as usual that I have to wait a few hours to check again (until 24 hours after my last manual attempt, which also said up-to-date).
The Continue Update is typically greyed out when an update hasn't already been downloaded, so you probably didn't have a failed update. I'm just getting a little upset that the October update is taking so long. Just saw this morning that the Nexus phones are already getting their November update...
Gary02468 said:
First thing this morning, my phone insisted on a password instead of fingerprint for "first attempt after restart". But the Status page shows that the phone has been running for more than 600 hours, and I'm still on API2, Sept. 1 security update. But the Update page has a greyed-out "Continue update". When I click on Software Update, it says up-to-date and tells me as usual that I have to wait a few hours to check again (until 24 hours after my last manual attempt, which also said up-to-date).
Click to expand...
Click to collapse
My device started the update this morning, it ran in around 253mb, so I would guess its a minor update. I haven't let it finish, I want to give the 935U a run
Got it now:
http://forum.xda-developers.com/att-s7-edge/how-to/g935aucu4apj4-oct-1-2016-security-update-t3496395
I got the update. They sneaked in Fullscreen app.
I manually checked for the update and got it just now. It's so irritating that ATT takes so long to release these updates to us!
Hurricane Andrew said:
The Continue Update is typically greyed out when an update hasn't already been downloaded, so you probably didn't have a failed update. I'm just getting a little upset that the October update is taking so long. Just saw this morning that the Nexus phones are already getting their November update...
Click to expand...
Click to collapse
Over 200MB ... should be more then just security update. Security update is usually something around 40-60MB
norbarb said:
Over 200MB ... should be more then just security update. Security update is usually something around 40-60MB
Click to expand...
Click to collapse
Yup, I got it yesterday afternoon as well. I noticed they finally removed the deprecated Milk Music app as well.
Here is the current update: Android 6.0.1 Marshmallow
The details
Release date: November 8, 2016
Android version: 6.0.1
Security patch level (SPL): October 1, 2016
Baseband version: G935AUCU4APJ4
Kernel version: 3.18.20-9439621
Build number: MMB29M. G935AUCS4APJ4
File size: 285MB
The updates
What's new: Full Screen – Mobile Video Service and Android device security enhancements
What's changing: Improved volume for Enhanced Push To Talk (ePTT) and fix for calls failing to go to Voice Mail when calling non LTE devices
What's going: Milk Music
Via AT&T
All they put in the update was the Full screen App which can be disabled with Package Uninstaller
Related
So a about a week ago I got a notification for a new security update but I skipped it due to the bad Internet connection i had that day, now whenever I check for a new update in (about phone) I can't find the update, what should I do?
Settings -> Lock screen and security -> Other security settings -> Security policy updates -> Check for updates
ssrij said:
Settings -> Lock screen and security -> Other security settings -> Security policy updates -> Check for updates
Click to expand...
Click to collapse
I tried that as well,it says that my security policy has already been updated to the last version!!
Any help?
I skipped it also, thinking it would ask again in a day or so, but it never did. Is May 1, 2016 the latest for the "Android security patch level"? If so, I guess it may have done the update on its own later that night?????
abcomputin said:
I skipped it also, thinking it would ask again in a day or so, but it never did. Is May 1, 2016 the latest for the "Android security patch level"? If so, I guess it may have done the update on its own later that night?????
Click to expand...
Click to collapse
Well yeah may is the latest, but mine shows 2 April not 1 may so It didn't definitely update automatically, 2 April is what I got first I bought the phone, it never changed
Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.
Hi I have an unrooted 6p I have never messed with the software but I am on the dp program I usually get the updates within hours of it being announced. But for some reason I have not gotten the 7.1.1 stable with December security patch which is odd but anyway I tried side loading the OTA and it gets to 40% and then says installation aborted. I have the and setup right and all that I can reboot into bootloader does anyone know why it would be doing this? When I was at work today I thought maybe if I disable the allow seamless update option in developer options maybe that will allow it. Any thoughts?
Ok I feel like an idiot. I tried again when I got home from work and it seems that the file I am trying to flash is from November 1 which I already have installed. It is the last one one the Google OTA page. So is it not out yet for the 6p? I'm confused can anyone help me out please
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
redduc900 said:
I believe you'll need to unenroll from the beta program first before attempting to sideload the OTA image. The latest OTA image is NMF26F, which includes the December security patch. And make sure you boot into recovery, and not the bootloader to install the update using adb.
Click to expand...
Click to collapse
Ok if I unenrolled from the dp program I should just get the OTA then I won't have to side load is what I'm guessing. It seems that Google had the stable build done before they released the last dp because the file says November 1 build and I got mine on November 5 that is why it won't allow it.
Since about 6 months ago, Google has been allowing stock 7.0+ Android users to manually request the latest monthly OTA updates the moment they are released. No side loading or beta sign ups required.
Step 1. While connected to WiFi, open Settings and then tap About Phone and System Updates.
Step 2. Ignore the text that says there are no updates found and tap to check manually.
Step 3. Wait about 10 seconds after it says there were no new updates and the OTA will begin downloading.
This will be the 6th monthly OTA I've received on my first try the day of its release in this fashion. Knowing it would happen again I recorded a video of this in action with today's May security OTA.
bblzd said:
Since about 6 months ago, Google has been allowing stock 7.0+ Android users to manually request the latest monthly OTA updates the moment they are released. No side loading or beta sign ups required.
Step 1. While connected to WiFi, open Settings and then tap About Phone and System Updates.
Step 2. Ignore the text that says there are no updates found and tap to check manually.
Step 3. Wait about 10 seconds after it says there were no new updates and the OTA will begin downloading.
This will be the 6th monthly OTA I've received on my first try the day of its release in this fashion. Knowing it would happen again I recorded a video of this in action with today's May security OTA.
Click to expand...
Click to collapse
Good to know.
Sent from my Nexus 5X using Tapatalk
So about a year ago, I did a factory reset while on the last beta, about a month before the final release was pushed out to everyone. I was properly enrolled in the beta program, so I didn't flash it myself.
After the reset, I was still on the beta but once the update was pushed out, I never received it. Manually checking for updates didn't find anything.
Security patch level: 12/1/2016
Baseband: 4ZPLN
My kernel version is is from "Fri Dec 23" which I'm assuming is 2016?
I have a Mac on High Sierra and I tried using Smart Switch but it would not find my phone. It would tell me to unplug the phone and try again, but I still got the same message.
What are my options now, since it has been a whole year like this. I put up with being on older software for all this time but now I think I've definitely pushed my luck with security patches, as well as getting the full features from Sprint in regards to optimization.
How do I get myself back up to speed? I'm already on 7.0, as I mentioned, so I'm hoping whatever needs to be done won't require a clean wipe.
PS, I took a look at my Samsung Members app and Samsung account and it had two devices listed as tied to my account. I think it's the same device, my S7, but one that has a check mark next to it was "last accessed" on the day I performed the factory reset, last January. The second one was last accessed currently, so I'm assuming it's the same device but Samsung sees it as two different devices.