Security updates???

bormasina

Senior Member
May 11, 2011
141
30
0
Technically no one gets its update from a carrier and no carrier has its own update server infrastructure. So technically is clearly wrong to say carriers provide the updates.

Second, for the non-branded versions (like my N910F) no carrier has any saying in when and how to release an update. It's Samsung to define, program, build and deploy the firmware.

Third, only for branded variants the carrier has a saying in how the firmware looks like, which addons have to be incorporated and they can test it, which may delay the publishing. But even then the build and final decision to publish is up to Samsung.

Having said this, it's absolutely clear that the lack of an update for N910F is only Samsungs fault. The carriers are not involved in any way.
I wont argue about the OTA server infrastructure, when I wrote my statement above I chose to say that to imply (and make strong contrast) that carriers (like ATT, Verizon, Sprint and T-Mobile in US, I was not arguing about the rest of the world) can only decide for their own variant. FCC is not pushing Samsung to wait what ATT, Verizon, Sprint or T-Mobile has to say about the SM-N950UZKAXAA device (or the OTA for SM-N950UZKAXAA). Now, what gets negotiated under closed doors when Samsung tries to launch new device (lets say what negotiations went when S8 was about to be launched) on a given carrier, that is everybody's guess. Verizon and ATT are so powerful that may negotiate some terms with Samsung that may affect updates. But these are things negotiated behind closed doors and are not a public knowledge.

The thing is that FCC is not forcing Samsung to wait Verizon, ATT, Sprint and T-Mobile to bless OTA for SM-N950UZKAXAA device. Technically, Samsung can do it whenever they feel like releasing OTA (given the OTA passes Google cert).
Now, what Samsung has agreed to behind closed doors .... ???
 

johnduggins

Member
Jan 17, 2011
32
5
0
Kansas City
It appears the hypothesis for the non-carrier variants is this:
Samsung won't push out the unlocked firmware to a country's unlocked phones unless/until all of the carriers the phone can work on in that country give their okay.

That situation would certainly explain why the unlocked phones don't get the updates until much later than the carrier versions. The majority of the phones on a network are that carrier's variant. The carrier wouldn't spend as much time testing out the unlocked firmware as their own and would get back to Samsung eventually. And if each carrier did that, the update wouldn't roll out in a timely manner.

I'm most familiar with the iPhone and Nexus updates so unlocked phones getting updates later than the carriers is new to me. For those phones, the manufacturer released a new firmware and made it available for download directly from them.
 

DummyPLUG

Senior Member
Dec 18, 2007
517
120
0
Hong Kong
I wont argue about the OTA server infrastructure, when I wrote my statement above I chose to say that to imply (and make strong contrast) that carriers (like ATT, Verizon, Sprint and T-Mobile in US, I was not arguing about the rest of the world) can only decide for their own variant. FCC is not pushing Samsung to wait what ATT, Verizon, Sprint or T-Mobile has to say about the SM-N950UZKAXAA device (or the OTA for SM-N950UZKAXAA). Now, what gets negotiated under closed doors when Samsung tries to launch new device (lets say what negotiations went when S8 was about to be launched) on a given carrier, that is everybody's guess. Verizon and ATT are so powerful that may negotiate some terms with Samsung that may affect updates. But these are things negotiated behind closed doors and are not a public knowledge.

The thing is that FCC is not forcing Samsung to wait Verizon, ATT, Sprint and T-Mobile to bless OTA for SM-N950UZKAXAA device. Technically, Samsung can do it whenever they feel like releasing OTA (given the OTA passes Google cert).
Now, what Samsung has agreed to behind closed doors .... ???
Don't take it too complex, you actually correct about samsung(so does every brand) can push what every firmware OTA they want(just need to agree to local telecom law, such as power level), but not many manufacture want to trade off a mobile connection stable firmware with a security update, unless it is in high demand.
For end user they may never see the impact on the network, but if you work as a telecom engineer you will know how serious it can be. Things get more complex when carrier use a mix of equipment from different brand due to cost cut.

---------- Post added at 12:09 AM ---------- Previous post was at 12:00 AM ----------

It appears the hypothesis for the non-carrier variants is this:
Samsung won't push out the unlocked firmware to a country's unlocked phones unless/until all of the carriers the phone can work on in that country give their okay.

That situation would certainly explain why the unlocked phones don't get the updates until much later than the carrier versions. The majority of the phones on a network are that carrier's variant. The carrier wouldn't spend as much time testing out the unlocked firmware as their own and would get back to Samsung eventually. And if each carrier did that, the update wouldn't roll out in a timely manner.

I'm most familiar with the iPhone and Nexus updates so unlocked phones getting updates later than the carriers is new to me. For those phones, the manufacturer released a new firmware and made it available for download directly from them.
Don't under estimate the power of apple :) and they do so many things behind it to ensure a smooth ride for end user, this is something other manufacture still can't complete with.
and about nexus, you know some firmware got buggy 3G/4G, right? and now you know what's going on.

---------- Post added at 12:12 AM ---------- Previous post was at 12:09 AM ----------

I am agree samsung can do better job on firmware update, at least in the US, they really need to step up and push the carrier harder.
 
  • Like
Reactions: jason504

dhaugru

Senior Member
Oct 22, 2015
143
38
0
I would usually say that it's not a good idea to return a phone because of the lack of updates. But.. latest model, high price and S8 got Oreo. So I understand You. I'm considering switching to Pixel 2XL but literally everyone is complaining about problems with that phone. Not just review websites but xda and people on Telegram too. And here getting a repair is almost impossible. They take Your phone ask for 80% of the phones price to fix it and if You disagree then You have to go to court and eventually after 8 months You will get Your phone or money back. So if my Pixel would have any problems I would be.. yeah.. then I saw Mi Mix 2 for $600 6/128 model.

But I guess I will just wait 1-2 more weeks and we will get new beautiful Oreo with even more improvements(UI, features) than Oreo for S8. Hopefully it will be worth waiting.

But Samsungs behaviour is really disappointing.
Buy the 2 XL. You won't regret your decision.

---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------

All that unlocked means is that you can use the phone with any carrier. Once you have it turned on through whatever carrier you use then the carrier pushes the update from Samsung to you. Which is the reason some people have received updates and others have not.

---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------

If I am wrong ain't it funny how everyone on ATT has all there updates? Tmoblie too.
I will add to your "youre wrong" camp.
 

BlueFox721

Senior Member
Jan 4, 2014
1,972
1,289
0
Foley
Um unlocked note 8 on AT&T , and still on August security patch. I have checked manually.
Nov. Security update leak posted on AT&T side

Only US carriers waiting for updates now are Verizon, Unlocked, and side carriers who can install main carrier Firmware...I do not keep up with the status of exynos sorry...
 
Last edited:
  • Like
Reactions: jason504

jason504

Senior Member
Mar 3, 2013
2,479
541
0
Um unlocked note 8 on AT&T , and still on August security patch. I have checked manually.
You have a lemon phone cause everyone I talked to on ATT has the update. As a matter of fact when I got my update it screwed my phone up because I didn't remove Sub. So I went to ATT to tell them what happened and they said yes we pushed a update through. Also I got a new phone because of this and as soon as I turned it on I went to updates and it was right there and I did the update before I even set my new phone up.
 
Last edited:

BlueFox721

Senior Member
Jan 4, 2014
1,972
1,289
0
Foley
You have a lemon phone cause everyone I talked to on ATT has the update. As a matter of fact when I got my update it screwed my phone up because I didn't remove Sub. So I went to ATT to tell them what happened and they said yes we pushed a update through. Also I got a new phone because of this and as soon as I turned it on I went to updates and it was right there and I did the update before I even set my new phone up.
Not a lemon...unlocked, he stated, if he did not add fota to apn he had to side load update so if that did not happen update notification never came...there is always a reason...people...lol
 

nuclearrage

Senior Member
Dec 2, 2011
486
194
73
Douglas
Not a lemon...unlocked, he stated, if he did not add fota to apn he had to side load update so if that did not happen update notification never came...there is always a reason...people...lol

Only have the ATTNEXTGENPHONE apn, so how would I add the fota so I can get the update?

Sent from my Galaxy Note8 using XDA Labs
 

ultramag69

Senior Member
Nov 6, 2007
5,885
1,021
243
Waratah
Guys, you can complain until you're blue in the face but nothing compares to updates for the Australian Note 8\S8\S8+...
For some stupid reason ($$$?) the Australian courts granted copyright to some icons used by all Android phones to Apple causing us to need "custom" roms that are different from other regions.
Seriously, it was for NFC which Apple doesn't support...
When the rest of the world gets updates they seriously don't do anything for us for another 6 months (how hard is it to delete a few icons),and if you're on a carrier phone then it may not come at all as the next lot of phones are out and they want you to upgrade...
Bloody Pathetic...
 
Last edited:

jason504

Senior Member
Mar 3, 2013
2,479
541
0
Not a lemon...unlocked, he stated, if he did not add fota to apn he had to side load update so if that did not happen update notification never came...there is always a reason...people...lol
I hear you but I was trying to explain to people that it's the carrier not so much Samsung.
 

BlueFox721

Senior Member
Jan 4, 2014
1,972
1,289
0
Foley
I hear you but I was trying to explain to people that it's the carrier not so much Samsung.
Yeah...right about that...i think, though, two updates since release (for U. S. carriers, sorry Australia) and a third leak for AT&T is far better than what has been before. Still yet, this is not what was said to be...we also know that devices usually get two major Android updates and we have not even had the first...I would rather see quarterly updates than monthly updates...and still see the two major updates...either way...the U.S has got most devices updated...the people that should be complaining are those in outside...especially Australia...they will not get updates like we will...silly Apple...lol...

Let's develop brain to brain communication and cut these yahoos out of the market...yay or nay...:D
 

kitch9

Senior Member
Feb 12, 2010
307
83
0
I think the decision has been made to get the KRACK fix done as quickly as possible so we're waiting for that. Google only released the code a while back I think.
 
G

GuestK00143

Guest
I hear you but I was trying to explain to people that it's the carrier not so much Samsung.
I admit I was WRONG. I just got the N950U1UEU2BQK1 (VZW) on the unlocked 950U1 from Best Buy. So it is carrier dependent now. I guess I'm never too old to learn lol. I'll post a link to the firmware. Oh and in case anyone is wondering Verizon did not add any any bloat to it.

View attachment 4345220
For Verizon N950U1UEU2BQK1
MD5: 79273cb604a82735f696634fdaec7b06
 
Last edited: