Pre-release for testing. Version stays 10.5; this is build 481.
The Airspy controls were doing nothing — and it was not the driver
Your last message is what found it: "LNA and Mixer AGC disabled then the sliders moved and no change to the signals at all." With both AGCs off and the stages written, something has to change. Nothing did — because nothing was ever written.
With the radio plugged into the phone, every control on the Airspy panel was sent through a method that only exists for network receivers. There is no network connection when the radio is local, so the call was silently discarded. Gain mode, LNA, mixer, VGA, both AGCs, bias-T and packing: all of them, every time, with no error anywhere. Behind it there was no bridge to the engine at all — the driver was fine and was never being told anything.
That is why 480 changed nothing for you, and why reinstalling could not help. Apologies — you reported it three times and it took the AGC detail to make it unmistakable.
Fixed end to end: the engine entry point, the bridge, and one sender in the app that goes to the server for a remote receiver and to the engine for a local one — written once, so a future control cannot be wired to only one of the two.
Please retest: gain mode and the three stages, bias-T, and USB packing. These should now respond immediately.
Also fixed
- "Airspy AIRSPY Controls" — the board already calls itself AIRSPY and we were prefixing our own name on top. It now reads "Airspy Mini".
- The tuner's IF filter is programmed on every open. On the RTL dongles it was never written at all unless someone chose a width by hand, so the radio ran on whatever the library's init left behind. This does not affect the Airspy, which has no variable IF filter, but it is in this build.
Still outstanding
The frequency-on-resume fault you reported (resumes on a station that should be clear, sounds like noise, tuning away and back fixes it). Build 480 should have addressed it and by your account has not, so it is a different path from the one I fixed. It would help to know whether that happens when you switch back to the app while it is still running, or after the app has been closed and reopened — those are two different code paths and only one of them re-opens the radio.