Live per-core clocks
Every core with its own meter and frequency, plus cluster layout, cache sizes, governor and instruction-set features.
Free · No accounts · No tracking · Nothing uploaded
Everything your phone knows about itself.
cpux is a device inspector for Android. It reads the processor, graphics, memory, battery, display, sensors, cameras, network and media codecs straight from the platform and the kernel, and shows them live.
Android 8.0 and later · 12 inspector tabs · Three normal permissions
Overview
8 cores · 12 GB RAM · Android 15
46%
CPU
72%
Battery
C00.90 GHz
C10.75 GHz
C21.10 GHz
C30.60 GHz
C41.40 GHz
C51.20 GHz
C62.10 GHz
C72.60 GHz
- Memory
- 7.4 / 11.6 GB
- Temperature
- 38.2 °C
- Renderer
- Adreno 7xx
12
Inspector tabs
1
Permission requested
0
Bytes sent anywhere
0
Trackers and ads
What it does
An instrument panel, not a spec sheet
Most device info apps print a static list. cpux keeps reading while you watch, so you can see a core ramp up, a thermal zone climb, or the battery draw change under load.
Real GPU identity
Renderer and vendor read from a live GL context — not guessed from the model name — with OpenGL ES and Vulkan versions, limits and extensions.
Memory and storage
RAM broken down from /proc/meminfo, swap and zRAM, every storage volume, and the app's own heap.
Battery telemetry
Level, current, voltage, temperature, health, design capacity and cycle count — everything the battery controller will report.
Sensors and cameras
Every sensor with vendor, range, resolution, power draw and FIFO depth. Camera2 characteristics: sensor array, optics, ISO range, hardware level.
Display and codecs
Resolution, density, every refresh mode, HDR and colour gamut — plus the media codec list, filterable by encoder, decoder and hardware acceleration.
Privacy by construction
It never sends what it reads
cpux is free because it shows ads, and that is the one thing in it that reaches a third party on its own. Not one reading it takes from your hardware goes with the request — no chipset, serial, sensor, battery or benchmark figure, ever. There is no analytics SDK. Crash reporting is off until you switch it on, and the speed test runs only when you tap it.
-
Verify it yourself under App info → Permissions
-
No hardware reading is ever attached to an ad request
-
Readings live in memory only, and are gone when you close the app
-
One stored value: which version of the terms you accepted
-
No account, no sign-in, no email address
-
No access to contacts, messages, photos, files or location
The twelve tabs
What each screen shows
| Tab | What it shows |
|---|---|
| Overview | Device identity, live CPU and battery rings, load history, memory and storage bars, temperature |
| CPU | SoC and microarchitecture, per-core live clocks and meters, clusters, cache, ISA features, thermal zones |
| GPU | Renderer and vendor via a live GL context, OpenGL ES and Vulkan versions, limits, extensions |
| Memory | RAM breakdown from /proc/meminfo, swap and zRAM, storage volumes, app heap |
| Battery | Level, current, voltage, temperature, health, design capacity, cycle count |
| Display | Resolution, aspect, density, refresh modes, HDR and colour gamut |
| Sensors | Every sensor with vendor, range, resolution, power draw and FIFO depth |
| Camera | Camera2 characteristics: sensor array, optics, ISO range, hardware level |
| System | Android and build details, kernel, runtime, security posture, provenance |
| Network | Active transport, addressed interfaces, SIM and operator |
| Codecs | Media codecs with encoder, decoder and hardware-acceleration filters |
| About | Version, privacy summary, and the full privacy policy and terms |
Questions
Frequently asked
Is cpux really free?
Yes — every feature, with no purchase, no subscription, no paid tier and no "pro" unlock. It is paid for by ads instead. In the EEA, the UK and Switzerland you are asked before any personalised advertising, and declining leaves you with ads chosen from context rather than from a profile.
Does anything the app reads about my phone get uploaded?
No. The app opens a connection for exactly three things: fetching an ad, running a speed test you started, and sending a crash report when it crashes. None of them carries a reading from your device — the ad request gets what any ad request gets (IP address, device model, Android version, advertising ID), the speed test transfers meaningless filler bytes, and a crash report carries a stack trace. The privacy policy lists all of it.
Why do some values show a dash?
Android restricts which kernel interfaces an app may read, and manufacturers restrict them further. Where a value genuinely can't be read on your device, cpux shows a dash rather than inventing a plausible number.
Why is CPU usage labelled an estimate on my phone?
Some devices deny apps access to
/proc/stat. On those, utilisation is inferred from core clock frequencies instead of measured directly — and cpux labels it as an estimate everywhere it appears.Why doesn't it show my Wi-Fi network name?
Reading it would require location permission. A device information app has no legitimate need for your location, so that reading is deliberately left out.
Who makes this?
One independent developer, working alone. There is no company, no team and no organisation behind cpux — see About.
See what your phone is made of
Free, ad-supported, and it keeps everything it reads to itself.