I highly doubt that they actually managed to do this, at least any time recently.
As another commenter noted, Android alerts you when an app is accessing the microphone in the background, and it would also absolutely destroy the phones battery life more than the FB app currently does. The only way that we have the “Hey Google/Siri” command prompts active all the time is with custom hardware not available to the apps, and certainly not without Android knowing about it.
Maybe they actively listen while the app is open, but even then I think recent Android/iOS would let you know about that.
Google’s “Now playing” feature constantly listens to what’s going on in the background to show you what songs are playing. They claim this is done with a local database of song “fingerprints”. The feature does not show the microphone indicator because: “…Now Playing is protected by Android’s Private Compute Core…”
I’m not saying that other, non-google, app do this to my knowledge; but the fact that this is a thing is honestly a bit scary.
As someone relatively ignorant about the mechanics of something like this, would it not make more sense that the app would be getting this data from the Android OS, with Google’s knowledge and cooperation?
The place I see the most unsettling ads (that seem to be driven by overheard conversation) tends to be the google feed itself, so it seems reasonable to me that they could be using and selling that information to others as well, and merely disguising how the data were acquired.
The place I see the most unsettling ads (that seem to be driven by overheard conversation)
There’s a simpler explanation – you’re in the same geospatial region or you’re connected to the same networks as the people you’re having conversations with, and those people also looked up the things they have conversations about.
If you have GPS, Wi-Fi, or (possibly) Bluetooth, then that’s how they can pretty easily associate you to those people.
It’s a reasonable explanation, and what I typically assume to be true. Still, I’m curious about the actual mechanics, and if it potentially could be being done by Google without the larger tech industry being aware of it.
That makes sense, but isn’t it assuming they’re processing data on the device? I would expect them to send raw audio back to be processed by Google ad services. Obviously it wouldn’t work without signal either, but that’s hardly a limitation.
As someone else pointed out, how does the google song recognition work? That’s active without triggering the light indicating audio recording, and is at least processing enough audio data to identify songs.
If they were sending that much audio back, people would see the traffic. You could record it and send it at a different time, but the traffic would exist somewhere. People have looked and failed to find any evidence of such traffic.
It’s something that could happen on device in the nearish future if there’s not anything now, but it would probably still be hard to hide.
Sorry, it’s been long enough and I haven’t saved any of the links, and the keywords are polluted as hell with garbage results. I can’t find anything specific.
Thanks for the info! I guess that’s ultimately what I’m looking for more about: how much do we know about cellular traffic? Obviously with encryption we can’t just directly read cell signals to find out what’s being sent, so do people just record the volume of data being sent in individual packets and make educated guesses?
It seems plausible to run a simple(non-AI) algorithm to isolate probable conversations and send stripped and compressed audio chunks along with normal data. I assume that’s still probably too hard to hide, but if anyone out there knows of someone that’s looked for this stuff, I’d love to check it out.
I highly doubt that they actually managed to do this, at least any time recently.
As another commenter noted, Android alerts you when an app is accessing the microphone in the background, and it would also absolutely destroy the phones battery life more than the FB app currently does. The only way that we have the “Hey Google/Siri” command prompts active all the time is with custom hardware not available to the apps, and certainly not without Android knowing about it.
Maybe they actively listen while the app is open, but even then I think recent Android/iOS would let you know about that.
Google’s “Now playing” feature constantly listens to what’s going on in the background to show you what songs are playing. They claim this is done with a local database of song “fingerprints”. The feature does not show the microphone indicator because: “…Now Playing is protected by Android’s Private Compute Core…”
I’m not saying that other, non-google, app do this to my knowledge; but the fact that this is a thing is honestly a bit scary.
As someone relatively ignorant about the mechanics of something like this, would it not make more sense that the app would be getting this data from the Android OS, with Google’s knowledge and cooperation?
The place I see the most unsettling ads (that seem to be driven by overheard conversation) tends to be the google feed itself, so it seems reasonable to me that they could be using and selling that information to others as well, and merely disguising how the data were acquired.
There’s a simpler explanation – you’re in the same geospatial region or you’re connected to the same networks as the people you’re having conversations with, and those people also looked up the things they have conversations about.
If you have GPS, Wi-Fi, or (possibly) Bluetooth, then that’s how they can pretty easily associate you to those people.
It’s a reasonable explanation, and what I typically assume to be true. Still, I’m curious about the actual mechanics, and if it potentially could be being done by Google without the larger tech industry being aware of it.
I believe technically-inclined people could monitor the traffic that exits the phone, or at least passes through the router.
Audio recordings would be larger than the kinds of stuff that’s just sent passively.
They can and do. Nobody has shown evidence of this happening.
It would take a lot of data. On device voice processing is not very advanced. That’s why most voice stuff doesn’t work without a signal.
That makes sense, but isn’t it assuming they’re processing data on the device? I would expect them to send raw audio back to be processed by Google ad services. Obviously it wouldn’t work without signal either, but that’s hardly a limitation.
As someone else pointed out, how does the google song recognition work? That’s active without triggering the light indicating audio recording, and is at least processing enough audio data to identify songs.
If they were sending that much audio back, people would see the traffic. You could record it and send it at a different time, but the traffic would exist somewhere. People have looked and failed to find any evidence of such traffic.
It’s something that could happen on device in the nearish future if there’s not anything now, but it would probably still be hard to hide.
Source? I would like to read about that
Sorry, it’s been long enough and I haven’t saved any of the links, and the keywords are polluted as hell with garbage results. I can’t find anything specific.
You probably won’t find a source about something not happening.
It’s almost like they were asking about sources for people looking or something.
If you’re not going to contribute, why are you wasting people’s time?
Thanks for the info! I guess that’s ultimately what I’m looking for more about: how much do we know about cellular traffic? Obviously with encryption we can’t just directly read cell signals to find out what’s being sent, so do people just record the volume of data being sent in individual packets and make educated guesses?
It seems plausible to run a simple(non-AI) algorithm to isolate probable conversations and send stripped and compressed audio chunks along with normal data. I assume that’s still probably too hard to hide, but if anyone out there knows of someone that’s looked for this stuff, I’d love to check it out.