How I Replaced My TV's Android TV With Linux

Summary of Technological Concepts / Product Features / Analysis

Core premise & feasibility (major clarification)

You cannot directly “flash Linux onto” the chip inside a modern smart TV. TV vendors typically do not publish bootloader keys, firmware source, or low-level hardware documentation, and the TV’s bootloader is locked. Without the manufacturer’s signing keys and hardware specs, replacing the TV’s internal OS is effectively infeasible for consumers.

---

What “replacing Android TV with Linux” actually means (working approach)

The practical solution is to make the TV act like a “dumb” HDMI display and move smart/media functions to an external Linux box. In this setup, the TV’s internal Android TV is functionally bypassed, because the TV only displays the HDMI output from the external device.

---

Working Setup (tutorial-like steps)

Hardware choice

Raspberry Pi 4 vs Pi 5

• Pi 4: good for 1080p playback.
• Pi 5: recommended for smooth 4K, because it includes hardware HEVC (H.265) decoding and supports 4K @ 60Hz with HDR10 via HDMI.

No special TV modifications are required—only HDMI connectivity.

---

Software choice

LibreELEC

• A Linux distribution built specifically to run Kodi as a dedicated home media center.
• It strips down everything to boot directly into Kodi, targeting:
  • fast boot (around < ~15 seconds)
  • low resource usage

---

Step-by-step process

1. Flash LibreELEC onto a microSD card using Raspberry Pi Imager
   • In Imager:
     • select the exact Pi model
     • choose LibreELEC under a “media player OS” category
     • select the microSD
     • write the image
   • No manual ISO hunting or building is needed.
2. Physical setup
   • Insert the microSD into the Pi.
   • Connect HDMI from Pi → TV.
   • Power the Pi (it boots automatically on power).
3. Fix the TV boot/input behavior (key troubleshooting area)
   • Many smart TVs boot into their internal interface first, even when an external HDMI source is present.
   • Solution: in TV Settings, set the specific HDMI port connected to the Pi as the default input/source so it switches automatically when a signal is detected.
   • The TV may still show a short boot splash/ads before switching; this part can’t fully be controlled, but the goal is to land on the Pi’s HDMI afterward.

---

First boot / Kodi configuration

LibreELEC boots into Kodi.

The initial wizard includes:

• Wi‑Fi setup (or Ethernet if used)
• language/time zone
• adding media sources:
  • local USB storage
  • network shares / NAS
  • Kodi add-ons for content

---

Remote control integration (feature)

HDMI CEC support

• Used to control the Pi/Kodi using the TV’s existing remote.
• LibreELEC supports CEC out of the box on most setups.
• TV brand naming differences may appear (e.g., Samsung AnyNet+, LG SIMPLINK, Sony Bravia Sync), but it’s the same HDMI CEC concept.

---

Live TV capability (optional add-on path)

Kodi + LibreELEC can support live TV, but it requires PVR (Personal Video Recorder) add-ons.

Live TV sources can include:

• IPTV via subscription services
• a physical tuner connected to the Pi

Configuration differs depending on the chosen live TV source type.

---

Alternatives addressed (and why they differ)

1) Termux (confusion/discussion clarification)

Termux on Android provides a Linux terminal/userland by leveraging Android’s Linux-based kernel, but:

• it does not replace Android TV
• Android TV (the manufacturer interface and boot process) remains underneath So it won’t achieve the goal of “no Android TV at all.”

2) CoreELEC (for different hardware)

CoreELEC is optimized for MiaLogic/MLogic-based chipsets commonly found in many cheap Android TV boxes (not Raspberry Pi boards). On those devices, CoreELEC may yield better hardware video decoding performance than LibreELEC.

3) Full Raspberry Pi OS + Chromium (browser-based streaming)

Using Raspberry Pi OS + Chromium can improve streaming compatibility by relying on web interfaces rather than Kodi add-ons.

Trade-offs mentioned:

• slower boot (full OS vs media-center OS)
• less TV-remote-friendly UX (browser/mouse-centric)
• higher hardware demands

---

Trade-off analysis (what you gain vs. lose)

Benefits vs stock Android TV

• Removes:
  • ads on the home screen
  • forced updates / menu changes driven by the vendor
  • performance degradation over time (background processes, forced updates)
• LibreELEC boots into a consistent Kodi UI and avoids many smart-TV behaviors.

Downsides

• Streaming app coverage can be weaker than official smart TV platforms:
  • Kodi streaming depends on community add-ons
  • add-ons may break, be missing, or require ongoing maintenance
• You lose one-tap official app convenience (e.g., Netflix/YouTube style apps) unless add-ons exist and work.

Decision guidance

• Most plug-and-play for local/network media + ad-free experience: LibreELEC + Raspberry Pi
• Best for maximum streaming service compatibility (at the cost of speed/UX): Raspberry Pi OS + Chromium

---

Practical cost/time/warranty constraints

• Estimated setup time (opening box → working media center on TV): well under 1 hour, including TV input menu configuration.
• Cost (if you don’t already own a Pi) is comparable to a mid-tier streaming stick, but typically without that device’s usual ads/forced updates/data collection.
• Emphasizes:
  • no opening the TV
  • no warranty voiding
  • no firmware modifications
  • the TV hardware remains untouched

---

Main speakers / sources (as stated in subtitles)

• Speaker: The video narrator (“I”) / creator of the project (no named person given in subtitles).
• Sources/tools mentioned:
  • Raspberry Pi Foundation (Raspberry Pi Imager)
  • LibreELEC / Kodi (software projects)