[MCPE-17659] Touchscreen Sensitivity always resets even it is customized by the player Created: 24/Oct/16  Updated: 21/Nov/17  Resolved: 21/Nov/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.16.0, 1.0.0
Fix Version/s: 1.2.3.6

Type: Bug
Reporter: John David Luna
Resolution: Fixed Votes: 2
Labels: None

Attachments: PNG File Untitled.png    
Issue Links:
Duplicate
is duplicated by MCPE-18504 Too much sensitivity Resolved
Confirmation Status: Confirmed
Platform: Android
CHK:
ADO: 39306

 Description   

When you play the latest version of minecraft, (0.16.0) maybe you want to customize your own sensitivity on your touchscreen.You've made it and until you played it again. But the sensitivity turns backs to normal! (0.30 Sensitivity) Then you go to the settings and then you see that it is on your customized Sensitivity!

Please fix it. I also experience this bug.

Phone used: Cherry mobile Spin 2
Laguna, Phillipines



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 21/Nov/17 ]

Fixed in an earlier version.

Comment by Ken Grant [ 19/Nov/16 ]

Same or similar issue on the iPad Pro, iOS 10.1.1. Touch sensitivity resets to around .3 every time the app is closed, even though sensitivity shown in settings is does not change. Workaround is to change sensitivity every time app is opened. This was first observed with one of the 0.15 releases in July or August, and has persisted through the latest 16.2 release.

To recreate:
Set touch sensitivity to 1
Movement responds as if sensitivity set to 1
Exit app
Close app
Open app
Movement responds as if sensitivity set to .3
Open settings
Sensitivity appears to be set to 1
Change sensitivity to any value
Return sensitivity to 1
Movement now responds as if sensitivity is set to 1

Comment by [MCPE Helper] Aspergerian [ 26/Oct/16 ]

I had a similar problem too, this started in the beta for me (sensitivity was manually put to 70, when loading a world it feels like 30 but the sensitivity was still at 70).

Generated at Sat Jan 11 15:16:19 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.