

“Strike 2” applies even in that scenario.
HW/FW security researcher & Demoscene elder.
I started having arguments online back on Fidonet and Usenet. I’m too tired to care now.
“Strike 2” applies even in that scenario.
Sure. And then all the developers who have made that functionality work need to be in on the conspiracy, and all the cybersec researchers need to be also (or incompetent). And the false positive rate would be sky high due to trying to match so many different words to the waveforms.
The phones don’t listen to your conversations.
Yeah - your boyfriend had watched the video. Your phone was then next to your boyfriends for some amount of time. That’s a well known location datapoint for ad targeting (and is the reason for why people freaked out when Facebook started recommending their therapist as “person you might know” etc).
I could’ve added that I spent 15 years working as a developer in the mobile phone industry, but in reality that shouldn’t be needed. All that’s necessary for you to independently verify what I wrote regarding how voice keyword triggers function and the difference in power draw between that and the full audio pathway for recording is available through the nearest search engine.
Smartphones are not recording conversations.
Strike 1: Battery life would be enormously impacted. “Ok google” and such keywords run on specific low power hardware that THEN wake up the rest of the phone when triggered. General recording would need the full phone to always be running == very short battery life.
Strike 2: The whole combined cybersecurity field are constantly probing mobile phones (hardware and software) for security issues. If there was either code or hardware that was always listening you would have seen lots of headlines with actual proof.
The word you’re looking for is “synchronicity”.
waving
Not sure what you mean with “mythical” though - whenever we’re allowed to talk publicly about something we happily do.
(My own speciality is in IoT devices, others focus on mobiles)