Somebody typed a query into the app drawer, watched the keystrokes fail to register, and filed it. Three more tracker IDs landed on the same fix [6]. The notification shade that would not pull all the way down carries six IDs [9]. Call audio defaulting to the phone speaker instead of the paired Bluetooth device carries four [8], and the Recents card that froze and clipped behind other apps carries another four [10]. Low-light Face Unlock that skipped fingerprint and forced a PIN carries three [11]. Those five entries alone hold 21 of the 33 tracker IDs in the list [22].
The single-ID entries look different in kind. Rendering apps below the display cutout, a developer setting, produced a transparent status bar and drew one report [12]. A WebGL freeze traced to an invalid memory read in the PowerVR driver's texture state processing drew one [13]. Duplicate volume follows the surfaces people touch dozens of times a day; the API edges get found by whoever happened to be testing that day. Teams often assume the tracker measures severity, but it actually measures how many separate people were annoyed enough to open the Beta Feedback app and file into Google's issue tracker [16], so each count is a floor on how many people hit the bug, not a severity score.
If Platform Stability is your gate for re-running compatibility suites, you have it on 19 Pixel models plus the emulator [14], and not on the four Pixel 11 models, whose C2 build 9to5Google says is coming soon [2][15]. That is the awkward part of a freeze. The newest hardware in the fleet is the one piece you cannot yet certify against it [23].
The sorting that helps here runs two columns per entry. Would our test suite have caught this, and would a user have opened a ticket about it. Screen mirroring to external USB-C XR glasses [4] and the WebGL crash [13] sit in the first column, where an automated build check earns its keep. The audio service lock during screen recording that blocked microphone use across apps, Gboard and Gemini included [7], sits in the second: nothing in the API contract moved, and the user knew within seconds. Entries that answer no to the first and yes to the second are the manual checks worth adding before the stable build, and both the thermal fault that rebooted devices mid-use [3] and the 80% battery limit crawling through its final 2% [5] live there. Every row you close on the A2 or B1 images stays provisional for the Pixel 11 line, which is a footnote worth writing into the test report now rather than explaining later.
