r/webos

Hi everyone,

I need help from someone who owns an LG OLED65C56LA (or another European LG C5 running webOS 25).

I imported my TV from Japan and I’m trying to switch it to the European region so I can use my French LG account, LG ThinQ, and the European LG Content Store.

I already have full access to the Service Menu (0413), but I don’t want to guess the Area Option value, as changing it incorrectly can brick features or cause compatibility issues.

IMPORTANT

Please don’t simply reply “use 3122” or another old Area Option value.

I know older LG OLEDs commonly used values such as 3122, but LG appears to have changed the Area Option tables on newer webOS 25 / 2025 models. My current Japanese TV already uses 4951, which confirms that the numbering is different from previous generations.

I’m looking for the actual values displayed on a European LG C5, not values from older models.

Could someone with a European LG C5 please check the following?

Open the Service Menu (0413).
Go to 1. Adjust Check.
Take a photo or tell me the values of:
Area Option
Country Group
Group Code / Group
Your exact TV model

My current values are:

Model: OLED65C56LA
webOS: 25
Region: Japan
Area Option: 4951
Country Group: 20 / JA

I’m not asking anyone to modify anything on their TV—only to read the values already shown in the Service Menu.

A photo of the screen would be perfect.

Thank you very much!

apart from the stock apps and some dedicated apps from app store, how are you guys downloading android apps ? if they are not available via web search, how can i get them ? i am a big fan of LG but this is limiting me from accessing some regional content.

Hey everyone,

I've put together a native webOS wrapper to run TorrServer directly on your LG TV. If you use apps like Lampa or just want to stream torrents directly on your TV without needing an external Android box or a PC running 24/7, this is for you!

https://preview.redd.it/lfws01w6zgah1.png?width=953&format=png&auto=webp&s=651f93da09c95261802a08b21e56af63548d9f1b

What is it?
It’s a homebrew webOS app (.ipk) that comes with a simple launcher UI and a background service. It automatically downloads the official TorrServer build for your TV's architecture, runs it in the background, and supervises the process.

Key Features:

• Native LG TV Support: Runs directly on the TV in the background.
• Auto-Updater: The .ipk is tiny. When you hit "Start", it detects your TV's CPU architecture (arm, arm64, x86, etc.) and downloads the latest official TorrServer binary.
• Autostart: Can be configured to automatically start TorrServer when the TV boots up (enabled by default, toggleable in the app).
• Remote Management: You can manage TorrServer from your phone or PC at http://<tv-ip>:8090.
• App Integrations: Includes a quick shortcut to launch Lampa (if installed) and the TV's native MediaPlayer.
• Simple UI: Use your Magic Remote to easily Start, Stop, Restart, Update, or view Logs right from your TV screen.

Requirements:

• A rooted LG webOS TV.
• The Homebrew Channel installed.

Where to get it?
You can check out the source code, see screenshots, and find the installation/build instructions on the GitHub repository:

👉 GitHub Repo - torrserver-webos

Quick Usage:

1. Install the .ipk via the Homebrew Channel or CLI.
2. Launch the TorrServer app on your TV and press Start (it will download ~70 MB on the first launch).
3. Connect your favorite streaming app (like Lampa) to 127.0.0.1:8090 or access the Web UI from another device at http://<tv-ip>:8090.

Let me know if you run into any issues, have feature requests, or just want to share how it runs on your specific TV model. Feedback and contributions on GitHub are highly appreciated!

I wanted Prowlarr running 24/7 without leaving a PC on, so I built it as a homebrew app that runs **directly on the TV**. It downloads the official self-contained Prowlarr build, runs it in the background, and you manage it from any device at `http://<tv-ip>:9696`.

The tricky part: webOS ships a 32-bit ARM glibc userspace that the .NET build won't run on. The app fetches Alpine **musl** libraries on first launch and runs Prowlarr through an isolated `ld-musl` loader, so it stays fully self-contained and never touches the TV's system libs.

**Features**

- One-tap Start/Stop/Restart/Update from a TV-friendly UI

- Autostart on boot (toggle in-app, on by default)

- "Update available" indicator (checks GitHub) + native toast when it's running

- Live log viewer that locks to the latest line

- Official Prowlarr logo + icon

**Requires:** a rooted webOS TV with the Homebrew Channel. Install the `.ipk` via webOS Dev Manager, press Start (first launch downloads ~95 MB), then pair with Sonarr/Radarr as usual.

Repo + build/deploy scripts: https://github.com/6ebeng/prowlarr-webos

Feedback welcome — happy to test on other webOS versions. Coded by Tishko Rasoul.

https://preview.redd.it/oiq8fobw94ah1.png?width=1464&format=png&auto=webp&s=e3055f7a6e468dca57a97648047d8a5855bb6ad9

Now that the price went up, I finally felt compelled to buy an Apple TV box (ATV) for the original price and get to see what it is about.

To give the context, I have an LG G5 with a tremendous amount of woe over their remote and UI, and some disappointment regarding their processing. To be precise, I thought the pointer and the scroller of the LG remote were neat, but I already broke one, which speaks to the quality of LG remotes. The UI was horrific until I turned off all ads, when it became tolerable. What was inexcusable was YouTube becoming slower to respond to the slider the longer I used the app in one session. And I was pretty much never happy with any particular picture setting. YouTube was the most disappointing, SDR content in general. Looks saturated until I enforced a warm color, which made it blend and look uniform. I figured some of these issues are not fixable by a box. But the ATV UI might come to the rescue a bit?

Now let's talk about Apple TV. Positives first.

The UI is smooth, yes.

The pictures also look cleaner. At least my partner is definitely convinced that Apple pictures are sharper and cleaner with more balanced color and brighter highlights. Something changed. I cannot exactly pinpoint what. The picture settings are definitely different between ATV and LG's webOS, which could also make the difference. The biggest suspect is that my ATV's picture setting is set to Dolby Vision (DV), so everything is up-converted to DV. That somehow solved my YouTube problem. Watching YouTube on ATV is much more pleasant.

The remote is sturdier than the LG remote. Definitely doesn't look like it is going to break in three months.

Now the negatives.

What's with the touchpad? I had to turn it off. And honestly, I have started to miss the pointer of the LG remote, which I think is neat. Why doesn't ATV even allow using the pointer? I guess it is complicated. I can't bring up LG's settings using the ATV remote. I hope I don't need to as much as I used to now that the picture is better.

What's with the ATV keyboard, showing all the letters linearly? It does not make sense. I know it can be changed. But the idea of Apple I thought was to let the user start with a set of well made choices. Maybe they want us to use siri instead.

And the UI is not uniformly better. In the Disney+ app, the slider is sometimes not working. I can only move forward or backward 10 seconds at a time. But if I try to slide further, the slider somehow did not work when watching a movie. Also, there is a downside to up-converting everything to DV. Some content is better in HDR10. It would have been better if there were a quick way of switching between the video formats.

Overall, my real question is whether it is worth spending so much given these pros and cons. I would say yes for the original price. No for the new price. And I wouldn't care about AI in the future versions unless it automatically figures out my intentions from my use and repeated change of settings and executes things accordingly.

It baffles me how bad the native LG webOS browser is, and yet, there are zero alternatives available!

It's especially shocking, because we can even sideload some apps on the tv, yet nobody has developed a decent fork of firefox or chrome in .ipk

I am hoping, there must be someone out there who can actually do it, and save everyone!

(sorry if I sound entitled, I am just disappointed in the browser, and if I knew any coding, I would have actually went ahead and did it myself.) But it's also possible that I don't know something crucial, and that is the reason why there are no third party browsers available on the webOS.

Hi everyone,

I’ll also post this in the LG subreddit, but I wanted to ask here in case anyone has an LG C5 or similar LG TV connected to Apple Home.

I have an LG C5 OLED65C5AUA on webOS 25, software 33.22.65, connected to Wi-Fi, and I’m trying to add it to Apple HomeKit.

The TV’s Home Hub guide mentions AirPlay / Apple Home, but I can’t find the actual AirPlay or HomeKit settings anywhere.

Under:
Home Hub → Mobile → Connect Mobile Device
I only see LG ThinQ, screen sharing, and audio sharing. No AirPlay, Apple Home, or HomeKit QR code.

This is my first LG. Has anyone fixed this on the LG C5 or a similar webOS TV?

UPDATE — Solved

The issue was the LG Services Country setting. Even though my TV is a US model and I’m in Puerto Rico, the AirPlay/HomeKit options were completely missing because the LG services region was apparently glitched or not set correctly.

What fixed it:

Settings → All Settings → General → System → Location → LG Services Country → turn off “Set Automatically” → manually select United States → restart the TV

After the TV restarted, AirPlay/HomeKit appeared.

I honestly didn’t know HomeKit/AirPlay options on LG TVs could depend on the TV’s service location.

Here in Puerto Rico, I have HomeKit available on all my Apple devices, so I assumed it was available everywhere or at least automatically enabled on supported models.

Anyway, doing this should solve the issue for anyone with an LG C5 or similar model where AirPlay/HomeKit is missing. It was not a Wi-Fi issue and it was not under Screen Share.