How We Test APKs

The rule

No APK gets a download button on this site until it passes every step below. A failed step means the build is rejected or held until it is fixed.

1. Signature and file check

We verify the APK signature matches the developer release and confirm the exact file size and version. The file you download is the file we tested: 2.4 MB, package com.ghostlock.app.

2. Malware scan

The build is scanned with multiple malware engines. Any detection, even a heuristic one, stops the release until it is investigated.

3. Real-device install

We install the APK on five physical phones: Galaxy A55 (Android 15), Pixel 8 (Android 16), Redmi Note 13 Pro (Android 14), Infinix Note 40 Pro (Android 14), and Galaxy A13 (Android 12). No emulators for the verdict; alarms need real sensors.

4. Alarm drills

Every alarm type is armed and triggered: motion, charger removal, pickpocket, SIM change, geo-fence exit, and failed-unlock intruder capture. The siren is checked on silent mode, and the power-off and network-toggle blocks are tested.

5. Battery measurement

The guard runs for a full 24 hours while we log drain. Our bar: under 5% per day on a healthy phone, or the build does not ship.

6. Permission audit

Each requested permission is checked against what the feature actually needs. Accessibility and device-admin are expected here; anything beyond that gets flagged in the review.