OnePlus 9, OnePlus 9 Pro Get New Oxygen OS 12 Update in India With March 2022 Android Security Patch


OnePlus 9 and OnePlus 9 Pro are receiving the brand new Oxygen OS 12 replace in India. The brand new firmware replace bears model quantity C.47. Additionally it is seeing a gradual rollout in Europe and will probably be quickly obtainable in North America, as per the corporate. The replace options a number of bug fixes and comes with the March 2022 Android safety patch. This Oxygen OS 12 replace is alleged to enhance the general system stability of the smartphones. Additionally it is claimed to repair points associated to incorrect operator names and the lack to ship MMS at occasions.

The official post shared on the OnePlus discussion board mentions the detailed changelog of the Oxygen OS 12 (C.47) replace. As talked about earlier, this replace is accessible for the OnePlus 9 and the OnePlus 9 Pro.

OnePlus 9, OnePlus 9 Pro replace changelog

OnePlus has begun the incremental rollout of this replace for the OnePlus 9 in India, the place it arrives as LE2111_11_C.47. The OnePlus 9 customers in Europe are receiving the LE2113_11.C.47 construct and North American customers will get the LE2115_11_C.47 construct. Moreover, OnePlus 9 Pro customers in India are set to obtain the LE2121_11_C.47 model. It’s being rolled out in the European area as LE2123_11.C.47, and the North American area will obtain the LE2125_11_C.47 construct.

The changelog says the OnePlus 9 and OnePlus 9 Pro are receiving the March 2022 Android safety patch with this replace. There are additionally mentioned to be enhancements to system stability. The handsets get fixes for the show of incorrect operator names. The Chinese language tech large additionally claims to have mounted a problem with the lack to ship MMS at occasions. The replace brings optimisation for secure communication and digital camera fluency for taking photos.

OnePlus has additionally confirmed in their publish {that a} SafetyNet bug that was inflicting points with Google Pay has been mounted. The error was being attributable to this replace and has already been resolved on the server-side.




Source link

Leave a Reply

Your email address will not be published.