OnePlus had announced it will be merging its OxygenOS and its sister concern Oppo’s ColorOS for an unnamed Unified OS. This was all part of its OnePlus 2.0 vision and something tech media started calling as Oppofication of OnePlus and OxygenOS. There was a lot of backlash from the OnePlus community and the larger tech media and Android fans. Well, probably owing to the mounting pressure from these social groups, the company has decided to call off its plans for this Unified OS. In other words, OxygenOS and ColorOS will retain their individuality, even though the internal codebase between the two OSes will be the same.
Now, that’s a major development, albeit a bit nebulous, not gonna lie. So, let’s try to read into what OnePlus has disclosed recently.
OxygenOS 13: What to expectAt a recent media roundtable, OnePlus c-suite said, “Our software philosophy for Oxygen OS has always been to offer users a light and clean experience that is close to stock Android and oriented towards usage globally. With Oxygen OS 13, we want to deliver an experience that long-time OnePlus users will be familiar with while ensuring it upholds hallmarks of Oxygen OS, like a fast and smooth experience, burdenless design, and ease of use. Oxygen OS 13 will retain its unique visual design and a range of exclusive customization features.”
Now, there are a few mixed signals here. As in, on one hand, they are talking about going back to their vanilla Android roots but also plans of continuing the customization features. Now, we are not sure if they are referring to the core OxygenOS features like Shelf, or the new thingies like the ColorOS launcher.
Also, one other thing that we came to know is the involvement of Google in the cooking of this new software. However, whether this is just the usual role it plays in guiding Android updates, we aren't sure. We will have to wait and see how this would materialize.
For more news, buying guides, features, reviews, and everything else tech-related, keep reading Digit.in.
from Mobile Phones News https://ift.tt/y2fWPKc
No comments:
Post a Comment