Android phones and tablets, wherever they are

Service Center

Hardware diagnostics for Android: battery, sensors, cameras, touch, thermals and the full spec sheet the device reports about itself.

  • Hardware tests
  • Battery health
  • Benchmarks

What a diagnostic actually proves

A phone lies by omission. It boots, the screen lights up, the camera opens, and none of that tells you whether the battery has lost a third of its capacity, whether the gyroscope drifts, whether two columns of the touch grid stopped answering, or whether the chip inside matches the chip on the box. The device knows most of this. It simply has no reason to volunteer it.

Service Center is the work of asking. We run a fixed sequence of tests on the hardware itself and read back what the system reports, then put the two side by side. Where they disagree — a declared storage size that the controller does not confirm, a model string that does not match the sensor set, a battery whose design capacity and present capacity are far apart — that disagreement is the finding. It is usually the only finding that matters.

Why the order matters

Tests are run cold first, then under load. A phone that benchmarks well in the first thirty seconds and loses a third of its score by the third minute is not a fast phone; it is a phone with a thermal problem, and the single score hides that completely. The same logic applies to the screen: a static colour sweep finds dead pixels, but only a traced touch pass across the whole panel finds the dead line under the glass that makes typing miss every fifth letter.

What you end up holding

A plain report. Each test, what it measured, what the device claims, and whether the two agree — written so you can hand it to a buyer, a seller, an insurer or your own IT team without having to interpret it for them. No score out of a hundred, no colour-coded verdict standing in for the numbers. If the battery has been through a lot of cycles and still holds most of its charge, the report says both things, because both are true and a single word would not be.

Most of the devices that come to us are fine. Knowing that, with the measurements behind it, is worth as much as catching the one that is not.

What gets checked

Battery health

Present capacity against design capacity, charge cycles where the device exposes them, voltage and temperature under a controlled drain. Not a percentage — the numbers it came from.

Screen and touch

Full-panel colour sweeps for dead and stuck pixels, uniformity and backlight bleed, then a traced touch pass across the entire grid to find dead rows, ghost input and edge rejection problems.

Sensors

Accelerometer, gyroscope, magnetometer, proximity, ambient light, barometer and fingerprint reader — each exercised and compared against the sensor list the device declares it has.

Cameras and audio

Every lens the phone reports, front and rear, checked for focus, stuck shutters and dead modules. Speakers, earpiece and microphones tested on both channels, plus the vibration motor.

System and device information

Chipset, cores and clocks, RAM, real usable storage, display resolution and refresh rate, Android build and patch level, network bands — the spec sheet read off the hardware rather than off the listing.

Benchmarks under load

CPU, GPU, memory and storage read/write, run long enough to show sustained performance and thermal throttling instead of the first clean thirty seconds.

What you can ask for

Tell us the device and the reason; the sequence is chosen from there.

Single device report

The full sequence on one phone or tablet, with the written report at the end.

  • Battery capacity and cycles
  • Screen, touch and sensor pass
  • Cameras, speakers, microphones
  • System information cross-check
Most asked for

Pre-purchase verification

For a device you are about to buy second-hand: does the hardware match the listing.

  • Declared spec vs reported hardware
  • Real usable storage check
  • Sustained performance run
  • Plain pass/fail notes per item

Battery assessment

When the only question is how much life is left in the cell.

  • Design vs present capacity
  • Cycle count where exposed
  • Voltage and temperature under drain
  • Charging behaviour notes

Fleet audit

For resellers and IT teams moving devices in batches rather than one at a time.

  • Same sequence across every unit
  • One line per device, one summary
  • Flags on units worth holding back
  • Export in a format your system reads

Scope and turnaround are agreed in writing before anything is run.

How it goes

  1. You tell us the device and the reason

    Model, rough age, and whether you are buying, selling, insuring or just suspicious. The reason decides which tests matter.

  2. We agree the sequence

    You get back the list of tests we intend to run, what each one measures, and what we will and will not be able to tell you from it.

  3. The tests run

    Cold first, then under sustained load. Nothing is wiped, nothing is rooted, and no personal data is read — the tests talk to the hardware, not to your files.

  4. You get the report

    Every measurement, the device's own claims beside it, and the disagreements called out in plain words you can forward to somebody else.

Ask us to check a device

Leave your name and email and say what you need verified. A technician reads it, not a bot.

  • A technician answers, with questions if the request needs them
  • You get the proposed test sequence before anything runs
  • No device is wiped and no personal files are read