Proximity sensor active during phone call with headset

As a configuration, maybe. As a default that would be a bad idea. Most of the times I'm on the phone, using a Bluetooth headset, I keep the phone in my pocket, and not having a proximity lock could present some interesting events.

@Mohjive: Having the phone in a pocket is a separate case as the display stays off as long as the proximity sensor is covered. The blank-due-to-proximity kicks in after the call has been answered and the display is on.

@spiiroin: I don't see what's different between what you said and what was said previously.

I could expand my use case. Sometimes I answer the call with the headset, and keep the phone in my pocket, but sometimes I pick the phone up, answer the call and put it back into my pocket. Even in the latter case I want the display (and touch) to be disabled by the proximity sensor. I would like the proximity sensor to always disable the screen/input.

@Mohive: Generally: the display will not turn on while the ps is covered, other that that the proximity state does not matter -> any part of display can be poked without it suddenly blanking. Exception: active call, no speaker or headset -> display turns on/off based on the proximity (assumed=at-ear) state.

Proximity blanking occurs with speaker/headset = deviation from intended behavior = bug. Someone wanting to keep/extend the "faulty" behavior = new feature, possibly opt-in via settings.

@spiiroin: that assumes that I knew that the proximity sensor should be disabled during a call with the headset was the intended behavior. That information was new to me.

But I guess that is ok, as long as the display does not wake as long as the proximity sensor is covered. I've learned to turn of the display using the on/off switch before putting it back into my pocket during a call, and as long as it stays of I'm fine with that.