#764 Screen does not turn off during call, facial contact results in random screen input responses

[Anonymous]

Originally created by: nicholas...@gmail.com

What steps will reproduce the problem?
1. Make a call through CSipSimple.
2. When call is connected, put the phone to your ear.
3. Facial contact to the screen results in "touching" the screen, resulting in random disconnects due to contact. Haptic feedback can also be randomly felt due to the facial contact.

What is the expected output? What do you see instead?
The stock dialer accounts for the facial contact and turns off the screen based on the accelerometer, turning the screen on on only when the hand takes away the phone from the face (approx 90 degrees vertically perpendicular to ground) to eye looking level (approx 60 degrees vertically perpendicular to ground). CSipSimple should replicate stock dialer behavior on this aspect.

What version of the product are you using? On what operating system?
0.01-01 [r615]. Android 2.2

Please provide any additional information below.
Unit tested on Motorola Milestone 2. Running Version 62.4.18.A953.AsiaRetail.en.03 Motorola stock ROM

[Anonymous]

Originally posted by: r3gis...@gmail.com

In fact this behavior is expected.

Actually CSipSimple can correctly handle the proximity sensor. However it does not on some devices cause of very good reason. (see issue 548).

Some devices has a wifi mode called PSP mode.
Cause of that the wifi driver/CPU goes in some "bad" mode automatically when screen goes off.
In this mode data packets are not recieved as frequently as it should. That's a mode some manufacturers implemented to improve the battery life. The bad side is that there is no way for developer in android 2.2 and lower to lock this mode.

As consequence the only workaround is to force screen to be on, when on wifi + a device with this behavior.

In android 2.3 there is a way for developpers to prevent this PSP mode and so when you'll be upgraded to android 2.3, you'll see, CSipSimple will just deactivate the PSP workaround so that a true proximity sensor behavior will be used just like it is already done on many other devices.

So that's absolutely not a bug, but something you should be happy to have cause else you'll experiment really poor audio quality ;)

If you want to try without the PSP workaround you could read this wiki page :
https://code.google.com/p/csipsimple/wiki/FAQ#When_screen_goes_off_sound_quality_is_bad
but you'll see, audio will be very poor (or will pledge device).

Status: Invalid

[Anonymous]

Originally posted by: DJVAN...@gmail.com

I have this problem too. But my device- dell streak won't be getting 2.3. The rom developer said they would be going straight to honeycomb. I believe I need the screen to be on during calls though : /

So I'll be on 2.2 for a few months. But can you just add a simple lock button so that the screen stays active but no buttons can be pressed?

[Anonymous]

Originally posted by: r3gis...@gmail.com

Issue 1069 has been merged into this issue.