Screens/Before the wires/A screen is not one thing
Lesson 2 of 16 · in 3D and VR

A screen is not one thing

The word screen covers a panel, a backlight, a controller and sometimes a touch layer. Each can fail alone, and two questions sort them out. Where do the pixels live, and who owns the refresh timing?

Lonely BinaryUpdated 2026-10-014 min readNo board required

View it in VR

Lesson 2 of the Screens course opens in a VR headset, on a table in front of you, and a voice starts three seconds after you arrive. Type this short address into the browser on a headset such as Meta Quest or Apple Vision Pro, and press Enter VR. No headset? Press Start the lesson: the same lesson, full screen.

learn.lonelybinary.com/vr/screens/2

The panel turns electrical drive into visible pixels. An LCD panel makes no light of its own, so a backlight sits behind it. The display controller is a chip that receives commands, accepts pixel data and decides how the panel is driven. Touch is a separate system again, often on its own bus.

That split explains the case of a glowing screen with no picture. The backlight can be fully on while the panel shows nothing valid, because the controller has not yet received its start-up commands. After initialisation the first picture appears. A lit backlight proves only that the backlight works.

Who keeps the picture

Some controllers contain display memory, called GRAM. The host hands over a picture, the controller keeps the pixels and keeps driving the panel, and the host can stop sending. Think of handing the artwork to a projectionist: you can walk away.

Other paths have no frame store on the display side. The host must keep supplying pixels in time with the display, like a live broadcast. Stop the host and the stored-frame display keeps its picture, while the streamed one goes blank or corrupted.

That picture answers one question, who keeps the picture. It does not describe the wires. From the next lesson on, the course draws the real signals.

Start with the controller

For an ESP32, the controller part number matters more than the connector name. It tells you which interfaces the chip supports, whether it has GRAM, and what initialisation sequence it needs. The interface name alone does not settle it, because one controller can offer several.

Ask the two questions before choosing a display. Where do the pixels live, and who owns the refresh timing? Everything later in this course is an answer to one or the other.

Common mistakes

  • The backlight is on, so the screen works. The backlight, the panel and the controller are separate parts. A controller that was never initialised gives light and no picture.
  • Every display remembers its picture. Only a controller with GRAM does. A display fed by a live stream depends on the host for every refresh.
  • A working display means working touch. Touch is a separate system with its own wiring. Either can fail while the other is fine.

Edit this page — content/fundamentals/screens/a-screen-is-not-one-thing.mdx

Discuss this article

Ask about this page. The answer stays here, on the page it belongs to, for whoever hits the same wall next.

Browse Fundamentals on the forum →