Osmo-Tetra Data Interpretation Bug
Budget: €8 – €30 EUR
I have forked Osmo-Tetra and everything compiles cleanly, yet one key function no longer behaves: after the demodulator passes its bitstream, the data interpretation layer spits out empty frames instead of decoded messages. The RF front-end, signal reception and bit-level decoding appear correct—IQ recording played through the stock build decodes perfectly—so the fault is somewhere in my custom tweaks to the interpretation code path.
Your task is to pinpoint and patch this functionality problem. The codebase is mostly C with a smattering of C++ and uses GNU Radio plus libosmocore. I will grant you access to the private repo and a recorded TETRA capture that demonstrates the failure. A successful hand-off means:
• Explain the root cause in brief comments or a short write-up.
• Provide the corrected source (or a clean patch) that restores proper message output.
• Show a test run—either logs or a screen capture—proving frames are now interpreted.
If you already speak Osmo-Tetra internals, burst decoding, and crc16 checks, this should be a quick win. Let me know your turnaround time and any clarifications you need.
https://github.com/cropinghigh/sdrpp-tetra-demodulator
Your task is to pinpoint and patch this functionality problem. The codebase is mostly C with a smattering of C++ and uses GNU Radio plus libosmocore. I will grant you access to the private repo and a recorded TETRA capture that demonstrates the failure. A successful hand-off means:
• Explain the root cause in brief comments or a short write-up.
• Provide the corrected source (or a clean patch) that restores proper message output.
• Show a test run—either logs or a screen capture—proving frames are now interpreted.
If you already speak Osmo-Tetra internals, burst decoding, and crc16 checks, this should be a quick win. Let me know your turnaround time and any clarifications you need.
https://github.com/cropinghigh/sdrpp-tetra-demodulator