[Update: Rollout resumed] This is why Samsung stopped Galaxy S8 Oreo update

Update [February 22, 2018]: After about a week, Samsung has resumed rolling out Android Oreo to the Galaxy S8 and S8+. The new update has been spotted in Germany, where it weighs about 530MB and comes with software versions G950FXXU1CRB7 and G955FXXU1CRB7, respectively.

Note that the update is rolling out to all Samsung Galaxy S8 and S8+ handsets, including those who had already upgraded to Oreo. If you hadn’t received the update during the initial wave, however, you’ll get a much bigger file than the 530MB rolling out to those who had already upgraded to Oreo.

Yesterday, we reported that Samsung had stopped the Galaxy S8 Oreo rollout for reasons only known to the Korean company. Given how unexpected this move was, many fans expected the company to at least give a statement on what really went down, forcing it to halt the S8 Oreo, especially after months of patience.

Well, folks at SamMobile reached out to Samsung for an explanation and apparently, they have one, which reads as follows:

“Following a limited number of cases where Galaxy S8 and S8+ devices have rebooted unexpectedly with the Android 8.0 Oreo, we have temporarily stopped the rollout of the update. We are investigating the issue internally to ensure that the impact to the affected devices is minimized and the rollout of the update can resume as quickly as possible.”

In Samsung’s world, the words “as quickly as possible” could mean anything from days to weeks, but hopefully the former is the case.

We haven’t experienced any issues with our Galaxy S8 handsets, but from Samsung’s words, it appears that some users have been suffering random reboots after the Oreo upgrade. It’s strange that this is happening even after Samsung held quite a lengthy beta testing program, but then again, it shouldn’t be anything new when it comes to software updates.

Posted by

Each one Reach one Teach one. Football Droid. Email: [email protected]ul.com

Leave a Reply

Your email address will not be published. Required fields are marked *