Valkirie / HandheldCompanion

ControllerService
Other
1.16k stars 91 forks source link

Endless vibrate on startup #776

Closed thienntm closed 10 months ago

thienntm commented 1 year ago

Device manufacturer

Device model rog ally

Handheld Companinion Version 0.18.0.1b

Describe the bug Endless vibrate on startup, causing lag and high memory. Restart the ally does not do the job, still vibrating during restart process and stopped after logged in to windows and HC auto start again.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Setting'
  2. Toggle on 'Auto-start application'
  3. Toggle on 'Open application in background'
  4. Toggle on 'Close minimizes'
  5. Go to 'Controller'
  6. Toggle on 'Vibrate controller on connect'
  7. Restart ally and see error

Expected behavior Short vibrate and stop

Screenshots No screenshot

Logs file Will be add log later

CasperH2O commented 1 year ago

I have noticed the vibration taking slightly longer (2 seconds?) on the latest release with my ROG Ally, but I cannot reproduce your issue as is.

Are you starting/booting anything else? Do you use a kind of start up manager? You mention lag and high memory, how much memory is HC using?

thienntm commented 1 year ago

I have noticed the vibration taking slightly longer (2 seconds?) on the latest release with my ROG Ally, but I cannot reproduce your issue as is.

Are you starting/booting anything else? Do you use a kind of start up manager? You mention lag and high memory, how much memory is HC using?

Hi, I only set steam big picture mode at booting. At first, I thought it caused by steam, but after move from steam to playnite fullscreen mode, the issue still there. This morning, I tried to disable auto start at boot to start it manually. After reboot device and everything has started, I manual start HC but it continue endless vibrate, it seems that the error is not due to auto start.

Before, I was in double input problem, like this issue https://github.com/Valkirie/HandheldCompanion/issues/770. In hidhide config show 2 controller, then I tick the second one and the issue has fixed. I have no idea if the vibrate issue related to this

CasperH2O commented 1 year ago

@thienntm not a solution, but as a workaround you could untick the vibrate controller on connect option on the controller page.

thienntm commented 1 year ago

@thienntm not a solution, but as a workaround you could untick the vibrate controller on connect option on the controller page.

I forgot to say that the issue is endless vibrate and controller didn't work. I already tried your workaround a day ago. It didn't vibrate but still unable to use controller. I have to force close HC in task manager and start again and everything work fine.

Edited: I'll try to uninstall and re-install again. Will feedback later

thienntm commented 1 year ago

@thienntm not a solution, but as a workaround you could untick the vibrate controller on connect option on the controller page.

Hi @CasperH2O , after a few day test, I'm sure my issue relate to double input in hidhide like this https://github.com/Valkirie/HandheldCompanion/issues/770. I tick the second one to disable and restart device and boom, endless vibrate.

sr1canskhsia commented 1 year ago

Just updated HC to the latest version (0.18.0.3) and started having the same issue. Device is ASUS Rog Ally. Also tried a complete clean install of HC but the issue is still there.

Valkirie commented 1 year ago

Will look into it today

AHandheldFan commented 1 year ago

Same issue here on AokZoe A1 Pro. But in HID Hide if I have one of them ticked then the continuous vibration stops.

azodev commented 12 months ago

Same here on rog ally (with MCU 313 update)

NightHammer1000 commented 11 months ago

Same here on OneXPlayer 2 Pro

Valkirie commented 11 months ago

It's fixed on forthcoming update. In the meantime, disable vibrate on connect.

NightHammer1000 commented 11 months ago

disable vibrate on connect.

Does not help in my case. But thanks for the info.

CasperH2O commented 10 months ago

This issue has been fixed for "all" devices. There was indeed a bug in HC that caused this at times.

On that note AOKZOE and OneXPlayer have a different issue, reported here: #818

Closing as fixed.