-
Notifications
You must be signed in to change notification settings - Fork 11
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
odroid go ultra controls cant be loaded #43
Comments
Could you tell me what you're having in /dev/input/by-path/ ? |
there are four files, platform-ffd1c000.i2c-platform-rk805-pwrkey.2auto-event platform-gpio-keys-event platform-odroid-go-ultra-joypad-event-joystick platform-odroid-go-ultra-joypad-joystick |
All four show a 0 in the far right of the screen. |
I'll need to implement a change in the joypad binary. In the meantime can you try using manual parameters bu creating a file named "paramcontrols.txt" within the "ThemeMaster" folder with the following content: |
That's strange, the paramcontrols file is being processed before the last output. |
Same issue anytime I launch the app and it still requires a hard reset to get out of the app. |
My bad, the file content was incorrect, try with this one Edit : file needs to be renamed "paramcontrols.txt" |
After putting in the new paramcontrols.txt file in the thememaster folder I get stuck at the same screen I posted previously but now if I press a,b,x,y,l1,l2,r1,r2 or the d-pad there are signs of recognized input. Nothing from the joysticks or start and select buttons though |
Was the app working fine before later ROCKNIX update? |
I have only had the device for a few weeks now so the only version of rocknix has been the latest version. |
I have installed latest rocking on my device and everything works fine. Could you try to run a clean install by deleting the ThemeMaster.cfg file and the data folder if existing. |
the Odroid Go Ultra with Rocknix 20241120 is giving the "controls cant be loaded. input driver not recognized." message. the device has to be hard reset after trying to open ThemeMaster.
The text was updated successfully, but these errors were encountered: