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

Slow performances on MiBox #65

Closed
Swordfish90 opened this issue May 16, 2020 · 5 comments
Closed

Slow performances on MiBox #65

Swordfish90 opened this issue May 16, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@Swordfish90
Copy link
Owner

It seems after a few tries that Lemuroid runs slowly on a MiBox, we should profile it to understand how we can improve it.

See #51 for more details.

@Swordfish90 Swordfish90 added the enhancement New feature or request label May 16, 2020
@rodrigoswz
Copy link

Apparently fixed after I updated the Mi Box to Android 9.

But unfortunately something in the latest beta version of Lemuroid does not accept the buttons of my bluetooth joystick (ipega 9025) so I can't play to test it.

@Swordfish90
Copy link
Owner Author

Hi @rodrigoswz . That's actually great news! Would be interesting to investigate how they fixed it but I'm happy anyway. Is the gamepad detected in Lemuroid? Are you able to navigate the UI and change key bindings?

@rodrigoswz
Copy link

rodrigoswz commented Sep 30, 2020

Yes, I can do all of that, only when I open a game on Lemuroid that my gamepad does not respond. It happens on my phone too btw, it is not something exclusive in Mi Box this time.

EDIT: gamepad works fine on others emulators/games.

EDIT 2: Tested with Dualshock 4, also does not work

@Swordfish90
Copy link
Owner Author

Ok. What I changed in one of the last update (which fixed some missing touch control issues) is trusting android entirely on the matter. When a device is connected, if android recognizes it as a gamepad it gets a portNumber > 0, otherwise 0.

https://developer.android.com/reference/android/view/InputDevice#getControllerNumber()

Could you please check with Logcat if you're able to see an error, or if the gamepad gets assigned 0?

If that's the case, I guess we should have an advanced option to manually force or disable gamepad detection (it's not the solution I like most, but we have cases of fingerprint readers recognized as gamepads, and gamepads not recognized as gamepads, so I don't think there is any other solution).

@Swordfish90
Copy link
Owner Author

@rodrigoswz . I might have a fix for the gamepad not working. I've added more details as #62 and I'm going to publish it to beta in the next days. Right now I'm closing this, if you have any feedback you can use the other issue.

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

No branches or pull requests

2 participants