This screenshot doesn't make any sense. Android won't allow a background app to access the microphone or camera. If it would, then there is an exploit in Android but I doubt it's a security bug since no one actually noticed it (Android notifies when an app access the microphone).
Also, if Whatsapp did somehow listen in the background , it seems like those are one-time accesses. WhatsApp would not benefit anything if it would listen for a very short time.
It seems like it would be a stupid action from WhatsApp, since they would have to go through the trouble of transcribing voice to text, and it costs power.
If WhatsApp would listen all the time, or for even a minute, the battery consumption would go very high. Doesn't seem feasible.
It seems like a bug in WhatsApp or a bug in Android's privacy dashboard.
> If WhatsApp would listen all the time, or for even a minute, the battery consumption would go very high. Doesn't seem feasible.
Regardless if it's true or not, should WhatsApp or any other app spy on the user by using the microphone in the background, the "safe" (from their POV) way to do that would be to tap into the audio signal, save it somewhere at low bitrate while removing silent parts, then wait when the user starts an update or any network/cpu intensive job and compress+transmit it in the background. No need to keep the CPU at high load 100% of the time.
> Dabiri is not the first to notice the issue. WhatsApp blog wabetainfo highlighted the bug a month ago, describing it at the time as “a false positive” affecting owners of some Pixel and Samsung devices. They added that restarting the phone may be a possible fix. Meanwhile, Google has said little about what could be causing the discrepancy, but confirmed it’s looking into the matter. "We are aware of the issue and are working closely with WhatsApp to investigate,” a Google spokesperson said in a statement.
I'm waiting to see further details from Google before rushing to conclusions. Ideally the bug will be in the open source part of Android so we can confirm what was going on.
Also notable that the screenshot is not from an official Android system screen, but from a third party app listed on the playstore as "privacy dashboard"
Every once in a while people want to call me through WhatsApp (from abroad, or no cellular connect, but with internet). The first time Whatsapp asked me for microphone permission, I clicked "this time only". The next time, Whatsapp didn't give me that option. Either permanently allow microphone always (google android writes "only when using the app", but we all know that simply means "always"). Now I see why Whatsapp requires that, so it can constantly record me.
I find the response to this depressing. Instead of an actual legitimate "Let's figure out if it's real, do some proper scrutiny and then get angry", we're getting the hydroxychloroquine jerks screaming - which does a great job of delegitimizing what could be a legitimate concern.
worldsavior|2 years ago
Also, if Whatsapp did somehow listen in the background , it seems like those are one-time accesses. WhatsApp would not benefit anything if it would listen for a very short time.
It seems like it would be a stupid action from WhatsApp, since they would have to go through the trouble of transcribing voice to text, and it costs power.
If WhatsApp would listen all the time, or for even a minute, the battery consumption would go very high. Doesn't seem feasible.
It seems like a bug in WhatsApp or a bug in Android's privacy dashboard.
iudqnolq|2 years ago
https://www.engadget.com/whatsapp-bug-is-making-some-android...
fancyfredbot|2 years ago
squarefoot|2 years ago
Regardless if it's true or not, should WhatsApp or any other app spy on the user by using the microphone in the background, the "safe" (from their POV) way to do that would be to tap into the audio signal, save it somewhere at low bitrate while removing silent parts, then wait when the user starts an update or any network/cpu intensive job and compress+transmit it in the background. No need to keep the CPU at high load 100% of the time.
iudqnolq|2 years ago
> Dabiri is not the first to notice the issue. WhatsApp blog wabetainfo highlighted the bug a month ago, describing it at the time as “a false positive” affecting owners of some Pixel and Samsung devices. They added that restarting the phone may be a possible fix. Meanwhile, Google has said little about what could be causing the discrepancy, but confirmed it’s looking into the matter. "We are aware of the issue and are working closely with WhatsApp to investigate,” a Google spokesperson said in a statement.
I'm waiting to see further details from Google before rushing to conclusions. Ideally the bug will be in the open source part of Android so we can confirm what was going on.
sigmar|2 years ago
Also notable that the screenshot is not from an official Android system screen, but from a third party app listed on the playstore as "privacy dashboard"
missingcolours|2 years ago
ThePowerOfFuet|2 years ago
serial_dev|2 years ago
Edit: Found it in the tweet replies: Settings, Security and Privacy, Privacy, Privacy Dashboard
goguy|2 years ago
nittanymount|2 years ago
how could/dare FB do this, hmm... interesting... like to learn more...
scarface74|2 years ago
smcleod|2 years ago
worldsavior|2 years ago
londgine|2 years ago
markx2|2 years ago
Who owns WhatsApp?
mmh0000|2 years ago
SilverBirch|2 years ago
MiguelX413|2 years ago
tjpnz|2 years ago