Scout Lite hardwired L86 GPS for Flipper Zero - fixes Marauder GPS no-fix

Flipper Zero GPS Detected But No Fix? ESP32 Marauder Wardrive GPS Fix (2026)

PINGEQUA Lab · Flipper Zero GPS Troubleshooting · 7 min read · Updated 2026-08-03

Your Flipper Zero's ESP32 Marauder wardrive screen shows a GPS module — sats counting, maybe a lock icon flickering — but a fix never lands, or the GPS disappears entirely after a soft reboot. This is one of the most-reported wardrive failure modes in the Marauder project, and most of the time it isn't a dead module.

Quick answer A Flipper Zero GPS "detected but no fix" is usually a cold-start / sky-view problem, not hardware failure: go outside, give it 30 seconds to 2 minutes with a clear view of the sky, and recheck baudrate detection before you touch wiring. If it won't detect at all, you may be hitting a known Marauder firmware bug (issue #1268) — see the ordered fixes below, or skip flying-lead wiring altogether with the hard-soldered GPS on the Scout Lite.

The classic symptom

One of the earliest, most-referenced GPS reports in the ESP32Marauder repo is issue #338, opened 2023-09-21. The symptom chain in that report is the one that shows up over and over in later threads: GPS is detected on boot and the sat count climbs, but no fix is ever acquired; the user performs a soft reboot to try to reset it; after that reboot, GPS is no longer detected at all. The reporter's own words: "Very confusing lol."

That exact chain — detected → no fix → soft reboot → not detected — is why the fix list below is ordered the way it is. Work through the cheap, non-destructive checks first, because a soft reboot mid-troubleshooting can turn a "no fix yet" state into a "not detected" state that looks worse than it is.

Fix it in order

1. Go outside, give it a real cold start

GPS on Marauder's wardrive mode is not a Wi-Fi radio — it needs a direct line of sight to satellites and time to lock onto them. Per the official wardrive wiki, GPS needs a genuinely open sky (not indoors, not under a carport, not pressed against a window) and a cold start of roughly 30 seconds to 2 minutes before it can produce a fix. If you power on next to a window and check the screen five seconds later, you haven't actually tested anything yet.

2. Antenna facing up

Most flying-lead GPS modules used with Flipper Zero wardrive builds have a ceramic patch antenna on top of the board. That side has to face the sky. If the module is tucked face-down in a case, wrapped in tape, or pressed antenna-side against your hand or a backpack, you're attenuating the one signal path that matters.

3. Check GPS baudrate / detection in the boot log

Before touching any wiring, check what Marauder's own boot log is telling you. Issue #1268, opened 2026-05-07 on ESP32-C5 hardware running firmware 1.12.1 and titled "Scanning does not start," shows the module failing at the detection stage rather than the fix stage: the boot log reads "Could not detect GPS baudrate," followed by "GPS Not Found." That's a different failure mode than "detected but no fix" — it means Marauder never got a valid handshake with the module at all, which points toward baudrate, wiring, or firmware rather than sky view.

4. Wiring and pin mapping on flying-lead boards

If you're running a flying-lead GPS module — jumper wires from the module's TX/RX/VCC/GND to your ESP32 dev board's GPIO pins — this is, by a wide margin, the most fragile part of the whole chain. A swapped TX/RX pair, a jumper one pin off from the mapping your firmware build expects, or a header pin making intermittent contact will all produce exactly the "detected but no fix" or "randomly stops detecting" symptoms described above. Re-seat every jumper, confirm the module's TX goes to the board's RX (and vice versa), and confirm the pin mapping matches the firmware you're running — assignments have shifted across Marauder versions and forks. This is the step most people get stuck on; read the honest note below before assuming a rewire will fix everything.

5. Firmware version and re-seat

Marauder ships frequent updates — v1.14.0 landed 2026-07-22 with the first device-to-WiGLE/WDGWars direct upload support, and v1.14.1 followed 2026-08-01 with installer manifest fixes. GPS detection bugs have been reported across multiple versions — 1.10.1, 1.11.1, 1.12.1 among them — so there's no single "update and it's fixed" guarantee. Still, updating to the current stable build and fully re-seating the GPS module (unplug, reflash if needed, plug back in) rules out a corrupted flash or a connector that loosened during a previous flash. See our firmware install guide for the flashing steps.

6. Confirm the .csv/.log is actually landing on SD

A GPS fix that never gets written to disk looks identical to a GPS that never got a fix — check both. Marauder's official FAQ requires an SD card of 32 GB or smaller, formatted FAT32; anything larger, or exFAT, fails silently or partially. SD init/mount failures are their own long-running issue thread (#227, #95), separate from GPS itself. Pull the card after a session and confirm a .csv or .log file exists with GPS coordinate columns populated, not just headers.

An honest 2026 note: Not every "GPS Not Found" report is a wiring mistake or a rushed cold start. Issue #1268 documents a baudrate-detection failure on ESP32-C5 hardware running firmware 1.12.1 that reads as a firmware-layer bug, not user error. If you've worked through every fix above — open sky, full cold start, correct wiring, current firmware, SD confirmed — and Marauder still won't detect the module, check the issue tracker for updates before assuming your hardware is faulty, and consider testing on a different known-good firmware build as a workaround.

The wiring problem, solved in hardware

Looking back at the fix list above, wiring is the step most wardrivers get stuck on — because a jumper-wire GPS setup on a Flipper Zero WiFi devboard is a mechanical connection sitting on a device that gets picked up, dropped in a bag, and jostled during actual wardriving. Every loose header pin is a support ticket waiting to happen.

The Scout Lite removes that specific failure mode at the hardware level: it ships with a Quectel L86-M33 GPS module hard-soldered directly to the board, with no flying leads and no pin mapping to get right — there's nothing to wire, so nothing to wire wrong. It also has onboard microSD, so no separate card-and-holder to work loose, and ships preloaded with ESP32 Marauder, mounting straight to Flipper Zero's GPIO ready to wardrive.

That's a hardware-layer fix for a hardware-layer problem. It doesn't change anything about the firmware: Scout Lite runs the same ESP32 Marauder codebase as a DIY flying-lead build, on the same ESP32-C5 chip, so firmware-layer bugs — including baudrate-detection issues like #1268 — are exactly as possible on Scout Lite as on any other ESP32-C5 board running the same build. What Scout Lite buys you is one less variable: if GPS misbehaves, you already know it isn't a bad jumper wire.

Skip the flying leads entirely

Hard-soldered Quectel L86-M33 GPS, onboard microSD, ESP32 Marauder preloaded — mounts straight to your Flipper Zero's GPIO.

Get the Scout Lite →
Read the setup guide →

FAQ

Why does my Flipper Zero GPS not get a fix?
Most commonly it's a cold-start problem: GPS needs a genuinely open view of the sky and roughly 30 seconds to 2 minutes to lock on, per Marauder's own wardrive wiki. Being indoors, under cover, or checking the screen too soon after power-on will all produce a "detected, no fix" state that looks like a hardware fault but isn't. If sky view and cold start don't fix it, move on to checking baudrate detection, wiring, firmware version, and SD logging in order.
Marauder says GPS Not Found, what now?
"GPS Not Found" or "Could not detect GPS baudrate" in the boot log is a different failure than "detected but no fix" — Marauder never established a handshake with the module at all. This exact log output is documented in issue #1268 on ESP32-C5 hardware running firmware 1.12.1. Check your wiring (TX/RX not swapped, correct pin mapping for your firmware build), then update firmware and re-seat the module. If it persists after all of that, it may be the firmware-layer bug tracked in #1268 rather than something you can fix by rewiring.
How long does GPS cold start take?
Roughly 30 seconds to 2 minutes with a clear, unobstructed view of the sky, according to Marauder's official wardrive wiki. That's a cold start — the first lock after power-on with no recent almanac data. Indoors, near tall buildings, or under any roof, it may never lock at all regardless of how long you wait.
Does Scout Lite need GPS wiring?
No. Scout Lite ships with a Quectel L86-M33 GPS module hard-soldered directly to the board, so there are no flying leads, jumper wires, or pin mapping to configure — it mounts to Flipper Zero's GPIO with GPS and onboard microSD already wired in. It still runs the same ESP32 Marauder firmware as any other ESP32-C5 board, so firmware-layer GPS issues are equally possible; what's eliminated is the wiring failure mode, not the firmware one.

Sources & further reading (verified 2026-08-03): Issue #338 — GPS detected but no fix, then not detected after reboot (2023-09-21) · Issue #1268 — Could not detect GPS baudrate / GPS Not Found on ESP32-C5, firmware 1.12.1 (2026-05-07) · Official Marauder wardrive wiki — GPS sky-view and cold-start requirements · Official Marauder FAQ — SD card requirements (≤32GB, FAT32) · Issue #227 and Issue #95 — SD card init/mount failures · Marauder v1.14.0 release notes (2026-07-22) · Marauder v1.14.1 release notes (2026-08-01).

For authorized security testing and education only. Test only networks and devices you own or have explicit written permission to test. You are responsible for compliance with all applicable laws and radio regulations (e.g. FCC Part 15 in the US). "Flipper Zero" and "ESP32 Marauder" are referenced for compatibility and comparison; PINGEQUA is independent and not affiliated with or endorsed by their respective owners.

Retour au blog