Philips OLED820 and OLED850: what they ship with and what comes off
· 8 min read
| Year | 2025 |
|---|---|
| System | Google TV on Android 14 |
| Resolution | 4K UHD |
| Panel | 4K Ultra HD OLED, 3840 x 2160 |
| Refresh rate | 144 Hz native on the 820; 120 Hz on the 850. VRR to 144 on both |
| HDR | All four: Dolby Vision, HDR10, HDR10+ Adaptive and HLG |
| Brightness | Philips publishes no figure in nits |
| Storage | 32 GB of flash; the RAM is not published |
| Sound | 70 W RMS: four 10 W speakers and a 30 W subwoofer |
| Processor | P5 AI Perfect Picture Engine |
| Connections | 4 HDMI: only 1 and 2 are 2.1 at 48 Gbps |
| eARC | On HDMI 2, which is one of the two fast ones |
| Ambilight | Three-sided on both |
| Sizes | 42", 48", 55", 65" and 77" the 820; 55" and 65" the 850 |
Philips is the brand where the model number decides whether this page is any use to you. And it is not a nuance: it is the difference between being able to disable packages and not being able to touch anything at all.
The OLED820 and OLED850 are on the good side. Both declare OS: Google TV™
on the official spec sheet, and the manual for this family says Android
14 in so many words. But a couple of steps further down, under a name that
looks almost identical, the system changes completely.
Where the line actually falls
The manufacturer's own spec sheets make it clear, model by model:
- OLED760 and OLED770:
OS: TITAN OS, with 8 GB of memory. - OLED810, OLED820, OLED850 and OLED860:
OS: Google TV™, with 32 GB.
Titan OS is Philips' own system and there is no Android underneath. Without Android there is no ADB, no package list and nothing to disable. Everything this site explains stops applying there.
That the 810, 820, 850 and 860 are the same platform is not a guess either: the OLED860 manual carries, in a single document, the EPREL numbers for all four series. The sizes come from that same list, and here they do not match: the OLED820 exists in 42, 48, 55, 65 and 77 inches, the OLED850 only in 55 and 65.
Four HDMI ports, two fast, and the eARC takes one
Both spec sheets say the same thing: HDMI 1/2: HDMI 2.1 full bandwidth 48 Gbps, up to 4K 144 Hz. HDMI 3/4: HDMI 2.0. And under connectivity, eARC on HDMI 2. The manual repeats it flatly: eARC is only available on HDMI 2.
Put the two sentences together and the problem appears. Of the four ports only two run, and the eARC lives on one of those two. Plug a soundbar into HDMI 2 (where it has to go) and you are left with a single fast port. And if you connect the console to 3 or 4 without checking, you will be playing at 60 Hz on a television that reaches 144, with nothing to warn you. Do this first.
The 820's 144 Hz and the 850's 120
There is a surprise here, and it runs against what the model number suggests.
The OLED820 declares 144 Hz native refresh rate. The OLED850 declares 120 Hz. Both declare, in a separate field, VRR up to 144 Hz, and both accept 3840 x 2160 at 144 Hz as an input resolution.
That is: on the 850 the 144 Hz arrive through variable refresh, and on the 820 the panel already delivers them. It is not an isolated case: the OLED860 also declares 144 native and the OLED810, 120. And the two models at the top of the catalogue, the OLED910 and the OLED950, declare 120.
So on native refresh the OLED820 is ahead of the OLED850 and of the two sets that sit above both of them. If you play from a PC, that figure counts for more than the commercial tier.
Where they actually differ
They share almost everything: a 4K Ultra HD OLED panel at 3840 x 2160, the P5 AI Perfect Picture Engine, all four HDR formats (Dolby Vision, HDR10, HDR10+ Adaptive and HLG), three-sided Ambilight, 32 GB, dual-band Wi-Fi 802.11ax 2x2, Bluetooth 5.2, two USB ports, Gamebar 2.0, FreeSync Premium, G-Sync compatibility, HGiG and a wirelessly charged remote. Both are energy class G, at 84 W in SDR and 112 W in HDR.
And the differences that are actually documented are these:
The sound, on the label. Both declare 70 W RMS and the same configuration: four 10 W mid-high speakers plus a 30 W subwoofer. But the 820 labels it 4.1 and the 850 labels it 2.1. Same speakers, different channel count, no published explanation.
AirPlay. The 850's spec sheet lists Works with Apple AirPlay; the 820's does not mention it. Both are listed as working with Apple Home and MATTER.
The stand and standby draw. The 820 has a central satin chrome metal stand; the 850, an arch stand. In standby the 820 declares less than 0.5 W and the 850, less than 0.3 W.
Brightness and RAM: the two gaps
Philips publishes no brightness figure in nits at all for either of these sets. Not in the spec sheet, not in the manual, not in the European energy label. This is not an omission on our side: it is in no document the manufacturer produces, so you have to rely on independent measurements.
Memory is the same story. The only figure that appears is
Memory size (Flash): 32 GB, which is storage, not working memory. The RAM
is not declared.
Ambilight is not an app
This settles a lot of nerves before anyone touches anything: Ambilight lives in the firmware, not in 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 picture processing.
On these two it is three-sided, not four-sided as on the OLED910 and the OLED950, with game mode, music mode and wall-colour adaptation. There are phone apps and third-party integrations to control it, and those can come off; Ambilight itself will still light up with the television.
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 read 14. With ADB connected,
getprop ro.product.model gives the same without walking through menus.
If your television mentions Android nowhere, it belongs to the other half of the catalogue and this page is not yours.
What it ships with
The Google side. The launcher (com.google.android.tvlauncher), the
recommendations engine (com.google.android.tvrecommendations), voice search
(com.google.android.katniss) and the services (com.google.android.gms).
That is the layer that decides what you see when you switch on.
The Philips side. Not much, and the important parts are not here: picture settings, Ambilight and P5 processing all live in the firmware. What you will see is a setup assistant and some own-brand content apps.
Third parties. Both spec sheets name Netflix, Prime Video, Disney+, Apple TV and YouTube. The remote usually carries dedicated buttons: the button stays even if you remove the app, and simply stops leading anywhere.
What comes off without much thought
The streaming apps you do not use. With 32 GB space is not the problem, but the rest is: they update themselves, they show up in the recommendations row and they talk to their servers. If you subscribe tomorrow, one reinstalls from the store in two minutes. The free content channels that fill the home screen are the second clear case.
What to look at first
The recommendations engine. Removing it leaves the home screen clean, but it also empties the "continue watching" row, which is missed in a house with several people in it.
And before touching any package, go through the television's own privacy settings. You can cut back a good deal from there, with no ADB and no risk.
What not to touch
Google Play services. They are the foundation of the store, the accounts and a good part of the apps. Without them the television boots and little more.
The launcher, as long as you do not have another one installed and working. A television with no launcher switches on to a black screen, and fixing that with the remote alone is far harder than planning ahead.
Anything starting with com.android. you cannot identify:
com.android.systemui is the system interface and com.android.settings is
the settings app itself.
And with particular care, anything to do with HDMI and external device control: that is where the HDMI 2 eARC, VRR, ALLM and the 144 Hz of the good ports live.
What you actually notice
The home screen stops pushing shows from services you do not have, content notifications disappear, and the set answers the remote a little sooner after switching on.
What does not change: the OLED panel, Ambilight, the P5 processing, the four HDR formats or the sound. All of that sits below Google TV.
All of this is reversible
Packages disabled over ADB come back with one command, and a factory reset returns the television to the state it left the box in. Nothing here touches the system: you only tell the set not to load something already installed.
If you own one
The app list from your OLED820 or OLED850, exactly as the set returns it, is the one thing missing to close its entry. And if you have a reliable brightness measurement, better still: that is the figure Philips publishes for none of its OLEDs.