Legion Go S - Ghost Input
When installing on go S pressing legion space and legion space quick access buttons, they seem to trigger mouse mode or move the joysticks wildly which triggers the quick button combos (vol up/down, brightness etc) seems to mess with both sticks.
Firmware up to date
16 Replies
What does firmware up to date mean
You're the second person to have that I can't get it to happen
Sorry for the delay.
Meaning all of the bios/firmware updates were completed as I was running bazzite solely, not dual boot.
In the past on the Go 1 I know that it’s “best” to have windows on it still for the controller and bios updates etc.
So before going into bazz I ensured I had UTD bios etc
Legion space does not have the last firmware
Do you use legion l + y?
I had yes
No I mean do you want to be able to use it
Oh. Eh… doesn’t really matter to me because I personally find it can interfere with bazz/steam TDP sliders
Thought I mentioned in my post but when I was testing it in the joystick calib page where you can see the live inputs.
When I hit the legion buttons there, the sticks would do a quick hard direction to the outer edge either right or up etc.
My interim solution was to double press Legion L or R to get the menu to pop up, but then it would trigger vol up/down and get hard stuck. So if it triggered vol up it would constantly apply that and even when I hit vol down it would fight it and go back up.
Volume up down?
Ah yes
You can try updating the firmware
But it will disable legion l + y for now
I’ll give it a try over the weekend thanks antheas
Disabling l + y isn’t too bad of a compromise
Solution
You can update from bazzite, just need to enable fwupd for the go s
It's disabled for now because it's a bit buggy and because of that
I mean that's the only way to update
Once you update you can no longer downgrade though
Doesn’t seem the isflash.bin file is in the go s fwupd exe when updating through kde
Or any other .bin
Video of the problem @antheas
Enable testing in fwupd and update
I’m a dope.
I thought I did all updates but there was one more through KDE Discover.
Seems to have fixed it now in my initial testing
I will test thoroughly over the next bit then either mark as solved or update with any issues thanks @antheas