TL; DR
- Rumors from last fall suggested that Google might switch from Samsung to MediaTek for its Tensor G6 modem.
- Earlier today, the certification documents of the Pixel 11 Pro Fold were published by the FCC.
- The reference to MediaTek algorithms in the RF component test adds credence to the idea that the Tensor G6 makes just that transition.
Pixel phones are unique for several reasons, and their Tensor processors should be at the top of the list for getting Google’s latest software updates. We’ve had pretty high expectations for these chips over the years, and even from Google like us keep getting frustratedThere is always hope that Google will be able to change things for the next generation. Earlier today we saw what appeared to be Pixel 11 Pro Fold documents pass FCCand if we dig into these documents, we might find a small clue about one of this year’s big Tensor changes.
While Tensor chips are Google’s babies, Google isn’t building them 100% from scratch and relies on IP from other firms for various purposes – two of the biggest being the GPU and modem on the chip. Until now, every Tensor has used a Samsung Exynos modem, but last year we heard that it might switch to Google. MediaTek modem for Tensor G6 It will strengthen the Pixel 11 series.
In particular, sources have pointed to a MediaTek M90 component, and we hope that such a move can help. reduce energy consumption Compared to the return of the Exynos modem.
As we review today’s FCC filing dump, we note SAR test report of the Pixel 11 Pro Fold. It’s designed to measure how much RF energy someone using the phone will be exposed to – so obviously the phone’s modem and radio hardware will play a big part here.
Pages and pages of it are dense tables of specifications and measurements. And then, on page 30, we see this: MediaTek.
Samsung is adamant that it won’t be using MediaTek algorithms in its Exynos modem, so it’s not a big leap to read this as confirmation of Google’s move to MediaTek, as we’ve been hearing for months.
Thank you for being a part of our community. Read our Comment Policy before deployment.
