OnePlus vowed to speed up the lead time for software updates when the company fused Oxygen OS and Hydrogen OS earlier this month. The phone maker is making good on that promise with the rollout of OxygenOS community build 3.5.3 for OnePlus 3.
Recall that OnePlus 3's OxygenOS version was updated to 3.5.2 only two weeks ago with a pack of changes like the "kill all background processes" button in the Recent menu, among others. Half a month later, we are now seeing a lot of significant improvements in the community build, including the ability to set the AOSP clock as default, a cellular data firewall and new UI for your contacts, and much more. Here are all the improvements in v3.5.3:
- AOSP clock as default clock
- Capability to uninstall some preinstalled apps, like FileManager, Weather, Recorder, MusicPlayer
- Expanded screenshots, you can now save a long screenshot of a scrollable page to cover more contents
- Cellular data firewall, you can control whether an app is allowed to use cellular network or WiFi
- "Favorite contact setting" in Priority mode
- Setting menu adjustment in Messages, added option to vibrate phone when receiving SMS
- Contact UI redesign
- Fixed community build cannot flash back to official build issue
- General bug fixes
The OnePlus 3 update doesn't include Android 7.0 Nougat, unfortunately. It's meant only for another Marshmallow-based community beta for OnePlus 3, though it is safe to anticipate the Nougat update sooner than later.
As always, this beta version could accompany a few bugs and compatibility issues with TWRP, though you can back up your data to avoid untoward consequences after installing the latest build.
If you're on the stable build, you'll need to flash the update. Keep in mind that should you decide to migrate back to the stable build from the community build, expect that your data and cache will be deleted.
Have you checked out the OxygenOS 3.5.3 community build? What troubles did you encounter? Share your experience in the comments below!
from Android Authority http://ift.tt/2dpbJ6u
via IFTTT
No comments:
Post a Comment