By television

Philips OLED950 and OLED910: what they ship with and what can come off

· 8 min read

Specification card for the Philips OLED950 and OLED910 showing its main figures
Philips OLED950 and OLED910: the figures that define the set
Specifications
Year2025
SystemGoogle TV on Android 14
Resolution4K UHD
PanelOLED; the 950 carries a META 3 panel
Refresh rate120 Hz native; VRR up to 144 Hz over HDMI
HDRAll four: Dolby Vision, HDR10+ Adaptive, HDR10 and HLG
BrightnessPhilips publishes no figure in nits
Storage32 GB; the RAM is not published
Sound70 W in 2.1 on the 950; 80 W in 3.1 with Bowers & Wilkins on the 910
Connections4 HDMI: only 1 and 2 are 2.1 at 48 Gbps
eARCOn HDMI 2, which is one of the two fast ones
AmbilightFour-sided on both
Sizes65" and 77" the 950; 55", 65" and 77" the 910

These two are the OLEDs at the top of the Philips catalogue, and they share almost everything: the same Google TV on Android 14, the same four HDR formats, the same four-sided Ambilight and exactly the same port layout.

What separates them is the sound, and it is a bigger difference than it looks. But before that it is worth looking at the ports, because there is a conflict there that you will have to settle the day you plug them in.

Four HDMI ports, two fast, and the eARC takes one

Philips documents this with welcome clarity, both on the spec sheet and in the manual: HDMI 1/2: HDMI 2.1 full bandwidth 48 Gbps, up to 4K 144 Hz. HDMI 3/4: HDMI 2.0.

And in the manual, in case of any doubt: eARC is only available on HDMI 2. Plain ARC as well.

Put the two sentences together and the problem falls out: of the four ports, only two accept 4K at 144 Hz, and the eARC lives on one of those two. If you connect a soundbar —which is the normal thing on a television of this class— you are left with a single fast port for everything else. Console on HDMI 1, soundbar on HDMI 2, and that is the whole allocation: there is no more.

If you have two consoles, you will have to choose which one goes without the 144 Hz. And if you plug the console into 3 or 4 without looking, you will be playing at 60 Hz on a television capable of a great deal more, with nothing to warn you.

Five minutes spent on this pays off better than any app clear-out. Do it first.

The 120 Hz, and the 144 that are not the same thing

Philips is honest here, and it is worth pointing out because not every maker is. Its spec sheet declares 120 Hz of native refresh rate and, in a separate field, 144 Hz of variable refresh rate. The brochure spells it out: 120 Hz native, and the 144 Hz arrive over VRR through HDMI for anyone playing from a PC.

That is: 120 Hz is what the panel gives, and 144 is a ceiling it reaches with variable signals. They are not the same thing, and Philips does not try to make them look alike.

The European energy label, the regulated document, also declares 120 Hz. It all lines up.

The brightness that nobody publishes

This is the hole in the spec sheet, and it is striking on a flagship OLED: Philips does not give a single figure in nits. Not on the technical sheet, not in the sales brochure, not on the energy label. The most concrete thing it says is that the panel reaches "astonishing levels of peak brightness", which is not a figure.

On the 950 it does name the panel: OLED META 3, the generation with the microscopic lens and the brightness booster. That is useful information, but it is no substitute for a number.

If brightness is what decides your purchase, here you will have to trust independent measurements, because the manufacturer will not commit.

Where they actually differ

The OLED950 carries the META 3 panel and the P5 AI Dual Picture Engine. Its sound is 70 watts in a 2.1 configuration: four 10 W drivers for mids and highs, plus a 30 W subwoofer. It is sold in 65 and 77 inches.

The OLED910 carries the P5 AI Perfect Picture Engine and takes the sound up to 80 watts in 3.1, with six 8.5 W drivers and the same 30 W subwoofer. And here is the interesting part: its speakers are Bowers & Wilkins, and the spec sheet says so in the configuration field itself. The 950 does not carry that signature. It is sold in 55, 65 and 77 inches, so it is the only one of the two that exists in 55.

In short: the 950 has the better panel and the 910 has the better sound. That is not the hierarchy the numbers would lead you to expect.

Both accept Dolby Vision, HDR10, HDR10+ Adaptive and HLG —all four formats, something almost no manufacturer offers—, both carry four-sided Ambilight, 32 GB of storage, Wi-Fi 6, Bluetooth 5.2 and two USB ports. Philips does not publish the RAM anywhere.

Ambilight is not an app

This settles a lot of nerves before anything gets touched: Ambilight lives in the firmware, not on the package list. There is no app you can disable by mistake and end up with no lights behind the television. The same goes for the P5's image processing.

Nothing this page explains can spoil either of them.

Illustration. Decorative: the diagrams in the text carry the detail.

How to tell whether this page is about your set

Under Settings → System → About you will find the model and the Android version, which here should say 14. With ADB, getprop ro.product.model gives the same thing without going through the menus.

And a warning that holds for the whole brand: not every Philips runs Google TV. The mid-range and entry models carry Titan OS, which is Philips' own system with no Android underneath, no ADB and no packages to disable. The border sits between the OLED770, which carries Titan OS, and the OLED810, which already carries Google TV. From there up —810, 820, 850, 860, 910 and 950— they all share the platform, and this page serves them all with very few changes.

If your television does not say anywhere that it has Android, this is not your case.

What ships on it

Google's. The launcher (com.google.android.tvlauncher), the recommendation engine (com.google.android.tvrecommendations), voice search (com.google.android.katniss) and the services (com.google.android.gms). It is the layer that decides what you see when the set comes on.

Philips'. Not much, and the important part is not here: its picture settings, Ambilight and the P5 processing are in the firmware. What you will see is some setup assistant and the maker's own content apps.

Everybody else's. Netflix, Prime Video, Disney+ and the rest arrive installed under a commercial agreement, and the remote usually comes with dedicated buttons. The button stays even if you remove the app: it will simply stop leading anywhere.

What comes off without much thought

The streaming apps you do not use. With 32 GB space is not the problem, but everything else is: they update themselves, they appear in the recommendation row and they talk to their servers. If you subscribe to one tomorrow, it reinstalls from the store in two minutes.

The free content channels that fill the home screen are the second obvious case.

What to look at first

The recommendation engine. Removing it leaves a clean home screen, but it also empties the "continue watching" row, which in a house with several people is missed.

And before touching any package, go through the television's own privacy settings. A fair amount can be cut back from there, with no ADB and no risk at all.

What not to touch

Google Play services. They are the foundation of the store, of the accounts and of a good part of the apps. Without them the set boots and little else.

The launcher, as long as you have no other one installed and working. A television with no launcher comes on to a black screen, and fixing that with the remote alone is a great deal harder than having thought about it beforehand.

Anything starting with com.android. that you cannot identify: com.android.systemui is the system interface and com.android.settings is the settings app itself.

And here with particular care, anything to do with HDMI and with the control of external devices: that is where the eARC on HDMI 2, the VRR, the ALLM and the 144 Hz of the good ports pass through, which is exactly the part that cost you the most work.

What you actually notice

The home screen stops proposing series from services you do not have. The content notifications disappear. And the television answers the remote slightly sooner in the first seconds after switching on.

What does not change: the OLED panel, Ambilight, the P5 processing, the four HDR formats or the sound. All of that lives below Google TV, and it is exactly what you paid for.

All of this comes undone

Packages disabled over ADB come back with one command, and a factory reset returns the television to exactly the state it left the box in. Nothing here touches the system: you are only telling the set not to load something that was already installed.

If you own one

The app list from your OLED950 or your OLED910 is the one thing missing to close its entry. And if you also measure the brightness, or have access to a reliable measurement, better still: it is the figure Philips publishes for none of its OLEDs, and today nobody states it with the source in front of them.

Everything here applies to a device you own, and every removal is reversible. The limits of this project: What we do and do not do