Blinking screen during the call if you remove the phone from your ear

[Marco Graziotti]

I have a problem with my Meizu MX4 (Arale r6).
During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call.
When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself.

[Launchpad Janitor (janitor)]

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

[Paola (paola87)]

This bug affect me too. Same behaviour.

[Ramin (raminzeb)]

hi there.

I had this problem occur regularly on krillin stable on my bq aquaris 4.5

this was present right up until the latest stable release. it was so often it caused me to install android on the phone as making calls was becoming impossible. most of the time after the call during the flashing the only thing I could do was to hold down power to restart the os.

sonetimes I would call someone and if they didn't answer I would end up leaving messages on their answerphone because I could not hang up due to the flashing.

I'm now back on Ubuntu but the Rc-proposed channel and I don't think I've expereinced it, but certainly had on the current stable.

[Ken VanDine (ken-vandine)]

I've seen this once on my arale with rc-proposed, it's like in a loop of wake events.

[Pat McGowan (pat-mcgowan)]

sounds like a series of invalid proximity events real or imagined

[royden (ryts)]

I too noticed this but a while back. Am on rc-proposed and since sometime in prep of OTA7 this went away, or at least dramatically decreased in frequency.

[Marco Graziotti (graziottimarco)]

Hi Ramin,

if you are affected too on your bq, subscribe the bug at this url:
https://bugs.launchpad.net/bugs/1512100 and add a comment with a detailed
event.

Cheers,

Marco
Il 01/nov/2015 19:50, "Ramin" <email address hidden> ha scritto:

> hi there.
>
> I had this problem occur regularly on krillin stable on my bq aquaris
> 4.5
>
> this was present right up until the latest stable release. it was so
> often it caused me to install android on the phone as making calls was
> becoming impossible. most of the time after the call during the flashing
> the only thing I could do was to hold down power to restart the os.
>
> sonetimes I would call someone and if they didn't answer I would end up
> leaving messages on their answerphone because I could not hang up due to
> the flashing.
>
> I'm now back on Ubuntu but the Rc-proposed channel and I don't think
> I've expereinced it, but certainly had on the current stable.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1512100
>
> Title:
> Meizu MX4 (Arale r6) - Blinking screen during the call if you remove
> the phone from your ear
>
> Status in dialer-app package in Ubuntu:
> Confirmed
>
> Bug description:
> I have a problem with my Meizu MX4 (Arale r6).
> During a call if you remove the phone from your ear, sometimes (not
> always) the screen remains turned off. When you try to push the power
> button to wake up the screen, that starts blinking and it's not possible to
> hang up. The screen remains in that condition even after the end of the
> call.
> When it keeps blinking I try to hold the button down and in few seconds
> the screen turns black and the phone starts working again. Sometimes,
> instead, it starts working again by itself.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1512100/+subscriptions
>

[Ramin (raminzeb)]

hi macro, isn't that URL this URL ? I'm sorry I'm a little confused

[Marco Graziotti (graziottimarco)]

Yes Ramin. I made a mistake. I'm sorry.

Cheers,

Marco

Il lunedì 2 novembre 2015, Ramin <email address hidden> ha scritto:
> hi macro, isn't that URL this URL ? I'm sorry I'm a little confused
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1512100
>
> Title:
> Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you
> remove the phone from your ear
>
> Status in Canonical System Image:
> Confirmed
> Status in powerd package in Ubuntu:
> New
> Status in unity-system-compositor package in Ubuntu:
> New
>
> Bug description:
> I have a problem with my Meizu MX4 (Arale r6).
> During a call if you remove the phone from your ear, sometimes (not
always) the screen remains turned off. When you try to push the power
button to wake up the screen, that starts blinking and it's not possible to
hang up. The screen remains in that condition even after the end of the
call.
> When it keeps blinking I try to hold the button down and in few seconds
the screen turns black and the phone starts working again. Sometimes,
instead, it starts working again by itself.
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+subscriptions
>

[Pat McGowan (pat-mcgowan)]

Powerd log from Ken

The signals are coming from 1:18 which is unity-system-compositor

[Pat McGowan (pat-mcgowan)]

Note the reason code is 3 which is proximity

Ken mentioned he received several message notifications during the call but had not looked at them.
Comment in u-s-c says
Notifications don't turn on the screen directly, they rely on proximity events

[Alexandros Frantzis (afrantzis)]

I am able to reproduce the issue by starting a (fake) call and covering/uncovering the proximity sensor for a bit (some times it can take some time but I always eventually get the problem).

It seems that powerd stops handling proximity events (although the kernel receives them) at some point. Pressing the power key somehow unblocks whatever is that has been blocked, and all queued events are then processed in quick succession. I don't know yet if it's a problem with powerd or some layer below it. Investigation continues.

[Alexandros Frantzis (afrantzis)]

More evidence that this is a problem at a level below either USC or powerd:

0. Build a test program to use and print out events from ubuntu application proximity sensor api (you can use [1] as a starting point, just remove other sensors to reduce irrelevant messages).
1. Use "tail -F /var/log/syslog" to follow powerd messages
2. Start a phone call
3. Start the test program (the one built in step (0))
4. Cover/uncover the proximity sensor, note the powerd output in syslog and the test program output
5. Continue covering/uncovering, at some point (you need to be patient) powerd will stop reacting to proximity events (the screen won't turn on/off). Note how at this point (a) there is no powerd output as a response to proximity in syslog (b) there *are* kernel message about proximity near/far in syslog (c) the test program has also stopped reacting to proximity events (i.e. the sensor api has stopped calling the event callback)

The observed behavior strongly indicates that this is a problem at a layer below powerd. If it was just a powerd issue the test program would continue responding to proximity events.

Note, however, that I haven't been able to reproduce this problem with just the test program running. This suggests (but it's just a speculation at this point) that some additional interaction in powerd (screen on/off?, suspending?) triggers the problem at the lower levels, or at least makes the problem more likely to occur.

[1] https://bazaar.launchpad.net/~phablet-team/platform-api/trunk/view/head:/examples/test_sensors_api.cpp

[Alexandros Frantzis (afrantzis)]

We have tracked down the problem in the Android sensor HAL code and we are currently working on a fix.

[Launchpad Janitor (janitor)]

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

[Alexandros Frantzis (afrantzis)]

The fix for this bug has been committed to our Android code tree. Waiting for this change to be released as part of a device image.

[Pat McGowan (pat-mcgowan)]

Also reported on krillin
Can we ensure device tarballs have been made available with this fix?

[Pat McGowan (pat-mcgowan)]

The commit is
https://code.launchpad.net/~tangxi-team/tangxi/+git/platform_hardware_invensense/+ref/m75_ubuntu

[Pat McGowan (pat-mcgowan)]

Checking if this landed for mx4 and if a similar patch applies to bq devices

[Pat McGowan (pat-mcgowan)]

Keep this bug mx4 specific

[Ethan Chang (ethan.chang)]

Tried rc-proposed #299 image on Arale, I can not reproduce this issue on device.

[Yuan-Chen Cheng (ycheng-twn)]

@ethan, thanks.

[Yuan-Chen Cheng (ycheng-twn)]

the device=20160331-e143fc2 for rc-proposed in version=299.

which is the same as it is in rc channel. So if QA verified it, I think it will be in ota10.

[Roascio Paolo (roa)]

Is this in OTA-10? After the update my phone (BQ Aquaris E4.5) still shows the same issue... Very annoying... I cannot hang up calls.

[Yuan-Chen Cheng (ycheng-twn)]

Oh ya, it was fixed in arale (meizu mx4 ubuntu version).

[Yuan-Chen Cheng (ycheng-twn)]

will open a new bug for bq device soon AFAIK.

[GTriderXC (gtriderxc)]

Is there already a bug for Aquaris? Mine is fully updated and I experienced the problem yesterday(02.05.2016):

https://www.youtube.com/watch?v=GZLGdf8rZSs

[Roascio Paolo (roa)]

As far as i can see, there is no bug for krillin... blinking screen is there after OTA-11 :(

[Pat McGowan (pat-mcgowan)]

Reported as bug #1592059 for Aquaris