Monday, June 12, 2017

Sources Suggest “Muskie” Pixel XL Successor has Been Cancelled, Likely Replaced by Larger Device

The Pixel and Pixel XL were highly anticipated devices, but ultimately they were primarily a first-generation, introductory release for Google, and though they weren't wholly-spectacular, we regarded them a "foundational release". What was and remains really exciting, however, is what can be built upon said foundations.

Not long ago, we saw buzz surrounding references to upcoming Pixel devices in AOSP — publications with sources informed on the matter went on to report about the existence of three Pixel devices, respectively equipped with a small screen, a large screen, and of course… an even larger screen. The one referenced in AOSP and understood to be the large-screen successor to the Pixel XL was codenamed "muskie", and we didn't end up learning much about it. Now we hear from Android Police, a website known for precise Nexus and Pixel leaks and rumors, that "muskie" has been scrapped, possibly in favor of a larger-screen successor to the Pixel XL.

David Ruddock from Android Police rates the confidence of this rumor with a 9 out of 10, though he reminded us that it's possible there is a Pixel XL successor regardless of muskie's fate. Droid-life had rumored a device codenamed "taimen" which is allegedly bigger than both the small-screen walleye and muskie. David Ruddock proceeded to state that he was "fairly confident" this will actually go on to become the 2nd generation Pixel XL, and thus it's possible Google is increasing the screen size of its large-screen Pixel flagship for 2017.

In summary, while "muskie" was confirmed to be in development, sources say the project has been cancelled, leaving us with two Pixel mobile devices for the year instead of three. It's likely that they will both be Pixel smartphones – one small, one big – though that remains unconfirmed and should thus be treated as speculation.


Source: Android Police



from xda-developers http://ift.tt/2rb5NFq
via IFTTT

No comments:

Post a Comment