Evan Blas, notorious for his accurate leaks and inside information, has unveiled new evidence for the Google Pixel Watch. The unannounced device has been talked about for a long time. Blass shares a screenshot with a direct reference to the code name “Rohan”.
On Twitter, Blas shared an image with a broken JPG. The name on the screenshot is Google Pixel Rohan. Rumors and previous reports have long referred to “Rohan” as an internal code name for Google’s Pixel smartwatch. Next to the code name of the Google Pixel Watch is another reference to the name along with the drop-down menu related to Wear OS 3.1. “It won’t be long now,” Blas tweeted.
It won’t be long now. pic.twitter.com/kIry1QdYNK
– Ev (@evleaks) April 15, 2022
Blass has a great reputation for gaining insight into technology. Given how reliable it has been in the past, this evidence really joins a growing pile indicating the existence of the watch.
Google has been rumored to have been working on the Pixel Watch for many years. In recent months, however, it has become clear that Google may be preparing for an upcoming revelation. In January, John Prosser said Google would hold an event on May 26. Here the company can reveal the smart watch.
According to reports, the Google Pixel Watch will run on Google’s Wear OS 3 version. Interestingly, the screenshot mentions Google Wear OS 3.1, although OS 3.2 is available in the Samsung Galaxy Watch 4 series
The renderings also show that there will be a minimalist design with a thin round dial. There will probably be a crown on the side. Like the Apple Watch, Google can look at an assortment of its own watch bands.
There has also been talk that the Pixel Watch has an iteration of the next generation of Google Assistant. Mentions of “PIXEL_EXPERIENCE_WATCH” have been found, suggesting that it supports Android’s own features.
There is still no firm confirmation that Google will introduce the Google Pixel Watch in May. However, as the evidence continues to flow, there is more reason to worry about the possibilities.
Image credit: @jon_prosser
Source: AndroidAuthority
Add Comment