OnePlus has done it again. The Chinese company has cancelled the roll out of OxygenOS 5.0 update based on Android 8.0 Oreo for the OnePlus 5 because of a bug. Earlier today, a staff member of OnePlus posted this news on the same page where they announced the roll out of the OTA update last week. Sadly, OnePlus did not reveal which bug has stopped the roll out. Going by OnePlus' nature, this bug might be a critical one.
The good news, however, is that OnePlus confirmed the OxygenOS 5.0.1 roll out would happen very soon. "Because of a bug on Oxygen 5.0, we have cancelled its global release. And we're preparing for Oxygen 5.0.1; the partial release will go alive soon," said Jimmy Z, a staff member at OnePlus.
OnePlus did the same with the OxygenOS 5.0 update for the OnePlus 3 and 3T. Firstly, they rolled out the update; then they pulled back the update because of a 'bug.' It is also to be noted that several users who updated their OnePlus 5 smartphone to the latest version are complaining app crashes and various bugs, and some users even reported that the update removed the Airtel VoLTE support in India.
OnePlus will roll out a new version of the update very soon. Also, our OnePlus 5T review unit which we updated to Open Beta 1 based on Android 8.0 Oreo is also experiencing severe app crashes, and the battery life is pretty ordinary too. Nevertheless, in our case, the update is still in beta stages, but in the OnePlus 5 case, the update is rolled out as a stable one.
Thankfully, OnePlus rolled out the update to a small batch of users and it even promised that a broader roll out of the OTA update for OnePlus 5 would begin in the coming weeks. The OxygenOS 5.0 update for the OnePlus 5 added all the Oreo features such as Picture-in-Picture (PiP) mode, Notification Dots, Smart Text Selection, Redesigned Settings app and quick toggles, bundled notifications, granular storage controls, extra battery settings. It' said to see OnePlus keep repeating the same again and again. Hopefully, the company is not pushing the updates just for a namesake and pull them back again, blaming some critical bugs.