Sign in
Skip to main content

Discuss Minecraft's user interface, menus, settings, and input methods. Share feedback on navigation, controls, accessibility, customization, and other features that affect how players interact with the game.

← UI, Input Methods and Menu Options
1
Follow

Controller Deadzone & Trigger Reset Issue (Android)

I’m experiencing issues with controller input in Minecraft Bedrock (Android), especially with analog triggers and joystick deadzones. Trigger issue (LT): Only registers as “pressed” around ~0.7–1.0 input To shoot again (e.g. bow), input must return to 0.0 (full release) Slight resting pressure (~0.05–0.1) is still considered “not released” This causes: Inconsistent hold/release behavior Need to fully lift finger every time Fatigue during repeated actions Analog stick issue: Deadzone feels too large and not configurable Small movements are ignored, then suddenly jump at a certain point This makes precise aiming difficult and inconsistent Lowering render distance (improving FPS) slightly improves input consistency, suggesting input may depend on frame updates. Controller works normally in external testers, so issue appears to be in-game input handling. Suggestions: Add trigger sensitivity / threshold setting Allow configurable release threshold (not strictly 0.0) Add deadzone settings for analog sticks and triggers Improve input stability regardless of FPS
Avatar
Registered User shared this idea

2 Comments

Post a new comment:

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 0
    Registered User commented
    Comment actions Permalink

    Agreed. This is a HUGE issue. The deadzone is set way too high (Have to tilt the joystick too much for any input to register) for controllers and the input latency/delay is insane. This is the only game I have this issue with. We need a setting to change this ourselves or at least an increase in deadzone sensitivity/lowering the threshold needed for input to register, that will allow more precise smaller movements. I'm playing on a z fold 7 and having this same issue, regardless of chunk rendering distance.

  • 0
    Registered User commented
    Comment actions Permalink

    From what I saw on reddit, folks have been asking for this for around 3 years now. I really hope they listen to the feedback and either fix it or implement a setting to change it ourselves!