Touch Problem on MX4

[Ronny Fuchs]

Can't swipe on the left- and rightside

Devise-Information:
current build number: 13
device name: arale
channel: ubuntu-touch/stable/meizu.en
last update: 2016-06-02 05:58:37
version version: 13
version ubuntu: 20160524.1
version tag: OTA-11
version device: 20160331-e143fc2
version custom: 20160504-975-19-6

[Krzysztof Tataradziński (ktatar156)]

Try in terminal:
gsettings set com.canonical.Unity8 edge-drag-width 3
gsettings set com.canonical.Unity8 edge-drag-width 4
and tell if that helps.

[Krzysztof Tataradziński (ktatar156)]

Maybe it's related to bug https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592417

[Ronny Fuchs (fuchsi585)]

thanks, The swipe on the side is easier now but I think it doesn't solve the uncontrollable scoll down and up, but I observe this now. The problem exists irregular.

[Jean-Baptiste Lallement (jibel)]

Thanks for your report. It really looks like a hw problem with the digitizer. Could you reproduce the problem and attach /var/log/syslog and the output of dmesg?

Thanks.

[Ronny Fuchs (fuchsi585)]

a syslog doesn't exists on my phone....

I don't know, if I can reproduce the problem, but the morning always starts the same.

1. alarm clock ringing (two or three times)
2. dekko
3. facebook (sometimes)

Only this morning was the problem even after a time gone. I hope the dmesg.log helps.

[Cédric Bellegarde (gnumdk)]

I can confirm this issue, happen time to time for me while scrolling in apps...

[Ronny Fuchs (fuchsi585)]

here the unity8 log file, maybe it helps

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joachim Van der Auwera (joachim-8)]

I also have this problem in periods. I happened to me me for a couple of weeks two or three months ago, and als the last few weeks. Rebooting always make input normal again. Sometimes it also detects keypresses when there are none, or in a different place (very hard to enter text or to type the unlock pin).

[Ronny Fuchs (fuchsi585)]

I had the problem today three times. Now with syslog.