Moneycontrol

Google disables Take a Message on older Pixel phones after rare microphone leak

Google has confirmed a rare bug affecting the Take a Message feature on older Pixel phones, where background audio was unintentionally sent to callers. As a precaution, the company is disabling the feature on Pixel 4 and Pixel 5 models that no longer receive Android updates.

January 30, 2026 / 17:17 IST
Story continues below Advertisement
Google Pixel
Snapshot AI
  • Google disables Take a Message on Pixel 4 and 5 due to a privacy-related bug
  • Bug caused rare cases of ambient audio being transmitted during missed calls
  • Call Screening and voicemail still work on affected devices

Google has acknowledged a privacy-related bug in its Pixel Phone app that caused the Take a Message feature to behave unexpectedly on a small number of older devices. The issue affected select models in the Pixel 4 and Pixel 5 series, prompting the company to disable the feature entirely on those phones.

Take a Message was introduced last year as part of Google’s broader call handling tools. The feature activates when a user declines or misses an incoming call. Instead of routing the caller directly to voicemail, the system asks them to leave a message while generating a live transcript that the user can view in real time. In theory, the interaction is meant to function like an enhanced voicemail without the phone’s microphone transmitting any ambient audio.

Story continues below Advertisement

However, over the past few months, a handful of users reported an alarming behaviour. In rare cases, Take a Message appeared to activate in a way that made it seem as though the call had been answered. As a result, callers could hear background sounds from around the phone while leaving their message. Apart from the standard microphone indicator at the top of the screen, there was no clear signal to users that their surroundings were being picked up.

Google has now confirmed that the issue was real, but extremely limited in scope. According to the company, the bug affected a very small subset of Pixel 4 and Pixel 5 devices and only occurred under specific and uncommon conditions. The company stressed that this was never a widespread problem and could not be easily reproduced.