PerfScope profiles Android and iOS games on real phones: frame time, jank, 1% lows, CPU, GPU, memory, heat and power. Its helper costs the phone 0.12% of its CPU, about 0.36 points all-in over Wi-Fi, measured on a Galaxy A26, not claimed.
Sample session generated for this page: the game, numbers and frames are synthetic, recorded with PerfScope's real charts.
A profiler that slows the game down measures itself. PerfScope runs one small helper as the phone's shell user, reads the counters the system already keeps, and does every calculation on your computer. Then it proves the cost with its own A/B benchmark: the same scene with the collector off and on, alternating.
Dashed line: the 1-point limit the benchmark enforces. The bars run to 1 pt.
| FPS change | under 1% | PASS |
|---|---|---|
| Device CPU change | under 1 pt | PASS |
| SoC temperature rise | under 0.5 °C | PASS |
| PerfScope's own cost | under 1% | PASS |
Windows alternate off and on (ABBA) with identical bookends, so drift can't hide a cost.
The loop a QA team runs on every build, in one desktop app for Mac and Windows. Plug the phone in over USB or Wi-Fi, pick the game, press Start.
Every second: FPS and frame times straight from the system compositor, jank by PerfDog's definitions, app and device CPU, per-cluster clocks and throttling, GPU, memory, heat and power. Screenshots follow the chart cursor, so a spike comes with the frame that caused it.
Press M during the boss fight. Each marker starts a segment with its own average FPS, 1% low and jank rate, so the report says which scene broke, not just that something did.
Line two recordings up by elapsed time. Every stat gets a difference, coloured only when it survives rounding: green when the new build is better, red when it regressed.
Export a single-file HTML report, CSV or JSON, or share a link anyone can open on perfscope.site. Every stat carries an explanation, so producers read the same numbers engineers do. Links are snapshots, and you can revoke them.
An honest profiler says N/A. When a phone doesn't expose a number, PerfScope shows the gap instead of filling it.
| Metric | Android | iOS |
|---|---|---|
| FPS | From the compositor, per game layer | While the game is in front |
| Frame times, jank, 1% low, stutter | Every frame | After recording, with Xcode installed |
| App and device CPU | All of the game's processes | Share of all cores |
| CPU clocks and throttling | Per cluster, with the allowed max | N/A |
| GPU | Load and clock (Mali) | Device, render and tiler |
| Memory | RSS and memory left | Footprint and memory left |
| Temperature | SoC sensor, thermal status | Battery |
| Battery power | On battery (use Wi-Fi) | On battery |
| Network | Whole device, minus PerfScope | Whole device, minus this computer |
| Screenshots | Optional, on the phone | Optional |
MeasuredPartlyNot available
Recordings live on your computer. Sign in with Google and they back up to a PerfScope folder in your own Drive and appear on your other computers; PerfScope can only see the files it created there. Nothing is uploaded anywhere else unless you press Share.
Every number on this page was measured on these phones. Each new device gets its quirks captured and tested before it's called supported.
PerfScope isn't publicly downloadable yet. Tell me about your game, your team and the phones you test on, and I'll get back to you.
Request accessabozaid1998.mma@gmail.com