so i looked on TMOs site at the software update page and it shows the august update, which i took OTA before i rooted with CFAR
on my phone my baseband is M8998TMO_24.71.01.87R NUS
but TMO says it should be M8998TMO_04.17.01.76R
https://support.t-mobile.com/docs/DOC-35970
is it different because of CFAR?
Their website hasn't been updated. They didn't match up since the release of the phone.
Sent from my Moto Z (2) using Tapatalk
Lol figures
Midnight_Rider said:
Lol figures
Click to expand...
Click to collapse
They even said it doesn't support T-Mobile video calling but it does and also has duo preinstalled. You can test it out. Throw it in airplane mode and turn on wifi. You can't place a video call unless you use the duo app. If you turn cellular back on you can use the dialer built in one.
Sent from my Moto Z (2) using Tapatalk
so the .87R is the newest one? that is what I'm on, but I have the June security patch
CadillacMike said:
so the .87R is the newest one? that is what I'm on, but I have the June security patch
Click to expand...
Click to collapse
That's the version I am on. There was an update almost as soon as the device came out. What carrier are you on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5X using Tapatalk
T-Mobile
looks like i have a different kernel as well. how does that get updated? via OTA as well? I'm on the moto support forum, but not getting any responses about the security patch
CadillacMike said:
looks like i have a different kernel as well. how does that get updated? via OTA as well? I'm on the moto support forum, but not getting any responses about the security patch
Click to expand...
Click to collapse
You didn't get the last update? Should have had one since the device was released.
Sent from my Nexus 5X using Tapatalk
That's the thing we haven't got it yet we're still factory
joemossjr said:
That's the thing we haven't got it yet we're still factory
Click to expand...
Click to collapse
So you are on T-Mobile also? I don't remember hearing others but the T-Mobile version getting an update.
Sent from my Nexus 5X using Tapatalk
Yup, this is my 3rd Z2 Force. The other ones had an update, I just didn't remember the details.
This one I have had since October 3rd, got it from a physical corporate T-Mobile store, no updates since I have had it.
I even tried swapping the SIM card hoping it would Kickstart something
Is anyone still on the initial release build with the baseband listed on tmo's website? [M8998TMO_04.17.01.76R]
If so, could you boot into fastboot mode and do "fastboot getvar all" from terminal?
I'd like the "ro.build.version.full" value so I can try to find the first OTA to NCX26.122-49.
I'm still stuck on the June 1, 2017 security patch. T-Mobile Z2 Force, have been using the phone for almost a month. No update.
I am still on June 1st with a Tmo Z2 Force
sixteasy00 said:
I'm still stuck on the June 1, 2017 security patch. T-Mobile Z2 Force, have been using the phone for almost a month. No update.
Click to expand...
Click to collapse
CadillacMike said:
I am still on June 1st with a Tmo Z2 Force
Click to expand...
Click to collapse
T-Mobile pulled the update
Midnight_Rider said:
T-Mobile pulled the update
Click to expand...
Click to collapse
Source?
Sent from my Pixel 2 using Tapatalk
Tidbits said:
Source?
Click to expand...
Click to collapse
Well it would seem odd T-Mobile's update won't flash with unlocked bootloaders but Sprint's will. Sprint's users are on September security patch now...
Edit: if you look at OP's hyperlink, you'll see TMobile says only original software is currently available...
Uzephi said:
Well it would seem odd T-Mobile's update won't flash with unlocked bootloaders but Sprint's will. Sprint's users are on September security patch now...
Click to expand...
Click to collapse
If you at the source of the update file it belonged to Lenovo. Also with the amount of people who have troubles with texts and notifications Motorola could have pull it themselves.
Sprint version firmware is different than T-Mobiles and isn't a good gauge. It's not like the whole 6P thing going on.
Sent from my Pixel 2 using Tapatalk
Tidbits said:
If you at the source of the update file it belonged to Lenovo. Also with the amount of people who have troubles with texts and notifications Motorola could have pull it themselves.
Sprint version firmware is different than T-Mobiles and isn't a good gauge. It's not like the whole 6P thing going on.
Click to expand...
Click to collapse
Yes, version is different, but the only logical explanation is either Lenovo or Tmo pulled the update since other models are updating fine and users were getting the update until recently, but other phones are still able to update to August and September security updates.
Related
So it's now January 18th and I've yet to receive the security update for January. Has anyone received it, via OTA?
Quite frankly I'm surprised that Google can be so late pushing it out given that there are probably not even 250,000 people who bought the thing.
Wouldn't surprise me if Google are holding off on it until a massive update is ready to fix/help other issues
Google will be lucky if 25,000 people bought the thing AND kept it.
undertaker2k14 said:
Google will be lucky if 25,000 people bought the thing AND kept it.
Click to expand...
Click to collapse
not sure they care about sale numbers.
Like previous Pixel devices, it's mainly for done for internal usage, PR, aura, showcase, exploring, reference platform, etc. And to acquire knowledge on how to build such devices.
The fact that they sell it to anyone is a just a bonus for fans and tech enthusiasts.
kgersen said:
not sure they care about sale numbers.
Like previous Pixel devices, it's mainly for done for internal usage, PR, aura, showcase, exploring, reference platform, etc. And to acquire knowledge on how to build such devices.
The fact that they sell it to anyone is a just a bonus for fans and tech enthusiasts.
Click to expand...
Click to collapse
interesting point. it would explain the lack of testing. but it does not explain the web site or many of the AMA answers or the AMA itself. google is certainly getting well deserved training on the return process with this device.
Yeah, I'm curious as well. Looked like the binaries had some pretty big updates
andreoidb said:
Yeah, I'm curious as well. Looked like the binaries had some pretty big updates
Click to expand...
Click to collapse
anyone get it ever, lol, its basically February. If no one got the January update, that does not bode well for future update support
Typically the images are posted to the developer website before any OTAs go out. No updated image has been posted (other than MXB48K, which we know isn't a January update), so I wouldn't expect any OTA.
ckevinwelch said:
Typically the images are posted to the developer website before any OTAs go out. No updated image has been posted (other than MXB48K, which we know isn't a January update), so I wouldn't expect any OTA.
Click to expand...
Click to collapse
Yeah, ik, It is weird since they did say they would be on a 6 week update cycle. Still nothing. Not a great sign, guess they are trying to work out the WiFi and touchscreen issues in the first update. They probably tough to fix
andreoidb said:
yeah, ik, it is weird since they did say they would be on a 6 week update cycle. Still nothing. Not a great sign, guess they are trying to work out the wifi and touchscreen issues in the first update. They probably tough to fix
Click to expand...
Click to collapse
6.0.1 (mxb48j) is out since today
nbpf said:
6.0.1 (mxb48j) is out since today
Click to expand...
Click to collapse
Does this new update include the February 1st security update? If so, could you provide a screen capture?
MXB48T was the latest firmware if not mistaken , but still no OTA release yet , expected comin next week
http://www.androidcentral.com/googles-first-pixel-c-update-now-available
TokyoGuy said:
Does this new update include the February 1st security update? If so, could you provide a screen capture?
Click to expand...
Click to collapse
I do not know. You would like a screen capture of what?
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bigboimike21 said:
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
Click to expand...
Click to collapse
Whoa you should have been prompted to update to 6.0.1 right away there's not even a 6.0 factory image.
seems this pixel c was really beyond what they promises to delivered. every 6 weeks for new update. in fact nexus brand can get update almost on time.
bigboimike21 said:
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
Click to expand...
Click to collapse
Same here. I had a warranty issue with my first Pixel, the replacement they sent me is also on 6.0, with no OTA to 6.0.1.
But honestly it seems to work better.
---------- Post added at 05:17 PM ---------- Previous post was at 04:34 PM ----------
In an attempt to ask Google why my device is still on October Security Patch and no 6.0.1 Update on my warranty replacement Pixel.
So I guess I just had to wait. I avoided flashing the 6.0.1 update since I had already set up my tablet using the "Setup my device" feature through Google Now from my 6P. Last night my Pixel C was prompted to install the 6.0.1 update and updated fine. I'm unsure of what be features are added other than security, but my home and back buttons are moved to the left while recent apps button is on the right. So I guess it worked. That and the fact that under about tablet it says 6.0.1 ha-ha.
It seems to run a bit smoother now so, there's that.
I got the OTA udpate last night. I am in San Diego, CA.
Yesterday I received MXB48T OTA update on my 32GB pixel C. The inconsistent WiFi speeds issues have not been solved.
Enviado desde mi Pixel C mediante Tapatalk
Updated with sideload instructions!
*Some links may be outdated as I am not actively maintaining them. If you want to know what's the latest, just reply to the thread.
Credit Rahilm with original instructions. CotoMtn for the link. Markieb for the magnet link. BMatney for mega link
Generic instructions for sideloading OTA package:
Flashing via this method WILL WIPE EVERYTHING SO BACKUP FIRST. Short tutorial (I'm not responsible for anything that goes wrong, but this worked for people):
1) BACKUP!! IT WILL FACTORY RESET YOUR PHONE!!
2) Download package (https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2BPE5-UP / https://mega.nz/#!eElQgD6A!CyME8PpXpK_xXcdpt6lMlh5XYzzf2ByrWr4DQf-2uUs or torrent [.CODE] magnet:?xt=urn:btihBFC71DCC7495932D6F43CB87598B74FAF7F3349&dn=SS-N920AUCU2APB2-to-U2BPE5-UP&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce [./CODE])
3) rename file to ota.zip
4) Reboot into recovery. Turn off phone and wait a minute for it to completely turn off. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
5) Select Apply Update from ADB
6) Make sure you have Android Platform Tools on your computer (there's other guides for this) (recommend Android studio adb)
7) command 'adb sideload (path to file)' (path to file example: C:/Windows/Users/Me/Desktop/Ota.zip)
8) will take 5+ minutes and may sit on att screen for awhile. Wait it out. Make sure it's plugged in
schhy said:
Three people in the AT&T Galaxy S6 forum have asked reps and they say the update is coming today, March 11th. You can check the screen shots for yourself. Really no way of telling if it's true till it happens
http://forum.xda-developers.com/showthread.php?t=3321144
Click to expand...
Click to collapse
...
I see March 14th in there several times... Not March 11th though...
And what does the S6 update have to do with the Note 5? These 2 updates are not going to be necessarily synonymous with each other - the framework and software packages are different between the Note series and the S series devices.
Just sayin'.
Krayziepop said:
...
I see March 14th in there several times... Not March 11th though...
And what does the S6 update have to do with the Note 5? These 2 updates are not going to be necessarily synonymous with each other - the framework and software packages are different between the Note series and the S series devices.
Just sayin'.
Click to expand...
Click to collapse
One says Today coming that's Note 5 , other March 14 for S6, so that's what it means.
Running On Samsung Galaxy Note 5 N920A Wicked Deadly Venom Theme
March 14 it is
http://www.phonearena.com/news/Rejo...r-Note-5-today-March-14-for-Galaxy-S6_id79196
Sent from my A1 using Tapatalk
barondebxl said:
March 14 it is
http://www.phonearena.com/news/Rejo...r-Note-5-today-March-14-for-Galaxy-S6_id79196
Sent from my A1 using Tapatalk
Click to expand...
Click to collapse
14th for s6, today for note5
Update today but it is still 5.1.1. Looks like a security update.
scottwood2 said:
Update today but it is still 5.1.1. Looks like a security update.
Click to expand...
Click to collapse
It is possible the reps don't know android well and thought security update was 6.0....
Venom0642 said:
One says Today coming that's Note 5 , other March 14 for S6, so that's what it means.
Running On Samsung Galaxy Note 5 N920A Wicked Deadly Venom Theme
Click to expand...
Click to collapse
LOL - nice. I see it now, post 26. I went through them all like 2 times looking for clues. I sucked at finding Waldo too...
On that token, I will believe it when I see it. I know how these staged rollouts go, and AT&T has never been super reliable on getting updates out lol. Let's just hope as well, that they have done their due diligence at working the bugs out... and while they are at it I hope they mess up the code and leave us a rootable loophole in the process! :cyclops:
Saw the post saying today on Android Central.
http:// www.androidauthority.com/att-samsung-galaxy-note-5-marshmallow-update-679296/
but of course it's all based on the same info and screenshots.
Sent from my SAMSUNG-SM-N920A using Tapatalk
jellybear456 said:
Saw the post saying today on Android Central.
http:// www.androidauthority.com/att-samsung-galaxy-note-5-marshmallow-update-679296/
but of course it's all based on the same info and screenshots.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
They all cite the xda thread
If it was coming today, wouldn't some of us know by now? It's 11am on the "East Side".
TeldenW said:
If it was coming today, wouldn't some of us know by now? It's 11am on the "East Side".
Click to expand...
Click to collapse
There is apparently a Pre-M update right now according to someone in another thread. Don't know when it came out or if it was included in the security date. I don't have a Note so I can't tell you much about it. But a pre-update would mean mm is about to be released
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take it with a grain of salt but here is what AT&T had to say a few minutes ago
No that's not the case. The security update from AT&T came out on the 9th of March. Not everyone got it right away so scottwood probably got the security update late.
schhy said:
There is apparently a Pre-M update right now according to someone in another thread. Don't know when it came out or if it was included in the security date. I don't have a Note so I can't tell you much about it. But a pre-update would mean mm is about to be released
Click to expand...
Click to collapse
I got the "pre-update" you're talking about. It was yesterday or Wednesday.
---------- Post added at 09:49 AM ---------- Previous post was at 09:49 AM ----------
ColoMtn said:
View attachment 3679404Take it with a grain of salt but here is what AT&T had to say a few minutes ago
Click to expand...
Click to collapse
Have you checked for update yet manually?
TeldenW said:
I got the "pre-update" you're talking about. It was yesterday or Wednesday.
---------- Post added at 09:49 AM ---------- Previous post was at 09:49 AM ----------
Have you checked for update yet manually?
Click to expand...
Click to collapse
Tried several times. Says no update available.
None here either
Sent from my SAMSUNG-SM-N920A using Tapatalk
Don't get too excited. Apparently there are some issues with MM on the note 5, including Verizon's recent update. http://www.techtimes.com/articles/1...ues-wi-fi-problems-battery-drain-and-more.htm
Sent from my SAMSUNG-SM-N920A using Tapatalk
jellybear456 said:
Don't get too excited. Apparently there are some issues with MM on the note 5, including Verizon's recent update. http://www.techtimes.com/articles/1...ues-wi-fi-problems-battery-drain-and-more.htm
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
it mean maybe we must wait more few days..
hoaihung said:
it mean maybe we must wait more few days..
Click to expand...
Click to collapse
Someone of att forums said that they could be slowly rolling it out and wait for bug reports
So, the current Android version and security update I'm on has issues playing hdr on Netflix (everything has a brownish yellow tint). I've watched an hdr movie rental on Google Play store. Not bad, but can clearly see that it's compressed. YouTube works great. But not Netflix. Seen on many Reddit forums that the issue is resolved in the Jan security patch. Which I'm assuming they may be holding off for us Canadiens for the Oreo update.
But I cannot seem to get any solid information about if it's even planned.
Anyone else stuck with the delayed security update?
Oct 1, 2017 yes. You are not alone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
Not same phone...heard same HD issue on Netflix though. I haven't tried to replicate. But held up on the patch all the same. I have V30+
chox_g5 said:
Oct 1, 2017 yes. You are not alone.
Click to expand...
Click to collapse
Oct? I'm on the Dec 1, 2017 security patch. Who's your carrier?
Somewhat relevant, I just received a update notice. Looks like a security patch...US998 unlocked. Perhaps they are finally making things available to North America?
vinniej said:
Somewhat relevant, I just received a update notice. Looks like a security patch...US998 unlocked. Perhaps they are finally making things available to North America?
Click to expand...
Click to collapse
Yes US received the Jan 1 security patch. It's reported to fix hdr issues. But no notice of it in Canada. Also the unlocked models are receiving oreo. Beta I think.
Simplyrobbie112 said:
Oct? I'm on the Dec 1, 2017 security patch. Who's your carrier?
Click to expand...
Click to collapse
Tmobile
chox_g5 said:
Tmobile
Click to expand...
Click to collapse
No idea what update frquency is like for the +. But still being on Oct 1 patch. Did you check with update software on PC?
Simplyrobbie112 said:
No idea what update frquency is like for the +. But still being on Oct 1 patch. Did you check with update software on PC?
Click to expand...
Click to collapse
Tells me it can't be checked. Not sure what that's all about. All other parts of LG Bridge work just fine.
Simplyrobbie112 said:
Yes US received the Jan 1 security patch. It's reported to fix hdr issues. But no notice of it in Canada. Also the unlocked models are receiving oreo. Beta I think.
Click to expand...
Click to collapse
No, it's the December patch. Just got it earlier tonight, on both my open market US998 V30+ and my wife's open US998V30. I turned off my phone on my spare V30, to wait to see the update. I want to see if LG Bridge will offer to update it and maybe download KDZ.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my official carrier unlocked LG V30+ US998
ChazzMatt said:
No, it's the December patch. Just got it earlier tonight.
View attachment 4391597
Sent from my official carrier unlocked LG V30+ US998
Click to expand...
Click to collapse
I got this update today as well on V30+ unlocked.
But I hear it fixed the hdr. Yet I'm on the Dec 1 patch, and still have hdr issues with Netflix. Maybe because I received it before the fix mine was not included?
The very, very slow Oreo update release for the V30 (H933) is disheartening. Not like this is a surprise, but it’s still frustrating.
I thought it would be out before the end of Jan. Wait and see in 2 days time if that's true I guess.
I don't care about oreo, but considering that this is their "flagship" phone, such late security patches and updates on Canadian model H933 means this will be my first and last lg phone.
My Lg V30 T-Mobile USA is still on October patch. How disappointing.
I don't know why companies these don't just release one world wide model of the phone. It would streamline updates so much easier.
ern88 said:
I don't know why companies these don't just release one world wide model of the phone. It would streamline updates so much easier.
Click to expand...
Click to collapse
Because that would cut out the carriers and make the phones less expensive.
Google basically tried that, and so do a few other direct to consumer OEMs. But in North America, apparently people love going to their carrier stores to get ripped off. There are very few phones Sprint will accept that are not Sprint branded phones (and I'm pretty sure exceptions involve the OEMs like Motorola paying Sprint some money, somehow).
Google has to sell Pixel phones in Verizon stores to get any kind of sales traction. Verizon and T-Mobile make it hard for non-branded phones to work well with VoLTE and Wi-Fi calling.
If you could buy the phone from anywhere (and it was the exact same phone), you would buy it off eBay from Chinese dealers. But carriers want their cut. So, they make it difficult. And they want their bloatware put on.
Sent from my official carrier unlocked LG V30+ US998
That's not how it works up here with the 933. Non of the phones are branded. And I think at this point any phone from any carrier can be used on any other carrier. What's more is its now not legal to sell sim locked phones here.
Doing the math with the available plans, its basically either a wash or cheaper to get i from the carriers.
We don't get much if anything as far as cheaper plans are concerned if you bring your own phone.
Any of the small amounts of bloatware we get is easily disabled via the system so not a big deal.
chox_g5 said:
Tmobile
Click to expand...
Click to collapse
Simplyrobbie112 said:
No idea what update frquency is like for the +. But still being on Oct 1 patch. Did you check with update software on PC?
Click to expand...
Click to collapse
I got you both beat, I'm on September security patch. Thanks, AT&T!
Sent from my LG-H931 using XDA Labs
Mr CATFISH said:
I got you both beat, I'm on September security patch. Thanks, AT&T!
Click to expand...
Click to collapse
Yeah... Google spies, but it seems to possibly be almost worth being vanilla on the internet and go with a pixel... LMAO. Just joking and venting...lol
I purchased my Nokia 8.1 a few days ago. After starting it, it updated one month at a time from the February patch to the August patch. I decided to try the Android 10 beta, and after playing around with it, I decided to return to Pie.
The rollback was delivered OTA and it installed fine. However, it had the June patch and it refuses to pick up the July or August patches. This is frustrating, as the whole point of having an android one phone was to receive the monthly updates. I tried removing my sim card and resetting to factory defaults, however this didn't make a difference.
Any ideas?
Give it some time. You'll get the updates rolling again within a day or so. Kindly be patient.
Sent from my Nokia 8.1
singhnsk said:
Give it some time. You'll get the updates rolling again within a day or so. Kindly be patient.
Click to expand...
Click to collapse
How do you know? It seems strange that they came through one after the other the first time and now I'm not getting any.
Pumpino said:
How do you know? It seems strange that they came through one after the other the first time and now I'm not getting any.
Click to expand...
Click to collapse
Because somebody on Nokia Community said that. Nokia is just taking a while to switch your update delivery server from the beta to the stable release.
It's essential because else there will be a big clash. Let's say you're on Beta release channel and you request downgrade. You get an OTA but didn't install it yet. And meanwhile Nokia changes you to stable release channel. What will happen? That downgrade OTA has to disappear because it isn't in the stable channel. And you'll be stuck on Android Q with not even beta updates and not stable ones.
So, just keep some patience. You'll be pushed to stable release after 24 hours. So that it is quite expected that you have taken the downgrade.
If you still don't get an update after a wait, then it will be something to think about, not yet.
Sent from my Nokia 8.1
singhnsk said:
Because somebody on Nokia Community said that. Nokia is just taking a while to switch your update delivery server from the beta to the stable release.
Click to expand...
Click to collapse
Thanks for the explanation. It's easier waiting now that I know nothing's wrong.
Yeah, just be patient. [emoji846]
I rolled back last night and there was no updates, but I just woke up and checked for update... Ta-da! [emoji16]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nokia 8.1 using Tapatalk
singhnsk said:
So, just keep some patience. You'll be pushed to stable release after 24 hours.
Click to expand...
Click to collapse
Like clockwork, after exactly 24 hours, the July patch was detected, immediately followed by the August patch. Excellent!
Pumpino said:
Like clockwork, after exactly 24 hours, the July patch was detected, immediately followed by the August patch. Excellent!
Click to expand...
Click to collapse
Good to know that [emoji2] What were the key issues in Q though?
Sent from my Nokia 8.1
singhnsk said:
Good to know that [emoji2] What were the key issues in Q though?
Sent from my Nokia 8.1
Click to expand...
Click to collapse
I was constantly losing signal during calls. I could hear the other side, but they couldn't hear me and signal strength was shown as no signal at all. I've read that you could fix that by turning VoLTE off, but VoLTE doesn't even exist in my country. [emoji1787]
That's the main reason why I rolled back. [emoji846]
Also, gesture navigation is buggy as hell. [emoji846]
Sent from my Nokia 8.1 using Tapatalk
singhnsk said:
Good to know that [emoji2] What were the key issues in Q though?
Click to expand...
Click to collapse
I couldn't really spot any differences, let alone advantages. Plus, the phone kept freezing; I'd go to unlock it and I'd just have a black screen. The only way to awaken it was to press the power button for several seconds and restart it.
There was an update for my Verizon Note 10+ 5G which supposedly failed and was successfully rolled back. I checked again and tried the PC tools which give me an error message saying my firmware is not compatible with the PC update tool. (I am NOT rooted.) I checked again OTA and now it says there is no update which means Verizon must have pulled it! I see no issues operationally with the phone - Note my s/w version as well. Anybody else run into this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 5086869View attachment 5086871
Sent from my SM-N976V using Tapatalk
View attachment 5086881
With AT&T I'm more afraid of their updates and automated downloads/flashes than malware... lol, still on Pie.
Best to keep updates blocked, let it roll out and see how many get rolled over by it.
Give it a couple weeks and then decide.
With Q I'm still not satisfied enough to load it and as such the backlog of security updates remain pending.
Whatever.
KruseLudsMobile said:
There was an update for my Verizon Note 10+ 5G which supposedly failed and was successfully rolled back. I checked again and tried the PC tools which give me an error message saying my firmware is not compatible with the PC update tool. (I am NOT rooted.) I checked again OTA and now it says there is no update which means Verizon must have pulled it! I see no issues operationally with the phone - Note my s/w version as well. Anybody else run into this?
Sent from my SM-N976V using Tapatalk
View attachment 5086881
Click to expand...
Click to collapse
I don't think it was pulled. I got the update a couple of days ago with no failures.
I have the Verizon Note 10+ 5G. Stock not rooted.
Sent from my SM-N976V using Tapatalk
View attachment 5087077
Then why does it say my upgrade failed but I have the most up to date version!?!?? What build do you have, does it match the build number in the photo shown of my phone?
Sent from my SM-N976V using Tapatalk
Girlfriends Verizon version got an update. She makes it known to tell me because of bad experiences with Verizon updates . I don't know what happened with hers though. She uses her pixel 4 as her personal but I'll ask.
coilbio said:
Girlfriends Verizon version got an update. She makes it known to tell me because of bad experiences with Verizon updates . I don't know what happened with hers though. She uses her pixel 4 as her personal but I'll ask.
Click to expand...
Click to collapse
Thank you for your reply but mine is specific to the Note 10+ 5G, so what you suggest is like comparing Apples to Oranges. I have noticed also as you can see by the photos originally supplied, although it tells me the update failed, the software version has changed and that may be why it also says there is no update available. I may actually be running the later version or not, there is no way to really tell, either way it was handled very sloppily by Verizon and is concerning.
However, I have also heard, Google will be discontinuing the Pixel line of phones so as they say, every company is screwed up, they are just screwed up different ways...!
Sent from my SM-N976V using Tapatalk
I was talking about her note, she has 2 phones.
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Guyinlaca said:
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Click to expand...
Click to collapse
Once I get a stable load that's running well, I leave it alone. Been running both Windows and Android like this for many years with very little trouble. As you are keenly aware of tracking down an update issue can be very time consuming*. Many times a hard reset due to malware be easier. Malware on Android has caused me only one hard reset in over 6 years.
I herd dinosaurs, lol, I take a conservative approach to updates because many times the cure is worse than the disease. A bare bones updated Windows or Android machine runs faster... I hate waiting.
Carriers are partnered with Samsung and jam their own crapware and app graphics "updates" in their too on OS upgrades.
These can make it usable... I remember the horror of Lollipop on my S4+, destroyed it... thanks AT&T. Not.
That's one reason I'm still running on Pie... with no issues.
*may be a settings issue. My Pie load runs best with all power management turned off especially 3rd party including Samsung. A new update means a Google search won't yield many solutions for it.
The first app I block is AT&T updates... no joke.
KruseLudsMobile said:
Then why does it say my upgrade failed but I have the most up to date version!?!?? What build do you have, does it match the build number in the photo shown of my phone?
Sent from my SM-N976V using Tapatalk
Click to expand...
Click to collapse
I don't know. Look up that error code 410.
Like I said, I don't think it was pulled.
Sent from my SM-N976V using Tapatalk
Guyinlaca said:
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Click to expand...
Click to collapse
Odd. I'm not having battery or BT problems.
Sent from my SM-N976V using Tapatalk