Galaxy S8 Oreo Update Stopped Because Of This Grave Reason

After what felt like an eternity, owners of the Galaxy S8 and S8+ were naturally overjoyed to finally receive the much-awaited Android 8.0 Oreo update. And, naturally, they were equally cross when Samsung halted and pulled out the update almost immediately. While they definitely have reason for their ill-feelings, Samsung has an even bigger reason why it did so. Apparently, the update has caused some handsets to randomly reboot, which would have been an even bigger fiasco than pulling it out before it spreads any further.

There does seem to be some truth to Samsung's excuse. According to SamMobile, some early updaters did report experiencing unexpected reboots. While not as fatal as, say, LG's notorious bootloops, they are just as frustrating, especially if they eventually lead to data loss.

Fortunately, Samsung hasn't ignored these complaints. Although it says there have only been a limited number of cases, pulling the update out hints it suspects it would be much more than that. Here's what Samsung had to say:

"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."

All good, right? Not exactly. This would have probably been acceptable if not for that fact that Samsung started its Oreo beta program for the Galaxy S8 and S8+ back in November. And that would presumably have been preceded by a limited or private testing period. Samsung definitely had a lot of time to have ironed out something as serious as a bootloop, especially if it happens on not a few devices.