A useful inspection ends with specific observations, not just a green score. Ask the seller for time to test the phone in its current condition. Record what you tried and what remains unverified. A browser checklist can reveal a problem worth investigating, but it cannot establish ownership, battery lifespan or the absence of previous repairs.
Start with the physical condition and the agreement
Before running software, inspect the frame, camera glass, charging port and display edges in ordinary light. Look for lifted edges, cracks, unusual gaps and signs of a damaged connector. Do not continue powered testing on a swollen, unusually hot or visibly liquid-damaged device. Ask about repair history and whether replacement parts are documented.
Clarify what accessories are included and what the seller permits you to test. Do not factory-reset someone else's phone during inspection. Account removal and setup belong in a seller-authorized handover, where you can verify that the device can be activated for its new owner. A TestMyPhone report does not check ownership, activation lock, carrier restrictions or stolen-device databases.
Check the display and touch as separate systems
- Clean the screen with an appropriate cloth. Run the solid-color inspection at comfortable brightness. Look for persistent dots, patches, lines or a faint old interface outline.
- Use gray as well as black, white and primary colors. Broad unevenness or an old logo outline is different from a single pixel-sized spot. If uncertain, use the display-defect comparison.
- Run the 96-region touch grid with one slow fingertip. Repeat any uncovered region and rotate the phone to compare the same physical area.
- Use the multi-touch canvas with two fingers and then more. Compare markers with the fingers actually held down. Do not interpret a lower session maximum as the hardware limit.
Inspect ordinary content too: a dark patch that responds to touch may be a display issue, while clean-looking glass can still have input problems. Browser chrome and test controls leave some areas untested; check those areas in a native app.
Test sound without masking the route
Disconnect Bluetooth and headphones before testing built-in speakers. Begin at low volume and play the left/right tones. A phone can mix both channels into a single physical speaker, so listen to ordinary speech as well and note whether output is clear, distorted or unexpectedly quiet.
Open the microphone test, say a short phrase, pause and speak again. Record and play it back. If output is silent, inspect both input routing and speaker routing before assigning blame. Compare the native voice recorder and a seller-authorized call if possible; these can use different microphone paths.
Check each camera you can access
Use the camera selector to compare front and rear preferences. Check the active label, actual stream dimensions and whether the view updates. Inspect an object at a normal focus distance in even light, then capture a snapshot.
Repeat in the native camera app for the lenses and modes you care about. Browser device selection may not expose every lens. Test focus changes, video recording and any zoom or stabilization modes in the app itself; a clear browser preview does not verify all of them.
Finish the checks that require the operating system
| Check | Useful evidence | Browser limitation |
|---|---|---|
| Battery and charging | Native health information where available; normal charging with a known-working accessory | Charge percentage is not remaining capacity or cycle count |
| Buttons and biometrics | Seller-demonstrated buttons and authorized setup or unlock behavior | A website cannot certify power buttons or biometric sensors |
| Connectivity | Wi-Fi connection, authorized call/data test and relevant accessory pairing | A short HTTP timing check does not verify cellular bands or modem health |
| Ownership and activation | Agreed handover and successful authorized setup | No browser diagnostic confirms ownership or account-release status |
Make the decision from unresolved issues
Write down the exact failed action, the conditions and whether it repeats outside the browser. “Rear preview dark in one browser” is more useful than “camera failed.” Preserve an observation of a visible defect with another camera if the seller permits it; avoid recording personal content.
A saved diagnostic summary is a record of tests attempted, including your judgments. It is not a certificate of sale condition. If an important function cannot be tested, treat it as unverified rather than assuming it works. A persistent defect or unclear repair history may justify professional inspection before you decide.