Don't black screen when on call with speakerphone

[Jean-Baptiste Lallement]

mako #175

The "proximity" sensor (screen turns off when something get close to the phone) should be turned off when loud speaker is on otherwise it's very difficult to interact with the phone and the dialer, or to unlock the phone if the call is long. (it might also depends on where the sensor is on the hardware)

TEST CASE:
1. Open the dialer and place a call
2. Switch on the loud speaker and put your phone flat on the table.
3. Get your hand close to the sensor

ACTUAL RESULT
The screen turns off and user cannot interact with the dialer app

EXPECTED RESULT
Screen stays on.

[Bill Filler (bfiller)]

actually the bug is not with the proximity sensor. The issue is whenever you are on an active call with speaker phone enabled, the screen should not fully blank and the phone shouldn't lock. The screen should just dim but not lock when on an active call

[Michał Sawicz (saviq)]

Is there a spec anywhere that it says that "the screen should only dim"? That would be behaviour different to any other phone out there? Input shouldn't work when proximity is triggered during a call either?

Or by "dim, but not lock" do you mean that it should turn the display off completely, just not lock?

[Bill Filler (bfiller)]

I don't think there is a spec.
I'm comparing to what iphone does. When on a call (with speakerphone enabled or not) and you lay the phone down on the table, the screen never locks. The screen does dim slightly after some seconds but never fully goes black. I think we should do the same. If we can't dim the screen then just leave it fully on.

So I think we have two bugs 1) we turn off the screen completely and 2) we lock the phone

Not sure what you mean about input not working when proximity is triggered during a call?

[Michał Sawicz (saviq)]

Sorry, I mixed it up with a bit with the normal handset use, not speakerphone. So it is related to proximity in that if during a call, it should only turn off completely on proximity, otherwise should stay on but dim.

This can be handled by a powerd request by the dialer app I believe. Same as `powerd-cli display on` does. Not sure if the switch to u-s-c handling brightness brought over the right behavior of dimming but not powering off?

[Michał Sawicz (saviq)]

From my tests it looks like no, u-s-c does not handle this properly, does not dim at all (it's only the complete power-off timeout that should be disabled).

Ah, and that means that unity8 is not really involved and the branch is actually unrelated in that if the screen does not power off, then unity8 wouldn't lock anyway.

[Michał Sawicz (saviq)]

The bug in unity-system-compositor:

`powerd-cli display on` (no "bright") keeps the screen in full brightness state. It should dim as usual, just not power off.

Between u-s-c and telephony-service (?):

The display lock should contain proximity and display on (not bright).

[Andreas Pokorny (andreas-pokorny)]

no change needed so far communication of necessary powerd state changes has to happen through telepathy-ofono

[Olga Kemmet (olga-kemmet)]

There is a related bug: https://bugs.launchpad.net/ubuntu-ux/+bug/1347913