Buggy Bluetooth Connection with Intel Wireless-AC 9560 on Ubuntu 19.10

I got it working on 16.04 on this machine following this guide but it had some problems with the links so here's exactly what I did...

(first you may want to navigate to an empty folder because we'll do some downloading & compilation & conversions. Files will be all over the place)

mkdir temporary
cd ./temporary

now we've created a folder and navigated to it we can proceed...

First, download this and place it in your empty folder.

The guide's very long but what's good about it is that it should work if you just follow it sequentially. If you don't understand what's happening just copy and paste the lines one after the other (or ask in a comment)

install the driver:

tar xf vfs495.tar
cd vfs495
sudo apt install alien
sudo alien Validity-Sensor-Setup-4.5-118.00.x86_64.rpm
sudo dpkg -i validity-sensor-setup_4.5-119_amd64.deb

Now the broken links part. Here are the links that should work:

sudo apt install libssl1.0.0
ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libssl.so.0.9.8
sudo apt-get install libcrypto++-dev
ln -s /usr/lib/libcrypto++.so.9 /usr/lib/libcrypto.so.0.9.8

Then just proceed. Install libfprint

mkdir libfprint
cd libfprint
rpm2cpio ../libfprint-0.0.6-18.20.1.src.rpm | cpio -i --make-directories
tar xf libfprint-0.0.6.tar.bz2
cp ../libfprint-validity.patch ./libfprint-validity.patch
cd libfprint-0.0.6/
patch -p1 < ../libfprint-validity.patch
sudo apt-get install libusb-dev libcrypto++-dev libssl-dev libglib2.0-dev libmagickcore-dev checkinstall
./configure --prefix=/usr
make
sudo checkinstall -install=no make install
sudo dpkg -i libfprint_0.0.6-1_amd64.deb

Install fprint_demo

cd ../..
sudo apt-get install libgtk2.0-dev
tar xf fprint_demo-0.4.tar.bz2
cd fprint_demo-0.4
./configure --prefix=/usr
make
sudo checkinstall -install=no make install
sudo dpkg -i fprint-demo_0.4-1_amd64.deb

At this point, we can start to register our fingers.

sudo /etc/init.d/vcsFPServiceDaemon start
sudo fprint_demo

...after you enroll your finger you can train in the "identify" tab. It'll display your fingerprint! It's so much fun :D sometimes I just go there and keep swiping XD

And just a side-note, don't take screenshots of your finger and share it around unless of course, you know what you're doing. Your fingerprint is valuable. Better keep it for your eyes only.

...anyway, continue. Install pam_fprint

cd ..
tar xf pam_fprint-0.2.tar.bz2
cd pam_fprint-0.2/
sudo apt-get install libpam-dev
./configure --prefix=/usr
make
sudo checkinstall -install=no make install
sudo dpkg -i pam-fprint_0.2-1_amd64.deb

Now we can start setting up fingerprint authentication. I recommend you stop here because I've been using it for a while and there are several issues with it. So far your driver is working and that's fine. You can try it for authentication and revert it if you want, but it's not robust for daily use.

Anyway, we need to edit the /etc/pam.d/common-auth file. Be careful with this file!!. If you mess it up you'd have to fix it from recovery mode.

This would make ubuntu ask you for your fingerprint or your password to grant you root access and also for login. So you can still use your password to login

sudo nano /etc/pam.d/common-auth

We need to add the lines:

# fingerprint authentication through fprintd
auth    sufficient                      pam_fprint.so

and modify the line that has pam_unix.so nullok_secure try_first_pass to make it sufficient, like this:

auth    sufficient      pam_unix.so nullok_secure try_first_pass

So finally here's what my file looks like.

Note that the behavior will depend on where you'll place the lines. If you place them above (the "Primary" block) part it'll first ask you for your fingerprint, then your password and vice-versa.

I hope someone can clarify or give a good pointer about how this file exactly works.

Finally...

cd ..
sudo cp vcsFPServiceDaemon /etc/init.d/
sudo update-rc.d vcsFPServiceDaemon defaults

and things should be working.

Ok I had the exact same problem. If you look at the error messages, it seems like there is no file called brcmfmac43602-pcie.txt. All you need to do is create that file manually by running the following command:

sudo touch brcmfmac43602-pcie.txt

in the directory /lib/firmware/brcm/ and the edit it by writing random letters (it doesn't matter what you write). This fools the software and bluetooth works perfectly after doing this. More on this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693521