OnePlus is definitely working overtime to ensure that its recently launched OnePlus 3 doesn’t get drowned in controversy and bad press, despite already encountering hurdles in just a few weeks. The OxygenOS 3.2.0 OTA that was supposed to address some complaints had to be abruptly pulled out due to equally serious issues. Now the company is rolling out update 3.2.1 to both continue the previously halted update as well include fixes to the broken updates, though it hasn’t responded to some other concerns raised in the previous OTA.
It is quite unfortunate, though not really unheard of, when an update that is intended to fix bugs actually introduces bugs itself. That was what OnePlus 3 owners encountered when they upgraded to OxygenOS 3.2.0. The biggest, and perhaps most grievous, complaint was how the update broke SIM card recognition on the smartphone, leaving the OnePlus 3 practically useless as a phone (though, of course, it could still be used when connected to Wi-Fi).
That is one of two things addressed by the new OTA, now bumped to version 3.2.1. The other one relates to some unidentified notification issues. Those two come on top of the previous update, which, among other things, added an sRGB mode and better RAM management. Here’s the full, cumulative list of fixes in OxygenOS 3.2.1:
• Fixed some notification issues
• Addressed SIM recognition issue
• Enabled sRGB mode in developer options
• Improved RAM management
• Improved GPS performance
• Enhanced audio playback quality
• Updated custom icon packs
• Improved camera quality/functionality
• Fixed some issues in Gallery
• Implemented latest Google security patches
• Fixed bugs in Clock/Music apps
Some questions, however, remain unanswered. The OnePlus 3 was previously reported to be sending its IMEI over unencrypted HTTP when checking for updates, and OnePlus is still silent on the matter.
The update also doesn’t include the just announced July security patches from Google, which isn’t exactly surprising considering the timing of OnePlus’ update.
Given the previous mishap over the 3.2.0 update, more wary users might want to wait for 48 hours or a bit more for the update to be more widely tested before diving into another update.