Oneplus sidesteps brickgate: updates resume after internal scare

A potential disaster was narrowly averted this weekend for OnePlus users, as the company swiftly identified and resolved issues that threatened to brick handsets during recent software updates. The near-miss, involving OxygenOS versions 16.0.7.XXX and 16.0.5.XXX, highlights a growing concern about the reliability of over-the-air updates and the potential for catastrophic user experience.

The glitch and the quick response

The situation unfolded rapidly. OnePlus initially paused the rollout of two OxygenOS updates after discovering that one build, not yet publicly released, was causing abnormal behavior – specifically, boot loops that rendered devices unusable. The company’s proactive move to halt the update before widespread deployment proved critical, preventing a potentially massive wave of bricked phones. No external users were reportedly affected, a testament to OnePlus’s internal monitoring systems.

OnePlus has now resumed the rollout of both updates, assuring users who have already installed them that their devices are safe to use. For those who haven't received the update, it's gradually being reintroduced. This swift action stands in stark contrast to the often-glacial response from other manufacturers, particularly Google.

Google's troubles: a tale of two woes

The OnePlus episode serves as a pointed reminder of the challenges in software deployment, especially when compared to Google’s recent struggles with its Pixel devices. Users of Pixel Watches have been grappling with issues like missing overnight blood oxygen and skin temperature readings for months, with little communication from Google. Furthermore, a separate bug prevents some Pixel Watches from displaying sleep data, despite the information being available in the Fitbit app. The situation escalated further when Google took over a month to acknowledge that a March update caused some Pixel phones to enter boot loop mode, effectively bricking them.

But what’s truly striking is the difference in transparency and responsiveness. OnePlus’s quick identification of the problem, followed by a clear and concise statement to customers, is a refreshing change from Google’s often opaque approach. While Google’s Pixel line aims for premium status, its customer service frequently falls short, leaving users feeling abandoned and out of the loop.

The contrast is palpable. OnePlus isolated the issue internally and halted the public rollout to protect its user base. Google, on the other hand, seems to exhibit a reluctance to acknowledge problems with its updates, let alone rush to provide solutions. The question remains: is Google truly committed to the Pixel line, or is it content to let user frustration simmer?

The incident underscores a critical point: in an increasingly interconnected world, a reliable software update process is not just a convenience—it’s a necessity. OnePlus’s handling of this situation demonstrates a commitment to user satisfaction that Google would do well to emulate.