Start in portrait
Scan around the status area, camera cutout, corners, and navigation region before the center. A protector edge, dust, reflection, or browser overlay can resemble a screen point on a dense display.
Device inspection workflowTouch-first phone display sequence
0 of 7 complete
Run this page on the phone itself. Tap through the display tools, keep bright static fields brief, and repeat area checks after rotating the device.
Run this on the phone itself. Start at a comfortable brightness, keep static bright fields brief, and repeat area-level observations in both portrait and landscape.
- Open touch-friendly fieldsEssential
Scan the dense screen for fixed points
Large tap targets and solid fields support a close visual scan without requesting camera or screen-capture access.
How to run and read this step
Run it: Rotate through black, white, red, green, blue, and grey; scan edges around cutouts as well as the center.
Look for: Follow the same physical point and distinguish it from dust, a protector bubble, reflections, and page content.
- Compare RGB channelsRecommended
Follow up on a colored point
Individual and mixed channel fields provide more context when one point looks red, green, blue, cyan, magenta, or yellow.
How to run and read this step
Run it: Tap through the RGB grid and keep the device orientation fixed during the first comparison.
Look for: A channel-dependent point may indicate abnormal subpixel behavior, but the page cannot diagnose its electronics.
- Open retention fieldsRecommended
Check OLED retention cautiously when applicable
Grey and color fields can reveal faint outlines from status bars, navigation controls, keyboards, or repeated app layouts.
How to run and read this step
Run it: Use a short manual pass at comfortable brightness; leave the guided sequence stopped unless you need it.
Look for: A fixed old-image outline may be temporary retention or permanent differential aging; one session may not separate them.
Keep in mind: Avoid prolonged static maximum-brightness fields and do not repeatedly force device maintenance cycles.
- Open RGB patternsRecommended
Compare RGB tint and area uniformity
Primary fields, ramps, and channel mixes help reveal broad tint or area changes on a small display.
How to run and read this step
Run it: Inspect portrait first, then rotate to landscape and repeat the same fields from a consistent viewing angle.
Look for: If the appearance rotates with content it may be rendering; if it stays in the same screen area it may indicate panel or overlay behavior.
- Open low-grey fieldsRecommended
Inspect near-black detail at low ambient light
Representable low-grey fields and a patch grid help compare black crush, lifted dark tones, tint, or low-grey non-uniformity.
How to run and read this step
Run it: Let your eyes adapt briefly, keep brightness practical, and compare more than one low-grey level.
Look for: Watch for missing dark steps or broad low-grey patches, not a promised measurement of black luminance.
- Compare both orientationsRecommended
Repeat a neutral field after rotation
Portrait and landscape comparisons help separate a physical screen area from orientation-dependent layout or viewing-angle effects.
How to run and read this step
Run it: Choose mid-grey, observe the corners and center, rotate the phone, and allow the browser layout to settle.
Look for: Record whether the observed region stays with the glass, shifts with the rendered field, or changes with viewing angle.
- Estimate mobile cadenceOptional
Check optional browser cadence
A browser timing sample can show current frame delivery under the phone power and thermal state.
How to run and read this step
Run it: Keep the page foregrounded and compare normal and power-saving modes only if that reflects your use.
Look for: Adaptive refresh, heat, browser policy, and battery saving can change the estimate.
Keep in mind: The result does not verify the panel specification or touch sampling rate.
Small-screen, touch-first workflow
Phone Screen Test
This phone screen test uses large controls and short visual comparisons for a dense mobile display. It separates pixel inspection from OLED retention, broad color or grey variation, near-black behavior, rotation effects, and browser-received pointer coverage.
Mobile setup
Use orientation and brightness as controlled variables
Rotate and repeat broad fields
Repeat mid-grey, RGB, and near-black observations in landscape. Record whether an area stays with the glass, rotates with rendered content, or changes because the viewing angle changed.
Keep static bright fields brief
Use a comfortable brightness first. A short visual comparison is enough to find a suspect location; leaving white or saturated fields at maximum brightness adds heat and offers little diagnostic value.
Optional input check
Trace browser-received pointer coverage
Drag one finger through the grid. A cell changes only when this page receives a Pointer Event over it.
This checks browser-received pointer coverage, not display pixels, touch latency, pressure, multi-touch capacity, or hardware health. Browser gestures, screen protectors, curved edges, and operating-system reserved areas can affect the trace.
Fullscreen and browser chrome
Mobile fullscreen may not cover every physical screen area
Fullscreen starts only after you tap the tool control. Mobile browsers may refuse the request, keep an address or gesture region, or expose different behavior in portrait and landscape. If the field remains embedded, inspect the reachable area there and use another orientation for regions covered by browser chrome. The phone screen test never tries to hijack navigation or request screen-capture permission.
Read a faint old image cautiously on OLED
Many phones use self-emissive OLED panels, but panel technology should be confirmed from reliable device information. A faint status bar, keyboard, navigation bar, or app outline visible on grey may indicate temporary image retention or longer-term differential aging. One browser session cannot reliably separate them, and this site cannot read compensation status. Do not repeatedly force maintenance cycles.
What the touch trace can and cannot show
A continuous marked path means the browser received pointer positions over those cells during that trace. A missed cell can result from the path itself, browser gestures, an operating-system reserved edge, a screen protector, or input hardware. Repeat deliberately in both orientations before interpreting a gap, and use the manufacturer’s built-in diagnostics or service process for a hardware decision.