WiFiAnalyzer: reading the Wi-Fi air from an Android phone
Android application to analyze Wi-Fi signals.
At a glance
- What is it?
- WiFiAnalyzer turns the Wi-Fi scan an Android phone already performs into access point, channel and distance views, with export and a vendor lookup. The hardware decides which bands and channel widths you ever see, and the project's own README stops short on the topic list it promises.
- Who is it for?
- WiFiAnalyzer suits anyone who wants a read only look at the Wi-Fi air from an Android phone they already own, and who will treat channel ratings as a starting point rather than a measurement. It is the wrong choice for an iPhone, for an unattended scan that has to keep running, or for anyone expecting a distance figure accurate to a metre.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 7 days ago.
- What is it written in?
- Mainly Kotlin, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- VREMSoftwareDevelopment/WiFiAnalyzer5,099 ★ · +126
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| VREMSoftwareDevelopment/WiFiAnalyzer | 5k | 5.1k |
126 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Nearby access points, channel graphs and a strength over time view
Everything WiFiAnalyzer shows comes from the radio scan your phone already performs, and the app sorts that scan into three views. One identifies nearby access points. One graphs channel signal strength, so you can see how loud each channel is and how the channels sit next to each other. One graphs the signal strength of a single access point over time, which is the view that shows whether a link stays steady or fades while people move through the building. On top of those, the app analyses the networks it sees and rates the channels, offers the access point list in a complete or a compact form, puts an estimated distance next to each entry, and can export the details.
Treat that distance number as an estimate rather than a measurement. The how-to section points at the free-space path loss page on Wikipedia for how distance is calculated, and free-space spreading is the assumption behind it. Walls, floors and bodies are not part of that model. If you pick an access point to walk toward on the strength of the figure, a few metres of difference means nothing, and the signal strength bars are the more honest comparison.
HT/VHT widths and the 6 GHz band depend on the phone, not on the app
Two lines of the feature list carry the same caveat. HT/VHT detection at 40, 80, 160 and 320 MHz, and the 2.4 GHz, 5 GHz and 6 GHz bands, are both marked as requiring hardware and software support. Your handset's radio and the Android release running on it decide what turns up in the scan, not a setting inside WiFiAnalyzer. A phone without 6 GHz support never produces a 6 GHz row, and a chipset capped at 80 MHz reports widths only up to 80 MHz.
So a blank column is not a bug. Before filing anything about a missing band or a missing width, check what the hardware itself reports. The app cannot widen the radio. Two phones running the same build can disagree about the same room for hardware reasons alone, which makes side-by-side screenshots a poor way to judge the app or the room.
Four filters and a compact view decide what you are allowed to see
The filter row narrows the access point list on four axes: Wi-Fi band, signal strength, security and SSID. The list view itself can be complete or compact, the theme can be dark, light or system, and Pause plus Resume let you freeze a scan while you read and restart it when you move.
Those controls are where results get misread. A high signal strength filter removes the weak access points that cause slow handovers, and an SSID filter hides everything except the network you already know works. The project routes SSID filter questions to issue 125 and channel graph display questions to issue 64, which says both areas had behaviour users had to ask about. Clear every filter before you conclude that a channel is empty or a network is missing.
Three copies ship, and every recent tag is named for F-Droid
The app ships under the package name com.vrem.wifianalyzer on both the Play Store and F-Droid, and the repository's releases page carries a third copy. Those are three supply chains: a store build, a build from a community index, and whatever the project attaches to a tag.
The tag names make that split visible. The three most recent releases are V3.3.1-F-DROID dated 2026-07-01, V3.2.2-F-DROID dated 2026-01-10 and V3.2.1-F-DROID dated 2025-06-14. Every one carries the F-DROID suffix, so what the releases page tracks is the F-Droid flavour of the build, and those names tell you nothing about which version the Play Store is serving now. The repository is ahead of all three tags: the last push to the default branch main is dated 2026-10-03.
If you install a build from outside the two stores, verify it before you trust its readings. SECURITY.md holds a SHA-256 fingerprint for APK signatures, and the project asks you to validate downloads against the assets on the official releases page. A Wi-Fi analyzer is exactly the kind of app that arrives as a link somebody pasted into a chat.
No internet permission means the OUI lookup never leaves the phone
The privacy section makes four claims: no personal or device information is collected, the app asks for as few permissions as it can manage, the source is open so nothing is hidden, and the application does not require access to the internet, sending nothing out and receiving nothing in return.
That last claim shapes what the features can be. Vendor/OUI database lookup, which turns a hardware address into a vendor name, cannot be a live call to a web service, so it works from data held on the device and has no answer for an address that is missing from that data. The same constraint means there is no cloud account, no sync of scan history between two phones, and no server side channel recommendation. Captures stay where they were made until you export them yourself.
The permission story has one tension worth naming. Android guards access point details behind location permission, which is why the repository keeps a wiki page on location service permission requirements. Small permission sets and useful scan data pull against each other on a current Android release, and WiFiAnalyzer resolves that pull by asking for location rather than by refusing to scan.
The documentation section promises a topic list that never arrives
The README points at USER_MANUAL.md as the complete guide, then says that for quick access to specific topics you should see a list. That list is not there. The section ends on the word see and a colon, and the next heading starts with nothing in between. Whatever the project meant to link at that spot lives in the manual or in the wiki.
The gap matters because the wiki holds the hard parts. Android Wi-Fi scanning throttling has its own wiki page, and it answers the complaint that every Wi-Fi scanner attracts: the list stops refreshing, or refreshes far more slowly than expected, because the platform limits how often an app may scan. Location service permission requirements have a page of their own. Secondary user accounts have a page too, which is the first place to look when the app sees no networks on a work profile or a cloned user.
The feature list carries its own gap, closing with a line saying the application has too many features to mention them all. So neither the README nor that list is a complete inventory, and anything past the thirteen listed capabilities has to be read out of USER_MANUAL.md or the source.
No password cracking, no phishing, and no iOS build
The project says it directly: WiFiAnalyzer is not a Wi-Fi password cracking or phishing tool. It reads what the radio already broadcasts, including the security type of each network, and stops there. Anyone who arrived hoping to get into a network they do not control picked the wrong app. The security filter in the access point list exists to tell you how a network is protected, not to change it.
There is no iOS build in this repository either. The README sends iPhone users to issue 69, a request in the issue tracker rather than a download link, so an iOS reader has nothing to install from here and needs a different tool entirely. The absence is worth stating plainly because unrelated products share the WiFiAnalyzer name.
The tracker is small: eight issues are open. Bug reports go to the issue tracker, formatting advice sits on a feedback wiki page, and a Discussions board runs beside them. Expect an answer to a concrete bug report rather than a roadmap, and search what is already filed before adding to it.
Android Studio import and the Gradle tasks that gate a commit
The project builds inside Android Studio: install it, choose Import project on the welcome screen, select the root directory of the repository, and the build runs by itself. The root does carry the wrapper, with gradlew, gradlew.bat, build.gradle.kts, settings.gradle.kts, gradle.properties and a gradle directory, so a command line build is reachable even though the import steps are the ones described. Alongside those sit AGENTS.md, CONTRIBUTING.md, SECURITY.md, USER_MANUAL.md, codecov.yml, _config.yml, fastlane/, images/ and scripts/.
What is written down is the set of Gradle tasks a contributor runs, and each one names the report it produces:
./gradlew ktlintCheck
./gradlew ktlintFormat
./gradlew lintDebug
./gradlew testDebugUnitTest
./gradlew jacocoTestCoverageVerification`ktlintCheck` and `ktlintFormat` cover Kotlin style, `lintDebug` writes app/build/reports/lint-results.html, `testDebugUnitTest` writes app/build/reports/tests/testDebugUnitTest/index.html, and `jacocoTestCoverageVerification` writes app/build/reports/jacoco/jacocoTestReport/html/index.html. Two GitHub Actions workflows back those tasks up, android-ci.yml and codeql-analysis.yml, and the badge row adds Codacy, Codecov, Snyk, FOSSA and Weblate, so style, tests, coverage, dependency scanning and translations are all checked somewhere other than your own machine.
Editorial conclusion
WiFiAnalyzer suits anyone who wants a read only look at the Wi-Fi air from an Android phone they already own, and who will treat channel ratings as a starting point rather than a measurement. It is the wrong choice for an iPhone, for an unattended scan that has to keep running, or for anyone expecting a distance figure accurate to a metre. Before installing a build from outside the two stores, match its signature against the SHA-256 fingerprint in SECURITY.md, and read USER_MANUAL.md rather than the README, which stops short on the topic list it promises.
Frequently asked questions
What does a Wi-Fi analyzer do, and what does WiFiAnalyzer show?
It reads the radio environment around a phone. WiFiAnalyzer identifies nearby access points, graphs channel signal strength and signal strength over time, rates channels, adds an estimated distance per access point, and can export the access point details.
What is wifi analyzer, in the case of WiFiAnalyzer?
WiFiAnalyzer is a Kotlin Android application for looking at Wi-Fi signals. Its feature list covers HT/VHT detection at 40, 80, 160 and 320 MHz, the 2.4 GHz, 5 GHz and 6 GHz bands, a complete or compact access point view, vendor/OUI database lookup, filters and pause or resume scanning.
how to use wifi analyzer android, and is WiFiAnalyzer the Android one?
Yes, WiFiAnalyzer is Android only and ships as com.vrem.wifianalyzer on the Play Store and on F-Droid. Scanning can be paused and resumed from the interface, and filters for Wi-Fi band, signal strength, security and SSID narrow the access point list. The repository keeps a wiki page on location service permission requirements.
How do you use WiFiAnalyzer to find the best channel?
The app analyses the Wi-Fi networks it sees and rates channels, and graphs channel signal strength so the quietest channel stands out. Band support for 2.4 GHz, 5 GHz and 6 GHz and HT/VHT widths of 40, 80, 160 and 320 MHz both require hardware and software support, so your phone decides which rows appear.
Is WiFiAnalyzer a good open source tool for analyzing WiFi networks?
It is open source under the GNU General Public License v3.0, hosted at github.com/VREMSoftwareDevelopment/WiFiAnalyzer and published on F-Droid. It needs no internet access, so it neither sends nor receives personal or device information, and the project states it is not a password cracking or phishing tool.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vremsoftwaredevelopment-wifianalyzer)Star history chart for your README
[](https://hysenlabs.com/projects/vremsoftwaredevelopment-wifianalyzer)Was this useful?