This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
The Search app continuously sweeps a defined frequency range using FFT spectrum analysis and locks onto any signal that rises above a configurable power threshold. It is designed for passive signal detection — it does not demodulate audio during scanning, but logs the frequency, time, and duration of each detected signal.
UI Overview
Settings
- Min / Max: The frequency range to search. Default is 100 MHz to 400 MHz. Settings are saved per app (see Settings Persistence).
- LNA (0–40): Low-noise amplifier gain. See Receive Quality Issues.
- VGA (0–62): Variable-gain amplifier gain. There is no RF amplifier control in this app; the amp is always off.
- Trig (5–255, step 5, default 80): Power threshold for signal detection. A signal is detected when its FFT bin power exceeds
Mean + Trig. Set this higher to ignore weaker signals and reduce false triggers; lower to catch weaker signals. - Snap to: When enabled, the detected frequency is rounded to the nearest step before being displayed and logged. Available snap steps: 25 kHz, 12.5 kHz, 8.33 kHz, 2.5 kHz, 500 Hz. Default is 12.5 kHz (enabled).
- LOG: When checked, creates a timestamped CSV log file on the SD card each time it is enabled (see Logging).
Status Indicators
- Mean: The average FFT power across all bins in the current scan, shown as a value from 0–255. The detection threshold is
Mean + Trig. Setting Trig above the noise floor is the primary tuning task for this app. - Slices: The number of 2.5 MHz slices the scan range has been divided into, shown as
X / 32. Each slice is one FFT capture. The maximum supported span is 80 MHz (32 slices). - Rate: The detection update rate in Hz, indicating how many full scan sweeps are completed per second.
- VU meter: Displays the peak FFT power across all bins. The marker line indicates the current detection threshold (
Mean + Trig). - Timer: A progress bar showing the detect or release countdown (see Detection Timing).
- Status text: Shows the current state —
Listening,Locked!, orOut of range.
Big Frequency Display
Shows the frequency of the currently detected or locked signal. When a signal is found outside the configured Min/Max range, it is shown as Out of range and displayed in grey.
Spectrum Display
A colored gradient spectrum bar is shown across the screen, representing the FFT power across the entire scanned range. This provides a visual overview of band activity.
Frequency Log Table
The lower portion of the screen is a running log of all signals that were locked during the session, showing frequency, time of detection, and duration (in 100 ms units). Selecting an entry from the log opens the frequency entry screen, where the frequency can be saved to a freqman file on the SD card.
Detection Timing
The app operates in 100 ms timing units:
- Detection: A signal must remain above the threshold for 500 ms (5 × 100 ms) before it is locked. This prevents single-frame noise spikes from being logged.
- Release: Once locked, a signal is released 600 ms (6 × 100 ms) after it drops below the threshold. The duration logged is the time from lock to release.
Frequency Accuracy
Each FFT bin covers approximately 9.8 kHz (2.5 MHz ÷ 256 bins). The raw frequency resolution is therefore ±4.9 kHz. Enabling Snap to rounds the result to a grid, which can improve readability for known channel plans.
Logging
When LOG is enabled, a new CSV file is created at the start of the session: LOGS/SEARCH_YYYYMMDD_HHMMSS.CSV. The format is semicolon-delimited: Time;Freq;Duration;. A new file is created each time LOG is toggled on; existing files are not appended to.
A beep is emitted on signal lock if Beep on packets is enabled in the global Settings → Radio menu.
Settings Persistence
The power threshold, Min/Max frequencies, and Snap settings are saved to rx_search.ini on the SD card when App Settings is enabled in the global Settings menu.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Start here
Contributors
How to collaborate
Contributing Guidelines
How to ask questions correctly
Hardware
- PortaPack Versions (which one to buy)
- Features
- HackRF Versions
- Description of the hardware
- Enclosure/cases
- Repairs
- Mods
User manual
Intended use and Legality
- Usage cautions
- First steps
- Firmware update procedure
- User interface
- Powering the PortaPack
- Troubleshooting
- Won't boot
- Config Menu
- Firmware upgrade
- Diagnose firmware update in Windows
- Receive Quality Issues
- No TX/RX
- TX Carrier Only
- H2+ speaker modifications
- Dead Coin Cell Battery
- Factory Defaults
- SD card not recognized by PC with the SD-card over USB selected
- DFU overlay
- Full reset
- SolveBoard
- How to Format SDCard
- What if I don't like some of the apps
Applications
- 📥 Receivers
- 📤 Transmitters
- ADS-B(S) TX
- Adult Toys
- APRS TX
- BHT Xy/EP
- BLE TX
- BLESpam
- Burger Pager
- CVS Spam
- EPIRB
- FlipperTX
- GPS Sim
- Hopper
- Jammer
- KeeLoq TX
- Key fob TX
- LGE Tool
- MDC-1200 TX
- Morse TX
- OOK
- OOK Brute
- OOK Editor
- P25 TX
- POCSAG TX
- RDS
- RTTY TX
- SAME TX
- Signal gen
- Soundboard
- Spectrum Painter
- SSTV
- TEDI/LCR
- TouchTunes
- TPMS TX
- 🔄 Transceivers
- 🟡 Recon
- 🔴 Capture
- ▶️ Replay
- 🖲️ Remote
- 🔍 Looking Glass
- 🛠️ Utilities
- 🎮 Games
- ⚙️ Settings
- 💻 HackRF Mode
Misc
Developer Manual
- Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi), or other weird distros
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
- Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.
