Related
I have not received any update for Android 5.0 yet. I find this pretty odd considering it has been out for a long time. Everything seems to be functionally normally, but I never get any OTA update notification and it says I have the latest updates. Is this something to be concerned about, or am I just extremely unlucky to be one of the last ones to get it? Thanks.
Dillon610 said:
I have not received any update for Android 5.0 yet. I find this pretty odd considering it has been out for a long time. Everything seems to be functionally normally, but I never get any OTA update notification and it says I have the latest updates. Is this something to be concerned about, or am I just extremely unlucky to be one of the last ones to get it? Thanks.
Click to expand...
Click to collapse
The Nexus 7 is experiencing issues with L. My dad's device also didn't get it yet.
However, nothing stops you from flashing the image yourself from Googl's developer site.
This is the first time I've heard of this. Thanks for giving us all a heads up!
Oh wait, there's only about 10 other threads on the first page about this very issue.
This happened with me on Lollipop as well, I never got the OTA until after Xmas, still not a sniff of Marshmallow. May be it is just me, but in theory you think owning a Nexus device means you get updates sooner but for me anyway the reality is by the time you get the OTA other manufacturers already have it out. My S5 got Lollipop before my Nexus 7 2013.
Anyone else have this issue?
I wish I knew the answer to your question. A co-worker got LP with in days of release and my tablet didn't see the update come down until 5.1 was out. Then oddly enough I saw MM with in three days of release and the small update that came after it the day it was posted.
I'm sure Google has some weird plan that only makes sense to them on when and what get the updates but it sure isn't any forum of logic I can understand. I think part of is they push the update to some devices and wait to see the telemetric data come back for a few days to see if there is any major bugs before pushing it out to "everyone." It's not like Google doesn't have the resources to just pump the update out for all to get at once like iOS does.
Samsung apparently has sent out a final notification to all those enrolled in the Nougat Beta that there will be no more updates and that the beta ends officially on December 30th and that they will attempt to push out the official update to everyone in January. Hope this means they were able to quash all major bugs.
http://www.androidcentral.com/galaxy-s7-and-s7-edge-receive-nougat-update-january
And it is officially Android 7.1.1, at least for those in the US.
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
JerseyDubbin said:
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
Click to expand...
Click to collapse
I haven't been rooted for over a year. I was on an LG G3 before my S7 and so far, I haven't found a real need to root. Before, I rooted because I used TiBu to backup my apps, but with the G3, they had their own backup utility that worked just like TiBu, but it's only for LG devices.
But with how Google Play uploads settings now, that appears to work just fine for me as well, so at this point, I have no reason to root. Plus, I really love Samsung Pay so I don't want to lose that.
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
Agree completely. The root process works well etc but I had to go through xposed and do a lot of tweaks to get it running well for really no gain over what I had stock.
JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
I completely agree. The G3 was the first phone I ended up not rooting. I did at first because I was just in that mode of, get a new phone, root, flash a custom ROM. But as I started getting used to a lot of the features, and found that the battery life wasn't bad, coupled with running Greenify in non-root mode, I could make the battery last 1.5 days. So, over the last year of the two years I owned it, I didn't root.
With the S7, no need to root. This is smoothest phone I've had yet. The quality of the phone itself is excellent. So, this phone will not be rooted.
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
iBolski said:
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
Click to expand...
Click to collapse
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
sklarskyj said:
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
Click to expand...
Click to collapse
I believe there were only two betas for VZW phones and then they cancelled the beta testing for VZW-based phones. Not sure why. Kind of sucks. Probably Big Red had something to do with it.
j0hnh0lmes said:
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Same here, tried rebooting and checking again a few times and still nothing.
Oh well
I spoke to Verizon about this and they dont know when the update will be out.
SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
Of course they don't. They have to add crapware, disable a bunch of stuff and add backdoors.
Sent from my SM-G930V using XDA-Developers Legacy app
SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
That's their usual response.
I've read US-Based carriers have no ETA yet. Grr.
iBolski said:
I've read US-Based carriers have no ETA yet. Grr.
Click to expand...
Click to collapse
I swear searching around the interwebs for information on release dates has at least as much mis-information as looking for information on the election candidates during the election. So much trash.
But I haven't found anyone stating they heard definite dates. I'm thinking it will be late January at this point maybe early Feb before it hits our phones.
i have given up speculating anything that involves verizon. nothing would surprise me.
Take it where its coming from but it looks like some US non-beta testers are starting to see the update. "Unlocked" phones only but still....
http://www.theverge.com/2017/1/19/14321980/samsung-galaxy-s7-edge-android-nougat-update
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
lickwid said:
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
Click to expand...
Click to collapse
I believe unlocked models should be getting it before us on Verizon. But, there was a story out that stated OTAs for some reason have stopped being pushed out and Samsung has acknowledged this and is looking into why it happened.
http://www.droidviews.com/samsung-galaxy-s7-android-nougat-problems-firmware-delivery-stops/
Whether the "bug" is in the firmware itself or with the update process that sends out the notifications is not mentioned.
Anyone have it, is TW going to send update?
not yet. I've searched in the last 2 weeks but nothing shows up yet.
Waiting is the best solution
I think buiterfly3 still have to wait HTC a9 other carriers finished upgrade to nougat.
Or maybe HTC butterfly 3 won't get any upgrade form HTC forever
I found this link with nougat 7.0 but I don't like how it starts with xda.
This kink claims to have nougat 7.1.1.
Any thoughts?
The second one maybe. The first one looks kinda shady
since htc 10evo(bolt) has similar specs,is it possible to port a nougat rom from it?
As per a statement posted on XDA, the OnePlus Nord OOS11 beta should be coming sometime this week, though the builds for the 7 series are still delayed as OnePlus is finally confronting the dreaded decryption issue that has plagued the series since its inception. This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP along with more custom ROM development on the way. This is very good news for the tinkering community. Hope more is to come in the near future.
I mean, we can hope, but at this point, I am afraid it's still just wishful thinking.
gboybama said:
I mean, we can hope, but at this point, I am afraid it's still just wishful thinking.
Click to expand...
Click to collapse
Well, seeing as it's the very reason for the delay, it wouldn't make sense for OnePlus to announce that they were delaying the beta to fix the encryption issue just for them to not fix it. If that were the case, they would just not say it, you know?
You're a couple days late;
And;
>This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP
except decryption that is, blobs are the same so I am not confident TWRP will be able to decrypt on OOS11. We have to wait and see, but they may have broken it on a hardware level.
> along with more custom ROM development on the way
No, it does not mean this.
Lossyx said:
You're a couple days late;
And;
>This means, that, likely after Android 11 is released for our devices, that we should be able to have a fully functional TWRP
except decryption that is, blobs are the same so I am not confident TWRP will be able to decrypt on OOS11. We have to wait and see, but they may have broken it on a hardware level.
> along with more custom ROM development on the way
No, it does not mean this.
Click to expand...
Click to collapse
On a good note it seems a couple more roms have come about
SenyorMauricio said:
Well, seeing as it's the very reason for the delay, it wouldn't make sense for OnePlus to announce that they were delaying the beta to fix the encryption issue just for them to not fix it. If that were the case, they would just not say it, you know?
Click to expand...
Click to collapse
Hoping I'm wrong of course, but the pessimistic scenario is that OP forgot there was an issue with the 7T and was caught flatfooted while testing the update on their various devices. Then, they start looking for a cheesy workaround that doesn't undo the original problem.
Considering the recent, less than impressive, decisions coming out of OnePlus, I'm feeling it's more likely that some quick, unsatisfying shortcut to patch the problem is rolled out. I can't imagine a world where they dedicate the precious time of a couple of heroic developers to undo a tricky design mistake on an old device.
Heck, that's not even the worst scenario. If they were really caught with their pants down on this and it looks like the update is really difficult to apply, I wouldn't put it past their managers to conclude that the 7T is a niche phone with a declining base and they could decide to just leave it on Android 10, saying it couldn't be updated.
Again, though, I hope I'm wrong!
gboybama said:
Hoping I'm wrong of course, but the pessimistic scenario is that OP forgot there was an issue with the 7T and was caught flatfooted while testing the update on their various devices. Then, they start looking for a cheesy workaround that doesn't undo the original problem.
Considering the recent, less than impressive, decisions coming out of OnePlus, I'm feeling it's more likely that some quick, unsatisfying shortcut to patch the problem is rolled out. I can't imagine a world where they dedicate the precious time of a couple of heroic developers to undo a tricky design mistake on an old device.
Heck, that's not even the worst scenario. If they were really caught with their pants down on this and it looks like the update is really difficult to apply, I wouldn't put it past their managers to conclude that the 7T is a niche phone with a declining base and they could decide to just leave it on Android 10, saying it couldn't be updated.
Again, though, I hope I'm wrong!
Click to expand...
Click to collapse
Yeah, I'm hoping for the best. In the original article, it says that had to team up with Qualcomm to begin fixing the issue, so I'm thinking it's both a hardware-software problem, but I wouldn't know since I'm not very literate when it comes to technical issues like encryption. But we shall see! I really just want Oxygen OS on Android 11 since most of the ROMs right now have bugs (as far I've seen—haven't been able to find a ROM that doesn't irritate me in one way or another).
I've read somewhere that the encryption issue has been fixed.and that it's assumed closed betas ether started or will start soon I'll see if I can find the article or if someone knows it feel free to post it
rob420p said:
I've read somewhere that the encryption issue has been fixed.and that it's assumed closed betas ether started or will start soon I'll see if I can find the article or if someone knows it feel free to post it
Click to expand...
Click to collapse
For them yes.
But here's the thing.
Let's assume it's the same issue.
They probably broke or implemented encryption differently on a hardware level, hence contacting Qualcomm to help them workaround (not fix) the issue. We as in users, don't know what broke or is different, and since we don't have the source code we can't possibly know how OnePlus worked around it to decrypt data.
Let's hope something else was broken / implemented differently and not in a hardware level, then maybe it's fixed.
In fact, I have tried the first version of the closed beta version of oosA11. I tried to flash the English version and the Chinese version of twrp in this version. His decryption work still cannot be decrypted. This is only the first closed beta version. Maybe in the future public beta version. Will solve the problem. I don’t know at least the decryption problem in the first closed beta version or not. Currently they are undergoing the second closed beta version test. I don’t know if the second closed beta version has solved the problem. Maybe in the future public test. Version will solve this problem!
谷歌原生 said:
In fact, I have tried the first version of the closed beta version of oosA11. I tried to flash the English version and the Chinese version of twrp in this version. His decryption work still cannot be decrypted. This is only the first closed beta version. Maybe in the future public beta version. Will solve the problem. I don’t know at least the decryption problem in the first closed beta version or not. Currently they are undergoing the second closed beta version test. I don’t know if the second closed beta version has solved the problem. Maybe in the future public test. Version will solve this problem!
Click to expand...
Click to collapse
I'm moving into the camp of saying I'd bet serious money they don't fix the encryption issue.
Are we even getting the beta at this point, it's 20th Jan
[QUOTE =“ gboybama，：84324093，：1342510”]
Yes, I don’t think they will solve the problem. They used a weird decryption method to push their OS to update when they upgraded to 11. They might not solve this problem fundamentally.
gboybama said:
I'm moving into the camp of saying I'd bet serious money they don't fix the encryption issue.
Click to expand...
Click to collapse
Yes, I don’t think they will solve the problem. They used a weird decryption method to push their OS to update when they upgraded to 11. They might not solve this problem fundamentally.