Offline-first | No ads | No account required
Know the Android phone in front of you.
Device facts, guided inspection, on-device benchmarks, and useful everyday tools in one focused Android app.
Read what the phone actually reports, test the hardware step by step, and keep results local unless you explicitly choose to share them.
No account or advertising SDK in the current app.
Unavailable values stay visible instead of being invented.
Reports are shared only through an action you start.
Five focused workspaces
Get a readable overview of the phone: model and Android details, security patch, CPU and GPU, memory, storage, battery, cameras, sensors, connectivity, and other values available through Android.
GPUX keeps unknown values visible instead of filling gaps with guesses.
Follow a guided checklist for display, touch, sound, microphone, torch, sensors, charging, biometrics, camera, and other practical checks.
Mark each step pass, fail, skip, or unavailable, and use the protected back action so an accidental press does not discard a session.
Run on-device CPU, GPU, memory, and storage tests. Results describe this phone under its current conditions; they are synthetic measurements, not a universal ranking.
For better comparisons, let the phone cool and close heavy background apps.
Open individual hardware retests, monitor battery and memory status, compare an imported GPUX report, and export a plain-text summary when you decide to share it.
Useful when checking a used phone, retesting after repair, or documenting a baseline.
Use a compass by default, then enable Qibla only when needed. Qibla can use an optional location permission or an offline city preset.
Utils also includes a surface and wall level, GPS speedometer, on-screen ruler, optional network speed test, and a relative sound meter.
Battery evidence
GPUX separates current charge from battery condition. When Android or the phone maker exposes the values, the app can show:
These values are device-dependent. A charge counter is not full-charge capacity, and a missing cycle count is not zero cycles. GPUX labels unavailable data instead of inventing it.
Practical context
GPUX is useful when you own a phone, receive a used phone, or want a repeatable baseline before and after repair. It can show observable differences in system-reported hardware and help you test the screen, touch, sound, sensors, camera access, torch, battery, and connectivity.
It cannot prove that a phone was never opened, identify every replaced part, verify that a component is original, or replace a professional diagnostic inspection. Use the report as evidence alongside the device history, seller disclosures, warranty status, and physical inspection.
Read the system facts, work through display, sound, camera, sensor, charging, and connectivity checks, then keep a simple record of what you observed.
Create a repeatable baseline with Device, Inspect, Bench, and Lab. Retest one area later instead of starting every check again.
Find hardware details without hunting through settings, then use a compass, level, Qibla direction, speedometer, ruler, network check, or sound meter when needed.
Honest diagnostics
GPUX is built to make Android's available information more useful without pretending it can answer questions the phone itself cannot verify.
Model codes, battery fields, camera counts, sensors, and cycle data depend on Android and the device manufacturer. GPUX identifies unavailable data instead of deriving a confident-looking answer from a different reading.
The app can guide practical testing, but the person holding the phone remains the final judge of display condition, button feel, speaker clarity, cosmetic damage, and physical repair signs.
Benchmark numbers change with temperature, battery state, power mode, background work, Android version, and storage condition. Repeat comparable tests before drawing conclusions.
Screenshot gallery
A focused look at each workspace, from the initial device snapshot to a shareable Lab report. The gallery keeps the rest of the page concise while preserving the real app interface.
A repeatable flow
Important answers
No. Compass mode is the default and does not require location. Qibla and GPS speedometer can request location when you enable them; Qibla also supports a city preset.
No background upload is part of the current app. Optional network tools run when you start them, and Android sharing sends only the content you choose to the destination you select.