Quiet Home
A calmer, tvOS-inspired home screen for LG webOS TVs, with your favorite apps, original app icons and rotating space photography.
- Sideload / dev mode
- Stable
- Low brick risk
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Before you start
- How hard is it?
- HardUses the command line or developer tools.
- What you need
- Comfort with the command line
- A computer
- Can it break my device?
- Very unlikely to break anything.
- Can I undo it?
- The project doesn't say. Assume you can't.
Did it work for you?
Did Quiet Home work on your LG OLED C3?
No reports yet.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: LG OLED C3.
No compatibility information yet.
Getting started
From the project's README ("Build and install"):
- Prepare your setup computer
Use Node.js 20+ and Python 3.9+. The TV service targets the TV's separate Node 8.12 runtime.
From this repository's folder:
npm ci --ignore-scripts npm run service:deps python3 -m venv .venv . .venv/bin/activate python -m pip install --no-deps -r tools/requirements.txt npm run registration:generate
- Fetch optional original app artwork
For your private installation, you can download the reviewed original provider icons:
npm run assets:fetch
You can skip this step and use native TV artwork instead. Provider icon files are excluded from this repository; see artwork and credits.
- Build the TV package
npm run build npm run package
Output: build/org.quiethome.launcher1.3.4all.ipk.
- Install and pair with your TV
Follow the step-by-step installation and recovery guide to enable LG Developer Mode, register your TV with the official CLI, install the package and approve pairing on the TV. Keep keys and preference backups outside the repository.
This source uses the generic app ID org.quiethome.launcher. It builds and packages locally, but has not been installed on another TV. It is a separate package from the maintainer's private TV installation, so it will not update that installation in place.
Risk and recovery
- Brick risk
- Low
- Requires opening the device
- No
From the project's README ("Updates, recovery and technical details"):
Guide Covers Installation and recovery Setup, pairing, preference backup, verified stopping, updates and removal Maintenance Day-to-day maintenance and source hygiene Compatibility and limits Tested platform, Home behavior, startup and remaining verification limits Security Pairing, private state and local network precautions Dependency audit Remaining development-tool advisories
Credits, license and support
- License
- MIT