Chamber test protocol
Field Test Protocol
No file reaches the download button without clearing our six-phase field test protocol on real hardware. Test builds get extra scrutiny because the file and the server are two separate things to verify.
The six verification phases
Phase 1
File forensics
The APK is scanned for malware and checked against the published build details: package name, version, file size, and hashes. A file that does not match is rejected before it ever touches a device.
Phase 2
Install on real phones
We install the build on a rack of real Android phones, from budget models to flagships. The install steps on this site are written from what actually happened on those phones, including failures.
Phase 3
Boot to test server
The build is launched and a Guest Mode session is opened. Loading screens, login paths, and the first resource download are watched, not assumed.
Phase 4
Claim-by-claim verification
Every headline claim is checked one by one: test content present, training options working, HUD and sensitivity controls responsive. Anything that does not hold up is written up as a limit, not hidden.
Phase 5
Server behavior watch
Because test servers are unstable by nature, we record login errors, server-full messages, and downtime honestly. The error guides on this site come from these sessions.
Phase 6
Sign-off
Arjun Mehta signs off on the build only after all five phases pass. The reviewer who signs off is named, and the build is retested before any update replaces it.
Reader reports feed straight back into the protocol. If a build misbehaves on your device in a way we did not document, the contact page is the fastest way to get it in front of the lab.