Surface Go (1) and trackpad stops after awakening from sleep

:pushpin:Question Description

Have you searched the community for related issues?

  • No similar issues found.

Please describe the problem you’ve encountered in detail:

  • Description:

So I have FideOS v20 for the Surface Go (1) installed on my Surface Go (1) 8/128 model. It works amazingly well but I have discovered a problem…

If I close the lid and let the machine go to Sleep, when it awakens the trackpad is frequently non-functional, but not always.

The touchscreen still works. The keyboard still works. But not the trackpad…sometimes.

I can make it work again by disconnecting the typecover and reattaching it again, but this is an annoyance.

Anyone else seeing this? Anyone else come up with a fix?


:computer:System & Device Information

  • Hardware & System Configuration:

    • Processor:
    • Graphics Card(Please specify if there’s a discrete graphics card):
    • RAM:
    • FydeOS Version:
  • Relevant System Logs:

    • Open the Chromium browser and enter /var/log/messages to retrieve logs.
    • Log Details:

Note: If you’ve lost your FydeOS subscription, please refer to this FAQ for assistance.


1 Like

i did finds the solution of it and its work 100% !!

for soution:-

go to your fyde os setting > power > and apply the same setting as mentioned in the attached screenshot

So…the solution is to disable Sleep Mode? Am I understanding you correctly?

That doesn’t seem like “fixing the trackpad not waking up from sleep mode.” That seems like “Never allow the device to enter Sleep mode so the trackpad never get disabled, but your device will run out of battery power in just a few hours of sitting there, even with the keyboard closed against the screen.”

What am I missing here?

Hello, I’m using a surface go 2 and I’m having the same issue.

Did you manage to find a solution?

I’m using FydeOS “For you” version for my specific device.

HI, same problem here on surface go 1. it will work if detach and retach the keyboard again…

Yeah, but thats a workaround and not a fix…

I hope stuff like this gets fixed at least in the “For you” edition.