06651dc97c
* BMP initial * Add vscode debug configuration as a template (#2109) * usb serial debug interface & usb serial async msg (#2111) * add serial_debug * not use OSS * add path print * add string print and vec * clean up * clean up * format * add an async blocking bool * add an async blocking bool - comment * protect the unexpected tx * naming * remove demo code * fix bottom-up format, and add auto extend, .. * bmp write * Minor additions * Minor * overwrite on create * Tmp * Basic view - WIP * debug * add literal str print in asyncmsg (#2113) * add literal str print in asyncmsg * remove debug things * accept suggestion per gull * fix documentary * Fix bug (#2114) * Disable Back button during Touch Calibration (#2115) * ADS1100 (#2116) * WIP * WIP * WIP * Corrected name * WIP * WIP * WIP * WIP * Added new calc * WIP * WIP * WIP * WIP * WIP * WIP * Added debug serial lines * WIP * Fixed issue * Fixed calculation issue * Added voltage to performance DFU menu * Added padding function and added voltage to perf menu * Clean up * Refactor * Fixed linting * Hides voltage if PP does not conatin IC * WIP showing battery % * made the percentage a int * Added % to header * Removed test UI * Removed comment * Added fix for precision too large * Added fix for precision too large * Linting * widget * auto zoom * remove debug * move in screen * fix math * remove test code * fix * fix compiler warning * BMP File viewer * Full screen * bg instead of noice * add comment * Handle some not supported formats. --------- Co-authored-by: E.T <tamas@eisenberger.hu> Co-authored-by: sommermorgentraum <24917424+zxkmm@users.noreply.github.com> Co-authored-by: Mark Thompson <129641948+NotherNgineer@users.noreply.github.com> Co-authored-by: jLynx <admin@jlynx.net> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| docs | ||
| firmware | ||
| flashing | ||
| hackrf@f5dd48a5bc | ||
| hackrf-portapack | ||
| hardware | ||
| sdcard | ||
| .clang-format | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| LICENSE | ||
| LICENSE.GPL-2.0-or-later | ||
| README.md | ||
| docker-compose-nogit.yml | ||
| docker-compose.yml | ||
| dockerfile | ||
| dockerfile-alpine | ||
| dockerfile-nogit | ||
| dockerfile-nogit-alpine | ||
| dockerfile-nogit-arm | ||
| format-code.sh | ||
README.md
[!WARNING] IF YOU'VE PAID FOR MAYHEM OR ANY PREPACKAGED PACKAGES, YOU'RE BEING SCAMMED. The only legitimate link leading to our repositories is the organization portapack-mayhem.
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+HackRF+battery (clone) with a custom 3d printed case
What is this?
If you are new to HackRF+PortaPack+Mayhem, check these:
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.
What to buy?
✔️ A recommended one is this PortaPack H2, that includes everything you need with the plastic case "inspired" on this.
✔️ Our friends at OpenSourceSDRLab give away five units every three months in our discord (check the badge on top) of their PortaPack H2, you can support them too by ordering.
⚠️ Be cautious , ask the seller about compatibility with the latest releases. Look out for the description of the item, if they provide the firmware files for an older version or they have custom setup instructions, this means it might be NOT compatible, for example:
⚠️ If it looks too different, this might mean that they are using their own recipe, check the different models in our wiki. For example all the H3 and clones of that version use their own version of the firmware. They do not contribute the changes back and eventually you will be left with a device that nobody maintains:
Where is the latest version?
The current stable release is on the 
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 collaborating your time and effort first. For coding related questions, if something does not fit as an issue, please join our Discord by clicking the chat badge on top.
To support the people behind the hardware, please buy a genuine HackRF and PortaPack.
What if I really want something specific?
If what you need can be relevant in general, you can request a feature.
You can create a bounty and invite people to your own bounty. This will incentivize coders to work on a new feature, solving a bug or even writting documentation. Start a bounty by creating or choosing an existing issue. Then, go to Bountysource and post a bounty using the link to that specific issue.
Promote your bounty over our Discord by clicking the chat badge on top.
Bountysource has not been reliable lately, so until this changes, please DO NOT post a bounty there. Go to our Discord by clicking the chat badge on top and discuss there.
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, and our Discord by clicking the chat badge on top.