If you also have this phone, then there is a big threat to privacy, sound can be leaked even after rejecting the call.
If you use Google Pixel smartphone, then this news is very important for you. According to a recent report, the smart calling feature ‘Take a Message’ of Phone by Google app present in Pixel phones can become a threat to the privacy of users. In the report of tech website 9To5Google, it has been claimed that due to this feature, the background audio of the user can reach the person calling.
Actually, ‘Take a Message’ is an AI-based feature, which automatically attends missed or rejected calls and records the message from the caller. This feature also shows live transcription, so that the user can read what the other person is saying without picking up the call. But now reports have revealed that in some cases this feature is not working properly.
What is the whole matter?
According to the report, many Pixel users reported that their phone’s microphone remains active even after rejecting the call. In such a situation, the caller can hear the surrounding sounds. Some users also noticed that even after the call ends, a green microphone indicator appears on the screen, indicating that the mic is on.
Although this problem is not seen in all users, but it is being considered a serious privacy issue. For this reason, Google has paid attention to this matter and according to reports the company is investigating it.
Which Pixel phones are affected?
At present it is not clear whether this bug is limited to only one model or not. In reports, users of both old and new Pixel devices have mentioned this problem. This means that there is a possibility that this bug may affect many Pixel models.
What should users do?
Until Google finds a permanent solution to this problem, experts recommend that Pixel users turn off the ‘Take a Message’ feature.
- For this, open the Phone app, tap on the three dots on the top right.
- Then go to Settings > Call Assist > Take a Message and turn it off.
At present, Pixel users are being advised to remain alert and keep an eye on app updates. Hopefully Google will soon release an update to fix this bug.
