Not so long ago, Carl Pei, co-founder of OnePlus, and known for his innovative designs, unveiled the Nothing Phone 1. Now there is some confusion over when precisely Android 13 would be released for the Nothing Phone 1, despite the fact that the company has promised three years of upgrades.
Launched with the promise of "good" Android compatibility, the Nothing Phone 1 has been met with mixed consumer reviews. Starting with Android 12, you'll get OS upgrades for a full three years and security patches twice a year for the next four years. It's comparable to the warranty terms for OnePlus devices.
However, Android 13 is now available and being rolled out to Pixel phones and in beta testing for smartphones from OnePlus, Oppo, Xiaomi, and more.
Meanwhile, Nothing hasn’t announced the Android 13 update schedule for Nothing Phone 1. Carl Pei provided an intriguing response to the question by stating that a phone is "more than simply its specifications, functions, and version numbers."
Though that makes some sense, it is hardly the statement that will win over or please its current and prospective customers. Although the rate at which software is updated isn't the deciding factor in whether or not a user enjoys their phone, it is an essential feature of any smartphone. In many cases (say with iPhones), it’s a significant selling point. Nothing boasts that the gadget offers "just the finest of Android" and a "perfected" experience on its website.
When there are still software issues with the current builds, answering a reasonable query like this might be perceived as a little off-putting, and Nothing's update commitment has already fallen behind most of the competitors. Max Weinbach has been tweeting about his first impressions of the Nothing Phone, noting problems like the phone's inability to auto-rotate.
Whatever the situation, we expect Nothing will provide an update on its intentions for Android 13.
For more technology news, product reviews, sci-tech features and updates, keep reading Digit.in.
from Apps News https://ift.tt/y5xLpgd
Comments
Post a Comment