Google confirms mic bug in Take a Message on older Pixels
In a recent software update cycle, Google publicly acknowledged a bug in the Pixel Phone app’s “Take a Message” feature that caused audio to be inadvertently sent to callers. The issue affected a small subset of users and raised concerns about privacy and call handling. Google has taken swift action by disabling the feature on older devices, specifically the Pixel 4 and Pixel 5 series, to prevent further unintended audio transmission.
What is Take a Message?
Take a Message is a Pixel Phone feature introduced last year designed to help users capture message intent when a call can’t be answered. In practice, it creates a short audio recording that the caller can hear or that can be relayed in other ways to provide context about the missed call. The feature was positioned as a convenient way to relay information without typing, but like many new tools, it needed refinement as real-world use exposed edge cases.
The bug and its impact
Google confirmed that a mic bug caused audio from Take a Message to be sent to callers unintentionally for a limited set of users. This raised privacy concerns and prompted questions about how gracefully the feature degrades on older hardware and software configurations. While not a widespread exploit, the bug was significant enough for Google to act quickly to protect users’ privacy and prevent potential misunderstandings during calls.
Why Google disabled it on Pixel 4 and 5
To curb the issue, Google rolled out a targeted safety measure by disabling Take a Message on Pixel 4 and Pixel 5 series devices. This decision reflects a cautious approach: if a feature is known to risk exposing audio in ways that users do not expect, removing it from affected hardware is a reliable short-term fix while a longer-term patch is prepared. Google has not indicated how long the disablement will last, but it suggests a focused bug-fix path for the older devices rather than a broad rollback.
What this means for users
Pixel users who rely on Take a Message should note that the feature is currently inactive on Pixel 4 and 5 devices. If you have one of these models, you’ll want to update the Pixel Phone app and system updates when available, as Google is likely to release a follow-up fix. For now, users can still answer missed calls in the traditional way or rely on alternative messaging features provided by Google Phone or broader Android capabilities. The company’s swift disablement signals a prioritization of user privacy and reliability over feature parity on aging hardware.
What’s next
Google typically resolves such issues with a combination of software patches and release notes that guide users through the changes. Expect a future update that re-enables Take a Message with a corrected audio-handling path or an alternative workflow that preserves the feature’s convenience without compromising privacy or call integrity. In the meantime, users on newer Pixel devices may experience fewer or no interruptions as Google continues its bug-squash effort.
Tips for Pixel users
- Keep Pixel Phone and system updates enabled to receive the latest bug fixes.
- If you rely on Take a Message, monitor Google’s official support pages for confirmation when the feature returns on all devices.
- Review app permissions for the Pixel Phone app to ensure voice data is handled according to your privacy preferences.
As Google works to stabilize take-a-message functionality across its lineup, affected users should expect clear guidance from Google Support once the bug fix progresses toward a full release. The current action—disabling the feature on Pixel 4 and 5—illustrates the company’s commitment to privacy and user trust in its communication tools.
