Bluetooth Mouse lag

Thanks for proposing this solution, I'm slightly embarrassed that I didn't think of it.  There is close to zero chance that Microsoft will remedy this problem at this point, so it's far more productive to just solve the problem ourselves rather than beg them to.  If MS is unable to fix the problem due to hardware issues, they should be shipping us Bluetooth dongles.  This, among other issues will certainly factor into my decision to buy MS products in the future.

Cheap adapter with positive reviews:

http://www.newegg.com/Product/Product.aspx?Item=9SIA1PU0NU0472

It is a Surface thread. You are right. And you are right in saying that MS is responsible for what they sell. just as anybody else are. 

But on the other hand, since this have been proven to be a Marvell issue, maybe the thread should be moved, since it is clearly no longer a Surface issue... :)

But than you are missing the point. Its not just the Surface that is has this problem. Its not a MS issue here. It is Marvel.

My point here is, that yes the chip is in the Surface, but its not ONLY in the Surface. It is in other devices as well. So a class action here, would be pointless in my book. Its not an MS issue.

MS is responsible for what they sell, and this is a Surface thread.

sure an external bluetooth dongle works

It's been already acknowledged that the problem is in the Marvel chip.

MS and Marvel might find some clever trick at driver level to minimize the issue, or we shall start a class action against MS: this kind of performance is unacceptable on a high-end machine such as the Surface Pro.

But than you are missing the point. Its not just the Surface that is has this problem. Its not a MS issue here. It is Marvel.

Fixing a hardware issue, using software, is close to impossible. Especially when it comes to interference. Years back, you had the same issue on radio. If you wanted to listen to a specific radio station, but somebody close to you, had the same channel, you wouldnt be able to listen to the one you wanted. My point here is, that yes the chip is in the Surface, but its not ONLY in the Surface. It is in other devices as well. So a class action here, would be pointless in my book. Its not an MS issue.

Just to confirm. That solution works?

As I said in my post before. I know it isnt a solution, but it is a work around for now. 

If that works, it also means that the problem is the Marvel device. That it uses the same antenna on 2,4ghz. To solve this with software, is not easy when the hardware is wired that way...

If you look at the link from page 3, it shows the connection on this chip/antenna.

http://www.marvell.com/wireless/assets/8787.pdf

It also means that the way I see it, there are only 2 options if you dont want to use the USB. Find a channel/frequency on your router that is not used by a device, or change router to a 5ghz. :)

sure an external bluetooth dongle works

It's been already acknowledged that the problem is in the Marvel chip.

MS and Marvel might find some clever trick at driver level to minimize the issue, or we shall start a class action against MS: this kind of performance is unacceptable on a high-end machine such as the Surface Pro.