Nevtech VMS · Reference handset

Ulefone Armor X32 Pro 5G

The standard body-worn handset for Nevtech VMS. A 280-gram rugged phone with a 6 nm SoC and a dedicated hardware H.264 encoder — chosen because it is the lightest device in its class that still carries LTE Band 71, and because every path the app depends on runs natively on it. We don't sell the hardware; buy it anywhere, install the app, and pair it in a minute.

Product render © Ulefone

280 g

Vest weight

$289.99

MSRP · direct

5,500 mAh

Battery

6 nm

Dimensity 6300

B71 · n71

600 MHz bands

Device specification

Manufacturer-published figures. Two to verify on receipt: the OS batch (Android 14 or 15 — either runs the platform fully) and your carrier's actual certification.

Physical

Weight: 280 g
Dimensions: 163.4 × 80.8 × 14.5 mm
Ingress: IP68 / IP69K
Shock: MIL-STD-810H
Glass: Gorilla Glass 5

Compute

SoC: Dimensity 6300 · 6 nm
CPU: 2×2.4 GHz A76 + 6×2.0 GHz A55
Memory: 8 GB (+8 GB virtual)
Storage: 256 GB + dedicated microSD
OS: Android 14+ (by batch)

Imaging

Main: 64 MP Sony IMX682 · f/1.9
Sensor: 1/1.73" · 0.8 µm · PDAF
Night: 25 MP IR (see fit table)
Front: 16 MP · f/2.2
FOV: ~80° diag · ~67° horiz

Display

Panel: IPS LCD (backlit — see fit table)
Size: 5.65" · 720 × 1440
Refresh: 90 Hz
Brightness: 600 nits peak

Radio

LTE: incl. B2/4/5/12/13/25/26/66/71
5G NR: incl. n2/5/25/41/66/71/77/78
Wi-Fi: 802.11ac (Wi-Fi 5)
Bluetooth: 5.2 · NFC yes

Sensors & I/O

Motion: Accelerometer · gyroscope
Position: GNSS · compass · barometer
Audio out: Loudspeaker + 3.5 mm jack
USB: Type-C 2.0
Charging: 18 W wired

Band lists abridged to the ones North-American fleets ask about; the full list is on the manufacturer's sheet. Carrier note: global-spec rugged phones are typically fine on T-Mobile, case-by-case on AT&T, and rarely certified on Verizon — verify one unit on your actual carrier and your actual account before a fleet purchase. That verification is a standing offer: send us your carrier and we'll test it with you.

How it maps to the platform

Each capability the app depends on, against what the hardware actually provides.

Platform requirement	Device provides	Fit
minSdk 26 / target SDK 35	Android 14 (API 34) or 15 (API 35)	Native Camera, microphone and location foreground-service types are first-class on both.
Camera2 · hardware pipeline	Camera2 full · PDAF · HDR	Native No compatibility shims required.
Hardware H.264 · we never transcode	Dimensity 6300 encoder, 1440p30-capable	Headroom The 1080p15 profile uses roughly a quarter of the encode budget.
Evidence capture quality (band-exempt)	64 MP IMX682 · 1/1.73" · f/1.9	Strong A large sensor downsampling to 1080p is oversampling, not upscaling — real low-light headroom.
Talkback · radio semantics (v1.2.0+)	Rugged loudspeaker + 3.5 mm jack	Strong The jack also takes a wired lapel mic or earpiece for noisy scenes.
20-second GPS breadcrumbs	GNSS + compass + gyro + accelerometer	Strong Barometer adds floor-level context in future work.
1.5-second SOS hold	Gorilla Glass 5, glove-capable touch	Fit The hold gesture tolerates imprecise gloved contact.
Offline evidence buffer + hashing	256 GB + dedicated microSD slot	Trivial The 2 GB dropout buffer is ~1.8 hrs of capture; the dedicated slot never costs the SIM tray.
Background survival	Near-stock Android, light OEM skin	Good One battery-optimization exclusion at provisioning; no Samsung/Xiaomi-class task killer.
Stealth screen dim	IPS LCD, backlit	Budgeted Stealth dim drops the backlight to a fraction of full-brightness draw, and the runtime table below already budgets the dimmed panel — so the shift figures hold as published.
Night-vision lens	25 MP dedicated IR camera	Headroom Night shifts run on the main 64 MP sensor and its low-light headroom; the dedicated IR module is future app work.
End-of-shift bulk needs	Wi-Fi 5 · USB-C 2.0	Plan for it Footage uploads during the shift, so there is normally nothing to dock — but a squad re-charging at 18 W takes 1.5–2 h, which is the practical argument for a spare unit per team.

Power and storage, shift by shift

Typical draw at the standard 1080p15 H.264 profile with the screen dimmed — the profile the platform actually records at, on duty, all day.

Draw component	Continuous capture	Event mode (buffering)*
Sensor + ISP @ 15 fps	0.40 – 0.70 W	0.35 – 0.55 W
H.264 hardware encode	0.15 – 0.30 W	0.10 – 0.20 W
App · hashing · file I/O	0.25 – 0.45 W	0.15 – 0.30 W
Flash writes	0.05 – 0.15 W	~0 W
Modem attached	0.20 – 0.40 W	0.05 – 0.15 W (sleeping)
GNSS breadcrumbs	0.05 – 0.15 W	0.05 – 0.15 W
Display, dimmed (IPS)	0.15 – 0.35 W	0.15 – 0.35 W
Total	1.25 – 2.50 W	0.85 – 1.70 W

*Event mode is the armed-buffering mode described below — its column is here because the power case is part of why it exists: ~a third less draw, and the modem sleeps.

Typical continuous shift: ~10–11 hours at ~1.7 W (sensor + encode + modem + dimmed screen).
Up to ~14 hours on good signal at moderate temperature.
Live streaming is the one setting worth planning — sustained LTE upload adds roughly 1–2 W while a stream is open, which is why dispatch-opened live view is the efficient default and why event mode keeps the stream closed until an operator opens the camera.
Year-two battery at ~80% capacity: plan on ~8.5 typical hours — for 12-hour shifts, pair with a pocket power bank or a second unit, standard practice across bodycam fleets.
Storage: ~1.1 GB/hr at the profile → a 10-hour continuous shift is ~11 GB; the 256 GB store holds weeks even before the microSD.

Deployment guidance

Pair long shifts with a pocket power bank — the same recommendation that has been on our body-cameras page from day one, and standard practice across bodycam fleets.
The figures above run the screen dimmed, which is the app's stealth behavior and the normal on-duty state.
18 W charging puts a full recharge at 1.5–2 hours; two units per officer covers back-to-back shifts with no downtime.
Android version varies by production batch (14 or 15 — both fully supported). Note the batch on receipt so your fleet records match your hardware.

Field of view — the wide-angle option

Coverage is a mounting decision, and it's one we make with you before the first unit goes on a vest.

The main lens sees roughly 67° horizontally (~80° diagonal). Add the 0.6× wide-angle converter we recommend for the mounting kit — a $15–40 optical part — and horizontal coverage moves to roughly 100–110°: commercial-bodycam territory, for the price of a lens cap.

Put the optic in the cradle, not on the phone. A cradle-integrated converter aligns itself every time the handset drops in — no clip to drift, vignette or get knocked loose mid-shift, and nothing for an officer to remember at the start of a tour. Ask us about mounting when you pilot and we'll spec the cradle and the optic against your vest.

Standard lens: ~67° horizontal (~80° diagonal) from the 64 MP main sensor.
With a 0.6× converter: ~100–110° horizontal, from a $15–40 optical part.
Self-aligning: set once in the cradle, correct on every shift — officers just drop the phone in.
What doesn't change: resolution headroom. Downsampled 64 MP at 1080p keeps plates and faces legible where a small-sensor bodycam smears them.

Auto-activation

The sensors this phone carries are the auto-activation platform.

The hardest failure in body-camera programs isn't equipment — it's activation. A Philadelphia compliance audit found footage missing in the large majority of encounters that required it, overwhelmingly from cameras never turned on, not cameras that failed. On this handset's own sensors: voice-fired SOS and spoken incident marks mid-shift, fall/shake detection from the accelerometer and gyroscope, and the armed mode — on-device sound classification for gunshot-family bangs, shouting, impacts, glass and doors, with a rolling two-minute pre-roll that saves the lead-up on every trigger. No holster sensor to buy, no vehicle kit, no per-sensor line item — the phone already contains the hardware. Full detail on the body-cameras page.

What the armed mode listens for — five trigger families from an on-device classifier watching 30 specific sounds: gunfire (a dedicated head we trained ourselves, with anti-fireworks voting), impacts and crashes, breaking glass, shouting/screaming, and doors — slams, knocks, forced entry. A door kicked open starts the recording, not just a gunshot.
Thresholds are tuned to your environment during onboarding — the gunshot head is trained on ~850 real recordings, and every trigger family is calibrated against your sites before it runs on a live shift.

Ears and balance. Every detector runs on the microphone, plus the accelerometer for falls — omnidirectional sensors that fire on what is happening around the officer whether or not it is in frame. Detection on this handset is audio and motion; the video is the evidence those triggers preserve.
All of it stays on the phone. Sound classification and speech recognition run on-device; raw audio never streams to a cloud AI. What leaves the phone is what always leaves it: the recording itself, under your retention rules.