Pressure-sensitive Left and right triggers on controller now "double-tap" after pressing

Can confirm, am experiencing the same issue on Android version 13 using a PS5 controller. Definitely only started after the latest update.

+

+

We also have this exact same problem, which started when Minecraft upgraded to 1.20.30.  Symptoms are identical on two different Android devices, a Google Pixel 6a running Android 13, and and a Pixel 3a running Android 12.

We are using PowerA MOGA XP5-X Plus controllers with both phones.  The buggy behavior happens the same way when the controller is connected to the phone with Bluetooth, or with USB cable. Just like in the original bug report, if inside the Minecraft software we remap the place/break block functionality to a different button, the buggy behavior follows the physical button, NOT the place-block or break-block functionality.  We tried three different controllers (all the same model), and they all show the same buggy behavior.  And of course the original reporter is using a completely different controller (Razer Kishi V2), so the particular model of controller doesn't seem to matter. 

We also have this exact same problem, which started when Minecraft upgraded to 1.20.30.  Symptoms are identical on two different Android devices, a Google Pixel 6a running Android 13, and and a Pixel 3a running Android 12.

We are using PowerA MOGA XP5-X Plus controllers with both phones.  The buggy behavior happens the same way when the controller is connected to the phone with Bluetooth, or with USB cable. Just like in the original bug report, if inside the Minecraft software we remap the place/break block functionality to a different button, the buggy behavior follows the physical button, NOT the place-block or break-block functionality.  We tried three different controllers (all the same model), and they all show the same buggy behavior.  And of course the original reporter is using a completely different controller (Razer Kishi V2), so the particular model of controller doesn't seem to matter. 

These other two bug reports sound similar, although not exactly the same:

MCPE-172475
Blocks are placed more than once when you press the place button, and same with when breaking too.

MCPE-174864
Xbox LT Button not Working in Minecraft

These other two bug reports sound similar, although not exactly the same:

MCPE-172475
Blocks are placed more than once when you press the place button, and same with when breaking too.

MCPE-174864
Xbox LT Button not Working in Minecraft

Im using a gamesir X2-pro controller (officially xbox licenced) and have the same problem only with the left trigger and of course only in Minecraft since the last couple updates.

Im using a gamesir X2-pro controller (officially xbox licenced) and have the same problem only with the left trigger and of course only in Minecraft since the last couple updates.

I have the same issue and can't build until this is fixed. It is incredibly hard to build with mobile controls, at least for me. 

I have the same issue and can't build until this is fixed. It is incredibly hard to build with mobile controls, at least for me. 

Haven't been able to play since the 20th.. I'm turning off auto updates cause of this..

Haven't been able to play since the 20th.. I'm turning off auto updates cause of this..

Didn't notice it with R2 until L2 started placing 2-3 blocks even with a light/half press on my Sony brand PS4 controller. R2 is definitely destroying faster as well. This all started with the last update I did. I updated manually some time in the last week. My current version is 1.2.32

Didn't notice it with R2 until L2 started placing 2-3 blocks even with a light/half press on my Sony brand PS4 controller. R2 is definitely destroying faster as well. This all started with the last update I did. I updated manually some time in the last week. My current version is 1.2.32

I'm having the same issue. But it is with all inputs from my PS4 controller. I have a (Galaxy Tab S5e) and when I play on Skyblock servers and have to use menus it takes forever. Because when I open it with a button press it will immediately close it with the double press bug.

Hope they fix this soon.

I'm having the same issue. But it is with all inputs from my PS4 controller. I have a (Galaxy Tab S5e) and when I play on Skyblock servers and have to use menus it takes forever. Because when I open it with a button press it will immediately close it with the double press bug.

Hope they fix this soon.

I also have the same problem. I'm using a PS4 controller in a Samsung Galaxy S23+. On version 1.20.32. It's not playable at all.

Is there a way to downgrade it until it's solved. Apparently it will take a while.

I also have the same problem. I'm using a PS4 controller in a Samsung Galaxy S23+. On version 1.20.32. It's not playable at all.

Is there a way to downgrade it until it's solved. Apparently it will take a while.

The mobile version of this game has been broken unplayable on controller for 30 days now.... kinda a joke at this point.

The mobile version of this game has been broken unplayable on controller for 30 days now.... kinda a joke at this point.

I have had this problem since 1.20.30 released on Android. Doors, gates, trapdoors are all being double activated. If you have a block/item in your hand, it will place it down immediately outside the door/gate. It is also causing blocks to be double placed, making building extremely difficult. 

Same experience that atp reported. I am also using a PowerA MOGA XP5-X controller.

Video link (too large to attach directly) https://photos.app.goo.gl/SVDD6QTpCEdcDRgh9

Also occurs with Razer Kishi (original model) on Android 14. Issue seems linked to analogue triggers which are considered as being triggered multiple times on a complete trigger press.

Also occurs with Razer Kishi (original model) on Android 14. Issue seems linked to analogue triggers which are considered as being triggered multiple times on a complete trigger press.

Just updated to 1.20.40 and have the same issues I had before.

Just updated to 1.20.40 and have the same issues I had before.

Wow still unfixed.. wonderful.

Wow still unfixed.. wonderful.

Can also confirm the bug still exists in 1.20.40. Tested on ROG Kunai 3 and Dualshock 4. Pretty crazy a bug this bad isn't fixed after over a month.

Can also confirm the bug still exists in 1.20.40. Tested on ROG Kunai 3 and Dualshock 4. Pretty crazy a bug this bad isn't fixed after over a month.

Is happening with me too, I'm using the Sn30 Pro Xbox version and after that update this started to happen, it's good to know that at least is a gener problem and not on a specific controller model

Is happening with me too, I'm using the Sn30 Pro Xbox version and after that update this started to happen, it's good to know that at least is a gener problem and not on a specific controller model

@Richard E Collard - hey man, what is that client you use on Linux? I so want that! I play Java Edition on Linux just because I can't find a good client to run it on Linux.

Thanks bro. 🙂

@Richard E Collard - hey man, what is that client you use on Linux? I so want that! I play Java Edition on Linux just because I can't find a good client to run it on Linux.

Thanks bro. 🙂

Tested Minecraft Android v. 1.20.40 with the following controllers.  Here are the results:

Xbox Controller - Works perfectly.  No duplicate block placing issues.  This would be expected since Microsoft makes both the game and controller... 

PS4/PS5 Contoller - Unplayable.  Both the L2 and the R2 registers a double press when pressing the trigger only once.  Lightly pressing the trigger half-way will result in only a single press, however, this is almost impossible to do consistently.  

Razer Kishi V2.  - Exact same behavior as PS4 above. 

Nintendo Switch Pro Controller - Gets even weirder..  The L2 button works as expected.  Yay!  Only one block is placed when fully pressing the trigger button.  Similar to Xbox controller.  HOWEVER, the R2 trigger button does not always register.  Whenever I attempt to mine a block and press and hold R2, the character only swings ONCE and then stops.  What should happen is pressing and holding should cause the character to continue to swing the tool to break blocks.  This bug makes is maddeningly frustrating to mine anything because you have to pull the trigger several times in succession just to do enough damage to mine one block.  

It's obvious that Microsoft/Mojang only tested the update on the Xbox controller.  When they saw that it worked, they assumed the job was done.  So either they did not do a thorough job, OR, they only want you to buy Xbox controllers which would be absurd.  

Tested Minecraft Android v. 1.20.40 with the following controllers.  Here are the results:

Xbox Controller - Works perfectly.  No duplicate block placing issues.  This would be expected since Microsoft makes both the game and controller... 

PS4/PS5 Contoller - Unplayable.  Both the L2 and the R2 registers a double press when pressing the trigger only once.  Lightly pressing the trigger half-way will result in only a single press, however, this is almost impossible to do consistently.  

Razer Kishi V2.  - Exact same behavior as PS4 above. 

Nintendo Switch Pro Controller - Gets even weirder..  The L2 button works as expected.  Yay!  Only one block is placed when fully pressing the trigger button.  Similar to Xbox controller.  HOWEVER, the R2 trigger button does not always register.  Whenever I attempt to mine a block and press and hold R2, the character only swings ONCE and then stops.  What should happen is pressing and holding should cause the character to continue to swing the tool to break blocks.  This bug makes is maddeningly frustrating to mine anything because you have to pull the trigger several times in succession just to do enough damage to mine one block.  

It's obvious that Microsoft/Mojang only tested the update on the Xbox controller.  When they saw that it worked, they assumed the job was done.  So either they did not do a thorough job, OR, they only want you to buy Xbox controllers which would be absurd.  

Here is what mine is doing with PS4 controller. Drives me insane. https://youtu.be/c2TjbEFoiQ4

Here is what mine is doing with PS4 controller. Drives me insane. https://youtu.be/c2TjbEFoiQ4

The same thing happens to me with the PS4 controller, please Mojang fix this, I didn't post this before in version 1.19

Video:

https://drive.google.com/file/d/1I2JhxnOJFMBS_AW7xSZDKnIRdKKipzXW/view?usp=drivesdk

The same thing happens to me with the PS4 controller, please Mojang fix this, I didn't post this before in version 1.19

Video:

https://drive.google.com/file/d/1I2JhxnOJFMBS_AW7xSZDKnIRdKKipzXW/view?usp=drivesdk

I am also still having this issue as of 11-08-2023. I am using the Minecraft app on android with a razor kishi v2 controller. At first I thought it was just the controller, but it only occurs when playing minecraft. It is as if it registers pressing a trigger as a button press and then fully pressing the trigger all the way down as a 2nd button press. This occurs with both L2 and R2. Please fix this issue as it is unplayable for me like this.

I am also still having this issue as of 11-08-2023. I am using the Minecraft app on android with a razor kishi v2 controller. At first I thought it was just the controller, but it only occurs when playing minecraft. It is as if it registers pressing a trigger as a button press and then fully pressing the trigger all the way down as a 2nd button press. This occurs with both L2 and R2. Please fix this issue as it is unplayable for me like this.

Same issue for me

Same issue for me

Here is the issue for me, makes building more frustrating than it's worth. https://youtube.com/shorts/wylqoCyA8H0?feature=share here is a short showing issue.

PS4 controller on a Samsung Galaxy tab S5e 

Here is the issue for me, makes building more frustrating than it's worth. https://youtube.com/shorts/wylqoCyA8H0?feature=share here is a short showing issue.

PS4 controller on a Samsung Galaxy tab S5e 

I had the same issue. Reported it, and got a reply saying it was invalid. Great that it's still not fixed after 2 months. 

I had the same issue. Reported it, and got a reply saying it was invalid. Great that it's still not fixed after 2 months. 

I have been experiencing the same issue since about the second to last update this year. I have always used a controller since I added the game to my phone. I have tried a number of controllers, all having the same problem.

Same thing happening to me with a PS5 controller. Hopefully they are able to fix this soon. 

Steps to reproduce:

Connect controller, play game, press L2 or R2 to place or break block. 

Same thing happening to me with a PS5 controller. Hopefully they are able to fix this soon. 

Steps to reproduce:

Connect controller, play game, press L2 or R2 to place or break block. 

I'm having the same problem, and there's no solution at the moment. It's very annoying trying to build and open doors, as they open and close instantly.

1.20.51 still broken...

1.20.51 still broken...

Also happens with razer kishi v2 for pixel 8 pro

Also happens with razer kishi v2 for pixel 8 pro

Same thing happening to me, I tried both Dualsense and Razer Kishi controller on my android. Both of them suffer from same issue. Really hoping this gets fixed soon since it makes doors unusable. 

Same thing happening to me, I tried both Dualsense and Razer Kishi controller on my android. Both of them suffer from same issue. Really hoping this gets fixed soon since it makes doors unusable. 

Is it possible that this report didn't mention it is a bug presented on the mobile Android version that Mojang didn't refer to the correct version to reproduce the bug?

Is it possible that this report didn't mention it is a bug presented on the mobile Android version that Mojang didn't refer to the correct version to reproduce the bug?

Same issue with DS4 controller on Android 13, Minecraft 1.20.60

Same issue with DS4 controller on Android 13, Minecraft 1.20.60

I can confirm 1.20.62 is still broken. Hotfix did not fix anything. Still placing 2 blocks when trigger is pressed. This makes the game unplayable and frankly is an embarrassment to Mojang that after 6 months you can't fix a simple controller bug. This does not happen on Apple version. Why do you not care about Android users that paid money for your broken product?  Ridiculous and disgraceful. 

I can confirm 1.20.62 is still broken. Hotfix did not fix anything. Still placing 2 blocks when trigger is pressed. This makes the game unplayable and frankly is an embarrassment to Mojang that after 6 months you can't fix a simple controller bug. This does not happen on Apple version. Why do you not care about Android users that paid money for your broken product?  Ridiculous and disgraceful. 

Apparently this bug is 6 months old?? Ridiculous.

Apparently this bug is 6 months old?? Ridiculous.

Hi All.

I understand the frustration here but Mojang are working hard on fixing this issue and are fully aware of the impact it’s having on players, however I can’t give any ETA for the fix.

On a side note please refrain from commenting “me too” or those type of comments as they don’t add any helpful information which works towards the bug being resolved. Please only comment if you have additional information to add

I can confirm that this is still a thing and caused me to die multiple times which could've been avoided because it wouldn't allow me to eat. The LT and RT triggers on Razor Kishi are glitched pressing multiple times instead of once when pressed. 

Not sure if Mojang considers this a a serious issue because this has been a thing since like 1.19 its been about a year. I stopped playing minecraft when it first started because I couldn't build, open doors, use menus properly. Came back thought it would be fixed after a month or so but I think it's been close to a year with no signs of a fix. 

Mobile Minecraft is probably the second largest community after Java with smart phones and tablets and the fact that we have been unable to use controllers for a year is mind boggling.

I can confirm that this is still a thing and caused me to die multiple times which could've been avoided because it wouldn't allow me to eat. The LT and RT triggers on Razor Kishi are glitched pressing multiple times instead of once when pressed. 

Not sure if Mojang considers this a a serious issue because this has been a thing since like 1.19 its been about a year. I stopped playing minecraft when it first started because I couldn't build, open doors, use menus properly. Came back thought it would be fixed after a month or so but I think it's been close to a year with no signs of a fix. 

Mobile Minecraft is probably the second largest community after Java with smart phones and tablets and the fact that we have been unable to use controllers for a year is mind boggling.

I can confirm this on my own Razer Kishi v2

Also I don't know how the issue works exactly because Xbox uses the same Pressing

Can confirm the bug with an:

• Gamesir X2 pro

• Gamesir G8

On Android 14 with Minecraft version v1.20.73.

I can revaluate the bug with my controllers if necessary.

Eating and opening doors is also affected.

Can confirm the bug with an:

• Gamesir X2 pro

• Gamesir G8

On Android 14 with Minecraft version v1.20.73.

I can revaluate the bug with my controllers if necessary.

Eating and opening doors is also affected.

I started having this issue on my AYN Odin 2. It gets worse after a while, rendering the game unplayable. I have a friend on PC who had this issue while playing on my world.

I started having this issue on my AYN Odin 2. It gets worse after a while, rendering the game unplayable. I have a friend on PC who had this issue while playing on my world.

Contacted Razer Support, they said they are not able to fix the issue because it's Mojangs fault

Also happens on trap doors

Im using dualshock. preciously I had tried to remap to less game breaking actions and it still didnt work. I can try again to see if its still the case that all buttons for me were bugged loke this

Im using dualshock. preciously I had tried to remap to less game breaking actions and it still didnt work. I can try again to see if its still the case that all buttons for me were bugged loke this

Bug is still present, but I'm now very skeptical it's a Minecraft issue.

I can't speak for everyone, but this seems to be an android issue. I have been playing Lego Fortnite with my son and it's behaving the exact same way, which is just as annoying. In menus, it will scroll pages twice at times, and it's infuriating when trying to get to a specific page.

That's probably my last edit, until the true culprit is resolved. I'm sorry for all the irritation the devs received from this issue. I apologize. Once the issue is fixed (by devs outside of MC) I may edit this post again just to say so, but at that point I didn't feel like it's necessary.

I have edited my post with this information.

Bug is still present, but I'm now very skeptical it's a Minecraft issue.

I can't speak for everyone, but this seems to be an android issue. I have been playing Lego Fortnite with my son and it's behaving the exact same way, which is just as annoying. In menus, it will scroll pages twice at times, and it's infuriating when trying to get to a specific page.

That's probably my last edit, until the true culprit is resolved. I'm sorry for all the irritation the devs received from this issue. I apologize. Once the issue is fixed (by devs outside of MC) I may edit this post again just to say so, but at that point I didn't feel like it's necessary.

I have edited my post with this information.

It's still a Minecraft Issue, because it used to work so ... FIX IT DEVS THIS IS IMPORTANT!

Regarding Richard E Collard's update today, that, "Edit 5: Bug is still present, but I'm now very skeptical it's a Minecraft issue. I can't speak for everyone, but this seems to be an android issue."

I don't agree.  As I posted back on 2023-09-24, for us, the bug started IMMEDIATELY upon Minecraft upgrading to version 1.20.30, and the symptoms were identical on two different Android devices, a Google Pixel 6a running Android 13, and and a Google Pixel 3a running Android 12.  That sounds exactly like a bug in Minecraft, not in Android.

I have no idea how the Android controller APIs work.  Perhaps the bug boils down to using the APIs in a slightly wrong way, or failing to use a workaround for a known underlying bug.  If the Lego Fortnite developers have the same bug, that's interesting, but it could also just mean that they made the same mistake Mojang did.  To investigate it properly requires access to the game source code and version control history.  (E.g., "What controller-related code did we change in version 1.20.30?")

I also see no reason to make excuses for Mojang when they haven't even posted anything substantive to this thread.  If they actually investigated and discovered that the problem is due to an Android bug, they should say so here.  Since they haven't, probably they haven't.

Regarding Richard E Collard's update today, that, "Edit 5: Bug is still present, but I'm now very skeptical it's a Minecraft issue. I can't speak for everyone, but this seems to be an android issue."

I don't agree.  As I posted back on 2023-09-24, for us, the bug started IMMEDIATELY upon Minecraft upgrading to version 1.20.30, and the symptoms were identical on two different Android devices, a Google Pixel 6a running Android 13, and and a Google Pixel 3a running Android 12.  That sounds exactly like a bug in Minecraft, not in Android.

I have no idea how the Android controller APIs work.  Perhaps the bug boils down to using the APIs in a slightly wrong way, or failing to use a workaround for a known underlying bug.  If the Lego Fortnite developers have the same bug, that's interesting, but it could also just mean that they made the same mistake Mojang did.  To investigate it properly requires access to the game source code and version control history.  (E.g., "What controller-related code did we change in version 1.20.30?")

I also see no reason to make excuses for Mojang when they haven't even posted anything substantive to this thread.  If they actually investigated and discovered that the problem is due to an Android bug, they should say so here.  Since they haven't, probably they haven't.

Still buggy. How has this not been fixed yet. You know if the devs just give us proper modding tools for bedrock this would've been fixed long ago...

Still buggy. How has this not been fixed yet. You know if the devs just give us proper modding tools for bedrock this would've been fixed long ago...

He didn't say, but it was probably this:

https://mcpelauncher.readthedocs.io/en/latest/
https://github.com/minecraft-linux/mcpelauncher-manifest

He didn't say, but it was probably this:

https://mcpelauncher.readthedocs.io/en/latest/
https://github.com/minecraft-linux/mcpelauncher-manifest

I have the Razer Kishi V2 Pro. I played Minecraft before with this controller without any issues.
Even with Minecraft version 1.20.81 it's not playable. I thought maybe because the triggers are not clickable like the Switch, Minecraft controls takes it after placing more blocks at the same time. However playing other games like Aspalt Airborne 8, I have no issues. I play Minecraft on laptop with my other third party controller with the same trigger effect, but no issues. I'm starting to believe the problem is somewhere in the game itself.
The pro version of the Razer Kishi V2 is however the same as the V2 but with an extra headphone jacket. I opened Razer Nexus app, where you can open games from launcher, and adjusted the button layout but I didn't touched the settings at all. The 2 extra buttons at the back of the controller works just fine partially. The left one 'L3' is placing blocks, sometimes it places 1 block and other 2 blocks. The other one 'R3' is opening inventory, if I want to go to the menu, it's also dubble pressing if I click one time. No matter the trigger buttons, the same issues lies in the inventory.
I have android 14.
I hope this information will does bring extra help.

I have the Razer Kishi V2 Pro. I played Minecraft before with this controller without any issues.
Even with Minecraft version 1.20.81 it's not playable. I thought maybe because the triggers are not clickable like the Switch, Minecraft controls takes it after placing more blocks at the same time. However playing other games like Aspalt Airborne 8, I have no issues. I play Minecraft on laptop with my other third party controller with the same trigger effect, but no issues. I'm starting to believe the problem is somewhere in the game itself.
The pro version of the Razer Kishi V2 is however the same as the V2 but with an extra headphone jacket. I opened Razer Nexus app, where you can open games from launcher, and adjusted the button layout but I didn't touched the settings at all. The 2 extra buttons at the back of the controller works just fine partially. The left one 'L3' is placing blocks, sometimes it places 1 block and other 2 blocks. The other one 'R3' is opening inventory, if I want to go to the menu, it's also dubble pressing if I click one time. No matter the trigger buttons, the same issues lies in the inventory.
I have android 14.
I hope this information will does bring extra help.

The only thing that everyone here including me hopes is that Mojang will take action for this issue and get it fixed as soon as possible.

The only thing that everyone here including me hopes is that Mojang will take action for this issue and get it fixed as soon as possible.

I think the issue got even worse with 1.21. Here's a capture I took immediately after loading a world. I was interested to see if it'd be fixed with 1.21. Oh, well. Guess I'll import my stuff to Minecraft Bedrock Launcher. Will import back when fixed.

I think the issue got even worse with 1.21. Here's a capture I took immediately after loading a world. I was interested to see if it'd be fixed with 1.21. Oh, well. Guess I'll import my stuff to Minecraft Bedrock Launcher. Will import back when fixed.

Im having this issue with Odin 2. But i found a workaround, the issue seems to happen when the L2/R2 triggers are set to analog, if i set them to digital (like on switch controllers), the problem dissapears. This fix works on my odin 2 because i can select the mode, but you cant select the trigger mode on most joysticks.
Giving that analog triggers give a signal between 0 and 1, making it so it places a block when the trigger value is greater than a threshold (ex: 0.5), and lock the ability to keep placing blocks until you either: want to keep placing = (threshold+0.3)+time_delay ; or you release the key and want to spam it (threshold-0.3)? Just throwing ideas.
But yeah, the problem seems to exist when the controller has analog triggers, not with digital triggers.
Also, a little rant, as another comment stated, if devs gave propper modding tools, things like this could be resolved in weeks, even in days by the community. Minecraft modding community must be one of the greatest, but Bedrock modding is very limited and is a pain.

Im having this issue with Odin 2. But i found a workaround, the issue seems to happen when the L2/R2 triggers are set to analog, if i set them to digital (like on switch controllers), the problem dissapears. This fix works on my odin 2 because i can select the mode, but you cant select the trigger mode on most joysticks.
Giving that analog triggers give a signal between 0 and 1, making it so it places a block when the trigger value is greater than a threshold (ex: 0.5), and lock the ability to keep placing blocks until you either: want to keep placing = (threshold+0.3)+time_delay ; or you release the key and want to spam it (threshold-0.3)? Just throwing ideas.
But yeah, the problem seems to exist when the controller has analog triggers, not with digital triggers.
Also, a little rant, as another comment stated, if devs gave propper modding tools, things like this could be resolved in weeks, even in days by the community. Minecraft modding community must be one of the greatest, but Bedrock modding is very limited and is a pain.

@troctor Ay, another Odin 2 user. I would've done that myself if it came to mind, but I already started importing my stuff to my Steam Deck, and I'm now playing Pocket Edition via Minecraft Bedrock Launcher. Bafflingly enough, those issues COMPLETELY disappeared on Steam Deck, despite the analog triggers. I wanna say it's Android, but this also doesn't happen with anything else I'm playing, so I'm at a loss.

@troctor Ay, another Odin 2 user. I would've done that myself if it came to mind, but I already started importing my stuff to my Steam Deck, and I'm now playing Pocket Edition via Minecraft Bedrock Launcher. Bafflingly enough, those issues COMPLETELY disappeared on Steam Deck, despite the analog triggers. I wanna say it's Android, but this also doesn't happen with anything else I'm playing, so I'm at a loss.

I cannot believe this isn't fixed. Bruh I could fix this so fast if I had access to the source code for the mobile version. All you have to do Mojang is a single "if statement" that checks if any of the triggers were pressed down before it was let go of. Seriously, how has it been almost 1 1/2 years without a fix...

I cannot believe this isn't fixed. Bruh I could fix this so fast if I had access to the source code for the mobile version. All you have to do Mojang is a single "if statement" that checks if any of the triggers were pressed down before it was let go of. Seriously, how has it been almost 1 1/2 years without a fix...

@Henry Clifton

I'm not a coder, but I agree with you. Not to mention the top pinned message, saying that Mojang are "working hard on fixing this issue". What's the point of knowing that Mojang is working hard to deal with this obvious controller bug if they just leave this issue to gather dust?

I've always wanted to play MCPE/Bedrock on a controller ever since I tried playing on Java with mods installed. If Mojang do care for the players who play on a controller, then they should've get this issue resolved the moment that @Richard E Collard created this issue.

@Henry Clifton

I'm not a coder, but I agree with you. Not to mention the top pinned message, saying that Mojang are "working hard on fixing this issue". What's the point of knowing that Mojang is working hard to deal with this obvious controller bug if they just leave this issue to gather dust?

I've always wanted to play MCPE/Bedrock on a controller ever since I tried playing on Java with mods installed. If Mojang do care for the players who play on a controller, then they should've get this issue resolved the moment that @Richard E Collard created this issue.

@AquaDynaDan12

You can actually play Bedrock with a controller on PC. It's wild that Bedrock PC has native controller support while Java does not. You can even play MCPE with Mouse & Keyboard.

@AquaDynaDan12

You can actually play Bedrock with a controller on PC. It's wild that Bedrock PC has native controller support while Java does not. You can even play MCPE with Mouse & Keyboard.

Okay, we have already waited enough. If the Bug would be affected on Xbox Controller then it would be most likely fixed. Stop saying your Game Supports Controllers if you added a Feature that makes everything double press. This never happens with other games you can't say you didn't do that on purpose. We just wanna play this awesome game with a controller we bought, that impacts the Player Base and you will definitely loose Players because of it. Please fix it, ask ChatGPT to fix it or go to an older version and copy and paste the old controller pressing code. Literally what the hell

I for one have already removed my Minecraft Realms subscription over this very issue. There is no point in keeping it if I can't use my controller with mobile.

I for one have already removed my Minecraft Realms subscription over this very issue. There is no point in keeping it if I can't use my controller with mobile.

I am noticing this issue with the RIG Nacon MG-X Pro controller as well as the Shaks S5B. I have not, however, noticed this issue when using my Xbox Elite 2 controller, or any other device that calls itself an "Xbox Controller" when paired with my Galaxy Z-Fold 5. After reading other comments, it makes sense that analog triggers seem to the the culprit, as the Elite 2 has trigger locks. I have also noticed failed attempts to eat food when equipped as pulling the left trigger often fails to register an input when on realms. 

I am noticing this issue with the RIG Nacon MG-X Pro controller as well as the Shaks S5B. I have not, however, noticed this issue when using my Xbox Elite 2 controller, or any other device that calls itself an "Xbox Controller" when paired with my Galaxy Z-Fold 5. After reading other comments, it makes sense that analog triggers seem to the the culprit, as the Elite 2 has trigger locks. I have also noticed failed attempts to eat food when equipped as pulling the left trigger often fails to register an input when on realms. 

I left a negative review in the google play store, because I'm frustrated.
For nearly 5 months there are no news, no fix, nothing.
Only (at least) 51 other people that have the same issues and felt the need to upvote this issue.

I left a negative review in the google play store, because I'm frustrated.
For nearly 5 months there are no news, no fix, nothing.
Only (at least) 51 other people that have the same issues and felt the need to upvote this issue.

I would think Microsoft would have the best coders in the world and the fact that their controller input has been broken for half the users for a year is crazy. I also play lego fortnite mobile and have not experienced any issue so it is a Minecraft thing. 

I would think Microsoft would have the best coders in the world and the fact that their controller input has been broken for half the users for a year is crazy. I also play lego fortnite mobile and have not experienced any issue so it is a Minecraft thing. 

GUYS GUYS I FOUND A SOLUTION AND WILL POST AN UPDATE AFTER I HAVE CONFIRMED THIS SOLUTION WORKS 100%!!!

Hello, everyone! I'm so happy to announce that I found a way to fix this issue, it's a little complicated and requires an app from the Google play store (Google play store apps have one of the best antivirus scans which means it's safe) I can confirm this works on the following devices 100% without any noticeable input delay: Google Pixel Samsung Galaxy and more!

Still should work on other devices though but let's start now:

1. Install this app from the play store: https://play.google.com/store/apps/details?id=com.irishin.buttonsremapper or Uptodown here: https://buttons-remapper.en.uptodown.com/android (THIS IS NOT AN ADVERTISING AND I'M NOT SPONSORED OF THIS DEVELOPER)

2. Open the app (obviously, did you think we let it just there)

3. Click the "+" Button

4. Klick the above button "Short and Long Buttons" (Make sure your Controller is connected)

5. At the "Button:" Text click the little arrow and select "other" and press the R2 button on Razer Kishi v2 or RT on Xbox or just the right shoulder Button on your other controllers! (I didn't need to enable long press but if it's not working for you try enabling it)

6. Click the arrow under "Actions:" and select "Button Action (ROOT)" (Note: You don't need to root your device)

7. Repeat these steps starting from 2. And select this time L2 for Razer Kishi v2 or LT for Xbox or just the left shoulder Button on different controllers!

8. Now don't click "+" again, instead click the toogle under "Settings" (I'm not talking about fast turn off) and continue with the instructions!

9. Make sure you go to app informations and select battery, over there click "Allow Background usage" and click it without touching the toogle and select "No Limitation" (may be different on some devices)

10. On devices that use something like Game Booster, I think you need to disable optimization so it works properly.

11. If it doesn't work sometimes just turn it off and on again!

12. For more questions please reply to this comment and sorry for spelling mistakes I wrote this really fast!

For those who are wondering, No it's a Minecraft issues or let's just say coding bug, if this was intentional isn't confirmed but it's easy to fix. The sensitivity is too high which makes it think the button has been pressed 2 times, the solution I provided makes Minecraft think it's only getting pressed 1 time. Basically the controller tells Minecraft hey, someone pressed the shoulder Button... Minecraft gets confused and thinks it's getting pressed 2 times. But with the solution it's like hey, someone pressed the shoulder Button (the app blocks this Input) and overwrites it with it's own input saying "hey, someone pressed the shoulder Button 1 time 1 TIME" Minecraft understands it probably now and the issue is resolved. This is actually all Minecraft's fault for coding it badly!

Hope you understand!

I found a fix on the kishi v2 controller. 

Open nexus app click menu go to controller settings and toggle off "auto xinput mode" then select either xinput or xinput plus and that completely fixes the issue the HID option still seems to do the double click 

I found a fix on the kishi v2 controller. 

Open nexus app click menu go to controller settings and toggle off "auto xinput mode" then select either xinput or xinput plus and that completely fixes the issue the HID option still seems to do the double click 

Wow, I didn't know there's another fix, for those who don't have a Razer Kishi v2 please follow my other fix!

I can't see the toogle for Auto x-input mode, is it not on Android yet?

@Blitz I'm trying your solution as I do not have a Kishi v2. After I downloaded the 'Buttons Remapper' app > Click on the '+' button > 'Short and Long Buttons' but then I dont see a "Button:" action. I see "Key:", "Action:" and "Active In". My controller is connected while I'm doing this, I'm navigating through the app and clicking the buttons with the actual controller. Any ideas on what I'm missing? 

@Blitz I'm trying your solution as I do not have a Kishi v2. After I downloaded the 'Buttons Remapper' app > Click on the '+' button > 'Short and Long Buttons' but then I dont see a "Button:" action. I see "Key:", "Action:" and "Active In". My controller is connected while I'm doing this, I'm navigating through the app and clicking the buttons with the actual controller. Any ideas on what I'm missing? 

@diamianos sorry, I have the app in German, seems it's key and not button!

Thanks for the reply, I did get instruction #5 working.

Did you pay for the app? I'm not seeing 'Click the arrow under "Actions:" and select "Button Action (ROOT)" or "Settings" to allow background usage. 

Thanks for the reply, I did get instruction #5 working.

Did you pay for the app? I'm not seeing 'Click the arrow under "Actions:" and select "Button Action (ROOT)" or "Settings" to allow background usage. 

Sorry maybe I wasn't clear enough in my post the auto xinput toggle is located in the controller options within the app that comes with the kishi controller it's called the razer nexus app. You want that toggle switched off and select xinput or ximput plus. The HID option is the one that causes the double click so it seems like maybe minecraft is auto selecting HID when that toggle is on auto which is weird because ximput is a Microsoft thing made for the Xbox controller 

Sorry maybe I wasn't clear enough in my post the auto xinput toggle is located in the controller options within the app that comes with the kishi controller it's called the razer nexus app. You want that toggle switched off and select xinput or ximput plus. The HID option is the one that causes the double click so it seems like maybe minecraft is auto selecting HID when that toggle is on auto which is weird because ximput is a Microsoft thing made for the Xbox controller 

@stromdrum I'm not seeing any x-input options

@diamianos, sorry, I'm talking about these arrows (see screenshot)

it looks like this on the nexus app for the kishi v2 maybe it's different in German? 

it looks like this on the nexus app for the kishi v2 maybe it's different in German? 

@stormdrum is that new? I'm not seeing this Option at the moment maybe it's coming later to Europe. Still thank you for showing me what to do!

I'm very happy to see that the months are passing and I don't see a corrective update for this problem. This makes me lose the desire to continue playing this game, which was my favorite.

 @stormdrum do you have the Razer Kishi v2 or razer Kishi v2 pro. Because Reddit says it's not available on the not pro model. Please let me know!

Oh, yeah it's the v2 pro I'm sorry I thought it would be the same for both

Oh, yeah it's the v2 pro I'm sorry I thought it would be the same for both

Same, I gave up hope and cancelled my realms subscription about 2 months ago. No point in paying for a game that doesn't work with my main method of playing it. Also left a negative review on the google play store detailing why. If enough people leave negative reviews on the play store they may eventually do something about it. Its not reasonable to have to do workarounds to play a game that should work as is as advertised. 

Same, I gave up hope and cancelled my realms subscription about 2 months ago. No point in paying for a game that doesn't work with my main method of playing it. Also left a negative review on the google play store detailing why. If enough people leave negative reviews on the play store they may eventually do something about it. Its not reasonable to have to do workarounds to play a game that should work as is as advertised. 

@Diamianos did my solution not work for you? I can help you!

Hey Blitz, unfortunately not. I got past Step 5 but now I'm not seeing 'Click the arrow under "Actions:" and select "Button Action (ROOT)" on Step 6 or "Settings" to allow background usage on Step 9. Not sure if those settings are in the paid version of the app or not because I didn't pay for it.

Hey Blitz, unfortunately not. I got past Step 5 but now I'm not seeing 'Click the arrow under "Actions:" and select "Button Action (ROOT)" on Step 6 or "Settings" to allow background usage on Step 9. Not sure if those settings are in the paid version of the app or not because I didn't pay for it.

@Diamianos the app is free, do you have an app where I can message you? Like discord, Twitter/X ect. Because there I can send screenshots and everything or even a video without needing to send links!

I send you a request with my name French Fries Guy and username iam best (Ik it sucks)

@Blitz thanks for the help. I can confirm your workaround fix is working! If only the devs could put some effort into fixing this so we didn't need to do this type of workaround.

@Blitz thanks for the help. I can confirm your workaround fix is working! If only the devs could put some effort into fixing this so we didn't need to do this type of workaround.

I have a Kishi v2 and I could not find the controller settings in the menu where it is in @Stormdrum 's screenshot however I was able to follow @BlitzGuitar657 's instructions and I am able to open doors and place blocks now! I really don't like recommending that my friends and family grant the "Accessibility" permission to the app though so hopefully Mojang and fix this soon now that they know about this workaround.

Hey, @Cookie Wookie_7! Great the solution worked! Google Play Store Apps are usually safe and secure! If I'm not mistaken the App is Open Source which means the code is public and everyone can see it, which means people can see if there is malicious code! Also about the Razer Kishi v2, unfortunately only the Razer kishi v2 pro is supporting at the moment. I hope Razer will add it to the regular one too!

I found a much simpler solution than the one I saw in the previous comments. You just need the official app for your controller, which probably already comes with an option to map the keys. Use the app to change the L button to L2, and L2 to L. Now open Minecraft and in the "controller" tab, change the "open/place blocks" from L2 to L, and the "swap items to the left" from L to L2. 

It worked with my 8bitdo pro 2, and like I said, I only needed the official 8bitdo app. This is probably a Minecraft issue, it can happen in other older games that don't support pressure triggers, but i think it's not an Android issue, as games that support this technology work perfectly well. 

@oGuilhermeAG your solution is simple and easy but unfortunately not many Controllers have these mappings option or even an app like yours. Also you need to change it everytime you play another game is kinda annoying...

Holy crap can you fix this already. I literally bought a Razer Kishi for playing Minecraft on my phone and can't even play it anymore... Like there's no way it's so hard they can't fix it in 10+ versions.

Holy crap can you fix this already. I literally bought a Razer Kishi for playing Minecraft on my phone and can't even play it anymore... Like there's no way it's so hard they can't fix it in 10+ versions.

@Henry Clifton check my solution for this!