Google Photos bug hits Pixel editing as Pixel Buds may add call mute tap
Android Authority reports a Google Photos editor bug on Pixel phones and Pixel Buds code for a future tap-to-mute call control.
According to Android Authority, the Google Photos editor normally lets users share, edit, delete, or add a photo to an album after taking it. Users can usually perform one action and then another; for example, after editing a picture, they can share it without leaving the editor. The bug breaks that sequence, leaving options such as sharing, deleting, and editing unresponsive once an edit has been made. The issue appears to affect multiple generations of Pixel phones. Android Authority noted that Google is already working to improve editing in the Photos app by upgrading markup tools, and earlier coverage found evidence that the company could add a brush size slider, additional colors, and text alignment. The report did not include a timeline for fixing the editor bug.
Separately, Android Authority examined version 1.0.981607934 of the Pixel Buds app and found text strings describing a Tap to mute & unmute feature. Current Pixel Buds touch controls already support answering, rejecting, and ending calls: a single tap answers an incoming call, and a double tap ends or rejects one. The new strings indicate that during a call, a single tap on either earbud would mute or unmute the conversation. They also state that the feature is limited to Pixel devices when using the Phone and Google Meet apps. One string warns that on some platforms, the microphone may remain unmuted if the host app does not support the mute command, even if audio transfer successfully occurs. Android Authority also uncovered an animation in the app illustrating the functionality. It is unclear whether the feature might be exclusive to specific Pixel Buds models, but the report says it would require a Pixel series phone alongside the Pixel Buds.
The Pixel Buds feature is not yet live, and the report did not say when it might arrive. The Google Photos bug report did not include a Google response or a fix timeline.