rf_sentinel / hardware
External hardware
Optional add-ons that hear further than a phone and see things Android hides: ESP32 boards, USB WiFi and Bluetooth adapters, and RTL-SDR / HackRF radios. Plug them in with a USB OTG cable while scanning, no root. What they hear merges into RF Sentinel's own list with a badge (ESP32, USB WIFI, USB BT). Settings → External hardware has the switches, and a log for each piece of hardware to export. How each one works inside, with the numbers: Hardware internals.
ESP32 boards
Supported firmware
| Firmware | Link | What RF Sentinel gets |
|---|---|---|
| OUI-Spy (recommended) | USB OTG | Flock-You, Detector and Sky Spy detections as they happen: Flock cameras, the board's watchlist matches, Remote ID drones with position |
| OUI-SPY App-Controlled | Bluetooth | Flock-BLE, Flock-WiFi, Sky Spy, Detector and (optional) Wardrive survey engines |
| GhostESP | USB OTG | The WiFi networks it scans, about every 10 s (no Bluetooth over USB) |
| ESP32 Marauder | USB OTG, or through a Flipper Zero | WiFi networks and client devices from its passive beacon and probe sniffers, batched every 2 s; on ESP32-C5 boards (Marauder v8, BFFB v2, LilyGo T-Dongle C5, C5 DevKit) both 2.4 and 5 GHz |
| V2X2MAP (ESP32-C5, Europe) | USB OTG | European car-to-car radio (ITS-G5, 5.9 GHz): emergency vehicles with their light bar and siren state at the position they broadcast, and their "emergency vehicle approaching" warnings. RF Sentinel only listens to the board's stream; nothing is sent to it. Not in North America, which uses C-V2X |
| FREE-WiLi 2 | USB OTG | The WiFi networks its ESP32-C5 scans from its console's WiFi menu (2.4 + 5 GHz) |
USB
Plug the board into the phone with a USB OTG cable while scanning: Android offers to open RF Sentinel for it, and with Always ticked it never asks again. Native-USB boards (ESP32-S2 / S3 / C3 / C5 / C6) and boards with CP210x or CH340 USB bridges work. RF Sentinel only asks OUI-Spy for its version and live table, only asks GhostESP to scan and list networks, and only runs Marauder's passive sniffbeacon / sniffprobe sniffers (no attack commands, no settings changes). Settings shows the board's status.
ESP32 Marauder, ESP32-C5 and Flipper Zero
Dual-band: Marauder on an ESP32-C5 (Marauder v8, BFFB v2, LilyGo T-Dongle C5, C5 DevKit) hears 5 GHz networks that the phone's throttled WiFi scan misses, which helps catch vehicle routers on a pass. Keep Channel Hop on in Marauder's settings; RF Sentinel says so if the board stays on one channel.
Flipper Zero (e.g. with the BFFB board): plug the Flipper into the phone and open GPIO → USB-UART Bridge on the Flipper; RF Sentinel then talks to the board's Marauder through it. A BFFB v2 can also be plugged in by its own USB-C port. The original BFFB uses a 2.4 GHz-only ESP32.
Bluetooth (OUI-SPY App-Controlled)
- Power the board and start scanning in RF Sentinel.
- Settings → Pair OUI-SPY board → pick
OUI-SPY-xxxx. - Pair only there, not in Android's Bluetooth settings: the board keeps no pairing keys, so a phone-side bond breaks the link. The app tells you to tap Forget if it finds one.
While scanning, RF Sentinel switches on the board's Flock-BLE, Flock-WiFi, Sky Spy and Detector engines and switches them off when scanning stops. By default it also runs the Wardrive survey engine so the board relays every WiFi network and Bluetooth device; those go through RF Sentinel's own watchlist, presets and rules. In that mode the board sends standard WiFi probe requests, so turn off OUI-SPY: relay every network and Bluetooth device to keep it purely listening. Settings → OUI-SPY engines chooses which detection engines run (turn the two Flock engines off where there are no Flock cameras). With Phone Bluetooth scan with OUI-SPY off, the phone's own Bluetooth scan pauses while the board is live and the board does the Bluetooth scanning (it hears farther); the phone's scan comes back if the board drops out. Keep relaying on with it, or only the board's engine matches come in. The board's UniPwn, PCAP and Foxhunter engines are never used.
The status line under Scanning shows connecting… / live · N reports; the ESP32 filter chip lists only what the board reported.
USB WiFi adapters
RF Sentinel drives the adapter itself in receive-only monitor mode and hops the channels: no Android scan limit, longer range, and client devices (laptops, phones, cameras connected to a network) that a phone's WiFi scan can't see. It also lists the WiFi names nearby devices ask for (Menu → Requested networks). Allow USB access on the prompt; single-antenna dongles are handled automatically.
| Chip | WiFi | Bluetooth | Adapters |
|---|---|---|---|
| RTL8811AU / RTL8821AU | 2.4 GHz, 5 GHz experimental | 8821AU | ALFA AWUS036ACS |
| RTL8812AU | 2.4 + 5 GHz, experimental | - | ALFA AWUS036ACH, TP-Link Archer T4U, Netgear A6200v2 |
| RTL8812BU / RTL8822BU | 2.4 + 5 GHz | 8822BU | TP-Link Archer T3U, ASUS USB-AC53 / AC58, Wise Tiger AC1200 |
| RTL8814AU | 2.4 + 5 GHz | - | ALFA AWUS1900, TP-Link Archer T9UH, ASUS USB-AC68 |
| MT7612U | 2.4 + 5 GHz | - | ALFA AWUS036ACM, Netgear A6210, ASUS USB-AC55 |
| MT7921AU (WiFi 6E) | 2.4 + 5 + 6 GHz | Yes, long range | ALFA AWUS036AXML / AXM, Comfast CF-952AX, Netgear A8000 |
| RTL8187 | 2.4 GHz | - | ALFA AWUS036H, Netgear WG111v2 |
| RT3070 | 2.4 GHz | - | ALFA AWUS036NH / NEH |
| AR9271 | 2.4 GHz, experimental | - | ALFA AWUS036NHA, TP-Link TL-WN722N v1 |
Recognised but not supported yet: RTL8811CU / 8821CU / 8812CU, RT5370, MT7610U, AR7010.
- Firmware: the GitHub build includes each chip's firmware. The F-Droid build asks once before downloading the non-free files from linux-firmware and checks each one's SHA-256; the AR9271's free firmware is built in.
- Antenna check (Tools): compares the signal on each of the adapter's antennas from one access point, with an A / B swap test.
- Record frames (Settings → External hardware): saves what the adapter or a V2X board hears as a .pcap for Wireshark, up to 200 MB.
- It also flags deauthentication floods and karma / evil-twin access points (details).
USB Bluetooth
The Bluetooth part of a combo adapter (MT7921AU, RTL8821AU, RTL8822BU), or a plain USB Bluetooth dongle, works as a second Bluetooth LE scanner next to the phone's own, listening only, with LE Coded long range where the chip has it. Turn it off in Settings → External hardware → Scan Bluetooth with a USB adapter to leave a combo adapter to WiFi only.
| Bluetooth chip | Dongles |
|---|---|
| Any standard controller | CSR8510 (TP-Link UB400), Broadcom BCM20702 (ASUS USB-BT400) |
| RTL8761B / RTL8761C | TP-Link UB500, ASUS USB-BT500, UGREEN CM390 |
| RTL8723BU / RTL8821CU | Edimax EW-7611ULB |
RTL-SDR and HackRF One
An RTL-SDR dongle (R820T / R820T2 / R860 tuner, e.g. RTL-SDR Blog V3 or V4) or a HackRF One (receive only: its transmitter stays off) adds:
- Two-way radio transmitting nearby: sweeps the public-safety radio bands and measures only how much energy each channel carries; nothing is demodulated or decoded.
- P25 control channel (experimental): finds a P25 trunked system's control channel (700 / 800 MHz) and lists which talkgroups get a channel and when (Tools › P25 talkgroups), with alerts for talkgroups you watch. Listen to P25 voice (experimental, off by default) plays clear calls; encrypted calls can't be played. Receiving radio signalling is legal in many places but not all: check the law where you are. With more than one SDR scan ticked, the dongle takes turns.
- Cellular transmitters (experimental, off by default): a rise on the LTE uplink bands, such as a vehicle modem travelling with you.
- TETRA handsets (Europe and elsewhere): spots their burst rhythm on 380-385 MHz. A second (and third) RTL-SDR on a powered USB hub watches that band nonstop, with a TETRA bar on the main screen (Far / Closer / Very close) and beeps that speed up as one gets closer. Antenna: a vertical whip about 19.5 cm long, on the roof if you can; two dongles can share it through a 2-way splitter.
- ADS-B aircraft (Settings → RTL-SDR radio): decodes aircraft on 1090 MHz with no internet, for the police-aircraft check.
- A live radio waterfall (Tools).
Network SDR: an RTL-SDR plugged into a computer running rtl_tcp on your WiFi works too (Settings → RTL-SDR radio → Network SDR, about 5 MB/s of WiFi). Step by step, with every setting and status line: RTL-SDR guide. How the sweep, P25 and ADS-B decoding work: Hardware internals.
Meshtastic
A Meshtastic LoRa node paired over Bluetooth lets Sentinel Link phones far apart share detections on a private channel (setup, details, troubleshooting). Not yet tested on real hardware.
Hardware logs
Each piece of hardware keeps its own log on the phone: what it did, step by step, so a problem can be found without the developer having the same hardware. Nothing leaves the phone unless you share it.
| Log | What it records |
|---|---|
| USB WiFi adapter | Driver start-up, firmware, channel hopping, frames received, recoveries. |
| USB Bluetooth adapter | Start-up, firmware, advertising reports per minute. |
| RTL-SDR / HackRF | Plug-in, which scan has its turn, P25 and pager searches, stalls and restarts, Network SDR connection. |
| ESP32 board | Serial port opened, which firmware answered, status changes, why it stopped. |
| Mesh radio (Meshtastic / MeshCore) | The node-list radio over Bluetooth: connecting, live, out of reach. |
| OUI-SPY over Bluetooth | Connection states, setup, failed commands. |
| Sentinel Link Meshtastic node | Pairing, reading its settings, the RFSentinel channel, and every 10 minutes: packets sent, received from other Sentinels, other mesh packets, dropped and unreadable. |
| Sentinel Link Bluetooth | Waiting or linked, advertising failures, bad messages. |
| Sentinel Link internet relay | Connecting, connected, refused or unreachable, without the broker's name or any IP address. |
To send one: Settings → External hardware → Export a hardware log, pick it (an empty one is marked "empty"), and share the text file by email, messages or Drive. Export all hardware logs puts every log that has something in it into one file: the easiest choice when you're not sure which part is failing. Each export starts with the app version, the phone model, the hardware's status at that moment and, for USB hardware, the USB devices plugged in.
What's never in them: nearby devices' addresses or names, network names, your position, or the relay server's name. Each log keeps about 1 MB on the phone, plus the one before it. A crash has its own log: Settings → Lists, tools & about → Export crash log.
Attach the file to a GitHub issue with the hardware's model and what you expected to happen.
Questions
Which ESP32 board should I buy?
RF Sentinel works with any board the firmware supports: XIAO ESP32-S3, ESP32-S3 DevKitC, LilyGO T-Dongle-S3 and others are targets of OUI-Spy. An external antenna connector (u.FL / IPEX) is worth having for range.
How do I flash OUI-Spy?
Follow the firmware's own README (PlatformIO or its flash script). RF Sentinel doesn't flash boards.