What these pages are, and are not
Every ScreenDetect device page is a source-backed screen profile: a plain-English read on what a display is good for, what tends to bother people, and what to check before you buy, return, or repair it. It is not a hands-on lab review. When a figure comes from someone else's testing, we say so and point to them, rather than restating a measurement as if it were ours.
That distinction matters. Most device pages online blur the line between a manufacturer spec sheet, a reviewer's measured result, and a writer's guess. We keep those three separate on purpose, because a buyer deciding on a screen deserves to know which claims are solid and which are still open.
Where the information comes from
We work from a clear source hierarchy, strongest first:
- Manufacturer and official pages for confirmed specifications, model numbers, and supported modes.
- Independent lab and review outlets for measured behavior the manufacturer does not publish, such as measured brightness, response time, or flicker.
- Support docs, retailer listings, and owner reports for setup quirks, common complaints, and return-window patterns.
When sources disagree, we do not silently pick one. We note the disagreement and, where it matters, send you to check the specific thing yourself on your own unit.
How we label confidence
Not every fact deserves the same weight, so we mark them:
Swipe sideways to compare columns.Scroll table to view all columns.
| Status | What it means |
|---|---|
| Official | Confirmed on a manufacturer or first-party source |
| Review-reported | Measured by an independent outlet, credited to them |
| Needs context | Real but varies by unit, region, firmware, or setting |
| Verify yourself | Best confirmed on your own screen, and we show you how |
Anything we cannot stand behind, we leave out or move into the "known, needs context, and unknown" section rather than guessing to fill a gap.
What we add that a spec sheet cannot
A spec list tells you the numbers. It does not tell you what to inspect the day a screen arrives, which faults are easy to confuse, or when a quirk is normal versus a reason to return. That is the part we own: the inspection lane. Each profile routes you to the specific ScreenDetect test for the symptom in question, so the page ends in an action rather than a shrug.
How we keep pages current
Screens change after launch: firmware adjusts behavior, new lab data lands, prices move. When something material changes, we update the page and record what changed in its update log, rather than quietly editing and bumping a date. If a page has not been re-checked recently, the visible "last updated" date tells you exactly where it stands.
Coming later: real inspection data
ScreenDetect's tests are run by real people on real screens. In time, and only once the sample size is large enough to be honest about, we plan to fold anonymized, aggregated inspection results into these pages so buyers can see what owners actually find, not just what a spec sheet promises. We would rather ship that late and accurate than early and misleading.