27f566be8f
New ui_scanner, inspired on AlainD's (alain00091) PR: https://github.com/eried/portapack-mayhem/pull/80 It includes the following: 1) A big frequency numbers display. 2) A Manual scan section (you can input a frequency range (START / END), choose a STEP value from an available of standard frequency intervals, and press SCAN button. 3) An AM / WFM / NFM scan mode selector, changing "on the fly". 4) A PAUSE / RESUME button, which will make the scanner to stop upon you listening something of interest 5) AUDIO APP button, a quick shortcut into the analog audio visualizing / recording app, with the mode, frequency, amp, LNA, VGA settings already in tune with the scanner. 6) Two enums are added to freqman.hpp, reserved for compatibility with AlainD's proposed freqman's app and / or further enhancement. More on this topic: ORIGINAL scanner just used one frequency step, when creating scanning frequency ranges, which was unacceptable. AlainD enhanced freqman in order to pass different steppings along with ranges. This seems an excellent idea, and I preserved that aspect on my current implementation of thisscanner, while adding those enums into the freqman just to keep the door open for AlainD's freqman in the future. 7) I did eliminate the extra blank spaces added by function to_string_short_freq() which created unnecessary spacing in every app where there is need for a SHORT string, from a frequency number. (SHORT!, no extra spaces!!) 8) I also maintained AlainD idea of capping the number of frequencies which are dynamically created for each range and stored inside a memory based db. While AlainD capped the number into 400 frequencies, I was able to up that value a bit more, into 500. Cheers! |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| docs | ||
| firmware | ||
| hackrf@43e6f99fe8 | ||
| hardware | ||
| sdcard | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| CMakeLists.txt | ||
| dockerfile | ||
| dockerfile-nogit | ||
| LICENSE | ||
| README.md | ||
PortaPack Mayhem
This is a fork of the Havoc firmware, which itself was a fork of the PortaPack firmware, an add-on for the HackRF. A fork is a derivate, in this case one that has extra features and fixes when compared to the older versions.
PortaPack H2 (clone) with a custom 3d printed case
Quick overview
If you are new to HackRF+PortaPack+Mayhem, there is an awesome introductory video by Tech Minds available:
Frequently Asked Questions
This repository expands upon the previous work by many people and aims to constantly add new features, bugfixes and generate documentation to make further development easier. Collaboration is always welcomed and appreciated.
Does it work on H1/H2 PortaPack?
Yes, both devices are the same. The one I am using to test all changes is this PortaPack H2+HackRF+battery, which is a kit that includes everything you need. Sadly, the people making the H2 never made the updated schematics available, which is not ideal (and goes against the terms of the license).
To support the people behind the hardware, please buy a genuine HackRF and PortaPack.
Where is the latest firmware?
The current stable release is on the 
Is this the newest firmware for my PortaPack?
Most probably: YES. If you find new features somewhere else, please suggest them.
Which one is actually the newest?
There is a lot of confusion of which is the latest version because no old version used any actual "version number". Additionally, since the files were distributed on facebook groups, github issue links and similar temporal sources, then there was no central location for them.
This fork (Mayhem) uses major.minor.release semantic versioning, so you can always compare your current version with the latest from Releases.
What about Havoc/GridRF/jamesshao8/jboone's?
- jboone's PortaPack: the vanilla experience
- Havoc: It was the most popular fork of jboone's PortaPack, currrently, it is not being maintained nor updated
- jamesshao8: He keeps his own version of the fork, while not attached as a fork to anything
- GridRF: They sell PortaPack clones with their own firmware based on a old version, which has no sourcecode available
How can I collaborate
You can write documentation, fix bugs and answer issues or add new functionality. Please check the following guide with details.
Consider that the hardware and firmware has been created and maintain by a lot of people, so always try colaborating your time and effort first. For coding related questions, if something does not fit as an issue, please join our Channel in Discord.
As a last option, if you want to send money directly to me for getting more boards, antennas and such:
What if I need help?
First, check the documentation. If you find a bug or you think the problem is related to the current repository, please open an issue.
You can reach the official community in Facebook.
What if I find incongruencies, or grammatical errors in the text?
If is on the Wiki, you can modify it directly. If is on files of the repository, you can send corrections as pull requests. As a last resource, open an issue.