Open on your phone
Use an up-to-date mobile browser over HTTPS. Remove thick cases when testing NFC, compass, vibration or proximity-related behavior.
Run a complete mobile hardware test online from one phone-optimized page. Check touchscreen and multi-touch, display pixels and refresh rate, accelerometer, gyroscope, compass, GPS, cameras, flashlight, microphone, main speaker, stereo channels, earpiece response, vibration, battery, NFC, Bluetooth, CPU, RAM, GPU, storage and more.
Scan capabilities first, then open any component for an in-depth guided test. Permission prompts appear only after you start the relevant module.
The report separates measured browser behavior, user-confirmed physical results, permission problems and APIs unavailable in this browser.
Rate the diagnostic center to help improve future CorrectionCopy tools.
Guided mobile diagnostic
Use real physical actions and live browser readings to verify each accessible component without installing an app.
Use an up-to-date mobile browser over HTTPS. Remove thick cases when testing NFC, compass, vibration or proximity-related behavior.
The page detects APIs available to this browser and labels each module supported, limited, manual or native-only.
Touch, rotate, shake, speak, listen, move outdoors or present an NFC/Bluetooth accessory as instructed.
Save a text or JSON summary that distinguishes confirmed behavior from permissions and browser limitations.
This all-in-one smartphone diagnostic page combines automatic browser readings, full-screen visual checks, performance measurements and guided physical confirmation.
Open a true full-viewport touch grid to trace edges, corners, rows and columns, identify touchscreen dead zones, detect ghost touch behavior, count simultaneous fingers and inspect pointer pressure.
Use black, white, red, green, blue, grayscale, gradient, checkerboard and fine-line screens to inspect stuck pixels, screen burn-in, tint, banding, flicker and frame stability.
Measure phone movement, gravity, shake response, angular rotation, portrait and landscape tilt, compass heading and magnetometer-related orientation behavior where the browser exposes it.
Read direct lux or experimental sensor values when available, with clearly labeled camera-assisted light and near/far response fallbacks plus GPS altitude-based pressure reference.
Test front and rear cameras, available lenses, rear LED torch on/off constraints, microphone level and waveform, main phone speaker, stereo left/right channels, frequency sweep and earpiece response guidance.
Check location accuracy, altitude, speed and heading; scan NDEF NFC tags; open Bluetooth LE and WebUSB choosers; and inspect browser-visible Wi-Fi, cellular and connection information.
Monitor battery percentage and charging events where available, inspect any vendor-exposed advanced battery fields, trigger vibration patterns, and follow safe manual checks for volume, power and mute controls.
View browser-visible architecture and logical cores, run bounded processor and memory benchmarks, identify the WebGL renderer, inspect graphics limits, estimate website storage quota and test private storage read/write speed.
The page includes deep tests for web-accessible parts and transparent guidance for protected hardware.
Trace touchscreen coverage, count simultaneous fingers, inspect dead pixels, colors, gradients, burn-in patterns and estimate refresh rate.
Read acceleration, rotation, orientation and compass heading, then use direct sensor access or clearly labeled camera/GPS-assisted fallbacks for light, proximity and environment checks.
Preview front/rear cameras, enumerate lenses, directly toggle the rear LED torch where exposed, inspect microphone input, test main speaker, stereo channels, earpiece response and vibration.
Measure GPS accuracy, review browser network indicators and open user-controlled Bluetooth, NFC and USB accessory tests.
Inspect battery and charging state, separate CPU, RAM, GPU and storage diagnostics, hardware buttons, screen orientation, safe-area insets and foldable-device APIs.
Pass/fail scoring uses observable results and user confirmations. An unavailable API is never automatically treated as broken hardware.
These modules remain visible so users understand exactly which deeper checks require the phone manufacturer or a native diagnostic app.
Web pages cannot read SIM slot health, carrier registration, signal dBm, cellular bands, modem logs or baseband firmware.
Battery percentage may be exposed, but cycle count, capacity degradation, cell voltage, temperature and charging wattage usually are not.
A browser may detect a platform authenticator, but cannot certify whether the exact fingerprint, face, iris or depth sensor is healthy.
Heart rate, SpO₂, thermometer, humidity, pedometer, hall, IR blaster and FM radio access is generally native or vendor-specific.
A browser can open a chooser on supported Android browsers, but electrical port health and all Bluetooth profiles cannot be certified.
General audio output can be tested, but reliable routing to the handset earpiece and modern proximity readings are not standardized.
Camera, microphone, GPS and sensor streams are used only while their tests are open. The page does not intentionally upload media, location trails or raw sensor readings. Only anonymous aggregate usage and star-rating values may be sent to Firebase.
Answers to common questions about phone sensors, permissions and browser limitations.
Run focused diagnostics when you need a larger graph, longer recording or a dedicated test workflow.