In a surprising turn of events, Google has issued an important advisory for Android users grappling with a frustrating new phone glitch.
As of January 14, 2026, the tech giant has acknowledged widespread complaints stemming from a specific issue that impacts the functionality of volume buttons on certain devices. So, what’s the problem? Users who have activated one of Android's widely utilized accessibility features, known as Select to Speak, are encountering difficulties. This feature is designed to assist individuals with visual impairments or reading challenges, providing spoken descriptions of text and images displayed on their screens. However, it seems that once enabled, Select to Speak interferes with the normal operation of volume controls.
Reports suggest that when this setting is active, pressing the volume buttons does not adjust sound levels in the way users expect. Instead of controlling media volume, the buttons only manage the accessibility volume. Furthermore, users have found that attempting to take photos using the camera while the feature is on fails to trigger the shutter.
"We have received reports of volume keys not functioning as intended on Android devices that have Select to Speak, an accessibility service for users with low vision or reading difficulties, enabled," Google clarified in their statement.
To mitigate this issue until a solution is implemented, Google recommends that affected users temporarily disable the Select to Speak feature. They guide users to navigate to Settings > Accessibility > Select to Speak, and toggle the Select to Speak shortcut off.
While there is currently no timeline available for when a fix will be released, Google is known for addressing such bugs promptly. Rest assured, we will keep you updated with any developments on this situation as they arise.
But here's where it gets controversial: Should users have to sacrifice accessibility features for basic functionalities like adjusting volume or taking pictures? This dilemma raises questions about how technology can balance inclusivity with usability. What do you think? Should companies prioritize fixing these kinds of bugs, or is it acceptable for some features to cause inconvenience? Share your thoughts in the comments!
