| Summary: | Hot-plugging Bluetooth controller causes force-quit on Android | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Anthony @ POW Games <ant> |
| Component: | joystick | Assignee: | Sylvain <sylvain.becker> |
| Status: | RESOLVED FIXED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | CC: | sylvain.becker |
| Version: | HG 2.0 | ||
| Hardware: | All | ||
| OS: | Android (All) | ||
|
Description
Anthony @ POW Games
2019-03-27 16:07:38 UTC
Not sure but is it working correctly when you add this very permission ? This sounds like Android is restarting the application due to a configuration change: https://developer.android.com/guide/topics/manifest/activity-element.html#config The default AndroidManifest.xml has this, can you try adding other values to see if one of those is triggering? android:configChanges="keyboard|keyboardHidden|orientation|screenSize" Adding bluetooth permission = no change. I tried adding different configChanges and sure enough, "navigation" worked! Now bluetooth controllers hot-plug nicely. So shall we add it as a default to the AndroidManifest.xml? Funny that this is how this activity is described: "navigation" The navigation type (trackball/dpad) has changed. (This should never normally happen.) I think the reason behind this is because the bluetooth game controller I was testing doubles-up as a keyboard, which probably comes with a DPAD? It's a MOCUTE-032X_B63-88CE Added to the default manifest, thanks! https://hg.libsdl.org/SDL/rev/f926c8070a2a |