Back to wiki menu

Platform: Reality Apps (mobile)

Hardware Compatibility, Security & Privacy

Last updated: July 8, 2026 at 20:16

Hardware Compatibility, Security & Privacy FAQ

Overview

For Verified Reality (VRA) to function as a trusted forensic instrument, it must enforce rigorous standards on the hardware it utilizes. We do not assume every phone is capable of testifying to the truth. Therefore, the application executes complex preflight gates to qualify the device before capture begins. Furthermore, the app includes robust security and privacy controls designed to protect both the integrity of the evidence and the safety of the operator in high-risk environments.

Hardware Requirements & Preflight Gates

VRA is built as a native forensic platform for Android, utilizing modern development frameworks (Expo / React Native) and deeply hooking into Android-native camera, sensor, PRNU, and Content Authenticity (C2PA) modules.

To ensure the integrity of multimodal active interrogation, the app enforces a three-tier preflight gate at boot. Devices that fail mandatory checks are blocked before capture begins. Verifiers are not sent into a job that the phone cannot mathematically complete.

Mandatory Static Checks (Tier 1)

These checks are performed against the device's stated specifications:

  • Operating System: Android 11+ (API 30+). Consult specific APK release notes for the definitive minSdk build version.

  • Architecture: 64-bit CPU.

  • Memory Floor: Approximately 5 GB of available RAM.

Mandatory Active Probes (Tier 2)

The app queries the physical hardware to ensure real sensors are responding, rather than emulators or virtual drivers. Probes include:

  • Gyroscope

  • Magnetometer

  • Accelerometer

  • Microphone

  • Root/Tamper detection

Advisory Checks (Tier 3)

Failure here does not block capture but will downgrade the device’s capability profile and update the Command Center device profile record:

  • Camera hardware capability level (Camera2 API).

  • ISP latency baseline.

  • Thermal and battery state at boot.

  • Official app signing fingerprint verification.

Runtime Device Tiers (Graceful Degradation)

VRA classifies qualified devices into coarse behavioral tiers based on RAM, model heuristics, and capability probes. The application dynamically adapts its behavior based on this runtime detected class.

TierTypical ClassForensic BehaviorLEGACYOlder or tight-RAM phones.Strict memory gates, shorter seal pacing, alternate C2PA paths (detached sidecars). Aims to produce uploadable truth packets, albeit with reduced forensic richness.STANDARDMid-range modern Android.Full standard seal pipeline. Unified C2PA injector path on capable builds.SUPERHigh-RAM flagships.standard pipeline with headroom for concurrent heavy workloads.

Field Operations Principle: We never strand a verifier in the field because a non-critical probe failed. Graceful degradation ensures capture continues where architected, even if optional metadata is corrupt or missing (server-side quarantine handles these packets post-upload).

Security & Privacy Posture (User Trust Framework)

VRA implements robust controls to maintain evidence chain of custody and protect the user.

ControlTechnical ImpactUser BenefitFLAG_SECURENative Android control.Blocks casual screenshots or screen recording over the capture UI during sensitive forensic work.Forced Update GateMandatory logic at launch.Blocks outdated APK builds. Verifiers must run builds with current forensic patches to maintain system trust.Offline Upload VaultNative file isolation.Sealed truth packets survive network failure. Field work is never lost; retry upload from Basecamp when a connection is restored.Ghost / Burner RAM ModelVolatile memory capture.Evidence can be held exclusively in RAM during high-risk capture sessions, utilizing disk shred paths for operator protection.Panic / Vanish ProtocolsDestructive safety sequences.Safety sequences for immediate operator protection (requires explicit user acknowledgment of data-loss risk).Session Token HygieneToken stripping logic.Bearer tokens are stripped from persisted session blobs where designed.Recursive ConsentCryptographic legal binding.Captures checkbox results and legal document hashes to prove exactly which Terms and Reality Oaths governed a specific session.

FAQ: Hardware & Troubleshooting

Q: Why is preflight blocking my phone? VRA requires uncompromised computational power to capture truth. If preflight blocks your device, it means the phone failed Tier 1 (Static) requirements (such as minimum RAM, outdated OS, or non-64-bit CPU) or Tier 2 (Active Probes) indicating the hardware is compromised, rooted, or lacking essential sensors like a gyroscope. Burner phones and easily manipulated legacy devices are physically locked out to protect algorithmic trust.

Q: Does the app work identically on every phone? No. Tier degradation is real and intentional. VRA adapts to what the specific silicon on your device can actually support. Older phones (Legacy tier) may use alternate C2PA paths or tighter memory gates while still attempting to produce a complete truth packet.

Q: My phone is mid-range, but Camera Hardware Level is LIMITED. What does that mean? This is common (e.g., on some Samsung A-series). VRA may skip certain deep ISP manual-exposure tests on LIMITED hardware, but other liveness channels (acoustic, motion, crypto) remain active.

Q: What if upload fails in the field? Never strand work in the field. VRA seals the work natively. If upload fails, the truth packet stays safely in the local Basecamp vault, waiting for you to perform a manual retry when you have a better network connection.