Keeping fingers on the invisible Android buttons makes the screen unusable

Bug #1436273 reported by Michal Predotka
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
John McAleely

Bug Description

I'm using bq phone here.

Steps to reproduce:
1. put your finger on the invisible Android button under the phone screen
2. try to do anything on the screen

Outcome:
The screen does not respond to touch

Expected outcome:
The screen does respond to touch

Short video attached

Tags: bq
Revision history for this message
Michal Predotka (mpredotka) wrote :
Revision history for this message
Michael Zanetti (mzanetti) wrote :

This seems to happen only with the production units and not with the prototypes.

tags: added: bq
Revision history for this message
Michal Predotka (mpredotka) wrote :

Hmm... the video does not work here. Check it on youtube then: https://youtu.be/JqgysF1ukko

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I can reproduce this on a retail unit running r20 image. It doesn't happen on prototype running same r20.

Changed in canonical-devices-system-image:
assignee: nobody → John McAleely (john.mcaleely)
Revision history for this message
Jonathan Cave (jocave) wrote :

Version: ubuntu-touch/stable/bq-aquaris.en r20 krillin

Confirmed on production unit

Changed in canonical-devices-system-image:
status: New → Confirmed
Revision history for this message
John McAleely (john.mcaleely) wrote :

@pat - can you triage this for a milestone please?

Revision history for this message
John McAleely (john.mcaleely) wrote :

I'm working with the OEM in project bug #1438132. I will update this public bug with progress and results as I have them.

Changed in canonical-devices-system-image:
status: Confirmed → In Progress
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

marking it for this week just so ts not lost

Changed in canonical-devices-system-image:
milestone: none → ww13-ota
status: In Progress → Confirmed
Changed in canonical-devices-system-image:
status: Confirmed → In Progress
Changed in canonical-devices-system-image:
importance: Undecided → Critical
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Can someone that is able to reproduce this bug run the following command and paste the output in this bug?

$ cat /sys/devices/platform/mtk-tpd/chipinfo

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

From my production one:-

ID:0x0 VER:0x15 IC:ft5336 VENDOR:ckt (dc)

From my android flashed one:-

ID:0x0 VER:0x40 IC:ft5336 VENDOR:ckt (dc)

Revision history for this message
Michal Predotka (mpredotka) wrote :

On my bq:
ID:0x0 VER:0x15 IC:ft5336 VENDOR:ctk (dc)

Revision history for this message
Richard Somlói (ricsipontaz) wrote :

bq:
ID:0x0 VER:0x15 IC:ft5336 VENDOR:ctk (dc)

Changed in canonical-devices-system-image:
status: In Progress → Fix Committed
Revision history for this message
John McAleely (john.mcaleely) wrote :

When this fix propagates to an OTA, you'll be able to confirm it worked by:

$ cat /sys/devices/platform/mtk-tpd/chipinfo

and then observing:

ID:0x0 VER:0x40 IC:ft5336 VENDOR:ckt (dc)

is reported. Of course, you'll also find the touch screen works properly!

Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.