Google rolling out Android 17 QPR1 for Pixel

Abner Li· Sep 15, 2026 · 6:00 PM UTC ·3 min read · 0 reactions · 0 comments · 5 views

More from 9to5Google tech Compare coverage Trending Talk Blindspots Daily Sources Live wire

TL;DR · WeSearch summary

There are a number of interface changes in Android 17 QPR1, starting with more blur effects across the system UI. The volume panel is where you’ll most likely notice the Dynamic Color-themed translucency, with the full bottom sheet also updated. The Power menu has also been refreshed and is joined by a background blur.

Key facts

▪There are a number of interface changes in Android 17 QPR1, starting with more blur effects across the system UI.
▪The volume panel is where you’ll most likely notice the Dynamic Color-themed translucency, with the full bottom sheet also updated.
▪The Power menu has also been refreshed and is joined by a background blur.

How this story was covered

2 outlets in our directory ran this story, first to last over 10 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1

▪ Google’s motion sickness helper for Android is breaking free of Pixels — Android Police

About this source

9to5Google files mainly under tech. We currently carry 420 of its stories.

All 9to5Google coverage →

Original article

9to5Google · Abner Li

Read full at 9to5Google →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	9to5Google
Canonical URL	https://9to5google.com/2026/09/15/android-17-qpr1-pixel/
Publication time	Tue, 15 Sep 2026 18:00:00 +0000
Retrieval time	2026-09-15T18:01:52.734Z
Last seen	2026-09-15T18:01:52.734Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	AuajKlw86cni · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

// Make sure that nineto5ads exists, it will load ad once google tag exists window.nineto5ads = window.nineto5ads|| []; if (typeof adSizes === 'undefined') { var adSizes = {"leaderboard":{"mobile":[[320,50],[320,100]],"tablet":[[728,90],[320,100]],"desktop":[[970,250],[728,90],[970,70],[970,90]]},"sidebar":{"mobile":[300,250],"desktop":[[300,600],[300,250]]}}; } function getLeaderboardApstagSlotsSizes() { if ( window.innerWidth < 768 ) { return adSizes.leaderboard.mobile; } else if ( window.innerWidth < 1024 ) { return adSizes.leaderboard.tablet; } else { return adSizes.leaderboard.desktop; } } window.nineto5ads.push(function() { apstag.fetchBids({ slots: [{ slotID: "div-gpt-ad-1436850350386-0", slotName: "\/1049447\/9to5google-Top", sizes: getLeaderboardApstagSlotsSizes() }], timeout:…

Excerpt limited to ~120 words for fair-use compliance. The full article is at 9to5Google.

Anonymous · no account needed

Discussion

0 comments