Table of Contents
The remote app allows you to create a custom remote UI and bind buttons to captures.
Main UI
- Remote Title - The top line is the title of the remote. Select it to edit it.
- Remote Buttons - Up to 12 customizable buttons per remote. Select a button to transmit the capture file. Press again to stop. Long-press select to edit or delete the button.
- Waterfall - A small waterfall is shown while transmitting below the button grid.
- Gain - Control the transmitter Gain and Amp. The color indicates the overall transmitter power.
- Loop - Continuously transmit until stopped.
- Filename - Shows remote file name. Select it to rename the remote file.
- Add Button - Add a new button to the grid. New buttons will open in edit mode when you press them.
- New Remote - Start editing a new, empty remote.
- Open Remote - Open an existing remote file (REM) from the SD card.
Button Edit UI
- Name - The button's text.
- Path - Select to pick a capture file.
- Freq - The center frequency to send on. Will default to the capture file's metadata if found.
- Rate - The sample rate of the capture file. Uses the capture file's metadata or defaults to 500K. Cannot be set in the UI.
- Icon - The icon to show on the button.
- FG Color - The button's foreground color.
- BG Color - The button's background color.
- Preview - Shows what the button will look like.
- Trash - Deletes this button and returns to the main screen.
- Done - Save this button and returns to the main screen.
Tips
- Remotes are automatically saved on exit.
- Use the IQ Trim tool to trim silence from captures so they start instantly.
REM Files
Remote files can be edited in a text editor.
Empty lines and lines starting with #
are ignored.
The first non-ignored line is the remote "Title".
The remaining lines (up to 12) are read as remote buttons. They have the following format.
capture path,button text,icon index,fg color index,bg color index,center frequency,samplerate
The position of buttons on the screen can be changed by reordering lines in the REM file.
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.
How to collaborate
How to ask questions correctly
User manual
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- 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
- Applications
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)
- 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
Hardware Hacks
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.