Bluetooth Mouse lag

I had this problem using a targus Bluetooth keyboard with touch pad, and a dell Bluetooth mouse. Enabling Bluetooth Collaboration was the resolution for me, but only after first disabling the touch pad on my keyboard.

I found the setting for Bluetooth Collaboration in the properties for the network adapter. Commonly, Bluetooth is included with the wireless chips. So to resolve:

Open Network Connections (In windows 8, select the windows key and X , then select network connnections

Select your WiFi adapter (not your Bluetooth adapter), right click and select properties.

In the WiFi properties window, select Configure button.

In the <your network adapter name> Properties window, click on Advanced property sheet(tab).

In the Property Option list, scroll until you find Bluetooth Collaboration.

In the Value option list, select On (instead of auto or Off).

click OK, and close all open windows.

Test.

it looks like this solution doesn't apply to the Surface's wifi-bluetooth chip / driver combination.

This thread doesn't discuss general wifi-bluetooth issues, but only Surface-related.

Changing the state of Packet Coalescing seems to solve the problem temporarily (turn it on if it's off, or turn it off if it's on). I have 3 BT devices connected to my Surface Pro and the mouse would lag horribly whenever anything was playing through the earphones. It stopped lagging once I changed the Packet Coalescing option's state. However, it came back after I did something to trigger it, which I have yet to determine. Ugh.

Do we already know if the Surface Pro 3 will have a different chip set? Also there was a post from MS a few weeks ago in this conversation saying the MS is actively working on a solution...

Please correct me if I am wrong but this issue was already known with the Surface Pro 1 and MS used the same buggy Marvell chip with the Surface Pro 2 because they don't care about user feedback AND they don't use their own products...

Also don't forget that in the case of the Surface the Soft- and the Hardware is from the same vendor = MS!

To the Workarounds:

1. switching to 5GHz means extra costs and it's not possible within any (business) environment.
2. using a USB Wifi (or Bluetooth Dongle) blocks the ONLY ONE available USB-Port of the Surface!

You are partly right. The issue was found at the Pro1. However, the cause wasnt. That came later. Would you stop production of a 100 million machines on a hunch? Thats what it was. A hunch.

It is still a business, and a partnership between Marvel and MS. There is no difference on this partnership, and the partnership between Apple and Marvel - and yes, that is also the same software and hardware vendor. That doesnt make any difference. This is a Marvel issue, and the fix (if one is possible) have to come through them.

The workarounds.

1. You are right. It does cost extra money, but it also gives you a lot more options besides this for the Surface. I am running 5ghz at home, and I get much higher internet speed, because there is no interference from neighbors or anything like that. So there are a lot of bonuses to this.
2. True, but you asked for options. The solution to this, HAS to come from Marvel. Thats the problem. It is their hardware, and their firmware. The 2 workarounds are the only 2 known to work. If you want a solution, talk to Marvel.

Talking to newspapers and so on, might help. I have no problem in that. It might actually get Marvel to find a solution. However, blaming this on MS, when it clearly is not an MS problem, will not lead to anything. Thats my point.

Given the fact that MS keeps silent on this problem and its sister issue (i.e. wifi slowdowns when bluetooth is under high usage), I'm going to send a letter to various IT magazine and webzine editors (e.g. wired, cnet, techradar, arstechnica, techcrunch, computerworld, itworld) to highlight this shameful question.

Any other recipients to suggest?

You do realize that this is not an MS problem? Apple, HP and Lenova  have the same issue. So when you write that letter, make sure to get the facts correct.

It is a problem. No doubt, but the problem is not a software issue. The problem is a conflict in the hardware. There is only 2 work arounds. Get a 5ghz router, or use a usb wifi. It is by the way, the same solutions Apple found...

Please correct me if I am wrong but this issue was already known with the Surface Pro 1 and MS used the same buggy Marvell chip with the Surface Pro 2 because they don't care about user feedback AND they don't use their own products...

Also don't forget that in the case of the Surface the Soft- and the Hardware is from the same vendor = MS!

To the Workarounds:

1. switching to 5GHz means extra costs and it's not possible within any (business) environment.
2. using a USB Wifi (or Bluetooth Dongle) blocks the ONLY ONE available USB-Port of the Surface!

Given the fact that MS keeps silent on this problem and its sister issue (i.e. wifi slowdowns when bluetooth is under high usage), I'm going to send a letter to various IT magazine and webzine editors (e.g. wired, cnet, techradar, arstechnica, techcrunch, computerworld, itworld) to highlight this shameful question.

Any other recipients to suggest?

You do realize that this is not an MS problem? Apple, HP and Lenova  have the same issue. So when you write that letter, make sure to get the facts correct.

It is a problem. No doubt, but the problem is not a software issue. The problem is a conflict in the hardware. There is only 2 work arounds. Get a 5ghz router, or use a usb wifi. It is by the way, the same solutions Apple found...