I'm using an iPega Bluetooth controller with my HTC Desire 510. For most things it works great, but I am running into some issues with Ravensword 2. Ravensword finds my controller and connects fine, but when I start playing, certain actions can't be performed (attacking being one of them). Is there a way to custom map my controller? I'm not on a rooted phone as I can't find a reliable way to root this device.

I’m facing a really annoying problem with the Bluetooth on my POCO F4 GT and wanted to share everything I’ve tried so far to see if anyone can help or if they're going through something similar. I’ve always used the BSP D3 controller on my phone without any issues, working perfectly in Android mode (holding the X button while turning it on). I believe that, at the time of the first pairing, my phone was still on an earlier version of the system. Then, I bought a new controller, the JK 02 model, and that’s when the problems started. It shows up in the Bluetooth device list, but it won’t connect at all. I thought it could be some interference from other paired devices, so I removed all of them—including the BSP D3. And that’s when I noticed the worst: now even the BSP D3 won’t connect in Android mode, which is the mode I always used. The only way to connect the BSP D3 now is by using the Xbox 360 mode, but in this mode, I lose the ability to remap the buttons, which was exactly the reason I used Android mode. Since then, I’ve tried absolutely everything: - Resetting the phone’s network settings. - Restarting Bluetooth, toggling airplane mode on/off, restarting the phone multiple times. - Clearing Bluetooth and other related service caches. - I performed a full backup and restored the phone to factory settings, but the problem persists. - I tested other devices—my Bluetooth headphones, for example, connect normally, which shows that Bluetooth is not completely unusable, but there’s clearly some bug with controllers in Android mode. - I tested both controllers on another old phone of mine (a Xiaomi Mi A3) and they both worked perfectly in Android mode without any issues. I also tested the JK 02 controller on my wife’s phone, and it worked right away. So, everything points to the problem being with the current system version on the POCO F4 GT. My phone is currently on Android 14, system version 1.0.10.0.ULJMIXM. Apparently, this update bugged the Bluetooth compatibility with controllers in Android mode. And it’s really frustrating because the only alternative now would be to use the controller in Xbox mode, which breaks the entire button mapping configuration in apps like Shooting Plus V3.

I have a phone with a physical keyboard (F(x) Tec Pro1 X). I would like to map that keyboard to game controller inputs so I can use it to play Android games that support controllers. Unfortunately I can only find Apps that do the opposite - mapping game controllers to keyboards. Is there a way (specific App, Tasker scripting etc.) to use a physical keyboard as a game controller on Android?

Gamepad is my main form of input when playing games on my Android devices, and one thing I enjoyed was the haptic feedback (rumble) of the controller. Prior to the 2023 release of the Samsung Galaxy S23 Ultra (GS23U), I was rocking its predecessor, the Galaxy S22 Ultra (GS22U). A month after its release, I bought the GS23U to see if an upgrade was worth it. When I jumped into a match of Fortnite (supports rumble) I quickly noticed that there was no rumble. After hours of googling and troubleshooting, I concluded that it might have been a quirk of the phone. It didn't matter much as I returned the GS23U anyway for reasons unrelated to controller rumble. Fast forward and I go through the same ordeal, this time with the Galaxy Tab S8+ (GTS8+) and the Galaxy Tab S9+ (GTS9+). Rumble on the last gen, none on the current gen. Pretty clear that the Galaxy devices of 2023 did not support rumble on Xinput controllers (I kept the GTS9+ anyway for the IP68 rating). And now, the present... I'll let the table do the rest of the talking. I tested 3 controllers. 2 Xinput, and 1 non-Xinput. - Same Android version across devices. (Android 14, OneUI 6.1.1) - The only meaningful hardware change across generations is the chipset, Snapdragon 8 Gen. 1, 2, and 3 respectively. - All connected via USB Pretty clear that something changed regarding Xinput 2023 & onwards, and rather than a solution (one would be nice though), I'm just curious as to what's going on. My first guess is drivers, but I'm not entirely sure how that works on Android.

I'm guessing this is some sort of Bluetooth keyboard recognition and/or selection/activation issue in Android that I can't seem to figure out. The iCade Arcade Bluetooth device is in essence a keyboard device. I can pair it with a Nexus 10 tablet, and after I do, I can see various characters appear in a text app when I move the joystick around and press the buttons. But my Android phone is being stubborn. It pairs ok, but the input refuses to get fed to the apps. I also have an actual Bluetooth keyboard, and it works ok with that phone. I've tried various Bluetooth connect apps, and there I can see a list of paired devices and the option to "connect" to a device. It refuses to work. What am I missing here? Does anyone know of a Bluetooth helper app of sorts that also gives immediate feedback on what it is picking up from the selected Bluetooth device? Is there anything specific I could look for in logcat? The phone is Android 4.4 and I can't upgrade it (Chinese phone with no firmware support). It's an ECOO S04 Aurora Plus 3GB. The Nexus 10 I think runs on Android Lollipop.

Logitech's Unifying standard seems very similar to Bluetooth (same 5-device limit, similar range, similar specs from what I've read on the Internet). I'm trying to connect a Logitech F710 wireless controller, to my Android phone over Bluetooth. It works if I plug the "unifying" USB dongle into a USB OTG cable (micro-USB to full-USB converter) and plug said OTG in my phone. It works fine (fiddling on the controller moves things around on-screen). But I need it to work without plugging into the phone's MicroUSB port. I've got a Samsung/Oculus Gear VR (that connects to the phone's MicroUSB port). But when I hook up the OTG cable to my Gear VR's charging Micro-USB port, it just doesn't work. I've read on Reddit that if you prevent the Oculus app from starting when you plug in your Android device (I'm using a Samsung Galaxy Note 5), then the Gear VR's charging port also registers that stuff. So any suggestions?

I bought a *Gamesir X2s* (mobile controller, similar to adding half an Xbox or PlayStation controller to either side of your phone) recently and have had connectivity issues with my Samsung Galaxy A54. When I plug the Gamesir X2s into my phone, it does not detect it. However, the Gamesir X2s has a USB-C port that can be used for charging the phone through the Gamesir X2s. If I try charging my phone like this, it will detect the Gamesir X2s, and I can unplug charging and the phone will continue to detect the Gamesir X2s with no issues. Presumably, because of capacitors inside of the Gamesir X2s, I can also plug in a charger into it when the phone is not plugged into it, and then take the charger out and plug my phone in, and they will properly connect. I can also unplug the Gamesir X2s from my phone and plug it back in and still have it detected. This seems to work up to about a minute after the Gamesir X2s has been either plugged into a charger or the phone. Is this an issue with the Gamesir X2s, or my Samsung Galaxy A54? And is there any way I can fix this issue (such as changing settings in my phone)? I found that a USB-C male to USB-A female adapter cable, when plugged into my phone, came up as a USB device. I thought this was odd because it is just a cable and not a USB device. However, I also have a USB-A male to USB-C female adapter, and in combination using both adapters and plugging in my Gamesir X2s into my phone, the Gamesir X2s is recognised and receives power. I can then unplug it all and quickly plug the Gamesir X2s directly into my phone and it all works. So I guess I have found a solution, though I'd still like to find the specific root cause of this, if possible.

I’m having an issue with my gaming controller - [Cosmic Byte Quantum](https://www.thecosmicbyte.com/product/cosmic-byte-quantum-dual-mode-bluetooth-wired-controller-for-ps4-pc-ios-android-switch-hall-effect-triggers-and-joystick/) and was hoping someone could help. Here’s the situation: - **Device Setup**: I have [Cosmic Byte Quantum](https://www.thecosmicbyte.com/product/cosmic-byte-quantum-dual-mode-bluetooth-wired-controller-for-ps4-pc-ios-android-switch-hall-effect-triggers-and-joystick/) gaming controller that I connect to my Samsung Galaxy Tab S8+ using Bluetooth. - **Problem**: The gyroscope on the controller doesn’t seem to be working when connected via Bluetooth. Checked it using [Game controller tester App](https://powgames.itch.io/game-controller-tester) - **Observation/Temporary Fix**: When I connect the controller to my tablet via USB, the gyroscope works perfectly. - **Interesting Observation**: If I connect the same controller to my iPhone via Bluetooth, the gyroscope functions correctly without any issues. Given this, I have a few questions: 1. **Why does the gyroscope work via USB but not Bluetooth on my Android tablet?** - Is there a compatibility issue between Android and the controller’s Bluetooth connection? - Could it be a problem with how Android handles Bluetooth devices versus how iOS does? 2. **Why does the gyroscope work over Bluetooth on my iPhone but not on my Samsung Galaxy Tab S8+?** - Does iOS have better support for Bluetooth gyroscope functionality? 3. **What can be done to solve this issue?** - Are there any settings or apps on Android that I can tweak to fix the gyroscope issue? - Can I root the tab and tweak something to fix this? - Any other alternates, like buying a [USB Dongle](https://www.thecosmicbyte.com/product/cosmic-byte-stratos-xenon-gamepad-dongle-for-pc-gamepad-not-included-black/) for the controller can fix this? Any insights, suggestions, or solutions would be greatly appreciated! Thanks in advance for your help! What did I try: - Tried updating the firmware of the controller - Tried using other apps/games to test Gyro - Tried other Android devices Expectation: - Get the gyro from the controller working so as to play games like asphalt8 and others using the Controller's Gyroscope

Is it possible to turn an Android phone into a USB gamepad for the PC? If yes, how?

I'm trying to connect a gamepad with my mobile but it is not connecting. 1. On mobile 1 (Xiaomi Redmi), I connected the gamepad it was not working. I found that the gamepad works only with applications that request USB permission. So I installed an app that asks for USB permission, and it worked. I installed a game, cast the screen on the TV and everything was working fine. After a few seconds, it stopped working. And now it is not connecting anymore. Before connecting, I tried to read an SD card through a USB port and it was working fine. Now even that is not working. 2. On mobile 2 (another version of Xiaomi Redmi), it shows that the gamepad is connected as the light is not blinking but always on. But nothing works. 3. On mobile 3 (OnePlus), did a few attempts, but it didn't work. But then it started working automatically. Without giving any additional permission. Probably it was trying to download some driver in the background, no idea. **Additional info** 1. USB tethering is disabled. It says the USB is not connected. But if I connect the data cable with a laptop then it's connected. How can I debug or fix this issue on Xiaomi mobiles? **Update** It seems weird. But when mobile battery is less than 15% then it automatically connects.

I have an R1 Bluetooth controller . When I connect this controller to my Android tablet, it is well recognized in Bluetooth but at the functional level, it works like a joystick. That is to say, when I move the joystick, it selects the tabs. What I would like is that this joystick works like a mouse and they indicate a mouse cursor. Is it possible?

Some time ago I played this game (_Coach Bus Simulator_ or something) that worked perfectly with touchscreen controls. But now, for some reason, it will detect a GamePad. There are two problems: * I can't play this game because touch controls get disabled when a GamePad is connected * I don't even own a GamePad or Controller or Joystick or Whatever™. Any help would be appreciated. The phone is: Xiaomi Redmi Note 9 System: Android 12, MIUI 13.0.3 (Global)

I have an Android 11 box (Android TV Box 11.0, 4GB 64GB Decodificador Android Box, Amlogic S905W2 Smart TV Box"), and am trying Retroarch. For controller 1, I have a Power A Liquid Metal XBox One controller. Works fine so far. But no matter what I configure as Input 2, the 2nd controller stills controls player 1. I tried several controllers for Input 2, and it's always the same thing. I tried a Wired Rock Candy Switch controller, BlueTooth Atgames Legends Mini, and I also tried using a second Power A Liquid metal Xbox One controller. No matter what I do, it seems to think that both controllers are the same controller. (both control player 1). What I noticed that's weird is that since it thinks both controllers are the same, and I mapped both Input 1 and Input 2 to it, when I'm in certain menu screens, when I hit down, it registers twice. I'm guessing because it thinks both players hit down. I tried both SNES9x and Final Burn Neo. The problem seems to be at the Android level (before getting to Retroarch). Is it normal to have an Android 11 device only accept one controller? Or is it possible that it's a problem with my device specifically?

When I plug in the Xbox 360 wireless controller dongle to my LG G3 running Android 5.0 Lollipop and load up a game such as Goat Simulator or Stranger Oddworld, the triggers are mapped to the right analogue stick. This means my view constantly rotates and moves upward. This is because the inputs are registering -1.0. When I move the triggers toward the centre of movement, the view stabilises. Can the triggers be remapped?

I have Quantum PS2-like Gamepad which doesn't work on my Xiaomi Redmi 1S. My phone's Android version is 4.3. I use a USB OTG cable which works fine with keyboards, mouses, and pen drives. Whenever I attach the joystick, just the red light in the joystick blinks, and nothing happens.

My son wants to play the mobile version of [Skylanders Trap Team](https://play.google.com/store/apps/detailsid=com.activision.skylanders.trapteam) on his micro tablet a.k.a. [LG Optimus Exceed 2](https://www.lg.com/us/cell-phones/lg-VS450PP-optimus-exceed-2) with no service. Apparently, it is not compatible with his phone, even though it runs Android KitKat 4.4.2. I tried some of the free Skylanders Android games on BlueStacks, and they seem to run well. Before I buy the game and [controller pack](http://www.amazon.com/Skylanders-Trap-Team-Tablet-Starter-Pack/dp/B00MG38CG8) , I'd like to hear opinions of whether the Bluetooth controller is likely to work.

I have an LG Aristo and I recently got an ípega Bluetooth controller off the wish website, the phone isn't rooted an I don't know much on what to do so it's not working for any of my games I don't know what to do please help...

I have a problem with my device while pairing my ipega 9037 Bluetooth gamepad controller. The joysticks are working and also the D-pad, but I have thought that can I use this controller over USB OTG. Does it damage the smartphone battery?

Is it possible to detect two of the Gear VR controllers at once, with programming in Unity? Has anyone heard of any way to do this, or does Oculus limits it to inspire you to get a Rift? It would open a whole world of possibilities for the Gear VR when used with Unreal or Unity.

How do I map a joypad (specifically the HAT switch/DPad) axis to a button with a key-layout file in /system/usr/keylayout/? I currently have this line in the appropriate file: axis 0x10 split 0x7f BUTTON_L1 BUTTON_R1. I'll explain the line token by token. First token refers to the input type. axis means I'm binding an axis. Second token is the axis ID. The axis I want to remap is 0x10. The Android developer's wiki page concerning key-layout files mention you can split an input axis into two outputs with split so I'm using it. The split is at the value immediately following split, in this case 0x7f. Input values below the split threshold map as the 1st token after the split threshold token. Here it is BUTTON_L1. Input values above the split threshold map as the 2nd token after the split threshold token. Here it is BUTTON_R1. However, when I use the line metioned above the axis does not map to anything anymore. Are you able to map device axes to Android buttons in the first place? If so, what is the proper syntax for it?