Recently, the Nothing Phone (2a) surfaced in a leaked render, revealing a surprising omission of the Glyph Interface along with a few design changes. However, it now turns out that the rendering of the upcoming offering was inaccurate.

Nothing Phone (2a)render

This has been confirmed by the publication that leaked the info as well Steve Hemmerstoffer (aka onleaks). Read on to know all the details.

Leaked Nothing Phone (2a)’s render was inaccurate

The Nothing Phone (2a) is an upcoming mid-range offering expected to be positioned below the flagship number series. It was assumed that the brand would be cutting costs by ditching the Glyph Interface as seen on the Phone (2a) render.

Another tipster Evan Blass was skeptical of the leaked render of the Nothing Phone (2a). He added that the CAD-based leaked render wasn’t Foxconn-sourced which is usually the case with Steve’s leaks. Hence the accuracy isn’t applicable.

Secondly, Nothing is teasing the upcoming smartphone with the tagline ‘See the world through fresh eyes’. This hints at the possibility of a redesigned camera island.

The publication cross-checked the Nothing Phone (2a)’s leak and found that the source had furnished Steve with manipulated renders. It belonged to an unreleased Nothing device that never made it to the market. Additionally, it can also be seen in one of the Phone (1) promo videos.

Blass also shared a side-by-side comparison of the latest and previously leaked renders of the Phone (2a). It turns out that the initial leaks (hands-on live image) were indeed right. The Phone (2a) could get a circular camera module with two sensors placed horizontally. It will be surrounded by Glyph lights that should excite Nothing fans.

Nothing Phone (2a) live shots emerge to hint front, rear design

The Nothing Phone (2a) is expected to debut at MWC in Barcelona later this month. Although the exact date has not been revealed, the London-based company is conducting an event on February 27.


Please enter your comment!
Please enter your name here

Captcha verification failed!
CAPTCHA user score failed. Please contact us!