Affiliate links on Android Authority may earn us a commission.Learn more.

AOSP code suggests unreleased HTC-made Pixel 2 wasn’t just a rumor

June 05, 2025

TheGoogle Pixel 2and Pixel 2 XLwere officially announcedearlier this month, but did you know that early whispers suggested Googlewould debut three models? Now we have signs that this may have been more than just a rumor.

As revealed by XDA, a new device branch called ‘muskie’ can be found in thelatest Android source drop, Android-8.0.0_r24. Muskie was the namepreviously associatedwith thiscancelled model.Diving deeper into the AOSP files yields some pretty interesting details about Muskie.

Article image

First, Muskie’s product manufacturer is listed as Google, meaning that this isn’t just some associated third party device. Furthermore, theint.common.usb.rcfile shows that the kernel path for the battery hasHTClisted within. Putting two and two together, this device was likely built by HTCfor Google.

Speaking of the battery, thepower_profile.xmlfile indicates the Muskie would have had a massive 3,830 mAh battery. That’s even bigger than the Pixel 2 XL’s 3,520 mAh battery. Other interesting tidbits suggest Muskie has the same DPI as the the Pixel 2 XL, at 560. The phone even supportedPixel Visual Core, the custom SoC found in the other two members of the Pixel 2 family.

So what happened to Muskie? It’s hard to say for sure, since we know very little concrete information about it outside of the details above. That said, it’s very likely that Muskie was the original attempt at a successor to the Pixel XL, before LG got involved. That means the HTCPixel 2 XL variant likely lacked an 18:9 display, and would have had the same design as Google’s Pixel 2 — only in larger form.

Once LG got involved, Google likely decided that having two large screen models was redundant. With all thedrama currently facing the Pixel 2 XL, you have to wonder if Google wishes it had released Muskie after all. What are your thoughts on the Pixel that never was? Let us know in the comments below.

Thank you for being part of our community. Read ourComment Policybefore posting.