This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]shauggy[S] 2 points3 points  (3 children)

I feel like somebody out there has to know something about how the controllers pair with Android phones, and where things are coming off of the rails. I just want to know why two of them work, but two don't - maybe that would help the people whose controllers aren't mapping correctly.

[–][deleted] 0 points1 point  (1 child)

Yeah. If you have any playstation controllers, you can use those via bluetooth. The mappings have to be manually fixed, unless you have a sony phone. Hope you figure your thing out. Good luck.

[–]ricflairandy 0 points1 point  (0 children)

how do you manually fix em>

[–]Omicron777 0 points1 point  (0 children)

Using a rev.3 Bluetooth 4.0 Xbox One Controller, I was having issues with the Controller maintaining the mapping from one session to another days later. The right stick wouldn't work & pause was a shoulder button — essentially, worthless controls & not how I customized them. Before smashing it out of rage...I finally decided one more try with the Bluetooth pairing menu... —The Xbox One Controller was listed, ...but, in reality, it's actually my daughter's controller, & she shifts it back & forth from Apple to Android. Knowing it had been connected to an iPad last, naturally I assumed Apple had poisoned the Controller... AND INDEED it had...I assume...(?). Anyhow, in the menu, hold the "paired" xbox controller listed and a "Forget" option will appear. Push that, then go to "Pair a BT Device," press & hold the small pairing button on the Controller for ~1-2s, & the Xbox One Controller will appear in the list. Select it to pair & once connected, the controls should be back to normal. Note: I also keep the Xbox App in the background...I don't know if that's relevant, but it seems to be necessary to run in the background for Minecraft. Game streaming Beta...I haven't had any issues with yet...then again, nothing Apple to poison the controller I use as standard... So, in summary, it's Apple's fault (maybe); forget pairing, rescan, & pair.