For Pixel owners quick to sideload or OTA update to the latest Android build, that being Android 14 QPR2 Beta 3, there’s a solid amount of bug squashing inside. Courtesy of the Android development team, we have the full list of what’s getting fixed.
The list has some solid fixes, such as a fix for an issue that caused multi-finger gestures to stop working, a fix for haptics that sometimes stopped working, as well as fixes for “various issues” that caused problems with system stability, performance, connectivity, and the camera. All in all, this is looking like a good beta update, so long as it doesn’t introduce too many new problems.
Here’s the complete list.
Resolved Developer, User-Reported Issues
- Fixed an issue where SPIR-V sequences of OpShiftLeft followed by OpShiftRight didn’t produce the expected results for ARM Vulkan driver versions 43.0 and 44.0.
- Fixed issues that sometimes caused Bluetooth connections to be interrupted for some devices.
- Fixed issues that sometimes caused a device to crash or become unresponsive after restarting.
- Fixed issues that in some rare cases caused devices to reboot while in idle mode.
- Fixed an issue that caused live wallpapers to stop animating.
- Fixed an issue that prevented Google Assistant from activating in some cases.
Other Resolved Issues
- Fixed an issue that sometimes caused multi-finger gestures to stop working.
- Fixed an issue where the device’s screen didn’t initially turn on when the screen was double-tapped or the power button was pressed.
- Fixed an issue that sometimes caused higher than usual CPU usage during video playback.
- Fixed a system issue that sometimes caused poor audio quality or higher power consumption when making calls.
- Fixed an issue where the keyboard was always shown even if the “Swipe up to start search” setting was disabled in system settings.
- Fixed an issue where sometimes when a user unlocked the device using their fingerprint, there was no haptic feedback.
- Fixed an issue for Pixel Fold devices where sometimes after a user unlocked the device while it was folded, the inner display didn’t turn on after unfolding the device.
- Fixed various issues that were impacting system stability, performance, connectivity, camera, and accessibility.
Google has a dedicated place to track current top issues here. Additionally, there is a bug in this build that reads as follows: “The Assistant At a Glance widget sometimes displays weather information for the wrong location.” That’s not world ending.
Go snag that update, Pixel friends.
Anyone have an issue on their Pixel 7 Pro that when on a phone call if you open another app (say you want to confirm something in your calendar, or take a note in Keep) it appears to mute the mic? I can still the person on the other end of the call, but they can’t hear me until I return to the phone app. It’s been this way for at least 2 months now. But hasn’t always been this way.
Has anyone noticed random screen unlock animation stuttering with Pixel 8 Pro?
I have noticed
Looks like my pixel issue get resolved. Sudden freeze
They fixed an issues on pixel 7 pro where the finger print reader was completely unresponsive… they forgot to mention that ????. I had to disable it completely but now it’s all good!
STILL no Cinematic Wallpaper on my poor P7P. There’s a P2 S2 open issue in that bug tracker since September, +1’d by 29 people. And no response from Google there, after that day.
I bet they won’t do anything and then close it as “obsolete” after 1-2 years.
They need to fix the slow 6 GHz WiFi band on the Pixel 8 Pro. I am only getting 5 to 7 Mbps even if I’m right next to the gateway.
I’m running gig and am pulling 600-750 meg speeds just fine on 5 ghz
Yep, I get good speeds then as well. On 5 GHz I get over 800 Mbps, but as soon as it connects to 6 GHz, it drops like a brick. It’s a problem others are having as well. If you can connect to 6 GHz somewhere, you should test yours. I’d call to replace mine, but others who did that got replacements with the same issue. For now, I disabled the 6 GHz band on my gateway. Our phones are the only things connecting to it anyway.
6Ghz has to be super close with no real barriers to even maximize. IF you running 5gh AX and locked 160 mhz, you’ll be flying on that 5gh AX channel even at 40 feet away.
Okay, good, because I kept saying to my wife, I says to her I says “There’s an issue where SPIR-V sequences of OpShiftLeft followed by OpShiftRight didn’t produce the expected results for ARM Vulkan driver versions 43.0 and 44.0.”
Android 15 Dev Preview March? ????