Bluetooth connections (Keyboard etc.) not working


  • Hi Nefarius! I am super exited about your software and I want to thank you for putting in your time and effort! It works great and my life is better because of it! 😄

    I am having trouble with my other bluetooth connections though. Some of these are important to me, and so I'm hoping that you might be able to help me. I am normally using a bluetooth keyboard that doesn't mess up my hands while typing , but after running the BthPS3 installation, following these superp guides (PlayStation(R) 3 Peripherals Unofficial Bluetooth Drivers (BthPS3)) and (BthPS3 Post-Setup Instructions), I am not able to connect my lovely keyboard anymore. When I try to connect any bluetooth device, windows just states that it couldn't connect, and it then suggests to turn on bluetooth (bluetooth is on though) or tend to the driver.

    In device manager the bluetooth device is showing a yellow triangle with an exclamation mark in it, and when I open the properties for the device, i get the following message under driver status:

    Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

    I tried uninstalling Vigem using the installer, then I tried uninstalling the bluetooth device itself in device manager, and in the end after letting windows reinstall the device, and after trying to install the original driver manually, the error persisted. I thought, well, maybe, if I can just attach a bluetooth dongle, it might be installed seperately, and then I would be able to keep both my keyboard and my PS3-controller functionalities 😄 , but I was not so lucky. It just added another bluetooth device with the exact same status.

    I tried reading through the Bluetooth Filter Driver for DS3-compatibility - research notes, and if I understood correctly, you made this version to exactly be able to run any bluetooth devices like keyboards along side with PS3-controllers right? Maybe I messed up something along the way?

    I used the following for installing the software:
    BthPS3 Bluetooth Drivers_v1.2.1.exe
    ViGEmBus_Setup_1.16.116.exe
    plus shibari and fireshock - - for which I don't exactly know the versions.

    I am new to the universe of debugging and handling custom driver issues, so if I can provide some kind of log or other information to make my problem more clear, let me know and I'll get it asap 🙂


  • Hello!

    Fantastic summary, really appreciate it! Odd that it gives you troubles, could you please start by sharing screenshots of the troubled devices in device manager (you can directly paste images into the forum posts here), thanks.

    Cheers


  • Yes of course! Nice feature 🙂

    8ebd8cfa-abb9-4fdf-8e2e-d22d2028ea83-image.png

    Under bluetooth you can see the internal bluetooth device (Intel) and the bluetooth dongle (Generic Bluetooth Radio) 🙂


  • Properties for both devices in Device Manager:

    41a5396f-5d25-4659-bd1a-f3778f11c2b1-image.png

    2795669e-430c-4d89-b596-e2e52fa2e585-image.png


    Oh, and when none of my attempts helped me in getting my keyboard up and running, I just reinstalled your software as per the toturials mentioned earlier, to be able to use my PS3-Controller again 🙂

    Also, thank you for the fast response!


  • Bloody hell, that looks far from optimal 😜 follow this please and install BthPS3 again.


  • Just found some extra info. Maybe it is helpful.

    fc98fa9e-6a45-440b-8768-22f301cac603-image.png

    d466c5c7-3c63-45e1-9434-36a6b830d84b-image.png


  • Your suggestion worked! Thank you SO much!

    My keyboard works, and I can still use my controller when wired in by USB at least 😄
    I removed the lower filter as instructed,

    (The background is from the link you gave me, the lower part is my registry editor)

    81164049-2d92-41f3-8231-fd8f5539c3fb-image.png

    LowerFilters deleted:

    72013511-de95-48db-a010-794793e784d1-image.png

    then I downloaded the version of the bluetooth driver linked in the toturial (BthPS3 Bluetooth Drivers_v1.2.2.exe), which is one generation after the one I used initially I guess. Then I uninstalled and reinstalled, and I regained control of my bluetooth connection in the process.

    This is my Device Manager now 🙂

    df9396b6-1507-419a-afd8-ef65b1833191-image.png

    The dongle is still showing the error, but luckily I don't need it now 😄 The other error is new though.
    The controller doesn't seem to connect by bluetooth. Maybe this new error reveals the reason?


  • That's unfortunately still the same error, just different symptoms... Uninstall, reboot, install again, the whole setup isn't cleanly run and as long as those exclamation marks are there it will not function.


  • Note to self: change filter driver installation crap code 😈


  • I'm sorry to ask, but how do I actually uninstall completely?
    The drivers seem to stay in the system after uninstalling. I uninstalled vigem using the dedicated installer, and I uninstalled the drivers using the uninstall option in the driver installer (BthPS3 Bluetooth Drivers_v1.2.2.exe). Then, after rebooting like you suggested, I have functional bluetooth for my keyboard, but many of your drivers seem to stay behind after uninstalling. This is from my Device Manager after the uninstall and reboot:

    5f97f77b-2276-4f8e-9d83-c9bd685c56ed-image.png

    I also tried to right click and choose uninstall for every bluetooth related item in the Device Manager, then rebooting, and they reappeared again.

    The guide by Forceflow called 'Nuking ViGEm completely (thorough removal)' seems to end with a comment, saying that the installer should be used in stead of the guide, but I'm actually not completely sure if that was the intent? Should I follow the guide in stead? 🙂


  • ViGEm has nothing to do with Bluetooth whatsoever so removing that will not change anything. I've seen a few cases like yours before, I have an idea for the next release to fix it, I'd send you a test package if you're available.


  • And you can't uninstall every Bluetooth device by the method you mentioned, some will come back because they need a different way of uninstall which the setup would do if functioning correctly.