OnePlus 7 Pro has launched a few days ago, and there are a number of cool features in it. Many of those features are part of Oxygen OS 9.5, which is the latest variant of the company’s proprietary ROM. But one feature that stood out among all software-based features was Zen Mode. It does nothing, except for making your phone partially useless for 20 minutes. Once you enable it you can’t use your phone for anything, except for receiving calls, making emergency calls and camera. Zen Mode, once enabled, can’t be turned off before its duration of 20 minutes runs out. Think of it as Android’s Do-Not-Disturb mode, but with a forceful approach.
What’s coming to OnePlus 6 and 6T
Now, while the world debates the logic behind such a feature in their device, OnePlus has revealed that Zen Mode will eventually also be making its way to OnePlus 6 and 6T via OTA updates. This was confirmed by the company in an emailed response to Android Authority, and you can be happy or unaffected by this news depending on how you feel about this feature.
However, one more thing has also been confirmed by the company in that same email. And I’m sure that you won’t be happy about it. The company said that Nightscape 2.0 – another major feature launched in OnePlus 7 Pro – is not going to be added to OnePlus 6 or 6T at any point of time because of hardware limitations. While OnePlus didn’t specifically explain which hardware limitations it’s talking about, our guess is that they may be talking about the new 48mp sensor which has been added to OnePlus 7 Pro.
Oxygen OS 9.5 also comes with screen recorder functionality, but the company has not confirmed whether this functionality will also make its way to the older devices or not. In short, right now only Zen Mode is that rare confirmed Oxygen OS 9.5 feature that’s certainly coming to OnePlus 6 and 6T. Let’s see whether other software-based features accompany it or not!
Get these updates via email for $0 (Limited time)
We will never share your details with anyone.
Thank you for subscribing.
Something went wrong.