No, I started with a fresh install of the PiAware 8.2 Image and really just did what I said at the very beginning.
My idea about the possible check-point is originated from the above citation.
As far my memory serves well, Nooelec V2 has RTL chip inside. This is why I thought that you can check your mini on your pi3.
(lsusb) âdetection attempt onlyâ
Try installing this on pi4
http://ftp.us.debian.org/debian/pool/main/a/airspy-host/libairspy-dev_1.0.9-4_armhf.deb
Good idea! I will check this tomorrow! I forgot that both have the same chip inside. 
Tried this and needed another dependency first â libairspy0
Changed nothing. The AirSpy mini is not listed with âlsusbâ.
1 Like
Hereâs the one you need:
http://ftp.de.debian.org/debian/pool/main/a/airspy-host/libairspy0_1.0.9-3_arm64.deb
or
sudo apt-get update
sudo apt-get install libairspy0
May requires also: libc6_2.28-10+deb10u1_arm64.deb
and libusb-1.0-0_1.0.22-2_arm64.deb
They are available also via (GUI) Add / Remove Software menu
Search for âlibairspyâ âlibusbâ and so onâŚ
Sure, did that before and installed the dependencies. 
Nothing changed. The AirSpy mini ist not listed using lsusb.
Then you will need to test the Airspy on a different device to verify if it is detected at all.
1 Like
Okay.
Try to check and fix broken packages.
sudo apt --fix-missing update
sudo apt update
sudo apt install -f
#see the output and remove the unnecessary packages
sudo apt autoremove -y
#dependency tree will be rebuilt
#if any packages need to be upgraded, do it
sudo apt upgrade -y
#still having the problem, do some cleanups
sudo rm -rf /var/lib/apt/lists/*
sudo rm /var/cache/apt/*.bin
sudo apt clean
Restart pi4 (lsusb again)
Try also the other USB connectors (though the controller chip might be the same)
- Check the usb cable if it is in use
Check mini on your pi3 or a Win machine too (as Foxhunter says)
After making sure that mini works on other machines but not on your pi4, try to reinstall OS on that. Pick an image from raspberry site (Iâd stay with a 32bit âdesktopâ one, but the choice is yours)
1 Like
Yes, I think so. I will try to get some data using SDR# under Windows soon.
Done that, but still not recognized by the rPi4.
Tried all ports (2x USB2.0 & 2x USB3.1 Ports)
Also tried direct connection without the 15cm USB3.1 extension cable.
The rPi3 is not booting with the AirSpy mini.
I already tried the official 32bit raspbian lite SD card image (see previous posts).
I guess the stick is broken, but will verify on a Windows maschine soon.
Maybe a bit of a long shot but make sure the switch on the Airspy is in the correct position and that it is not in DFU/Recovery mode. The switch should be towards the SMA connector for normal operation.
1 Like
then you have a different problem. The Airspy should never prevent the device from booting.
What, if you connect the Airspy after the Raspberry is running? It should work with Hotplug and been detected after a while.
To me it all sounds like the Airspy is some sort of broken
I checked this! Switch is in correct position.
Funny thing is, that it is listed under lsusb in DFU mode.
I donât know how it affects the warranty, maybe it would be worth trying a firmware update. (overwriting the current one) âŚor simply replace it in the store with another one, if the original one doesnât work anywhere else.
Yes, that is my plan, once I get a Windows Notebook from a friend.
For getting the firmware updated, the device need to be recognized by the operating system. This is not yet given as far as it can be read from his last posts.
A Linux Notebook would be even easier
In DFU mode it works.
see:
This was under Kali Linux. In ânormalâ mode Kali Linux also does not see the AirSpy mini, so I try to update the firmware using a windows maschine very soon.
Yeah.
There is no other solution. As far as I know, firmware update is still not supported on linux.
Reason? Who knowsâŚ
Yes, I will get back once I managed to update the firmware on a windows maschine.