Downloaded the current version of MCPE to my Google Pixel XL, and I am unable to use the Xbox One S controller connected via Bluetooth to properly control the game. Once in a game, the left stick will control movement, but nothing else works. None of the buttons or triggers are recognized, nor is the right stick. The phone recognizes the controller as an input device, and I can use the buttons to control things within the OS (menu navigation and such), so the problem appears to be isolated to just Minecraft.
Linked issues
Comments 22
Have verified that other games that support Bluetooth controls are working correctly with the same controller connected to the phone.
This bug has been reported to our internal bug tracker for further testing. It doesn't appear to affect all devices as some work correctly.
If anyone else is having trouble using their Xbox One Bluetooth controller to play, please list the affected device details below.
To clarify, the problem is NOT connecting the controller to the phone; the problem is Minecraft recognizing the controller that is connected. As stated in the description and earlier comments, the controller connects properly, and operates correctly in other games that support Bluetooth controllers.
Actually, issue still persists. I`m on Samsung Tab 10.1" with Android 9+ OS. I experience horrible input lag as described with no background apps running and a octo core processor with 32 gigs internal barely utilized.
I commented on the iOS version since that was the only open bug the search brought up, please address broken search.
Additional on observations....
It requires turning off auto jump in all input types to actually turn it off. So apparently Minecraft doesn't correctly detect which input has been chosen,
So there is overlap, maybe the option to manually turn off other input types may help. Perhaps move option that are available across all inputs to separate section to remove redundancy may also assist in resolving this issue. Ability to increase controller priority would suffice.
@Louis That is a separate issue from this. This issue was for Bluetooth controllers 100% not being enabled as input devices on the Amazon App Store version of the app.
The search issue is inherent to JIRA, Mojang can't fix that. Would highly recommend you open up individual bug reports for both issues you are encountering (input lag, auto-jump not disabling due to multiple input detection). Tagging these in on separate issues only serves to muddy the waters, and makes it more difficult to get the individual problems fixed.
Will do, please remove comments. I wish they would move to better bug reporting format tbh. I thought auto jump would be pertinent since linked to inputs.
I tried changing the triggers key mapping and they dont respond but when i use the right stick it assigns the triggers down is the right trigger and right is the left one. Without the right stick the controller is basically useless. ive looked at at least 5 different threads on jira all about the same issue and this is the closest ive seen to any kind of solution of which i have found none. My controller was working fine on mobile until about 5 days ago when i opened the game again. I dont know what caused this i had downloaded the newest update before the problem showed up and its only an issue with minecraft i have the newest firmware update as well. i really hope this thread can actually get some support from mods, as i dont play mobile without a controller.
Please note, this ticket has been resolved (check the ticket state), as the issue it was opened for has been fixed. Please open a new ticket, as comments on this issue are likely to be ignored from Mojang, as they consider the issue it was opened for fixed.
Based on your description, you failed to mention a few details that you will want to include in the ticket when you open it:
What device are you using?
Where did you buy Minecraft from? (Apple App Store, Google Play Store, Amazon App Store)
What controller are you using?
Are you able to use the controller with any other games?
You may also try reaching out to the community on the Minecraft Discord (linked on the support pages).
Just updated to 1.8.0 and the issue still exists.