All replies
-
1 of 1 people found this helpfulWhen Samsung is done with the update. T-Mobile doesn't write the code for the phones.
-
Acknowledge that T-Mobile doesn't write the code! That is not what I am trying to find out.
When is a reasonable time frame for Us users to expect to be able to download Oreo for our S8s, considering that T-Mobile has to "package" code when received from Samsung to put it out over the air
Thank you
-
rsnic wrote:
Acknowledge that T-Mobile doesn't write the code! That is not what I am trying to find out.
When is a reasonable time frame for Us users to expect to be able to download Oreo for our S8s, considering that T-Mobile has to "package" code when received from Samsung to put it out over the air
Thank you
T-Mobile can't give you an answer because it's not up to them... Think about for a minute...
T-Mobile does not package the code. It's already done and the update comes from Samsung servers... It's like the biggest BS lie being passed around for years.
All carriers do is test it and when it passes those test Samsung prepares it go out.
Can you tell me when the Hawaii rail is going to be completed? You wouldn't be able to give me an estimate simply because you are not working on it. I don't understand why people expect a date or some sort when thinking rationally. If you expect T-Mobile to give a date, well then sometime after Samsungs date which Samsung has never given themselves.
-
Keep in mind that even after Samsung finishes it's changes T-Mobile will still have to put it's own spin on it adding more time to the process. Have patience... Better to have a polished version of Oreo.
-
That has been passed around and is utter BS. Samsung admitted in multiple occasions that they get everything in advance from carriers and they assign a team to work on said update. They even charge for it too. They are not going to hand over proprietary code to allow carriers to do as they please.
Sony and Google did an AOSP project and learned that carriers were the least of the delay problems. At most it was only a month. The problem was more with the FCC and licensing. One of the reasons Google decided to push out the HAL when they completed it to shorten the time for OEMs to push out updates. The average time for this was cut down from an average of 6 months to 3 months or less. The average time for carrier testing or involvement was 1-2 months depending if the OEM wanted more or changes to code if that code is proprietary for capability issues.
OEMs could stop these "carrier spins" but they love charging for it. They will not because they make money before a device is ever sold, and when something happens consumers are 99% to blame the carrier instead of them.
-
-
I see frustration in your response. Let me brake it down for you from client prospective and why your clients bug you for the dates.
1. We as T-mobile client, bought phone from T-mobile which has been branded by T-mobile and we are paying T-mobile for the phone. It is natural for people to bug T-mobile for the support and update not Samsung.
2. The reason why user bug carrier for the update is that, Carriers are continuously failing to set the proper expectations. In other words carriers are poor in planning and communication. When new update release It is a project for Samsung and T-mobile team to run with it. Writing the project plan with estimate completion date is very normal practice and it is even followed by small businesses. The only problem here is T-mobile is not willing to share the estimated completion date with users. When Samsung start the work on update project, I don't see any reason why Samsung will not share estimated completion date with carriers and I don't see why carriers can't estimate update push windows based on that.
The real reason behind all these issues is that carrier choice to not give any update window to their users, they are firing over Samsung solders. Clearly it is not healthy for carrier business to give update window and set people expectations in any way and face their criticism later. Rather it is more healthy for business to stay silence and deliver surprise one day to all the users and there will be no one to complaint or blame T-mobile.
Not sure when carriers will understand that it is impotent pieces of information they should share with all the users on time or they just have this specific department running with no planning what so ever.
-
-
dharmpreet wrote:
I see frustration in your response. Let me brake it down for you from client prospective and why your clients bug you for the dates.
1. We as T-mobile client, bought phone from T-mobile which has been branded by T-mobile and we are paying T-mobile for the phone. It is natural for people to bug T-mobile for the support and update not Samsung.
2. The reason why user bug carrier for the update is that, Carriers are continuously failing to set the proper expectations. In other words carriers are poor in planning and communication. When new update release It is a project for Samsung and T-mobile team to run with it. Writing the project plan with estimate completion date is very normal practice and it is even followed by small businesses. The only problem here is T-mobile is not willing to share the estimated completion date with users. When Samsung start the work on update project, I don't see any reason why Samsung will not share estimated completion date with carriers and I don't see why carriers can't estimate update push windows based on that.
The real reason behind all these issues is that carrier choice to not give any update window to their users, they are firing over Samsung solders. Clearly it is not healthy for carrier business to give update window and set people expectations in any way and face their criticism later. Rather it is more healthy for business to stay silence and deliver surprise one day to all the users and there will be no one to complaint or blame T-mobile.
Not sure when carriers will understand that it is impotent pieces of information they should share with all the users on time or they just have this specific department running with no planning what so ever.
1. Just because it's T-Mobile branded even in a court of law even says the OEM is liable. See LG and bootlooping phones. Not one carrier has to do a thing and it's all on LG even if it carrier branded. So people have the wrong way of thinking things, and it's time to change it if we want better support don't you think? I honestly been saying this for years. Notice Europe, and Asian have better overall support? We point to carriers and they point to OEMs. Think about it.
2. When am I going to get my pizza I just order? When is the Rail in Hawaii going to be finished? You are not going to know the answers to these questions because you don't work or have any knowledge about these. So exactly how is T-Mobile going to communicate something they are not working on or even know. It's unrealistic expectations. Like I said easier Samsung doesn't even release these dates for their unlocked and unbranded. Even Google doesn't release when they'll finish with their next major update. So at what point you think T-Mobile will get that information? The company I currently work for we have projects with Samsung and Sony and both have never given us a projected finished date for any of those projects. We are almost finished with a project and we only know this because we are currently working on the project side by side with them on various aspects. If we didn't and had to wait for them we wouldn't know. Trust me my lazy boss has asked multiple times for a timeline and the best answer we got was... "Soon". Sound Familiar?
3 major manufacturers released timelines, and they all had one thing in common. They took ownership for all of development. Carriers didn't touch code like the online media, and people spew from those online media. In fact Sony, and Googles AOSP project proved this as well. One of the reasons if you noticed Google has stopped saying carrier delays in their official statements. The real reason why dates are not given because something can happen and delay updates or large projects. OEMs don't release dates to save face than to miss a soft date that people will treat like promises like you said. They sure are glad though people in the states blame carriers.
-
-
-
-
Google play ---> search Oreo UI for Android Beta
-
-
Cheu Hoi!
I fully understand who controls what. All I'm trying to get is an estimate
Have a great day
-
Since they are not working on the update they can't give an estimate. Most people take these estimates as promises. They'll get blamed if it is missed even if the update is out of their control. Best to ask Samsung and see what they say. Keep in mind they don't even give estimates on their products that are not branded.
-
Talk about a major buzz killer. Jeez, can't even get excited about anything on this site without killing it from these responses on here. Man, I thought forums were supposed to be positive, not starting problems, but it looks as if you ask something, it is a problem started.
-
So pointing out the truth is a buzzkill and not getting excited? Just because it's not something a person wants to hear isn't the forums fault or the people telling it how it is fault. In a perfect world things would be different but alas we do not live in a perfect world.
-
Sounds like someone does not have friends. Grumpy a lot?
-
sslman71 wrote:
Sounds like someone does not have friends. Grumpy a lot?
Usually the one who makes those kinds of statement online tend to be trolls. yes we can read context in everything. I just cut to the chase and don't sugarcoat things for anyone. I think the world is lacking more people like me.
-
-
-
1 of 1 people found this helpfulAnd actually if you read that, that is just telling people what to expect from the update when it's done.
The update is actually not complete for any of their devices at this time. They just released beta 4 today only. This is for t-mobile and spring customers that enrolled in the beta. It does seem like it is near completion though. I would suspect it would be out either late January or February based on the S7 Android 7 beta to when it was released when I was in that beta back then.
-
I have 2 Nexus 5's that were updated to Oreo and had nothing but problems with over heating, constant rebooting
and shut downs that the phones became unreliable so I bought me a used LG stylo 3 plus just to have a reliable phone.
-
-
-
-
You want an update every 2-4 weeks then get an iPhone.
-
February or so. Same as it has been for years.
-
Hey, all! I know this is going to be the final bucket of water on the fire, but tidbits is right -- we don't have a date to share. I think that theartiszan makes a great point as someone participating in the beta -- as long as these beta trials are ongoing, it's unlikely that the update would be pushed (though I agree that it would be a rad holiday gift).
Ultimately, SW updates start with the OS, then go to the MFR, who details them for each carrier. Then the SW comes to us for testing, and goes back for final edits. When it's all done, new software is pushed to your equipment. It's precisely the number of steps involved in this process that prevents a timeline, but once our Software updates page gets its Oreo facelift, you can follow along with the process!
-
Well,
All I wanted to do was to get a better understanding of what is going on; did not mean to start such a furor
Anyhow, to all Merry Xmas & Happy Holidays!
-
It's a totally reasonable question to ask, rsnic! I know you might not get the Oreo update, but I hope you get everything else on your list.
-
Even if T-mobile can't control when it comes or Samsung whether they can give an answer, but when someone ask a question or gives feedback to be excited about getting what they asked about, and then someone comes in and just says, "Not going to happen," (my quote), in not exactly said this way, but meaning this, is a buzz kill. Buzz kill is when someone loses that excitement over someone saying something that brings that excitement down or kills the moment. That was killed right after the OP. Even if that wasn't meant for or done on purpose but it is a buzz kill to hear.
-
The truth can sometimes be that way.
-
sslman71 wrote:
Buzz kill is when someone loses that excitement over someone saying something that brings that excitement down or kills the moment. Even if that wasn't meant for or done on purpose but it is a buzz kill to hear.
Sort of like when someone slips up and tells you Santa isn't real.
-
-
sslman71, sincere thanks for your feedback. I know what you've said to be 100% true -- and as an eternal optimist, it's not fun to be the one to deliver the buzzkill news. The truth is that hinting that we'll be able to offer a timeline would honestly be *worse*, because we won't. As much as I don't love telling folks that we can't provide one, I would really hate pretending that we can and prolonging the letdown.
Our Software updates page's lovely (and timely!) Oreo facelift is complete! As we agree upon starting the update processes with MFRs, we'll add devices to that page so that customers and Community members can follow along with the progress -- from development, to testing, to complete. Since we know we can't offer timelines, we feel like being transparent about where we are on the journey from "agreed to update" to "update ready" is the next best thing.
I hope that helps a bit, and thanks again for posting.
- Marissa
-
-
-
-
-
I wanted to add that link in the first thread is about the update, which is in BETA and not what is officially out.
-
Not trying to spark another heated debate, but can anyone offer anything as to veracity of this post:
Samsung releases Oreo kernel source code for the Galaxy S8/S8+
-
They are complying with GPL. They started to push out the update in Germany, and they had already been pushing it out in Korea. That is the source for the Exynos version. So when the Snapdragon version happens to start getting updates we'll see the same thing.
-
-
tidbits et al,
Got a Google Feed this morning about Android 8.0 out for testing on a device, so I just thought I'd check again for my device. So I went to software update on my Samsung S8 (T-Mobile is my carrier) and manually checked for updates.
After about 20 minutes or so, voila, I now have Android 8.0 on my phone, fnally
Excelsior!
