QWE AI Academy Is my Samsung TV actually listening for the baby and the dog?
Owners keep asking that after late October 2026 posts about a 2025 Tizen set, on-board sound classifiers, and an OpenAI suspension. Features exist. Some were marketed. Telemetry paths are real. Your move is settings plus network hygiene – not rooting threads.
Key takeaway: Treat the set like any always-on appliance with a mic path. Kill Voice Wake-up and Viewing Information Services first. Block known telemetry at DNS. Use a chat tool only to map public menus. Most of the privacy win sits there – no brick risk, no warranty void, no API ban lottery.
Think of it less like a spy movie and more like a smart speaker that also happens to be your biggest screen. Same category of defaults. Same habit: assume cloud interest until you prove otherwise with your own logs.
What just dropped
Community posts from @log4j (Oct 21-24, 2026) describe a rooted 2025 Samsung Tizen TV with ambient classifiers – dog-bark and baby-cry counters in telemetry – always-on voice-related services, ACR-style fingerprinting, a packet logger (rmdemon), and traffic toward Samsung cloud endpoints plus partner lists. Same week: OpenAI suspended the account. The researcher said the work stayed local reverse engineering, tripped an automated cyber-abuse / daybreak-style classifier, and burned roughly $500 in credits (status post).
Not pure stealth, though. Samsung already demoed audio-sensor home care at CES 2025 under SmartThings – baby cry, dog bark, glass break, notifications with the screen off. Capability was public. The living-room gap is defaults, how obvious the counters feel in the UI, and whether toggles actually stop packets.
Jake Stevens separately claimed Codex helped strip screenshot fingerprinting, HDMI input reading, and Bixby wake detectors, with a ~3× snappier feel afterward; Claude refused rooting-style asks. Different lane: April 2026 work from Calif showed Codex escalating from a browser shell to root on an older KantS2 Tizen build. Privilege-escalation lab ≠ this privacy dump. Don’t mix the two when you plan a living-room fix.
Method A vs Method B for regular owners
Two paths. Only one fits most households.
| Approach | What you do | Risk | Upside | Who it fits |
|---|---|---|---|---|
| A. Full reverse / root + AI agent | Dump firmware, disable packages at system level, custom launcher | High (brick, ban, missed updates, new holes) | Maximum control; anecdotal ~3× speed | Experienced researchers only |
| B. Settings + network audit (AI on public docs) | Every privacy toggle, then Pi-hole / NextDNS / AdGuard lists; optional AI for menu labels | Low | Reversible; keeps warranty and updates; catches most mic + ACR paths | Everyone else |
Viral posts sell A. B is what you finish tonight and undo tomorrow if a firmware push gets weird. Winner for this guide: B.
Walkthrough: the safer privacy audit that still works
Remote only. Labels drift by year and region; clusters on 2024-2026 Tizen stay familiar. Paths below match patterns in Samsung’s Bixby support docs (AU examples updated 2026) – re-check after big firmware drops.
- Settings → All Settings → General / Privacy (or top-level Privacy Choices). Terms, Viewing Information Services, Interest-Based Advertising, Smart Hub. Viewing Information / ACR-style options: Off. Write the date down.
- Advanced Features → Voice → Bixby Settings (or General → Voice). Voice Wake-up / Hands-free: Off. Disable Allow Audio Recording Review and voiceprint options. Some models won’t uninstall Bixby; wake-up off is the lever that matters.
- SmartThings / Home Care / Pet & Family Care: if baby-cry or pet-bark alerts are on, choose on purpose. Don’t need phone pings? Turn the ambient path off.
- Hardware mic mute on the remote or bezel – use it. Unpair the soundbar for a clean test night.
- DNS filter on the TV (Pi-hole, AdGuard Home, NextDNS). Community Samsung telemetry/ad lists change; watch the query log 24 hours. Standby noise surprises people.
Pro tip: After toggles, ask a coding/chat model only for “current Samsung Tizen privacy menu paths for model year X” or “public support pages on Viewing Information Services.” Screenshots of your own Settings screens are fine. Stay off firmware dumps and privilege escalation. That classifier lane is how accounts died this week.
Ground truth is boring: TV in standby, leave the room an hour, read DNS logs. Talk near it with wake-up off. Soundbar still twitches? Power it down or unpair.
Edge cases the viral threads skip
The catch is opt-out isn’t binary. As of October 2026 coverage of Watching-the-Watchers-style tests, Samsung Tizen units still showed ACR-consistent traffic across built-in apps, antenna, HDMI, and other inputs after the official Viewing Information-style toggle. Setting = necessary, incomplete. Router blocklist = backup.
No built-in mic ≠ silence. Voice client can grab a paired soundbar or Bluetooth mic and aim audio at Bixby paths – behavior called out in the same @log4j community write-ups. Matching soundbar owners: test cold.
AI policy is messy. Codex helped strip packages for some; Claude said no to rooting; OpenAI automation banned at least one researcher who insisted the RE stayed local. Binary-heavy day job? Keep deep reverse work on local or air-gapped models. The ~$500 credit hit wasn’t hypothetical that week.
CES 2025 sold the baby/dog sensor out loud. Internal names like always-on voice services and SOUNDSENSOR-style counters feel colder in a dump. Marketing slide and firmware counter can both be true.
One open question I still turn over: on a normal evening, how many ambient classifiers stay fully on-device, and how many counters leave the house? Public posts and the marketing pages still don’t close that loop.
FAQ
Did OpenAI really ban someone just for reverse-engineering a TV?
Yes – per the researcher’s posts. Suspension, credits gone, cyber-abuse-style classifier, local-only claim. Similar appeals often end final.
Can I just turn everything off in the menu and be done?
Most of the way. Voice Wake-up off, Viewing Information Services off, SmartThings ambient alerts off, then DNS blocking. Hardware mute plus soundbar unpair covers the obvious leftover vectors. Full package removal needs root; that’s outside a safe beginner pass.
If you only flip menu switches and skip DNS, you’re trusting a toggle that independent traffic tests already poked holes in. Logs or it didn’t happen.
Is the baby/dog listening a secret spy feature or a sold SmartThings product?
Both show up in the record. Samsung demoed cry/bark/glass detection for home care at CES 2025. Researchers later matched counters, always-on service names, and cloud endpoints on a 2025 set. The transparency problem is UI honesty day to day – not whether the product slide existed. Never turned on home-care alerts? Flip related toggles off anyway and verify with your network log, not a screenshot of a marketing page.
Tonight’s move: remote → Voice Wake-up and Viewing Information Services off → DNS filter on the TV → read the query log for 24 hours. That changes what leaves the living room.