From 1a38853e02ecc0c22945a42731458deb4dbf4a9b Mon Sep 17 00:00:00 2001 From: Sam Lantinga Date: Wed, 24 Apr 2019 12:53:15 -0700 Subject: [PATCH] Fixed bug 4566 - Hot-plugging Bluetooth controller causes force-quit on Android Anthony @ POW Games 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 --- android-project/app/src/main/AndroidManifest.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/android-project/app/src/main/AndroidManifest.xml b/android-project/app/src/main/AndroidManifest.xml index e994e46b7e802..bcd2ede3831de 100644 --- a/android-project/app/src/main/AndroidManifest.xml +++ b/android-project/app/src/main/AndroidManifest.xml @@ -56,7 +56,7 @@ android:label="@string/app_name" android:alwaysRetainTaskState="true" android:launchMode="singleInstance" - android:configChanges="keyboard|keyboardHidden|orientation|screenSize" + android:configChanges="orientation|uiMode|screenLayout|screenSize|smallestScreenSize|keyboard|keyboardHidden|navigation" >