HTC Appears To Be Building Google’s Pixel 2 Phones Powered By Snapdragon 835

While nothing is yet official, there is some evidence to suggest that HTC will be building Google's forthcoming Pixel 2 and Pixel XL 2 handsets, which are due out later this year. That would not be shocking—HTC built Google's original Pixel and Pixel XL phones last year and the two have been partners in the hardware space for quite some time, as Google does not currently manufacture its own hardware.

The latest news comes from a Japanese-language blog that took a peek inside HTC's U11 system files. Inside the blog found entries pointing to international versions of the Ocean, which is the codename for the U11, along with entries pointing to S2 and M2 devices. Those likely point to the Pixel 2 and Pixel XL 2, as the first generation versions carried the codenames S1 and M1.

Google Pixel Phones

HTC's U11 system files also point to both phones using Qualcomm Snapdragon 835 system-on-chip (SoC). That coincides with previous rumors and leaked information pointing to the same chipset. Among them is a GFXBench entry that labels the Pixel XL 2 as "Pixel XL2" and as toting a 5.6-inch display with a 2560x1312 resolution (18:9 aspect ratio). If that listing is correct, the Pixel XL 2 will also wield 4GB of system memory.

Finally, the Japanese-blog found a reference among the system files to LG. The site seems to believe that LG might be manufacturing the larger size Pixel XL 2, though previous rumors pegged Google as launching three Pixel devices, one of which could end up being a tablet codenamed taimen.

Either way we will find out before the year is over. Google SVP of Hardware Rick Osterloh confirmed back in March that Google's second-generation Pixel flagships would arrive by the end of 2017, likely with Android O installed. As points of reference, Google in the past has launched major handsets on September 29 (Nexus 6P and Nexus 5X, in 2015) and October 4 (Pixel and Pixel XL, in 2016).

Via:  HTC Soku
Show comments blog comments powered by Disqus