-
Notifications
You must be signed in to change notification settings - Fork 20
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
[Issue]: Android TV (android 10) can't manage to get motion sensors to work #98
Comments
Android 10 does not have proper drivers for gyro on controllers, and there's currently no driver override for DualSense. Luckily I just implemented driver override for wired ProController, you can use a USB dongle that converts DS to ProCon and use gyro there. |
I have been looking for such a dongle but I cant seem to find one. I have the 8BitDo one but that one only supports motion on the switch. Do you know of one that I could buy. I am trying really hard to give the Nvidia Shield TV Pro an opportunity. However no motion supports kills the whole experience. I tried all the streaming options, Steam, Nvidia geforce, moonlight with sunshine, parsec, ... I just found out of apollo and artemis and everything is so promising. Even if I don't end up using the shield I for sure will not go back to normal moonlight might need sunshine for the PC use. Thank you very much |
Not working, Android does not recognize the adapter |
Hi and thank you so much for taking the time to respond. I tried that, my pc does see the remote as a switch pro controller. But on the shield, whenever I change into switch mode the ds4 keeps vibrating as if it was connecting and disconecting. It seems to work for 2 second because artemis does ask me for the switch pro. But no matter what it goes into vibrating berserk mode right after. The rest of the modes do work. It is only with the switch. I tried with artemis Uninstalled just in case it was a driver problem. No luck. |
I just tried and Android does not even recognize it... And I tried another adapter it can not pair with DS5 Maybe just get a third party Switch Pro with hall effect sticks... |
Oh, well that is a shame. But if android doesn't recognize it then the driver will never work with the "pro controller". Maybe it is that the dongle emulates a plugged pro controller? |
It works with several cloned ProController and legit ProController. The 8BitDo dongle can't be recognized correctly though Another different dongle can connect to ProControllers and report itself as a ProController, but has some quirks. You need a USB hub to connect it to Android, otherwise it'll not respond to any input... These gadgets all have broken USB stack and I'm kinda frustrating about them... |
OK I understand. Thank you so much for your time and your efforts. I am really enjoying artemis and I switched to Apollo just yesterday. Soooo good both. Thank you |
You're welcome! |
Describe the bug
Hey, I tried installing artemis on my Sony bravia, it has android 10 which I think might be the issue here.
I'm connecting a dualsense controller, tried both usb and Bluetooth.
The option in the setting of forwarding the motion sensor doesn't appear in the settings menu, and searching for it does find it but when I press it it doesn't seem to actually go to it.
In practice, the controller appears as a 360 controller, without recognizing the touchpad or gyro.
The same controller when paired to the phone does show up as a ds4 controller.
Steps to reproduce
Affected games
No response
Other Moonlight clients
None
Moonlight adjusted settings
None
Moonlight adjusted settings (please complete the following information)
No response
Moonlight default settings
Yes
Gamepad-related connection issue
No
Gamepad-related input issue
No
Gamepad-related streaming issue
Yes
Android version
android 10
Device model
sony bravia 90l
Server PC OS version
windows 11 latest
Server PC GeForce Experience version
No response
Server PC Nvidia GPU driver version
No response
Server PC antivirus and firewall software
No response
Screenshots
No response
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: