testmyphone.online Run Test
📋

Phone Diagnostic Guide

How to check a phone for hardware problems using browser-based diagnostic tools. A step-by-step workflow for testing every major component.

Before You Start

To run the full diagnostic, you need:

  • A modern web browser (Chrome, Firefox, Safari, or Edge)
  • A stable internet connection
  • 5-8 minutes for the full diagnostic suite
  • A quiet environment for microphone and speaker tests
  • Good lighting for camera tests

Tip: Close other browser tabs and background apps before running the diagnostic. This prevents system load from affecting test results, especially for the FPS and refresh rate tests.

Step 1

Device Information

Start by checking your device's reported specifications. The Device Info page auto-detects your OS, browser, screen resolution, CPU cores, GPU renderer, RAM, battery status, and network connection type.

This establishes a baseline for your device and helps you understand what hardware you're working with. If fields show "Unknown", the browser doesn't expose that data — this is normal and doesn't indicate a problem.

Check for:

  • OS and browser version are correct
  • GPU shows a real graphics card name (not "SwiftShader" or "Software Renderer")
  • Battery status shows charge level and charging state
  • Network connection type is reasonable for your setup
Run Device Info Test
Step 2

Display

The display is the most visible component. Run the Screen Test first to cycle through solid colors and check for color uniformity, then run the Dead Pixel Test to systematically scan for dead or stuck pixels across 5 colors.

For the Dead Pixel Test, examine each color carefully at different viewing angles. Some defects are only visible from certain perspectives, especially on IPS panels. Clean the screen with a microfiber cloth before testing — dust and fingerprints can look like dead pixels.

Check for:

  • Color uniformity across the entire screen
  • Dark spots (dead pixels) or bright colored dots (stuck pixels)
  • Backlight bleeding on dark backgrounds (LCD panels)
  • Any physical cracks or damage visible on the screen surface
Step 3

Touch

The Touch Screen Test uses a 6x4 full-screen grid. You must touch every tile to verify the digitizer works across the entire display area. Touched tiles turn cyan. If certain tiles don't respond, those may be dead zones.

After the Touch Screen Test, run the Multi-Touch Test to check how many simultaneous fingers your screen can track. Place 2, 3, 4, or more fingers on the screen and watch the maximum count. Most modern phones support 5-10 simultaneous touches.

Check for:

  • All 24 grid tiles respond to touch
  • Touch accuracy (touches register where you tap, not offset)
  • 2+ simultaneous touch points detected
  • No ghost touches (tiles activating without input)
Step 4

Audio

Audio testing involves three components: speakers, headphones (if available), and microphone. The Speaker Test plays a 440 Hz tone on the left and right channels independently. You confirm whether you hear sound from both sides, one side, or neither.

The Headphone Test adds a frequency sweep and phase test for more detailed audio verification. The Microphone Test records 3 seconds of audio and plays it back so you can verify the microphone captures sound clearly.

Check for:

  • Both speaker channels produce sound
  • No crackling, buzzing, or distortion at normal volume
  • Microphone records and plays back clear audio
  • Frequency visualizer shows dynamic response when speaking
Step 5

Camera

The Camera Test grants access to your camera, displays a live preview, and lets you capture a still snapshot for closer inspection. Check the preview for focus quality, color accuracy, and exposure.

The Webcam Test is a simpler utility for quickly checking the webcam feed and capturing a photo — useful for quick visual verification or profile pictures. Both tests require camera permission.

Check for:

  • Camera feed appears (not black or frozen)
  • Image is focused and clear
  • Correct camera is active (front or rear as expected)
  • Snapshot is sharp and well-exposed
Step 6

Sensors

The Gyroscope Test checks your device's motion sensors. You tilt your device to roll a ball into a target ring and hold it for 1.5 seconds. If the ball responds to tilting, the accelerometer and gyroscope are working.

The Vibration Test triggers your device's haptic motor. If you feel a brief vibration, the motor responds to software commands. Note: vibration is not supported on iOS Safari.

Check for:

  • Gyroscope ball responds to device tilting
  • Alpha/beta/gamma values change when device moves
  • Vibration motor triggers on supported devices
Step 7

Performance

The Refresh Rate Test counts display frame callbacks over 3 seconds to estimate your screen's refresh rate (60Hz, 90Hz, 120Hz, etc.). The FPS Test renders an animated canvas scene for 6 seconds and measures current, average, and minimum frame rates.

Both tests require the browser tab to be active and visible. Do not switch tabs or minimize the browser during measurement — this will pause the frame counting and produce inaccurate results.

Check for:

  • Refresh rate matches your device's advertised spec
  • Average FPS of 60+ for smooth performance
  • Minimum FPS not significantly lower than average (no severe frame drops)
Step 8

Connectivity

The Internet Speed Test measures network latency and jitter. It sends HEAD requests to a test server and measures round-trip time. Under 50ms latency is excellent. Under 30ms jitter means consistent connection quality.

This test does not measure download/upload bandwidth (Mbps). It specifically tests connection responsiveness, which is more relevant for real-time applications like video calls and gaming.

Check for:

  • Latency under 100ms for good responsiveness
  • Jitter under 50ms for consistent connection
  • Results are consistent across multiple runs
Run Internet Speed Test →
Step 9

Generate Diagnostic Report

After completing individual tests, use the One-Click Full Diagnostic wizard from the homepage to generate a complete TestMyPhone Diagnostic Report. The wizard walks through all tests in sequence, records pass/fail results, and generates a report with a letter grade and downloadable certificate.

The report is a summary of your device's condition at the time of testing. It can be shared with buyers when selling a device, used to document a device's condition before a repair, or saved for personal reference.

Important: The diagnostic report represents results from browser-based TestMyPhone tests. It is not an independent hardware certification. It confirms whether components respond through the browser and operating system — the same layer that everyday apps use.

Start Full Diagnostic

Frequently Asked Questions

Do I need to run all the tests?

For a complete device check, yes. If you're only concerned about a specific component (like the touchscreen after a drop), you can run just that test. The full diagnostic is recommended when buying or selling a used device.

How long does a full diagnostic take?

The one-click diagnostic wizard takes approximately 5-8 minutes depending on how long you spend on each test. Individual tests take 30 seconds to 2 minutes each.

Should I run diagnostics before or after a factory reset?

Run diagnostics after a factory reset if you want to test the hardware without software variables. Run them before if you want to check the current state of the device as-is.

Can I use these tests to document a device's condition for a buyer?

Yes. The diagnostic report with a letter grade can serve as documentation of the device's condition at a specific point in time. However, it represents a snapshot — it doesn't guarantee future performance.