I started using an Xbox One controller with my phone to play Minecraft. When building in my Creative world, I noticed that my phone was vibrating whenever I broke a block using the controller for input, even though I had disabled vibration by turning off the "Destroy Block (vibrate)" option under Touch settings. After extensive testing, I confirmed the following things:
Breaking blocks in Creative mode with a controller will always cause vibration, even when "Destroy Block(vibrate)" is turned off.
Breaking blocks in Survival mode with either input method will only work when breaking certain blocks (crops, flowers, etc. cause vibration; dirt, stone, etc. do not), regardless of whether "Destroy Block(vibrate)" turned on or not.
Touch input in Creative mode appears to be the only input method that responds properly to the "Destroy Block(vibrate)" option.
EDIT: I do not currently have a way to use mouse/keyboard with my phone, so I did not test that as an input method. Further investigation may be required.
Linked issues
is duplicated by 17
relates to 2
Attachments
Comments 19
Just in case it helps...
When I turn off the "Destroy Block (vibrate)" setting in Minecraft, my phone still vibrates when blocks are destroyed when I play using a DualShock 4.
Prior to update 1.16, some blocks (torches and flowers for example) did this but not all blocks.
Since 1.16, every block destroyed causes vibration.
I have a Samsung Galaxy S9+, model SM-G965U.
I've attached a screenshot of my phone's software info.
[media]I am almost waiting two years for this problem to be solved. And there is still no solution for that. I've tried everything: disabling all vibrations system wide, disabling vibration in touch setting, rooting my devices and so on but still when I connect any controller to the devices and want to play Minecraft my phones are still vibrating when I destroy a block. I am wondering how difficult it could be to just implement an option into the setting so you can turn of vibration when a controller is connected?
I mean I know that you are busy implementing updates and stuff but come on guys that's just a little setting which will have a big effect. Please let us enjoy your hard work you put in this game. I am sure everyone appreciates it including me. Thank you Mojang Team.
I have a fix for this, may sound a little involved but it does work, and works for any app, without affecting vibration anywhere else on your phone, using the android official developer tool ADB. Actually fixing it is 1 line, step 11, and the first 10 steps are getting adb working on the same phone it's affecting using Termux, a famous and beloved android terminal app (you can google to ensure it's safe if you like.)
There are a thousand tutorials online to do this with a second computer attached via USB to your phone, which is how the system's traditionally used, so you can skip steps 1-10 and just do 11 if you use those, (Google "get adb shell",) but these steps mean you can do it without any device other than your phone. It looks like a lot of text but I've tried to explain it in as much detail as possible so even non-techy people can follow along, and it's super quick to actually do if you follow the steps to a T 🙂
Note: never add quotation marks, I've used sporadically which is probably confusing. If I say " type or hit" it means to type and then hit enter.
If ppl need pics or w/e I'll be happy to add em
Step 1) get Termux from the play store, open it
Step 2) type "pkg install android-tools" & hit enter. You might have to hit "Y" to confirm. This will install ADB into termux
Step 3) You'll need to enable developer options on your phone by going to settings > about phone and tapping "build number" 7 times quickly, you'll get a little alert telling you developer settings are enabled
Step 4) we're going to use the same phone to act as the other computer running adb on itself, instead of having another computer operate on it. So go to settings > system > developer options > enable "wireless debugging", click "allow" to let devices on your local network request access. This looks scary but is completely safe, cos you need to enter a code to authorise anything connecting anyway
Step 5) get the wireless debug settings and termux app in multi window mode, so both apps are on top of each other on the same screen at the same time. This isn't optional! Using another computer the traditional way its expected you'd keep the settings page open while connecting, so if you switch away normally the passcode you need resets. To do this, hit the button to switch apps, and press the circle above the app on one, hit "split top", then select the other app. If this is confusing, just google " android mult-window" you'll see what I mean
Step 6) on the wireless debug settings menu, hit the button that says " pair device with pairing code". It will give you an number that looks like 192.168.0.10:12345 . Note that this is DIFFERENT to the similar number on the settings screen before you hit the button. We'll use this on the next step, but replace the number before the : with the single word "localhost". So in the example it becomes localhost:12345. You'll also see a passcode that looks like 567123, we'll need that too
Step 7) back on termux, type " adb pair localhost:12345" (replace 12345 with the correct number) it will ask you for a pairing code. Type the second number (567123 in the example.) You should see something saying "successfully paired to localhost"
Step 8) go back to the wireless debug settings, the little window with the pairing code should have closed. If it hasn't press back once. You'll notice that on the page, under "device name" there's another number that looks like 192.168.0.10:54321, once again we'll change this to "localhost:54321". Note the second / port number is different from the one from before!
Step 9) go back to termux, type adb connect localhost:54322 (using the new number.) You should get a notification saying "wireless debugging connected"
Step 10) type "adb shell". This will change the new line slightly and means you can issue development commands to your phone. We'll use this to turn off vibration for Minecraft (woot woot!)
Step 11) type " appops set com.mojang.minecraftpe VIBRATE ignore" (case sensitive) immediately after this, vibration should be disabled for Minecraft and Minecraft only. You can use this exact process for any other app, you just need to find out the package name and replace com.mojang.minecraftpe with it
CLEANUP) it's a really, really good idea to turn off wireless debugging when you're done. Again, the risk of misuse is vanishingly small, but it's better to have no risk at all. Just turn the slider back off. If you're unlikely to use developer options again, you can just slide that back off too. You can always redo it again later if you need 🙂
And yes lol it is absurd that I need to recommend dev level device tweaking to solve a problem as trivial and dumb as this after like a decade of maturity for one of the biggest games in history. Waddayagonnado
Sorry for disturbing but I would like to ask you another question@unknown My phone can't run Termux and I don't have a PC, do you have any other solution
Affects 1.12. Tested with DualShock 4 wireless controller