Philips TV stuck in a “Your Privacy Choices” loop on FAST channels – cause, key logs and fix (thanks to Claude)

**TL;DR** Allow All kept looping back to the privacy screen. I wanted to avoid drastic options like a factory reset, so I asked Claude (an AI assistant) how to find the real error. From my adb logs it worked out that two Philips system apps disagreed about the saved consent, and it suggested clearing both and rebooting. That fixed it.

TV: Philips [oled 707], software [latest and no further provided. ]. I ran the commands and pasted the logs. Claude read them and suggested each step.

**The fix Claude suggested** “` adb shell pm clear org.droidtv.nettvregistration adb shell pm clear org.droidtv.fastip adb reboot “` Then press Allow All once. The reboot matters (see below).

**What Claude suggested, in order** 1. Easy things first: back out and relaunch the app, and power cycle the TV. [Say whether you tried these.] 2. Clear the cache, then the data, of the "TV" app. I did both. No change, because it was the wrong app. 3. Check for updates. None were available. 4. Change DNS (e.g. 8.8.8.8). I tried it. No change. Network and clock were fine. 5. Other low-risk options: More Choices > Reject all/Confirm choices, a phone hotspot, automatic date and time, the TV's privacy settings, and force stop plus unplugging for a minute. [Say which you tried.] 6. Drastic options, which I wanted to avoid: uninstall the app's updates, factory reset (not possible for me), or disable an app via adb. 7. I asked how to see the actual error, so Claude suggested adb: connect over Wi-Fi, then `dumpsys window | grep mCurrentFocus` while the consent screen was showing, to identify the app. 8. Reading the logs, it spotted the mismatch (excerpts below). 9. Clear both apps' data. The loop stopped, but channels were black. 10. Reboot. Streams played.

**Key log excerpts** (PIDs trimmed, and one long stream URL shortened.)

1. Which app owns the consent screen. It's not the "TV" app: “` $ adb shell dumpsys window | grep mCurrentFocus mCurrentFocus=Window{cbae016 u0 org.droidtv.nettvregistration/org.droidtv.nettvregistration.onetrust.IABActivity} “`

2. The choice WAS saved when I pressed Allow All: “` 20:37:17.423 D NetTVRegistrationDeviceState: setCmpShowTouValue val=false “`

3. Yet the wizard was launched again, by another uid: “` 20:37:16.936 I ActivityTaskManager: START u0 {act=org.droidtv.tv.intent.action.SHOW_IAB_TOU_WIZARD cmp=org.droidtv.nettvregistration/.onetrust.IABActivity (has extras)} from uid 10058 “`

4. Who is uid 10058: “` $ adb shell pm list packages -U | grep "uid:10058" package:org.droidtv.fastip uid:10058 “` So the FAST channels service kept relaunching the consent screen, although the registration app had saved my answer. That's the mismatch.

5. After clearing both apps, the loop stopped but channels were black. The channel metadata loaded fine, but the TV app had no service connection: “` 20:57:56.900 D FastIpServiceConnector: onFastIpMetadataResponse-responseType 0 responseStatus 0 eTag 2|5298 20:57:56.945 D FastIpServiceConnector: triggerNowNextDataForChannel() mFastIpSvc NULL “`

6. After the reboot, the stream played: “` 21:03:19.970 I StreamTransferListener: onTransferInitializing: https://…playouts.now.amagi.tv/…/1920x1080_4716800/index.m3u8 21:03:20.349 D FASTPlayer: onVideoSizeChanged, width=1920, height=1080 “`

7. Things ruled out: “` D ChannelListUtil: isFastIPCountrySupported retVal true 3 packets transmitted, 3 received, 0% packet loss Wed Oct 21 20:51:43 BST 2026 “` Region supported, network fine, clock correct, and no FATAL/AndroidRuntime crashes anywhere.

**Side effects** 1. Black channels until the reboot. 2. The loop came back once ("signing on", then the privacy screen). Repeating the fix worked and has survived a restart. 3. Terms of Service and "Statistics to help us improve" prompts reappeared, because the registration app's stored answers were wiped. They're optional. 4. A "New device found" Fire TV notice appeared. Claude thought it was probably normal network discovery, but we don't know.

**Noise to ignore** This one is a harmless security-policy line: “` W PerfettoTrace: … avc: denied { write } for name="traced_producer" … app=org.droidtv.nettvregistration “` Also the Google Assistant app-scan spam, `callFailed: interrupted` (a cancelled ad-tracking request) and `responseStatus 5 … unhandled`.

**Connecting adb** Settings > System > About, tap Build 7 times. Enable USB debugging in Developer options, then `adb connect <TV-IP>:5555` and accept the prompt. On my phone I used Termux from the Play Store (`pkg install android-tools`) and it worked fine. Turn USB debugging off afterwards.

**Where Claude got it wrong** Its first suggestions were to clear the "TV" app, which was the wrong target. Its first adb guess for the package name (`grep -i philips`) wasn't reliable. One log filter it gave matched version numbers (403/404) and flooded the screen. It couldn't see the TV, only what I pasted or photographed, and it never found the original trigger.

I believe other people have noted to specifically find those apps and clear. And it might be stale and return in 180 days.

Worth knowing how to identify issue. And fixes. Both adb and in app.

Very impressed with Claude once I got it debugging.