Fieldwatch listens to Wi-Fi and BLE and identifies radios around you from a signature catalog you manage in-app (tags, body-cams, drones, vehicle APs, etc.). Set alerts when a watched signature or MAC is heard. Work a sit to compare the same area or drive over time. Track radios moving with you and generate reports from that data. Here is what’s new since my last update: Fieldwatch 1.1.8 is on GitHub. Signature catalog is now 75. Name Wi-Fi the way you already name BLE: fleet cars, mesh, guest APs, and the locally administered BSSIDs that used to hide the pencil. If your local fire trucks trip the Compex signature, edit the Advertised name to “Fire Truck Station 51.” Works on any radio Fieldwatch treats as a non-rotating MAC. Manage named radios under Settings. The Detail page now describes the radio from the signature match. A Raven on Wi-Fi Direct reads as a gunshot sensor. New signatures for privacy awareness: Digital Ally and other body/in-car cameras, wearable recorders, camera glasses, and roadside names Fieldwatch can hear. Since 1.1.4 you can refresh the stock catalog with Update stock catalog from GitHub under Settings. Add observer notes to a radio: a short caption you write. It shows on Detail, as a chip on the Live list, and in every report. Walk the ground, then see the walk. Path is a north-up trace of this phone for the sit you named. Red dots are Extra attention. Blue dots are radios you named. Dots mark where you were when you heard them — not a pin on the other radio. Works offline in Airplane mode. The same trace prints on Debrief and Compare PDFs. Two rooms, two days, one question: what was only here? Compare sits is presence only — only in this window, only in the other, or in both. Kind plus MAC. Text, PDF, and a paste-ready AI addendum. Not a second inventory for a chatbot to reprint. Export logs or sits as CSV, JSON Lines, GPX, KML, or WiGLE CSV. Plus a lot of cleanup. If you haven’t pulled the latest APK in a while, this one is worth it. The user manual is updated to match.

Noticed the Fieldwatch radar sweep had stopped sweeping. I admit this is a bit of a silly view, maybe, but it is still the fastest way to see the whole field at once. Blips are louder (closer) toward the center. Signature matches are the bigger dots, in that family’s color; unmatched radios are smaller. A watchlist hit pings, then keeps a phosphor ring so you can still find it. Tap a blip for that radio’s detail. Pinch to zoom; double-tap resets. Ver. 1.0.6: the sweep moves again, and fades off the beam. github.com/OffGridPete/Field…

Fieldwatch 1.0.3 is the TAK / CoT pass. Same idea as before: UDP Cursor-on-Target of radios Fieldwatch already labeled. Not a plugin. What changed: • Remote ID - ASTM Basic ID sticks. TAK keys the aircraft on UAS ID, so one marker moves instead of a new dot every BLE rotation. • Pilot pin - if the ad decoded operator lat/lon, that’s a second pin, linked to the aircraft. Not the aircraft pin. • Heard here - Extra attention still sits on your GPS. Callsign ends in (here) so it does not look like the camera is at that point. Maroon vs Yellow vs Orange so the map reads without opening remarks. • Gone - when the radio leaves, ATAK drops it. The 10 s / 30 m hold is unchanged; sent this tick flashing to 0 is that hold. On the feed is how many pins Fieldwatch is keeping. • Where it goes - This phone (127.0.0.1:10011) for ATAK CIV on the same handset, LAN multicast for other ATAKs on this Wi-Fi, Custom for a unicast IPv4. UDP. A TAK server’s TCP 8087 is not this feed. github.com/OffGridPete/Field…

If you want to know what devices are actually being used around you, Spectre is an Android app that listens to the Wi-Fi and Bluetooth your phone already hears, matches them against a signature database, and flags what matters. Useful for: • Lost or hidden tracker tags • Devices moving with you (including a tag under a car seat) • Card-skimmer class radios • Flock-style cameras still talking BLE or Wi-Fi • Axon-class body cams • Fleet / public-safety radios • Meta glasses and wearables • Flipper, Pineapple, Marauder • Known vehicles with a stable keyless / TPMS / infotainment address • Drones — if Remote ID is on BLE, it decodes position and aircraft info Beep, voice, and on-screen alerts. Watch list. Night mode. Multiple views, sorts, and saved filter presets. Catalog is editable. Add IDs directly in the app. Spectre will suggest candidates and fill defaults. Then drill vendor, signal, session, raw payload, and decoded fields when they aren’t encrypted. Push detections to TAK as CoT — ATAK, WinTAK, iTAK. No ads. No subscription. No backend. Works offline. Receive only — no deauth, no handshake capture, no cracking, no connecting. Don’t be a jerk with it. Built for me. Shared because it earned its keep. User guide is in the repo.

After looking at a number of Flock detection projects, including the original research by NitekryDPaul, the wildcard probe work from DeFlockJoplin, colonelpanichacks’ flock-you firmware, and several CYD-based ports, I decided to put together my own version on the ESP32 Cheap Yellow Display (ESP32-2432S028R) with a 2.8” touchscreen. Because there are multiple detection techniques, and Flock has made changes over time that affect how well different methods work, I implemented all the known passive methods and added a menu so you can enable or disable them as needed. This is my first attempt, and I’m sure some of the existing solutions are far superior, but I had fun rolling my own. No deauth. No attack frames. It simply listens in WiFi promiscuous mode, hops channels, and matches what it hears against a compiled OUI table plus known signatures: • Wildcard probe requests from known OUIs (highest confidence) • LiteOn vendor IEs • SSID keywords (flock, raven, etc.) • Frames addressed to Flock MACs • Optional BLE (XUNTONG / Raven UUIDs) When something is detected, you get a full-screen alert showing the method, MAC, OUI, RSSI, channel, and confidence, along with optional piezo, RGB LED, and microSD CSV logging. Next I plan to put together a more sophisticated SIGINT-style solution for Android phones. Same core idea, but running on a device you already carry. My goal is to make it highly configurable so you can use it to quickly identify just about any BLE or WiFi signature that isn’t pure random.