LG V30 Leaks: Snapdragon 835, 6GB RAM, Dual Camera

LG is set to reveal its flagship device, the LG G6, at the Mobile World Congress on February 26th. The company has implemented a clever marketing approach to generate excitement for the product. Numerous renders, prototypes, and live images have been released, leaving little to the imagination. In addition to LG’s teaser campaigns, speculations about the upcoming LG V30 have begun circulating among rumor mills, even before the official announcement of the LG G6.

LG V30 Leaks: Snapdragon 835, 6GB RAM, Dual Camera – Overview

LG launched the V-series in 2015 with the LG V10, targeting the phablet market. In the previous year, LG focused on making the V20 exceptional after the LG G5’s underwhelming sales performance. Despite having impressive specifications, the V20 failed to captivate consumers based on sales figures. A recent Weibo post suggests that LG is considering transitioning its flagship series from G to V, making the LG V30 the event flagship.

The LG V30 is expected to incorporate the Qualcomm Snapdragon 835 processor, which LG was unable to secure for the LG G6 due to Samsung’s early acquisition. This choice aligns with the latest flagship trends. The device is rumored to feature 6GB RAM, a standard for high-end smartphones, with the LG G6 also expected to have this amount of RAM. Additionally, the smartphone will reportedly boast dual cameras, one on the front and one on the back, making it the first device to offer this feature.

The dual-display functionality will likely return, and it would be interesting to see if LG introduces a dedicated AI feature, similar to HTC’s Sense Companion. The LG V30 is anticipated to be unveiled in Q2, with a possible release in late August or early September. As rumors unfold, more details about this device will surface. Keeping in mind the nature of speculations, take this information with a pinch of salt.

Origin

Feel free to ask questions concerning this post by writing in the comment section below.

About The Author

Reply

error: Content is protected !!