The expected Pixel update schedule has changed in recent months for the Pixel 6 and Pixel 7 series.<\/p>\n
Both the Pixel 6 and Pixel 7 series of phones should still be supported through 2026, 2027, and beyond<\/a>, we\u2019re just starting to question what the cadence for updates will be going forward. I bring this up because folks who own these devices are likely wondering where their updates are after several misses in recent months, starting around July 2025.<\/p>\n Google has issued monthly updates for its Pixel devices from the day they were introduced, so a missed month or two is a noteworthy event. For a device to miss updates for several months is really something that should be drawing some attention. That in mind, no where in Google\u2019s official documentation does it say that their Pixel devices are guaranteed to receive monthly updates, but that\u2019s how they have sent them. Their support documents simply state the number of years of expected support.<\/p>\n We\u2019ve asked Google to give us more information<\/a> on what we believe is a change in the update schedule for the Pixel 6 (and Pixel 7), but they have so far not gone into specifics, only suggesting that all of the still-supported Pixel devices are \u201ccompliant.\u201d When we asked what was up with Pixel 6 updates, they responded with the following:<\/p>\n \u201cPixel phones will remain security compliant for the full duration of their support windows, which can be found\u00a0here<\/a>.<\/p>\n Your device will remain private and secure through Pixel specific patches, Google Play System Updates and fixes through the Android Security Bulletin. You can also expect your phone to get better over time with regular Pixel Drops and updates to the latest OS for the device\u2019s full support window.\u201d<\/p>\n Because of that vague statement, we thought it was time to start a running timeline of updates for these devices to help you keep track of what the current releases are for each. And just maybe, this will give us some clarity around expectations going forward.<\/p>\n Pixel 6 and Pixel 6 Pro update timeline, current build: The current Pixel 6 and Pixel 6 Pro update you should be on is CP1A.260305.016.<\/p>\n June 2025 update: Received on June 10<\/a> as the first stable Android 16 build (BP2A.250605.031.A2) NOTE: Google hasn\u2019t confirmed, but it looks like the Pixel 6 and Pixel 6 Pro are officially on a quarterly update schedule.\u00a0<\/p>\n Pixel 6a update timeline, current build: The current Pixel 6a update you should be on is CP1A.260305.016.<\/p>\n June 2025 update: Received on June 10 as the first stable Android 16 build (BP2A.250605.031.A2) NOTE: Google hasn\u2019t confirmed, but it looks like the Pixel 6a is officially on a quarterly update schedule. <\/p>\n Pixel 7 and Pixel 7 Pro update timeline, current build: The current Pixel 7 and Pixel 7 Pro update you should be on is CP1A.260305.016.<\/p>\n June 2025 update: Received on June 10 as the first stable Android 16 build (BP2A.250605.031.A2) NOTE: Google hasn\u2019t confirmed, but it looks like the Pixel 7 and Pixel 7 Pro are officially on a quarterly update schedule.<\/p>\n Pixel 7a update timeline, current build: The current Pixel 7a update you should be on is CP1A.260305.016.<\/p>\n November 2025 update: Received on November 11 with November security patch (BP3A.251105.015) NOTE: The Pixel 7a first missed the December update and has received the January, February, and March 2026 patches. Still, because of the December miss, we\u2019re now tracking it.<\/p>\n We\u2019ll continue to update this post each month unless the updates start showing up monthly again. We\u2019ll also add devices if they slip from the monthly cadence.<\/p>\n UPDATED MARCH 3, 2026 WITH INFO ON MARCH UPDATE. THERE\u2019S NO OTHER WAY TO LOOK AT THIS THAN GOOGLE MOVING PHONES TO QUARTERLY UPDATE SCHEDULES WITHOUT ANNOUNCING IT.<\/p>\n","protected":false},"excerpt":{"rendered":"The expected Pixel update schedule has changed in recent months for the Pixel 6 and Pixel 7 series.…\n","protected":false},"author":2,"featured_media":452161,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[49,48,190,61],"class_list":{"0":"post-513073","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-mobile","8":"tag-ca","9":"tag-canada","10":"tag-mobile","11":"tag-technology"},"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts\/513073","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/comments?post=513073"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/posts\/513073\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/media\/452161"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/media?parent=513073"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/categories?post=513073"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/ca\/wp-json\/wp\/v2\/tags?post=513073"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nJuly 2025 update: Did not receive a July update
\nAugust 2025 update: Did not receive an August update \u2013 received another June build in August (BP2A.250605.031.A5)
\nSeptember 2025 update: Received on September 3 as QPR1 and build (BP3A.250905.014)
\nOctober 2025 update: Did not receive October update
\nNovember 2025 update: Did not receive November update
\nDecember 2025 update:\u00a0Received on December 2<\/a> as December quarterly update (QPR2, BP4A.251205.006)
\nJanuary 2026 update: Did not receive January update
\nFebruary 2026: Did not receive February update
\nMarch 2026: Received on March 3<\/a> as March quarterly update (QPR3, CP1A.260305.016)<\/p>\n
\nJuly 2025 update: Received on July 8<\/a> with July security patch (BP2A.250705.008)
\nAugust 2025 update: Received another July build (BP2A.250705.008.A1)
\nSeptember 2025 update:\u00a0Received on September 3 as QPR1 and build (BP3A.250905.014)
\nOctober 2025 update: Did not receive October update
\nNovember 2025 update: Did not receive November update
\nDecember 2025 update:\u00a0Received on December 2 as December quarterly update (QPR2, BP4A.251205.006)
\nJanuary 2026 update: Did not receive January update
\nFebruary 2026: Did not receive February update
\nMarch 2026: Received on March 3<\/a> as March quarterly update (QPR3, CP1A.260305.016)<\/p>\n
\nJuly 2025 update: Received on July 8 with July security patch (BP2A.250705.008)
\nAugust 2025 update: Received on August 5 with August security patch (BP2A.250805.005)
\nSeptember 2025 update:\u00a0Received on September 3 as QPR1 and build (BP3A.250905.014)
\nOctober 2025 update: Received on October 8 with October security patch (BP3A.251005.004.B1); received 2nd October update on October 30 (BP3A.251005.004.B2)
\nNovember 2025 update: Did not receive November update
\nDecember 2025 update: Received on December 2 as December quarterly update (QPR2, BP4A.251205.006)
\nJanuary 2026 update: Did not receive January update
\nFebruary 2026: Did not receive February update
\nMarch 2026: Received on March 3<\/a> as March quarterly update (QPR3, CP1A.260305.016)<\/p>\n
\nDecember 2025 update: Did not receive December update
\nJanuary 2026 update: Received on January 12 with January security patch (BP4A.260105.004.E1)
\nFebruary 2026: Received update on February 3 with February security patch (BP4A.260205.001)
\nMarch 2026: Received on March 3<\/a> as March quarterly update (QPR3, CP1A.260305.016)<\/p>\n