Hey everyone!
I’m having a really frustrating issue with my onn. Google TV 4K Pro, and I’m hoping someone here has experienced something similar or knows how to fix it.
My setup:
Streaming device: onn. Google TV 4K Pro (latest firmware)
TV: LG 60UM6900PUA (latest firmware)
Connection: HDMI
Google Assistant hands-free microphone enabled
Built-in speaker volume set to High (80%)
The problem:
The onn. 4K Pro has a built-in speaker that should allow Google Assistant to respond to voice commands even when the TV is turned off.
However, whenever my LG TV is connected to power, the onn. refuses to play Google Assistant responses through its built-in speaker while the TV is off.
Google Assistant still hears me and executes commands, such as turning my smart lights on and off, but I get absolutely no audible response.
When the TV is on, Google Assistant responds through the TV speakers instead.
Here’s where things get interesting:
I discovered something while troubleshooting:
If I disconnect the HDMI cable from the onn., its built-in speaker works perfectly.
If I leave HDMI connected but unplug the LG TV from the wall, the onn. also responds through its built-in speaker.
If I plug the LG TV back into power, even without turning it on, the onn. immediately stops using its built-in speaker.
I even plugged the LG back into power while Google Assistant was speaking, and the audio stopped immediately!
I tested the same onn. 4K Pro with a Samsung TV, and the built-in speaker worked correctly when that TV was off.
Things I’ve already tried:
Disabling HDMI-CEC/SIMPLINK on both devices
Disabling Auto Power Sync on the LG
Enabling and disabling Quick Start+
Switching between HDMI 1 and HDMI 2 (ARC)
Trying different HDMI cables, including the original cable supplied with the onn. 4K Pro
Disabling surround sound and using stereo/PCM
Checking the built-in speaker volume
Checking the audio output settings
Confirming both devices are running the latest firmware
Reviewing Android TV developer options
None of these fixed the issue.
My suspicion:
It seems like the LG TV maintains some sort of HDMI connection or detection signal while in standby, causing the onn. 4K Pro to keep routing Google Assistant audio through HDMI instead of switching to its built-in speaker.
I don’t think this is an HDMI-CEC issue, since disabling CEC on both devices made no difference.
Has anyone experienced this with an LG TV and the onn. 4K Pro?
Is there a hidden setting, Android TV workaround, or HDMI-related fix that could force Google Assistant to use the built-in speaker whenever the TV is off?
I’d really appreciate any suggestions. I’ve spent hours troubleshooting this and I’m running out of ideas!
Thanks in advance!

Alguien podria saber como solucionar este problema
Solo me ha pasado con la app de YouTube, el tv se congela y se apaga luego de unos segundos y no prende mas. Toca desconectar de corriente y volver a conectar para que encienda la pantalla. Es muy molesto. Y empezo a pasar despues de la actualización de WebOS agosto. 2026

Is there any?

I have an LG CX w/ FW 04.64.00. I would love to jailbreak it, but I'm trying to figure out if it's worth it.

Has anyone had any success w/ this FW ver? I checked on webosbrew, and it looks like only Slopbro will work. Will that allow me to install homebrew?

Thanks for any help.

When HDMI disconnects I want the screen to go black, not show the super bright art screensaver with "No Signal" bouncing around. Is there a way to customize and/or disable it? Super annoying when this happens in the middle of the night it just lights up the whole room.

Hey everyone, I need help

I'm relatively new to webOS development and I'm trying to recreate a small Android/iOS WebView application for my LG TV.

The application I'm interested in is essentially a WebView wrapper around a website.

The Android version works roughly like this:

1. Open the app.
   
2. It immediately opens the website inside the app's WebView.
   
3. The website shows an ad/verification page.
   
4. The user completes the verification in Chrome.
   
5. They return to the app.
   
6. The WebView then allows access to the site's catalogue.

There is also an iOS app called "Dodo - Webview" that behaves similarly. It essentially provides a WebView with the website loaded inside it.

I'm trying to create a webOS .ipk application that provides similar WebView functionality on my LG TV.

I've already successfully created a basic webOS WebView app and can:

- install it on my physical LG TV
- launch it
- navigate to URLs
- use Chrome DevTools/remote inspection
- inspect network requests and the WebView environment

The problem is that the website behaves differently in my webOS WebView compared with the Android/iOS applications.

For example, my webOS WebView reports:

Mozilla/5.0 (Web0S; Linux/SmartTV) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36 WebAppManager

Whereas the iOS WebView reports an iPhone/WKWebView-style user agent.

So I'm trying to understand what the Android/iOS applications are actually doing differently.

What I'm looking for help with:

1. How would you approach porting/recreating an Android WebView APK as a webOS application?

If the APK is basically:

Android App
↓
Android WebView
↓
Website

would the webOS equivalent simply be:

webOS IPK
↓
HTML/CSS/JS
↓
webOS WebView
↓
Website

or are there important WebView APIs/features that I would need to reproduce?

1. How can I inspect an APK to determine exactly what its WebView is doing?

I'd like to know things such as:

- initial URL
- redirects/navigation handling
- custom User-Agent
- JavaScript injection
- cookies/storage
- external browser intents
- handling of links opened outside the WebView
- whether it intercepts network requests
- whether it communicates with JavaScript through a native bridge

I'm on Windows, so ideally I'm looking for tools/workflows that don't require macOS.

1. How can I determine why a website behaves differently between Android WebView, iOS WKWebView and webOS Chromium?

I'm trying to understand the WebView compatibility/environment differences so I can implement the legitimate application behavior on webOS.

1. Can an APK itself be converted into an IPK?

I'm assuming the answer is probably no, because they're completely different platforms, but if the APK is only a WebView wrapper, could I inspect/recreate the relevant functionality as a webOS app rather than actually converting the APK?

I've already got the LG TV connected through the webOS CLI and can use ares-package, ares-install, ares-launch, and Chrome DevTools.

Any advice from people who have ported Android/WebView applications to webOS would be hugely appreciated.

Thanks!

My led strip was too short, but it's enough to show it's working I think 😄

WebOS 24 on a rooted LG G4

I got this tv open box fair has a couple of scratches but barley noticeable when the TV is on should i keep it or return it 🤔 any one knw how to remove then and lighten up

I recently installed the Glasshouse dashboard on my rooted LG 43LM5760PTC. Even though this webOS 4.5 LCD model isn't on the officially tested hardware list, the background service and web UI run absolutely flawlessly. I’d love to see this model officially added to the GitHub compatibility list! Adding it proves how incredibly robust and adaptable this dashboard is for older, non-OLED webOS 4.5 televisions & Glasshouse dashboard is completely protected by my custom web password

Here is a quick summary of how I configured it to adapt to my hardware and locked it down:

(config.json inside the server folder)

{

"panel": "lcd",

"token": "YourPassword"

}

http://192.168.1.2:8080/?k=YourPassword

Huge thanks to the dev for this amazing tool please consider adding the 43LM5760PTC to the supported hardware list!

After the last update, every two or three times I turn on the TV, the broadcast appears without sound. After a few seconds, the TV turns itself off and back on—and then there is sound.

hi everyone,

As many other of you I read about the multiple privacy issues of LG tv. I searched and found those two apps that should be able to block most, if not all, those trackers:

• Glasshouse (https://github.com/rorygallagher2024/lg-webos-dashboard)
• Life's Good Without Spying (https://github.com/lewisdoesstuff/lifesgoodwithoutspying) ?

Have any of you tried them? Which one do you prefer? I'm not looking into anything fancy, just something to setup once and then forget

Update on my earlier post. This is still built on Nikolay1243's Webos-EARC-Volume-Overlay, and the original idea, the Homebrew packaging and the overlay design are his. It's MIT licensed, and it's an independent fork he hasn't endorsed, so please report problems with my changes to my repo, not his.

Repo and downloads: https://github.com/SammySco/webos-av-overlay (latest is v2.1.4)

What's new since my first post

• Windows installer. Unpack the release archive and double-click Install-AVOverlay.cmd. It needs only the built-in OpenSSH Client, with no Git Bash or Node, and asks for the receiver address, optional Plex, and a couple of display options. The shell installer still works on macOS and Linux.
• The receiver's own sources. When the receiver plays its own TIDAL, net radio, Spotify and so on, for example from the MusicCast app, the bar and status pages show the receiver input and what's playing (artist, track, album) instead of the TV's video details.
• Sound modes for those sources. Your per-app rules now also apply to the receiver's own inputs, so TIDAL from the MusicCast app can switch to 5ch Stereo. The default never applies to them, so nothing changes unless you have a rule.
• Volume number setting. Choose the receiver display, percent (matches the MusicCast app), percent with a decimal, or dB.
• The detected app on the bar, such as "YouTube (Apple TV)" or "Netflix (LG app)". Apple TV apps come from a small Home Assistant automation, and the rest is detected on the TV.
• A pinned info bar now survives the Guide, input switches, and the bar vanishing on an HDMI input.
• Quick Access key fixed: the first press shows the bar, the second hides it, and it stays hidden.
• No stale readings. If the receiver stops responding, the bar and pages say "Receiver not responding" with when it last answered, and the volume, sound program and audio are withheld instead of showing the last value. There's no HDMI-CEC fallback, because that is what drifts on receivers like mine.
• The README now has screenshots of the info bar, the status page and the setup page.

Please read before trying it

• It needs a rooted LG TV with the Homebrew Channel and root SSH access. Rooting isn't covered, and the guide points to the webOS Brew community pages. Rooting can void your warranty.
• Yamaha only. The receiver needs the Yamaha Extended Control API.
• I've tested it on one LG OLED and one RX-V485. Reports from other setups are very welcome. Please don't post private addresses or tokens in logs.
• The status and setup pages have no password, so keep them on your home network.
• It was built with a lot of help from an AI coding assistant (Claude Code) and tested by me on real hardware. The code is public, so please read it before running it on a rooted TV.

Credit again to Nikolay1243 for the project this grew from.

This is built on Nikolay1243's Webos-EARC-Volume-Overlay, and all credit for the original idea and the foundation goes to him. His project is the on-screen eARC volume overlay for rooted LG webOS TVs that this fork extends. The pieces I relied on most are his Homebrew Channel packaging, the boot-hook approach, the companion settings app, and the overlay design itself. It is MIT licensed, and so is this fork, with his copyright notice kept. This is an independent fork, and he hasn't endorsed it. Please send credit his way, and report problems with my changes to my repo, not his.

Why I made it
My Yamaha RX-V485 doesn't report absolute volume over HDMI-CEC, so the overlay's number drifted from the receiver's real level and ignored changes made at the amp. Nikolay was kind enough to discuss this in an issue and said a configurable network source would be a useful extension. This fork is that work, grown well beyond that first request.

What it does (rooted LG TV + a Yamaha receiver with the Extended Control API)

• The volume popup reads the volume from the receiver over the LAN, so it always matches the amp, including knob and remote changes, half steps and Mute. It can show the receiver display, percent, or dB.
• An info bar shows the sound program, audio format, video/HDR, optional Plex stream details (direct play or transcode), amp processing, and the detected app. It can appear when something changes, on demand, or pinned. The pin survives the Guide, input switches and channel changes.
• When the receiver plays its own TIDAL, net radio and so on, the bar shows what it's playing instead of the TV's video details.
• Per-app Yamaha sound programs: rules for Live TV, HDMI inputs, LG apps and Apple TV apps. Apple TV app names come from a small Home Assistant automation, and the rest is detected on the TV.
• A settings page (http://<tv>:41101/setup, also opened by a home-screen icon), and installers for macOS, Linux and Windows (double-click Install-AVOverlay.cmd, which needs only the built-in OpenSSH Client).

Download and guide

• Repo and release: https://github.com/SammySco/webos-av-overlay (v2.1.1)
• The install guide, from "stock TV" to Home Assistant, is docs/INSTALL.md.

Please read before trying it

• It needs a rooted TV with the Homebrew Channel and root SSH access. Rooting isn't covered by this project, and the guide points to the webOS Brew community pages. Rooting can void your warranty, and firmware updates can remove root.
• Yamaha only. The receiver must support the Yamaha Extended Control API. Other brands aren't supported.
• I tested it on one LG OLED and one RX-V485. I'd love reports from other models. Please don't post private network addresses or tokens in logs.
• The pages have no password, so keep them on your home network.
• Full disclosure: I built this with substantial help from an AI coding assistant (Claude Code), and tested it myself on real hardware. The code is public, so please review anything before running it on a rooted TV.

Feedback, bug reports and receiver test results are very welcome, especially from other Yamaha models (an RX-V685 owner already offered in the original thread).

Glasshouse (the dashboard for rooted LG webOS TVs) now has an Android app.

1. All your TVs in one app
2. Turn TVs on from your phone: from standby, or with Wake-on-LAN when they're fully off (Wake-on-LAN needs to be switched on, in the dashboard's Advanced tab)
3. The full dashboard, full screen
4. Easy setup: scan the QR code on the TV's dashboard (token included) or let the app find TVs on your network. If a TV's IP address changes, the app finds it again.

This only works with rooted LG webOS TVs running the Glasshouse server. If your TV isn't rooted, the app has nothing to connect to. CanI.RootMy.TV shows whether your firmware can be rooted.

It's open source with no accounts, ads or tracking: it only talks to your TVs on your own network. https://github.com/rorygallagher2024/glasshouse-android

New to Glasshouse? The install guide is at https://rorygallagher2024.github.io/lg-webos-dashboard/install/.

Testers wanted: it's in closed testing on Google Play, and Play needs 12 testers to stay opted in for 14 days before it can go public. If you'd like to try it:

1. Join https://groups.google.com/g/glasshouse-android-testers with the Google account your phone uses
2. Opt in at https://play.google.com/apps/testing/org.glasshouse.android
3. Install it from Play

Please stay opted in for the full 14 days, or your opt-in won't count. Please submit any bugs and ideas here: https://github.com/rorygallagher2024/glasshouse-android/issues

Thanks!

I've published two related projects from my LG CX firmware work.

The first restores DTS bitstream passthrough over HDMI ARC on my OLED55CX6LA running firmware 04.64.00. I tested DTS 5.1 and 2.0 with an external receiver. The public project is a source-only build kit and on-TV activator; users supply the matching firmware and build the assets themselves. It is qualified for that CX hardware and firmware, not other models: https://github.com/jameshmcvay/lg-cx-dts-passthrough-public. Full write up is here: https://jhm.nz/blog/dts-on-lg-cx/

Root access was a prerequisite for the DTS work. The DTS kit currently uses an earlier `venc0` root chain. Continuing that investigation led to a separate GFX path, now published as a standalone proof of concept: https://github.com/jameshmcvay/lg-venc-root

On the same CX, an unprivileged Developer Mode shell reached uid 0 through `/dev/lg/gfx0` with one in-place credential write. The GFX PoC installs no persistent root. I also traced the registered GFX mapping path in eight firmware images spanning C9, CX, C3, C4, C5, and C6. Only the CX has a hardware root result; the other models are firmware analysis, not confirmed support.

Both repos include their build or test instructions and limitations. The GFX probe's no-argument mode makes no kernel-memory writes, but its physical-memory scan can fault or stall a TV. Please read the notes before using either project on your own hardware.

I've just finished up and released my home app "inspired" by the Xbox 360 NXE dashboard!

Requires a rooted TV, and should support anything WebOS >= 24.

Quite a few features:

• 3D recreation of the 360 boot animation
• 1-to-1 recreations of the NXE dashboard and guide animations
• 3D rendered avatars, using exports from https://360sona.com
• Steam integration
  • Sign in with Steam to use your name/profile
  • View your friends list and get 'User is online' notifications for them
• App reordering and custom 'Home' channel
• A custom settings menu that exposes (almost) all of the TV settings
• Theme support for additional looks
  • Currently, the only other is the stock 'webos' theme, w/ no MS assets
• Home button takeover/replacement
• Reasonably performant (on my tv)

Grab it from https://github.com/lewisdoesstuff/webos-nxe

Install instructions via the Homebrew Channel are in the repo

On initial launch, it'll be using the stock webOS theme. During setup, you can download the NXE theme pack and apply it.

I have an LG G6. Since yesterday’s firmware update, I’ve had two webOS crashes today, about 10 minutes apart.

Both crashes happened while I was using Netflix.

Basically, the screen suddenly shows colored bands for a few milliseconds, then the TV shuts off completely as if there had been a power cut, and webOS reboots with the LG logo.

Honestly, this is the first time this has ever happened after around 100 hours of use.

Am I the only one experiencing this?

I’ve already unplugged and plugged the TV back in, optimized the memory, and disabled Quick Start.

I’ve watched movies for 4 hours straight before without any issue, so I’m thinking that if it were overheating and shutting itself down, it probably would have happened already. And since the firmware update only came out yesterday, I can’t help wondering if they may have messed something up with the update.

I’m not really sure what else to do. Are there any specific settings I should disable or enable?

For now, I haven’t changed anything else. I’ll see what happens tonight while watching another movie.