Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPD Win Mini: Rumble stops working after suspend #255

Open
justinweiss opened this issue Jan 18, 2025 · 2 comments
Open

GPD Win Mini: Rumble stops working after suspend #255

justinweiss opened this issue Jan 18, 2025 · 2 comments

Comments

@justinweiss
Copy link
Contributor

justinweiss commented Jan 18, 2025

After suspend and resume, the rumble stops working. Here are the inputplumber logs starting after resume:

Jan 18 13:25:37 chimeraos inputplumber[10421]: [2025-01-18T21:25:37Z INFO  inputplumber::input::manager] Found missing device, adding source device "evdev://event9" to existing composite device: "/org/shadowblip/InputPlumber/CompositeDevice0"
Jan 18 13:25:37 chimeraos inputplumber[10421]: [2025-01-18T21:25:37Z ERROR inputplumber::input::composite_device] Failed running device: "error occurred running device"
Jan 18 13:25:37 chimeraos inputplumber[10421]: [2025-01-18T21:25:37Z INFO  inputplumber::input::manager] Preparing for system resume
Jan 18 13:25:37 chimeraos inputplumber[10421]: [2025-01-18T21:25:37Z INFO  inputplumber::input::composite_device] Preparing for system resume for: /org/shadowblip/InputPlumber/CompositeDevice0
Jan 18 13:25:37 chimeraos inputplumber[10421]: [2025-01-18T21:25:37Z INFO  inputplumber::input::composite_device] Restoring target devices: ["touchpad", "xb360", "mouse", "keyboard"]
Jan 18 13:25:37 chimeraos inputplumber[10421]: [2025-01-18T21:25:37Z INFO  inputplumber::input::manager] Finished preparing for system resume
Jan 18 13:25:38 chimeraos inputplumber[10421]: [2025-01-18T21:25:38Z INFO  inputplumber::input::composite_device] Setting target devices: ["xb360", "keyboard", "mouse", "touchpad"]

This is using inputplumber v0.40.0.

I also see these warnings in the logs when a rumble effect should be happening, but they also seem to be present when the rumble is working, so I don't know if it's related:

Jan 18 13:26:45 chimeraos inputplumber[10421]: [2025-01-18T21:26:45Z INFO  inputplumber::input::composite_device] Setting target devices: ["xb360", "keyboard", "mouse", "touchpad"]
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::source::evdev::gamepad] Unable to find existing FF effect with id 0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from iio://iio:device0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from evdev://event5
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::source::evdev::gamepad] Unable to find existing FF effect with id 0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from iio://iio:device0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from evdev://event5
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::source::evdev::gamepad] Unable to find existing FF effect with id 0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from iio://iio:device0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from evdev://event5
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::source::evdev::gamepad] Unable to find existing FF effect with id 0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from iio://iio:device0
Jan 18 13:26:51 chimeraos inputplumber[10421]: [2025-01-18T21:26:51Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from evdev://event5
Jan 18 13:26:53 chimeraos inputplumber[10421]: [2025-01-18T21:26:53Z WARN  inputplumber::input::source::evdev::gamepad] Unable to find existing FF effect with id 0
Jan 18 13:26:53 chimeraos inputplumber[10421]: [2025-01-18T21:26:53Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from iio://iio:device0
Jan 18 13:26:53 chimeraos inputplumber[10421]: [2025-01-18T21:26:53Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from evdev://event5
Jan 18 13:26:53 chimeraos inputplumber[10421]: [2025-01-18T21:26:53Z WARN  inputplumber::input::source::evdev::gamepad] Unable to find existing FF effect with id 0
Jan 18 13:26:53 chimeraos inputplumber[10421]: [2025-01-18T21:26:53Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from iio://iio:device0
Jan 18 13:26:53 chimeraos inputplumber[10421]: [2025-01-18T21:26:53Z WARN  inputplumber::input::composite_device] Unable to find source effect id for effect 0 from evdev://event5
@pastaq
Copy link
Contributor

pastaq commented Feb 25, 2025

Is this still occuring in the latest version? In #284 we started refreshing all target devices after suspend.

@justinweiss
Copy link
Contributor Author

Yeah, this is still happening for me in version 0.48.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants