Most Android signage builds render the app window at 1920 x 1080 and stretch it 2 x 2 across the 3840 x 2160 panel, so a 4K layout shows up soft or shows a quarter of itself. Real 4K signage takes a build that exposes a 3840 x 2160 display mode and an app that requests it with preferredDisplayModeId; a 50% preview of your design tells you whether you need any of it.
A 4K panel and a 4K interface are two different things. On most Android signage players, the system renders every app window at 1920 × 1080, and the display hardware stretches that image across the 3840 × 2160 panel. Your signage app is not broken and the layout file is not oversized: the player gave the app about two million pixels to draw on, and the panel carries four times that. This page explains where the split between video resolution and interface resolution comes from, what the two symptoms mean on a real sign, whether your sign needs the extra pixels at all, and what to test before you pay for 4K hardware.
What the player is really rendering
Every display reports two sizes to an Android app. The logical size, returned by getSize(), is the surface the app draws into. The physical size, returned by getPhysicalWidth(), is the panel. Android's own documentation calls out the case where the interface is drawn at a lower logical resolution and upscaled to a larger physical one, and warns that the two numbers can differ. On signage boxes sold as 4K, the common case is a logical 1920 × 1080 surface on a physical 3840 × 2160 panel: every pixel the app draws becomes a 2 × 2 block on the glass.
The build exposes its list of display modes to the app as Display.Mode. If that list stops at 1920 × 1080, no app setting can create a larger surface. If the list contains 3840 × 2160, the app still has to claim it by setting preferredDisplayModeId on its window; the value must be one of the supported modes for that display, and 0 leaves the choice to the system. Some Android TV 12 builds render the interface at 2160p first and then scale it back to 1080p, so the real check is what the window receives on the finished panel, measured with the setting in place.
Why 4K video still plays sharp
Video decoding runs on a separate path from the window surface. The chip's video hardware can carry a 3840 × 2160 file to the panel at full resolution while the app interface sits on its 1920 × 1080 surface, which is why a box can be honest about 4K video and still show soft text. Some builds also match a video's frame rate without ever switching the display mode, so the resolution the player started in is the resolution it keeps. Only preferredDisplayModeId changes the mode.
A signage app that composites video with text, images and prices draws everything into one window surface, so the video-only 4K path is no help to it. The 4K file itself is heavier: 4 times the pixels means roughly 4 times the data at the same picture quality, so size the bitrate with margin and test video bitrate before you deploy.
The two symptoms, and what each one means
| What you see | What the app did | What it tells you |
|---|---|---|
| The whole layout, visibly soft | Drew at the logical 1920 × 1080 | The build renders 1080p and the scaler stretched it 2 × 2 |
| One quarter of the layout, cropped | Drew at the physical 3840 × 2160 with no scaling | The window surface is smaller than the canvas |
Soft is the common case: every element sits where the design puts it, letter sizes are preserved, and the loss is edge crispness. Quarter-and-cropped means the app trusted the physical number: the panel is showing 1920 × 1080 of a 3840 × 2160 canvas, enlarged to fill the glass. The same failure family turns up on HMI panels, where a project built for one resolution is shown on another and a quarter of the project fills the screen, as in this HMI display scaling issue that shows a quarter of the project.
Portrait adds a second requirement: the build has to rotate the interface and expose the larger mode at the same time, and rotation fails in its own ways, covered by when a signage player lacks portrait rotation support. Design and check the layout against the resolution the app really renders at, never the panel datasheet; checking portrait signage layout fit walks through the fit test.
Worked example: a 2160 × 3840 portrait menu board on a 1080 × 1920 surface
A cafe fits a portrait menu board on a 3840 × 2160 panel mounted upright, so the design canvas is 2160 wide × 3840 high. The player's build gives the app a logical surface of 1080 × 1920, the logical-versus-physical split described above.
The rule: an app can show only what fits its surface. Drawn at surface size, the panel shows the design at half linear scale. Drawn at canvas size with no scaling, the panel shows the surface's share of the canvas.
The arithmetic:
- Share visible, unscaled: 1080 ÷ 2160 = 0.5 across, 1920 ÷ 3840 = 0.5 down, and 0.5 × 0.5 = 0.25, so a quarter of the menu fills the screen.
- Pixel budget, scaled: 2160 × 3840 = 8,294,400 pixels in the design file; 1080 × 1920 = 2,073,600 pixels on the surface; 8,294,400 ÷ 2,073,600 = 4, so the design carries 4 times the detail the surface can hold, and every design pixel lands as a 2 × 2 block.
Result: either way, the glass delivers 2,073,600 pixels of detail.
Decision: open the design file at 50% zoom, which is exactly the detail a 2 × 2 upscale preserves, and read the smallest line, the price row and the allergen note. If they read cleanly at 50%, this player does the job and the design needs zero changes. If the 50% preview falls apart, the design depends on all 8,294,400 pixels, and the fix is hardware whose mode list contains 3840 × 2160 with an app that requests it.
When 1080p rendering is enough
Sharpness matters only when the viewer stands close enough to see pixel edges. Plan letter height with the FHWA planning figure this site publishes: 30 ft of viewing distance per inch of capital height, and 20 ft per inch for fast reading. A menu board with 1 in capitals is planned for 20 to 30 ft. A counter sign read from 6 ft needs capitals of 6 ÷ 20 = 0.3 in.
Upscaling preserves size: a letter keeps its height on the glass whatever the render surface, so a scaled 1080p interface shows text at the same physical size as a native one. What degrades is edge crispness, and at reading distances a 2 × 2 upscale of well-sized text is hard to see; walk to within 2 or 3 ft and the softened edges show, from 10 ft they are gone.
So for menu boards, lobby signs, elevator notices and waiting-room screens read from 5 ft out, a 1080p interface is the right tool. Our panel-mount displays, 1920 × 1080 panels from 11.6 in up, are built for exactly this work, and they are the wrong choice for a true 4K canvas. Reserve real 4K rendering for signs with fine detail read up close: dense wayfinding, small print, dashboards with 1-pixel rules.
How to check a player before you buy
Ask one question, of the manufacturer rather than the reseller: does this model's Android build expose a 3840 × 2160 display mode for the application window, and does your signage app request it? Have it demonstrated on the model you will receive. A build that has sat still for years, like Android 5.1.1 with a March 2016 security patch, has no update waiting, and a mode the silicon vendor's build never exposed is not something the box maker can add.
On the unit, the test takes about ten minutes. Install your signage app and a display-information utility that lists Display.Mode, and look for 3840 × 2160. Then load a test slide with a 1-pixel checkerboard patch and text at your smallest design size, run the app full screen, and look from 3 ft: a doubled 1080p render blurs the checkerboard into grey, a real 4K surface keeps the squares distinct.
The usual suspects are noise here. A bigger card changes how much content fits, and app storage can even be moved to a microSD extension, but the render surface stays what the build provides; configuring app storage on a microSD extension is that storage job, and it touches none of this. The same goes for a new cable and a reinstall. Fold the display-mode check into the basics in choosing a digital signage player.
What to buy
Recommendation: treat 4K as two line items, video decode and interface resolution. Buy against a demonstration on the unit, never a datasheet. If the 50% preview of your design reads cleanly at the sign's real viewing distance, buy a 1080p player and design at 1920 × 1080. That covers menu boards, lobby signs, elevator notices and most retail screens read from 5 ft or more. If the design genuinely needs all 8,294,400 pixels, buy only hardware that shows a 3840 × 2160 mode in Display.Mode with your app running full screen, demonstrated on the model you will receive.
If no Android option passes that test, run the sign from a small x86 PC. Desktop signage software renders the interface at the panel's native resolution by default, so a true 4K canvas is straightforward there; the trade is a maintained computer instead of an appliance, and the lockdown settings differ by Windows version, as why a signage player can go missing from Windows 10 kiosk mode shows for one common case.
For a larger screen from our own range, the wall models through 75 in are quoted per project, so confirm interface resolution, software, orientation and mounting in the quote before you order.
Questions
Is a smart TV with built-in apps a way around this?
A display with a built-in Android board has the same split between a video decode path and an app interface surface, so run the same Display.Mode check on the TV before you trust it. If the mode list stops at 1920 x 1080, the apps on that TV are upscaled like any external box. The two reliable routes stay the same: hardware with the 3840 x 2160 mode demonstrated on the unit, or a small x86 PC behind any 4K panel.
What resolution should I design the layout at?
Design at the resolution the app really renders at, confirmed from the Display.Mode list, and let the panel scale in whole steps. A 1920 x 1080 file maps onto a 3840 x 2160 panel as exact 2 x 2 blocks, with no odd pixels left over. Designing at 3840 x 2160 only pays once a real 4K render surface is confirmed.
Can a firmware update add the 4K mode later?
Only if the silicon vendor ships a new Android build that exposes the mode and the box maker passes it through to your model. Players left on old builds have gone years without such an update; the system reports it is up to date because, for that board, it is. Buy against a demonstration on the unit and treat a promised update as worth nothing until it arrives on your model.
Why does the same app quarter its layout on one 4K player and look fine on another?
Two builds that both advertise 4K can behave differently: one exposes a 3840 x 2160 mode and the app claims it, the other renders 1920 x 1080 and scales. The quartered one is an app drawing at the physical size on a smaller surface. Ask each vendor for the mode list demonstrated on the unit, because the panel specification is identical on both and says nothing about the interface.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.