Scout Lite + Biscuit DIY: Phone Wardriving vs SigRoam on Flipper Zero

Scout Lite can run Biscuit DIY as a community configuration. That turns the same ESP32-C5 hardware into a phone-controlled Biscuit device. It is useful, but it is a different wardriving architecture from Scout Lite running SigRoam or ESP32 Marauder.

The short version: Biscuit uses the phone as the control surface and GPS source; SigRoam uses the Flipper Zero as the control surface and Scout Lite's onboard GNSS as the position source.

Compare SigRoam, Biscuit, Marauder and GhostESP →

Scout Lite with Biscuit DIY: what changes?

Why Biscuit is interesting on Scout Lite

Biscuit DIY uses a single ESP32-C5 and gives it access to the same Biscuit Manager workflow used across the Biscuit ecosystem. That includes dual-band Wi-Fi scanning, Bluetooth scanning, Wardrive All, phone-based GPS mapping, session export and OTA firmware updates.

The important limitation is architectural, not a missing feature: one C5 has to share radio time between Wi-Fi, Bluetooth and the BLE connection to the phone. Biscuit's own documentation notes that combined scans can be less thorough than on Biscuit Pro or Ultra, where a second ESP32 handles the phone/system side.

That makes Scout Lite + Biscuit DIY a useful low-cost way to experience the Biscuit workflow without buying a separate Biscuit device, but it is not the same architecture as Pro or Ultra.

Biscuit Pro and Ultra are different from DIY

Biscuit Pro and Ultra use two ESP32 chips:

• ESP32-C5: Wi-Fi/Bluetooth scanning and wardriving.
• ESP32-WROOM: phone BLE link and system-management work.

This keeps the C5 focused on radio work. Ultra also adds an SD card for local storage and long-running capture. Pro and Ultra can act as a Manager for Biscuit Nodes, distributing scan roles across multiple C5 devices. DIY cannot act as a Node Manager.

All Node observations are still mapped with the Manager phone's current GPS position, so Biscuit remains fundamentally a phone-location architecture.

SigRoam and Biscuit solve the UI problem differently

Both projects avoid treating wardriving as just another command buried inside a general-purpose firmware, but their control models are almost opposites.

Biscuit

• headless scanner
• phone map and control UI
• phone GPS
• rich mobile interface
• Pro/Ultra can scale to multiple Nodes

SigRoam

• scanner firmware on Scout Lite
• Flipper Zero as field display
• onboard L86-M33 GNSS
• local microSD survey logging
• Dash / Strm / GPS / Sess diagnostics on the Flipper

There is no universal winner here. Biscuit is stronger if you want a phone-centric map and a scalable Node ecosystem. SigRoam is aimed at users who specifically want the Flipper to remain the instrument and do not want phone GPS in the critical survey path.

Community-tested Scout Lite compatibility

Hackazillarex demonstrated Biscuit DIY running on Scout Lite's ESP32-C5. Biscuit's current DIY documentation also states that ESP32-C5 boards with sufficient flash can run the DIY firmware, although Scout Lite is not listed as a named official profile.

How to try Biscuit DIY on Scout Lite

1. Disconnect Scout Lite from the Flipper Zero.
2. Open Biscuit's official DIY documentation and Web Flasher.
3. Enter ESP32-C5 bootloader mode with BOOT / RESET as documented by Biscuit.
4. Use the compatible ESP32-C5 DIY profile demonstrated by the community guide.
5. Install Biscuit Manager on iOS or Android.
6. Grant Bluetooth and Location permissions.
7. Connect to Scout Lite and start with a passive scan.
8. Confirm the phone GPS and live scan results before beginning a longer wardrive.

Official Biscuit DIY documentation: Biscuit DIY.

Returning to the Scout Lite native workflow

Experimenting with Biscuit is reversible. The Scout Lite Web Flasher provides the supported firmware path for the board.

1. Disconnect Scout Lite from the Flipper.
2. Open Scout Lite Web Flasher.
3. Enter bootloader mode.
4. Flash SigRoam for the dedicated Flipper wardriving workflow, or ESP32 Marauder for the broader general-purpose toolkit.

FAQ

Can Scout Lite run Biscuit DIY?

Yes as a community-tested ESP32-C5 configuration. Scout Lite is not currently a named official Biscuit DIY profile, so board-specific peripherals should not be assumed to work unless documented.

Does Biscuit use Scout Lite's onboard GPS?

Not in the documented Biscuit workflow. Biscuit Manager uses the phone's location for wardriving. Scout Lite's L86-M33 is used directly by the native SigRoam and Marauder workflows.

Can Biscuit DIY wardrive Wi-Fi and Bluetooth together?

Yes. Biscuit DIY supports Wardrive All. Because DIY has one ESP32-C5, Wi-Fi scanning, Bluetooth scanning and the BLE phone connection share that chip, so combined scans can be less thorough than on dual-chip Pro or Ultra.

Does Scout Lite microSD work for Biscuit wardrive logging?

Scout Lite-specific Biscuit wardrive logging to the onboard microSD is not documented. Biscuit supports SD features on supported board profiles, but do not assume Scout Lite's pin mapping is covered.

Can I switch back to SigRoam or Marauder?

Yes. Use the Scout Lite browser flasher and select the firmware you want.

Use wireless survey tools only where collection and testing are lawful and authorized. Biscuit, Flipper Zero and ESP32 Marauder are referenced for compatibility and comparison; PINGEQUA is independent of those projects.