on 09-02-2018 13:47
The Oreo update is now being rolled out in Germany, Poland and India.
Does O2 have a release date yet?
Solved! Go to Solution.
on 29-03-2018 11:00
on 09-02-2018 14:03
09-02-2018 14:30 - edited 09-02-2018 14:32
09-02-2018 14:30 - edited 09-02-2018 14:32
wrote:
The Oreo update is now being rolled out in Germany, Poland and India.
Does O2 have a release date yet?
Not currently, but I would stress that for most vendors, each country is essentially classed as a 'market' and the roll-out plan can vary wildly from one to the other. It's not set in stone, but the German, Polish and Indian markets tend to be a typical seeding ground for new updates, and thus tend to be the first to receive them.
I can confirm we're testing Oreo for S8 devices though, and working with Samsung on our outcomes - but have no ETA or date available. As soon as thing's are a bit clearer, i'll keep everyone posted.
edit: Forgot to mention, if you're running an 'open market' device (eg, not purchased from O2) then your update would come directly from Samsung whose release schedule may differ from our O2 updates. Only Samsung would know for sure what sort of schedule they have for this.
on 10-02-2018 17:04
on 12-02-2018 07:27
on 12-02-2018 07:27
DO we know how long this takes to test? I have friends on unlocked devices who got their update yesterday.
There are lots of features i want from the new upgrade
on 12-02-2018 07:49
on 12-02-2018 07:49
on 12-02-2018 11:08
on 12-02-2018 11:08
I don't understand why O2 have to test it, Samsung have already with the long beta test. It's not like my handset came bundled with any O2 crapware liker they used to.
As of now Oreo is rolling out to unbranded S8s in the UK. Also carriers in the following countries are rolling it out. :
on 12-02-2018 11:12
on 12-02-2018 11:12
Now rolling out to EE customers in the UK. O2 lagging behind EE, that's not a good look.
on 12-02-2018 11:29
on 12-02-2018 11:29
on 12-02-2018 15:40
on 12-02-2018 15:40
wrote:
Now rolling out to EE customers in the UK. O2 lagging behind EE, that's not a good look.
Are we, though? 😉
You and I are different people and at dinner time, we'll have different requirements - as a result of my pretty restrictive diet, mine would probably arrive first (since there's less to cook), but it started getting cooked at the same time as yours.
And it's the same with software updates - not all networks' requirements and testing are equal. If network 'x' got the update first, that could be because they don't have the same features or requirements needing tested or updated, or it could simply even be because they didn't encounter the same issues we did during testing. Point I'm trying to make is, don't assume we're 'lagging behind' just because we don't have it at the same time - I get that's what it may look like from a certain angle, but at the end of the day when our update drops, it'll have been tested fully to ensure the customer experience is as it should be, and all our network features work entirely as expected - both for the customer and from a network perspective. And just on that, just because 'network x' doesn't experience calling issues (for example) on 'software z' doesn't mean 'network z' won't - different systems and technologies could lead to further testing or issues needing resolved.
We know you guys want Oreo on your S8 and we're working on it - we don't want you getting a half baked update that has issues calling/texting/whatever it may be. I'll keep everyone posted when there's more to share but for now, please understand pushing out an update isn't a press of a button. It's far more complex, and for some more than others.