With the impending launch of the next generation of Google Pixel phones, known for now as the Pixel 2 and Pixel XL 2, many fans were looking forward to Google benefiting from a little bump in the current processor market for flagship phones. Early rumors indicated Qualcomm was working on an updated chip that would be the Snapdragon 836 succeeding the current top-of-the-line Snapdragon 835. Last week that fell apart when word surfaced the Snapdragon 836 would not be ready for the Pixel 2 devices. Sources familiar with the plans now say the Snapdragon 836 was indeed going to be used, but now there is a question as to whether that processor will ever be produced.
According to Evan Blass, Qualcomm had indeed informed Google and their partners that they could expect the Snapdragon 836 to be ready for the new Pixel 2 devices. At some point though, Qualcomm realized they would not have the new chip ready in time to meet Google’s, HTC’s and LG’s production timelines as the chip needed to be delayed until early 2018. Thus far no information has surfaced regarding what changes to the chip compared to the Snapdragon 835 were causing a problem.
With the extensive delay, the situation has even changed to where it is uncertain whether the Snapdragon 836 will ever be released with that model name and number. Depending on how much of an advance the new chip is compared to the existing Snapdragon 835, the new processor could end up being the Snapdragon 845 rumored to be used in the Galaxy S9. Qualcomm could also decide to go for a completely different model designation.
So, 836: QCT had told GOOG to expect it, but then delayed it until early next year (tho perhaps under diff branding), forcing Pixels to 835.
— Evan Blass (@evleaks) September 8, 2017
Whatever happens with the Snapdragon 836 and whether it becomes a reality, Google is going to end up with the Snapdragon 835 in the new Pixel 2 devices.
Do you think Pixel fans and potential buyers will be satisfied with a processor equal to the rest of the flagship market?
source: Evan Blass (Twitter)