Killer 1535 WLAN/BT Problems & Solutions

@Killer_Networking Is there any known bugs with v1803.619? I think BT is not working properly especially BT Audio. I see that, removal of paired devices such as headphones re-appear instantly as Paired w/o even pairing! On Linux, I just checked, for a minute or two it was connecting or showing incorrect device being connected as Audio Source/Sink when sound was played through my headphone. I rebooted again on Linux, removed all existing paired devices and voila, everything is working on Linux even BT audio. On Windows 10, BT audio doesn't work after updating to 619 and now downgraded to build 590 and still have issues. Any ideas on how to cleanup existing BT entries for clean reset like experience?

 

Unfortunately, this is an issue with Windows, not any specific Bluetooth adapter, and it has been going on for a lot longer than 1803. You can find a very long Microsoft Answers thread on the subject here - https://answers.microsoft.com/en-us...ndows-10/ea6da83d-583e-4b80-8714-367510879f07.

The Bluetooth adapter and device driver do nothing but provide connectivity. The operating system and the device drivers for each Bluetooth device are responsible for everything else.

I have yet to find any real fix to the many Bluetooth issues with Windows 10. I can only suggest updating to 1809 to see if that resolves the problem.

-- Anthony with Killer Networking

 

Thanks for the reply Anthony. I'll try the steps mentioned in that thread!
I want to know if there's any workaround from Killer dev team to try?
I refrained from updating to v1809 because it brought only few things to the table and 99% of the time I have seen the problem it caused on perfectly working hardwares.
Can you give any insight whether https://www.ath-drivers.eu/ is reputed or not? I installed the bare bone driver on my old laptops with atheros BT drivers and after 3 years I finally have a BT audio working w/o running W7 driver.

 

I don't normally use many BT devices but since my Surface Pro 5 tablet(Marvell AVASTAR Wireless AC) has only one USB port I use a MS BT Surface mouse and Samsung BT Level On headphones.

Both BT devices work well with the Surface Pro.(Marvell BT)and have yet needed to be paired again due to a loss of pairing or loss of sound from the Samsung

A set of Beoplay H5 BT earbuds had a great many pairing issues so they are not usable with the Surface Pro.

Using a MS BT mouse with an MSI GS60 notebook(Killer 1550) often required manually unpairing and pairing after losing connectivity so I use a USB MS mobile mouse without any issues.(Intel BT)
Intel BT driver 20.120.0.3

My Android phones have headphone jacks so I don't deal with BT sound issues.

 

@Killer_Networking and @WhatsThePoint
BT isn't working on any Qualcomm based cards. They just work on Linux 18 LTS w/o any issues.

 

Unfortunately, we do not have any workaround as we have not been able to duplicate the issues. I wish I had a better answer.

The only reason I suggested updating to 1809 is because I have had a few users tell me that this resolved the issue for them. Reinstalling Windows altogether also tends to resolve this issue, although nobody likes that answer, myself included.

Regarding https://www.ath-drivers.eu/, I really can't say. I haven't heard anything specifically bad about them, and I know people do use the drivers from there. However, I have no idea where that website gets those drivers, or how thoroughly they are tested, or which devices each driver is actually meant to support, as opposed to just matching hardware IDs, which doesn't always work as you might expect. Still, it's certainly worth trying, if you're willing to take the risk. You can always set a system restore point, test, and then roll back. If you do find a driver that solves this issue, please let me know which version (or just send me the link) so that I can suggest it to other users with this issue. I'm always looking for solutions.



-- Anthony with Killer Networking

 

No backup 100% risk and drivers are near identical copies just like MSFT update catalog. A bare metal inf installations only.
Can you please provide me the details or any forums wherein v1809 fixed BT issues?
EDIT: Found them. There're loads of threads in reddit.

 

It's honestly hit or miss. It's just a possible solution, not necessarily the solution. I have suggested it to users, and some have said that updating to 1809 solved the issue, while others have said that it did not. However, at this point, 1809 is pretty stable and has had a big cumulative update as of late January, so it's as safe as anything Windows 10, and it's not like you won't be forced into the update very soon anyway.

 

Anyway, thanks for the heads up. I'll wait for 19H1. I think they changed A2DP and entire BT stack for v1809.

 

The April 2019 Windows 10 update for everyone is said to be what is known today as Windows Insider 19H1(Redstone 6) with build 18346 released yesterday to Insiders on the Fast Ring.

Listed as one of the fixes in this build....We fixed an issue which caused the Bluetooth Hands-Free audio driver to hang.

Whether this will fix your issue is not known.

As I alluded to in my previous post is that all problems may not be OS related but related to the BT devices themselves.

 

On the machines with v1803 installed, BT audio never worked after 441 update to fix A2DP BSOD.

 

The April update will be v1903 that is currently under development as 19H1 but there is a pause in new Insider releases due to gaming issues related to 3rd party anti cheating software.
BT has been around many years but it still has major issues.
On my Surface Pro 5 tablet BT works very good with the 2 BT devices I use with it.
Where's all the BT 5.0 devices?
BT 5.0 has been out for a year!

Use the Microsoft Feedback Hub to report your issues.

 

Feedback app is the very first thing I uninstalled.

 

I don't think there is any real push for BT device manufacturers to put out 5.0 devices. Most people aren't going to replace their 4.x devices with 5.0 just because it's a bigger number, and the vast majority of people don't know what the numbers mean, so it's more profitable to keep making the 4.x devices for now.

Audio won't see much of an improvement if any. The higher available bandwidth should increase audio quality, but most Bluetooth devices don't make use of the bandwidth that was already available with 4.2.

Most people don't use their Bluetooth devices far enough away from the host devices for the increase in range to matter and, even then, since Bluetooth still operates on the incredibly oversaturated 2.4 GHz range, people that have issues likely won't see an improvement with 5.0.

Transfer speeds are still, at maximum. 2 Mbps with Windows, which is painfully slow by today's standards and file sizes.

The most significant improvement is the ability to trade off range and quality (or vice-versa), but that's not very useful for most end users.

Like 4.2, 5.0 is mostly an Internet-of-Things feature set more than an end-user feature.

I think we're more likely to see it slowly creep in as entirely new devices and drivers are created, where it doesn't make sense to use an older format, but it won't cost extra to go to 5.0.

Keep in mind that Bluetooth is weird in that a whole number is a hardware revision while a decimal number is a software revision. This means that Bluetooth 5.0 devices will also be Bluetooth 5.x devices, with x being whatever future improvements to the standard can be had without changing the hardware, so long as a new driver is coded, and the host system supports the new software standard. I'm hopeful that 5.1 will have more meaningful features and that Microsoft will, therefore, adopt it early.

-- Anthony with Killer Networking

 

If I'm in the market for a new BT device I'd surely opt for the newest tech I could find from a company that has produced the best previous generation devices.

My WiFi cards have BT 5.0 support so why not look forward and not backward.

I'll always buy the latest over last years models.

I don't care what's around the corner but if I'm buying today I want the newest model Mainboard,CPU,Graphics,SSD,Networking etc that will run my software a bit better and efficiently than those I could have bought yesterday.

 

Absolutely, I do the same, as long as it is within my price range. Well, with the possible exception of GPUs since the previous generation is almost always better, dollar to horsepower. I was simply explaining why Bluetooth 5.0 devices are still rare, and will probably remain rare for a while.

-- Anthony with Killer Networking

 

I am completely opposite and I always prefer old release to avoid early adopter tax and possible GP testing as a Service(GpaaS)

 

@Killer_Networking Installed 19H1 and BT Audio and everything works.
BT pairing takes a little long time than Linux using the latest driver from Killer website.
BT Audio, WSAH(Windows Spatial audio for headphones), swift pairing works. No regression for time being. Windows update is disabled. UI is horrible than Win 95 High Contrast White Theme. Everything is just very bright.
Killer 1535 BT and Wifi along with KCC just works on Win 10 19H1 18346.

 

Nice! I hope it sticks when that hits release. I would absolutely love to be able to tell everyone with these weird Bluetooth issues to simply update Windows.

-- Anthony with Killer Networking

 

I hope this time they don't screw up. I have disabled updated for time being.