Share via

Logitech Bluetooth mouse not smooth.

Anonymous
2019-09-04T12:33:42+00:00

Hi!

On my Surface Laptop 2, when using a Logitech M590 Bluetooth mouse, the movement of the mouse is not smooth, but rather "jittery" or "jerky" when you move it. The mouse can be used in another mode with Logitechs own USB receiver, and when using this the mouse pointer movement is completely smooth.

Is this some problem that is known in general with Bluetooth mice, or with this particular model? Anyone has experienced something similar?

I have found the problem described in other places, and the solution people refer to is to turn off "Bluetooth Collaboration" on their Wifi driver properties, but this setting does not exist on the Surface Laptop 2:s Marvell driver.

BR

//Thomas

Surface | Surface Laptop | Display and screen

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 No comments

34 answers

Sort by: Most helpful
  1. Anonymous
    2019-12-05T04:18:14+00:00

    I fixed mine.  In device manager > Bluetooth > uninstall the Marvell Avastar Bluetooth Radio Adapter - make sure to check the box that asks to delete the software as well.  For good measure I also uninstall in device manager > Network Adapters >  Marvell Avastart Wireless AC Network Controller.  I then restarted my surface book.  I had to manually connect to the Wifi and type in my password again, but the mouse automatically reconnected and is smooth again.

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-09-04T14:35:06+00:00

    It's a problem with the Marvell Avastar bluetooth. I have a host of bluetooth peripherals and all of them are flakey on the Marvell Avastar. My Logitech unity stuff all works fine, and all the blue tooth stuff works seamlessly on my Thinkpad P50, but all I get with my Surface Studio 2 is intermittent problems or inferior performance. I have complained about this many times in many threads.

    6 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-12-17T22:56:59+00:00

    I fixed mine.  In device manager > Bluetooth > uninstall the Marvell Avastar Bluetooth Radio Adapter - make sure to check the box that asks to delete the software as well.  For good measure I also uninstall in device manager > Network Adapters >  Marvell Avastart Wireless AC Network Controller.  I then restarted my surface book.  I had to manually connect to the Wifi and type in my password again, but the mouse automatically reconnected and is smooth again.

    I did exactly like in the instruction given by AllenH427 and shut down the laptop and then turn it on. Then after I added one more step. Download Logitech Unifying Software and follow the instruction. After this finally my mouse paired and works smoothly... for now - touch wood!  

    Thanks Allen!

    5 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-09-04T13:38:33+00:00

    Hi!

    I'm experiencing the same issue with my Surface Laptop 2. I'm using a Logitech Mx Master mouse. When using the Unify dongle everything is smooth. When I switch to Bluetooth, the cursor is also "lagging".

    I guess there is an issue with Bluetooth drivers somewhere :(

    Hakan

    5 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-09-04T14:50:12+00:00

    The Marvell component was made bespoke for Microsoft Surface products, you wont find it on any other device. You would think that being Microsoft from the ground up that the performance would be superior, but no there have been so many complaints and the firmware fix never shows up, every update is the same .. blah blah .. wifi .. blah bluetooth .. blah blah Marvell Avastar broken.

    The support team are well aware of the issue, but nothing ever seems to fix the issues. Like you I worry that it is an intrinsic hardware issue, that Microsodft refuses to acknowledge for fear of mass returns class action etc.

    4 people found this answer helpful.
    0 comments No comments