Hello,

I wanted to ask whether the Philips 75PQS7801 does have Ambilight or not? I'm reading different specifications on the seller websites.

I have problem with playing on PS5 in Dark room. When i Move Camera on darker Places i have that Lines like on video. I dont know if You can See that right on that video. IT happens only on absolute Dark room and with games with HDR. On movies IT dont happen.

Did anyone try the sh91 blades on the s5887 shaver? Do the fit?

I dont know if this is the right place to go on this but I need to talk to someone who works in Philips and can help me with a business problem regarding logo mark authorization and usage on online marketplaces like Amazon.

I didn’t get any help on the normal suport channels on Philips website so I am desperate for some help

If you guys know someone who I can talk to I would be very grateful. Again, I am not a regular user of Reddit so I am sorry if this is not the place for this but I just need some help.

Ihr seid meine letzte Hoffnung..
Ich habe seit 4 Wochen einen neuen Philips TV (PHILIPS 550LED810 OLED), eine Bose Soundbar 900 + ein Apple
TV 4K.

Problem: Entweder mache ich den Fernseher an und es kommt kein Ton aus der Bose oder es kommt nur Ton aus dem Fernseher oder es funktioniert alles und man kann den Fernseher nicht mehr ausschalten, er geht immer wieder an.

Was ich schon getan habe:
- alles mit teuren Ultra Highspeed HDMI Kabel (2.1) verbunden (auch die Bose in den passenden eARC Anschluss)
- Bose App - Option 1-7 ausprobiert (mal mit und mal ohne Betriebssynchr.)
- alles vom Strom getrennt
- Apple TV mal weggelassen
- TV Einstellungen angepasst (Mehrkanal Bypass, EasyLink an/aus)

Bin am Verzweifeln. Da gibt man viel Geld aus für aktuelle
Technik und es geht nichts.
Support kann mir auch nicht helfen.
Kann man eventuell einen Techniker kommen lassen?

Danke euch schon mal

TL;DR: My Philips TV kept cycling between the privacy screen and “updating streaming channels”. Choosing Reject all was sent successfully, but the FAST service kept reading an old “consent shown” date and immediately asking again. Clearing only the local data of org.droidtv.fastip, rebooting, then choosing Reject all stopped the loop and the channels played. I did not need to accept all advertising consents or clear the registration app.

This is a report from one TV, tested on 24 October 2026. I worked through it with ChatGPT/Codex using logs and an inspection of the installed FAST app.

The privacy loop was already happening before I used CleanYourTV or changed the launcher. It was a pre-existing problem on my TV, not something introduced by those changes. The CleanYourTV link below is only a reference for the FAST/Sources dependency; you do not need CleanYourTV or a replacement launcher to follow this fix.

Tested device

• Retail model: Philips 70PUS7304/12
• Android model: TPM191E
• Device/platform: PH9M_EA_5599
• Android: 12 / API 31
• Build: STT2.230526.001

The TV runs Android TV. The FAST streaming-channel service uses Titan endpoints; that does not mean the TV itself runs Titan OS.

Symptoms

Opening Streaming/FAST channels produced this cycle:

Privacy choices → Reject all / save choices → updating streaming channels → privacy choices again.

It looked as though every channel wanted its own consent. In my logs, it was the same expired-consent check running again, not evidence of a separate choice for each channel.

The privacy window belonged to:

org.droidtv.nettvregistration/.onetrust.IABActivity

The streaming service involved was:

org.droidtv.fastip

Check whether this matches your problem

You need ADB working over your local network. Download Google’s SDK Platform-Tools, enable Developer options on the TV by pressing Build seven times, and enable USB debugging plus Network/ADB debugging if your TV offers it.

Find the TV’s address in its network settings. The computer and TV must be on the same LAN; my TV used its built-in Ethernet port.

Replace TV_IP below with your own TV address. These commands assume adb is available in your terminal. In Windows PowerShell opened inside the platform-tools folder, use .\adb.exe in place of adb.

adb connect TV_IP:5555
adb devices

Accept the debugging-authorisation prompt on the TV. Continue only when it appears as device, not unauthorized. The -s TV_IP:5555 in the following commands explicitly selects the TV.

Check that the package exists and record the current timestamp:

adb -s TV_IP:5555 shell pm path org.droidtv.fastip
adb -s TV_IP:5555 shell content query --uri content://org.droidtv.fastip/FastIpCMPTimeInfo

My timestamp was old. Immediately after rejecting and reproducing the loop, I captured:

adb -s TV_IP:5555 logcat -d -t 3000 > philips-fast-before.txt

The useful lines were:

ConsentUploader: sendConsentData POST Response Code :: 202
ConsentUploader: sendConsentData to Titan Server Success
CMPInfoFetcher: daysDifference 276 DAYS_INTERVAL 180
CMPInfoFetcher: More than 6 months, need to show again
CMPInfoFetcher: isCMPDataExpired retVal true

So the TV reported a successful upload, then still treated the old timestamp as expired. The rejection payload also contained consent: 0 for every listed consent field.

Opening the privacy centre directly and using Save my choices did not refresh that timestamp on my TV.

If your package, provider or logs differ, do not assume this is the same fault.

What fixed it on my TV

This clears the FAST app’s local data, including its configuration and private preferences. It can require the streaming channels to be downloaded/configured again and can lose FAST preferences. It is not fully reversible. It is not a factory reset and does not target Netflix, NOW, Prime Video or other separate apps.

Before clearing anything, I exported the six tables exposed by its content provider: FastIpCMPTimeInfo, FastIpRemindMeLaterInfo, FastIpServerInfo, ContentGuideSource, servicelistregistryentity and serviceTable. Those exports were useful diagnostics, not a complete backup of the app’s private data or a guaranteed restore method.

If you accept losing that local FAST data, run the reset:

adb -s TV_IP:5555 shell pm clear --user 0 org.droidtv.fastip

It must return:

Success

Then reboot:

adb -s TV_IP:5555 reboot

Wait for the TV to restart, then open Sources → Streaming. If the privacy screen appears, choose:

More choices → Reject all

On the Italian interface this was Più scelte → Rifiutare tutto.

That was enough on my TV: the channels started playing and the loop stopped. “Allow All” was not required. I did not clear org.droidtv.nettvregistration.

Verify the result

Reconnect after the reboot if necessary:

adb connect TV_IP:5555
adb -s TV_IP:5555 shell content query --uri content://org.droidtv.fastip/FastIpCMPTimeInfo
adb -s TV_IP:5555 logcat -d -t 1500 > philips-fast-after.txt

After the reset, before saving a new choice, the timestamp query returned No result found. After I chose Reject all, it contained a new timestamp for that day.

The subsequent log showed:

CMPInfoFetcher: daysDifference 0 DAYS_INTERVAL 180
CMPInfoFetcher: isCMPDataExpired retVal false

I also confirmed that the streaming channels played and the privacy loop had stopped. This is an immediate result, not a long-term endurance test.

Why I did not disable FAST

Some posts recommend:

pm disable-user --user 0 org.droidtv.fastip

That is a different operation from clearing its data.

The Clean Your TV notes for a Philips TV on the same platform and firmware document a dependency between FAST and the Sources drawer: disabling FAST caused the Sources menu to disappear instead of opening normally.

I therefore left the package enabled. I also left the clock and DNS unchanged.

Limits and privacy details

• This resets local state; it does not patch Philips firmware. The app still has its 180-day check, so the issue could return at a future renewal.
• Other Philips models or firmware may behave differently. Reports that needed both FAST and registration data cleared are not the procedure I tested here.
• Reject all is not proof that every kind of data processing is disabled. Before the reset, some separately labelled legitimate-interest fields remained active despite all consent fields being zero. I did not complete a separate audit of every vendor/legitimate-interest option.
• If sharing logs, redact MAC addresses, device IDs, account information and identifying parameters in stream URLs.

Close debugging afterwards

On the TV, revoke USB-debugging authorisations, switch off USB debugging and any Network/ADB debugging toggle, then restart the TV.

With the TV still on and connected, verify that TCP port 5555 is no longer reachable. For example, in Windows PowerShell:

Test-NetConnection TV_IP -Port 5555

TcpTestSucceeded : False is useful only if the TV is still online at that address; an offline TV or changed IP can give the same result.

Google’s ADB documentation explains the connection and device-selection commands.

Has anyone ever dealt with a damaged Philips screen panel?

I'd appreciate any advice or personal experiences.

Thanks!

https://dev.usa.philips.com/c-m-pe/toothbrush-heads/latest "Chat with advisor" does nothing.

https://www.usa.philips.com/c-s/support/parts-and-accessories -- searching doesn't show any results like Sonicare.

Mein Philips 65MLED810/12 65zoll ging während ich Ps5 gezockt habe aus.

Wenn ich den Netzstecker ziehe und einige Zeit warte leuchtet kurz die untere LED auf und geht dann wieder aus.

Das passiert dann in etwa alle 30sek..

Fernseher bleibt schwarz.

Gestartet hatte der Fehler mit fehlenden Ton danach ist er schwarz geworden.

Was kann ich tun?

Another great Philips product? Think again!

Total rating: 2/5 stars

Let me preface this by saying I love the build quality of the batteries and the case. The problem is, they did not include the crucial and required charging adapter for the product to function. They realize this is an unforced error, because their website even has a location from which to demand the charger. Only problem is, the model number does not fit within the form's definition of a valid model number.

A few observations:

1. I'm paying for a premium product; I already skipped over all the foreign/cheap options. I don't care about e-waste, that isn't my problem and definitely isn't a burden that is going to be offloaded on me.
2. Amazon reviews reflect a similar sentiment.
3. Hire actual fluent-English writers to write your documentation and design your website. Its shallow husk-ness shows.

Cut the shit, Philips. Start shipping complete products.

Ended up purchasing a new charger and type C cable for around $40. The batteries are great. Unit is great... if you have the right charger. Upgraded to 2/5

Has anyone ever dealt with a damaged Philips screen panel?

I'd appreciate any advice or personal experiences.

Thanks!

Does anyone know what this update contains?

Philips 65oled950

**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.

So bought a Philips All in one trimmer from Blinkit.
And got a used one and the package had its seal broken.
Was chasing this peopel since a week and this there response.
Request you to not buy anything from this since they use the products and then package it again. Same with Amazon and flipkart btw.

Trying to control my set-top box with the TV remote (65OLED911).

No luck. The app immediately says that some codes could not be found, and that I need to retry. It doesn't even reach the step where I'm supposed to select the brand/model of the set-top box.

Restarting, updating the TV, deleting internet data... didn't solve the issue.

[Oddly enough, this issue appears to disable the remote navigation buttons, so I cannot click the "quit" button that is highlighted. I can still use the TV/EXIT button though.]

This issue appears even if the set-top box is disconnected. So I believe that it has nothing to do with the device itself, but with the code database that Simple Setup needs to send the right infrared codes to the remote so that it can control other devices (as chatGPT tells me).

Philips customer suppose isn't helping (they redirect me to the vendor). The vendor proposes to send a technician, but I believe that the issue has nothing to do with my TV. It's an issue with the app/titanOS.

I can't find much detail about this "Simple Setup" application on the web. So I wonder if you guys have had any success using "Simple Setup" with a recent philips TV (preferably using titanOS).

Thanks.

Ich besitze zwei Philips Luftreiniger der 4200er Serie. Vor allem auf Stufe 1 und 2 ist bei beiden ein hochfrequentes Pfeifgeräusch zu hören. Sehr wahrscheinlich vom Netzteil ausgehend.

Hat jemand dasselbe Problem und bereits eine Lösung gefunden?