Bluetooth Mouse lag

Anonymous
2013-05-01T15:27:34+00:00

Recently bought the Surface Pro 128GB.

Having been annoyed by the temperament of the touchpad, I bought a Microsoft Bluetooth mouse.

What I've found is that, when copying data over a network, the bluetooth mouse begins to lag.

Using the touchpad/pen is unaffected.

Makes me wonder whether the Wireless NIC and Bluetooth Module are using the same bus and/or whether this is a known issue.

Surface | Surface Pro | USB-C

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

169 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-08-09T20:42:30+00:00

    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.

    I have a Surface Pro 3 (i7, 512GB).  After working fine for several hours using a Bluetooth keyboard (FILCO) and mouse (Microsoft Arc Touch), I started experience the lag issues described on this thread, both with the mouse and the keyboard (keys would occasionally stutter, as if the key-up signal wasn't received).  Turning Packing Coalescing off, as suggested above, has done the trick so far.  Hopefully it's stays fixed!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-08-10T16:57:58+00:00

    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.

    I have a Surface Pro 3 (i7, 512GB).  After working fine for several hours using a Bluetooth keyboard (FILCO) and mouse (Microsoft Arc Touch), I started experience the lag issues described on this thread, both with the mouse and the keyboard (keys would occasionally stutter, as if the key-up signal wasn't received).  Turning Packing Coalescing off, as suggested above, has done the trick so far.  Hopefully it's stays fixed!

    just tested your trick on my SP2, and sadly it doesn't have any effect on the mouse lag.

    I also tried rebooting, switching Bluetooth off/on before reporting.

    Test with this: start downloading a big file > 200Mb (e.g. download libreoffice). You'll see that after a while the mouse will lag to the point of being unusable, independently from the packet coalescing option's state.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-08-12T19:18:15+00:00

    Greetings Everyone,

    Seems a new firmware for the Surface Pro was pushed out earlier today. According to the changelog, some improvements regarding Bluetooth performance can be expected. Unfortunately, no update was released for the SP2.

    Does the issue still persist with the SP?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-08-12T19:57:04+00:00

    Well there's promise here. I just installed it and started downloading a file across my home network while connecting with my wedge mouse, and there was no noticeable lag. I will use the wedge more in the coming days, as well as pairing other Bluetooth devices at the same time, and report in again. But as a first impression it seems good. I certainly hope this has done it!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-08-13T11:54:34+00:00

    Hello verd02,

    Appreciate your input on this. Would be helpful to hear back from you once your further testings will have taken place.

    Has anyone else had the chance to tinker after yesterday's update?

    Was this answer helpful?

    0 comments