Loading today’s stories
Product1 distinct publisher3 min readPublished
Beta 4 gathers summaries, the organizer and cooldown behind one Notification intelligence door ahead of December's stable release, alongside a Pixel 11 build number that nobody can download yet.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
Someone films a bug for the help desk, and then voice typing is dead in Gboard until they restart the phone. Beta 4 fixes that one: an audio service resource lock triggered during screen recording prevented microphone use across apps and input methods including Gboard and Gemini until a device restart [6].
The fix list is where a changelog records what people were actually doing. 9to5Google's Beta 4 notes cite 33 tracked issue IDs across 16 entries [14][15]. Six entries carry more than one ID, and between them they account for 23 of the 33, close to 70% [16]. Duplicate IDs are duplicate reports. The notification shade that would not pull all the way down drew six [7]. Call audio defaulting to the phone speaker instead of a connected Bluetooth device drew four [8], as did app drawer search that would not process typed text [9]. Low-light Face Unlock failures that skipped fingerprint and forced a PIN drew three [10]. Opening the shade, taking a call in the car, finding an app, unlocking in the dark: that is the traffic.
Notification intelligence sits at the other end of the same release. The entry describes a consolidation and nothing more [2], which is worth something on its own, because three AI behaviors that lived in separate places now share one door, and one door can be closed in a single visit. What the notes do not offer is any read on use. A tidier menu is not evidence that people leave summaries on, and nobody outside Google can see retention or opt-out rates from a settings screen.
Two other lines set the calendar. Build CP41.260814.003.C2 is named for the Pixel 11, 11 Pro, 11 Pro XL and 11 Pro Fold, was not available as of Friday afternoon, and is officially due soon [4]. The notes also flag a platform stability milestone [5] against a stable December release [1]. My read: the notification surface you can screenshot this week is roughly the one you will be answering for, across a support fleet that 9to5Google's own install instructions already put at 19 Pixel models [19], with four more on the way.
For triage, sort each entry on two axes: whether it moves a control the user already set, and whether it changes what happens if the user does nothing. Moved control with unchanged behavior produces tickets saying a setting has vanished, and a screenshot in your internal doc handles it. Unchanged location with new behavior produces a complaint from the person whose notifications got rewritten, and only a default change explains that. Both at once is the quadrant Notification intelligence could land in, and it is the only one worth pre-empting. The test is cheap: one device on Beta 4, the notification settings captured before the update and the same screen after, toggle by toggle.
Ranked by verification strength, evidence, and original report placement.
9to5Google describes Android 17 QPR2 Beta 4 as not as big as the last release but still a sizable update ahead of the stable December release.
Beta 4 adds a new Notification intelligence menu that consolidates the AI-powered Notification summaries and organizer, as well as Notification cooldown.
Other Beta 4 changes listed include new badges in Wallpaper & style, a long-press menu tweak, and status bar customization.
Build CP41.260814.003.C2 is for the Pixel 11, 11 Pro, 11 Pro XL and 11 Pro Fold, but was not available as of Friday afternoon; officially the build "will be available soon".
The Beta 4 notes list a platform stability milestone.
Beta 4 fixes an audio service resource lock triggered during screen recording that prevented microphone usage across apps and input methods like Gboard and Gemini until a device restart (Issue #538229807).
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 28, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
product
Pixel 11: a flatter camera bar, seven grams, and a software lockout1 distinct publisher
product
LineageOS 23 reaches the Galaxy S22 with about six months left on Samsung's clock1 distinct publisher
product
Google's $50 clear case is priced against its own catalogue, not the market1 distinct publisher
product
Google moved the Pixel 11 Pro's upgrade case into software. Judge it on rollout risk.5 distinct publishers
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Primary notes, one narrator
Thirty-three Google issue tracker numbers sit under sixteen fixes, and every one of them is checkable by a reader who cares to look — harder sourcing than most product write-ups manage. What holds the score down is everything around the list: 9to5Google is the only voice here, the piece says "Updating…" and will change under readers' feet, the install paragraph is still written for Beta 3, and the Pixel 11 build number is a string nobody can yet verify by downloading it.
Shipped to the beta channel
What is documented is availability, not use. The build is out and install guidance covers 19 Pixel models; there is not a single enrolment count, download figure or developer-uptake number in this reporting, and one whole hardware family — the Pixel 11 line — is named without being served. Beta channels are also self-selecting by design, so even full uptake here would not describe the installed base.
Mildly ahead of what ships
Restrained for a beta write-up — 9to5Google opens by calling Beta 4 smaller than its predecessor and flags the Pixel 11 build as unavailable instead of teasing it. The slight overshoot lives in two places: "Notification intelligence" sounds like new capability when summaries, the organizer and cooldown all existed already and have simply been given a shared door, and a published build number reads as Pixel 11 support arriving when nothing arrives.
Traffic loop over vendor notes
Beta changelogs are an annuity for Android-focused outlets, and this one works the mechanism openly: it asks readers to check back often, publishes while still incomplete, and routes them into 9to5Google's own step-by-step install guide. Meanwhile the substance belongs to Google — the fix list is exactly as complete as the vendor chose to make it, with no known-issues counterweight and no independent testing between the notes and the reader. Neither pull is concealed; neither is absent either.
Specific, uncorroborated
Confident on the granular stuff and shaky on everything above it. Sixteen fixes with named subsystems and 33 issue numbers would be hard to fake and easy to check; the December date, the stability milestone and the Pixel 11 build rest on a single outlet reading a single vendor document, in a write-up that admits it is not finished.