19 - Nov - 2026

I tested my Android vs. my ESP32 for network scanning, and the winner wasn’t what I expected

My phone has multiple CPU cores, gigabytes of RAM, and a polished Wi-Fi analyzer app I’ve trusted for years. My ESP32 has two cores, a few hundred kilobytes of SRAM, and costs less than a fancy coffee. On paper, this isn’t even a fight, but the ESP32 can do a lot of useful things for your network.

So when I decided to put them head to head to see which one does a better job of mapping the Wi-Fi airspace around my home, I expected a quick knockout. What I found instead wasn’t expected, but should’ve been obvious.

My Pixel versus a chip that costs less than lunch

Same home network, same fight, very different rules

I ran both scanners against the same network: my home Wi-Fi, which hosts well over twenty devices ranging from my home lab server, my Home Assistant virtual machine, smart bulbs, plugs, projectors, five laptops, and half a dozen ESP32s for my various ESPHome deployments. This is a pretty busy network with limited bandwidth and a router that’s bordering on requiring an upgrade.

On the Android side, I used WiFiAnalyzer. It shows every nearby access point with its SSID, signal strength, channel, and security type, plus graphs that make channel congestion painfully obvious. On the ESP32, I flashed a sketch that runs a Wi-Fi scan on a loop and pushes the results to a small webpage. The phone has a small head start here because installing WiFiAnalyzer takes a few taps, while the ESP32 takes a computer, the Arduino IDE, and a USB cable.

Android treats your Wi-Fi scans like a limited resource

Four scans every two minutes, then the graph freezes and sulks

WiFiAnalyzer is a polished app, and my Pixel’s radio sees 2.4 GHz, 5 GHz, and 6 GHz networks. But that’s about where the Pixel’s advantage diminishes.

Since Android 9, a foreground app can only trigger four Wi-Fi scans every two minutes, and background apps get far less. WiFiAnalyzer’s own documentation admits it can’t scan faster than the OS allows, whatever you set its scan interval to. This means that the sustained rate is about one scan every 30 seconds.

You can switch throttling off in the Developer options, but that’s a system-wide tweak most people wouldn’t want to deal with. Android also insists on location permission and location services before any app can scan for Wi-Fi at all. Walking around with the phone hunting for a dead zone, the signal graph updated in bursts and then froze, which is exactly the opposite of what you want in a network scanner.

The ESP32 scans whenever it likes and never asks permission

No throttling, no location prompt, no questions asked

The ESP32 has no permission layer or throttle sitting between your code and its radio. If you call the scan function, it scans the network, no questions asked. Mine ran a full sweep of the 2.4GHz band every few seconds, all day, without a single complaint, and logged every result so I could watch neighboring networks hop channels overnight. It doesn’t need a lot of power, meaning a regular USB port is enough to run it, so instead of a one-off scan, you can now run and record longer scans of your network — a much more useful log of data when you’re working out network issues.

There’s one more capability that the ESP32 brings which WiFiAnalyzer simply can’t: listening to raw Wi-Fi frames. Access points are only half the picture. This feature, also called Promiscuous mode, lets the ESP32 spot client devices like phones, laptops, and smart plugs as they chatter and send probe requests, even on networks it wasn’t connected to. The catch is that modern phones randomize their MAC addresses, so one phone can show up as multiple devices. Regardless, it’s a level of visibility a stock Android phone simply won’t allow an app. Stick to your own airspace, and don’t log or share other people’s device identifiers.

The ESP32 is deaf to everything above 2.4 GHz

Great at scanning, blind to your entire 5 GHz network

esp32-s31-board-isometric
Image taken from Espressif’s website.
Credit: Espressif

The ESP32 is the better network scanner, but there’s one major flaw holding it back. Most ESP32 boards, including the classic, S3, and C3, only see the 2.4 GHz band, so every 5 GHz and 6 GHz network around you is invisible to them. Newer chips like the ESP32-C5 support 5 GHz, but 6 GHz is still off the table. That means the ESP32 misses a lot of networks, likely the ones you care about.

WiFiAnalyzer also gives you channel graphs, time graphs, and vendor lookups in seconds, while the ESP32 gives you whatever you bothered to code. Thankfully, there are tons of tutorials and examples on the internet for you to get started with, or you can copy mine here on GitHub, but you will likely have to code any advanced functionality you want yourself. It’s not too tough to do, especially if you’ve got an AI model assisting you, but it is an extra step.

A cheap chip beat my Pixel, just not on paper

Use the phone for quick checks and the chip for the long game

If you just need to know which channel your router should be on, the phone gets you there faster. And pulling it out of my pocket beats squinting at a serial monitor every single time. My Pixel 9a sees more networks across more bands and makes the data far prettier, but Android ultimately restricts it, and for good reason.

The ESP32 can’t hear 5 GHz or 6 GHz, but it scans nonstop, logs everything, and sniffs out client devices my phone can’t see. If you’ve got a spare one sitting in a drawer, flash a scanner sketch, plug it into a wall charger, and let it watch your airwaves.

Leave a Reply

Your email address will not be published. Required fields are marked *