MCPE-4812Screen is glitching its self out... Again!
Automatic movement/areas of the screen become untouchable after holding it there for a while (e.x. moving forward).
Samsung Galaxy S3 Mini & sometimes Motorola DROID RAZR (MAXX, maybe?)
Watch the video to spot these things:
- Jittery, shakey touch movement despite not really having a shakey hand,
- The game stopping touch input suddenly when mining,
- Unlike previously, this does NOT affect movement, player rotation, or any other button.
Created Issue:
Screen is glitching out.
Sometimes, when I move/fly, the screen buttons disappear for a consecutive, split second disappearing of the gui, including the buttons. Probably has to do with the lag;
Sometimes, when I move/fly, the screen buttons disappear for a consecutive, split second disappearing of the gui, including the buttons. Probably has to do with the lag;Automatic movement/areas of the screen become untouchable after holding it there for a while (e.x. moving forward).
Automatic movement/areas of the screen become untouchable after holding it there for a while (e.x. moving forward).
Automatic movement/areas of the screen become untouchable after holding it there for a while (e.x. moving forward).
Samsung Galaxy S3 Mini & sometimes Motorola DROID RAZR (MAXX, maybe?)
Screen is glitching its self out...
Automatic movement/areas of the screen become untouchable after holding it there for a while (e.x. moving forward).
Samsung Galaxy S3 Mini & sometimes Motorola DROID RAZR (MAXX, maybe?)
Automatic movement/areas of the screen become untouchable after holding it there for a while (e.x. moving forward).
Samsung Galaxy S3 Mini & sometimes Motorola DROID RAZR (MAXX, maybe?)Watch the video to spot these things:
- Jittery, shakey touch movement despite not really having a shakey hand,
- The game stopping touch input suddenly when mining,
- Unlike previously, this does NOT affect movement, player rotation, or any other button.
Screen is glitching its self out... Again!
Cleaning up old issues, please reply if affecting 0.9.3
This issue NEEDS to be reopened...
I am not the only one with this issue.
Updated for 2019's version (rather than making a new issue; sorry if this is redundant to do)