Bluetooth Mouse lag

I hope someone at Microsoft sees this post and escalates. There needs to be a firmware and/or driver update for the Marvell Avastar chipset.

Intermittently, any bluetooth mouse I use with my Surface lags and jumps around the screen so bad it's useless. Drivers and firmware are all up to date. I tried everything imaginable. Microsoft Surface support was extremely misinformed on basic computing concepts and they had no escalation process. Because of this issue and a few other quirks (Type cover randomly stops working, tethering to iPhone for internet via bluetooth drops randomly), I got the Surface Pro replaced under warranty. Unfortunately, the new unit had the same bluetooth issues. Video of the mouse lag here: http://www.youtube.com/watch?v=GsXsZNfv20U

Finally figured out how to make it stop and steps to reproduce. My iPhone was paired with Windows on the Surface, but most of the time it wasn't actively connected. They were simply aware of each other. The iPhone was listed under devices, but not connected. What I discovered is that if I disabled bluetooth on my iPhone, the mouse would immediately act normal and smooth. So even though they weren't actively connected, the fact that it was on caused interference with the Surface Marvell Avastar chipset. It's possible that the same remedy would work for others having bluetooth issues with other types of devices causing interference. Disable bluetooth or turn off your other accessories even if they're not connected and see if the lag clears up.

Note that I have been tethering my iPhone with several laptops via bluetooth for a few years now to get internet access when no WiFi was available. I chose bluetooth tethering over WiFi to save battery. With the Surface, it pairs, but the connection gets really flaky and drops after a few seconds to a few minutes. It's the only system I've ever had this problem with.

UPDATE: I upgraded to Windows 8.1 and did all the Microsoft updates. Bluetooth driver is now 14.69.24039.134. Same problems. I called Microsoft Store Sales and Support (1-877-696-7786) and pressed the option for getting a refund. After explaining the situation, the representative got it approved to get me a full refund on the Surface Pro and extended warranty. I later got an email saying that I wouldn't get a refund. I'm at a loss on what to do.

Having a similiar problem.

I´m using a Wedge Mouse and it works fine most of the time. I dont have any trouble when using WiFi.

I´m getting the lag as soon as I connect another bluetooth device e.g. a bluetooth headset (Arctic P311) or keyboard. The mouse begins to recognizable lag behind my input. The headset periodically won´t play sound and the microphone is not recording and the keyboard will just miss entered characters. Having only one of the devices connected at a time makes them work flawless.

Looks like the surface can´t handle two+ bluetooth devices at the same time which is really annoying for a mobile device.

All current updates/firmware for the Surface Pro are installed (not using 8.1 preview as I´m using the Surface for business) and I´m using the newest drivers for the mouse and headset.

Given the time since the first reports of this problem Microsoft seems clueless, unable or unwilling to fix this which is a real shame for an otherwise great piece of premium hardware.

I just installed Windows 8.1 Preview yesterday.  I have been using my Surface Pro 128 with a MS Wireless Notebook Presenter Mouse 8000 (Bluetooth) and the Microsoft Sculpt Mobile Keyboard (Bluetooth) since February and I did not have any lag issues.  When I installed 8.1 Preview, I noticed the lag using my mouse.  The keyboard would function just fine, not noticing any lag.  When I turn OFF my keyboard, the mouse lag disappears.  When I turn the keyboard back on, the lag on the mouse reappears.  Is there a conflict between the keyboard and mouse somewhere within the Bluetooth drivers?

Please help since I hate using the touch/type keyboard of the surface more than composing simple emails.  When I really work, I need a real keyboard and mouse that works.

This is a definite bug...hopefully MS fixes it