#235 Proximity sensor on HTC Legend 2.1 is not released

[Anonymous]

Originally created by: phil.med...@gmail.com
Originally owned by: r3gis...@gmail.com

On version -36, the proximity sensor works with my Legend (ie disables screen when phone is close to my head) while csip is in focus, however, after I exit back to the main screen, the proximity sensor is still activated. If my thumb covers the sensor as I swipe down the status bar, for example, the screen is turned off.

Also, when testing for reproducibility of this, I found out that the proximity sensor doesn't work at all in -34. Hadn't noticed this until now.

[Anonymous]

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

Indeed feature to use the proximity sensor that turn off the screen is new in -36.
Previously it was just adding an overlay.

Did csipsimple exit call screen with a crash or a normal end call?
I'm interested in logs anyway (follow the wiki page on how to collect logs).

[Anonymous]

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

Indeed feature to use the proximity sensor that turn off the screen is new in -36.
Previously it was just adding an overlay.

Did csipsimple exit call screen with a crash or a normal end call?
I'm interested in logs anyway (follow the wiki page on how to collect logs).

Labels: -Priority-Medium Priority-Critical
Owner: r3gis.3R
Status: Accepted

[Anonymous]

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

Sorry for duplicate I'm in travel and poor connection here ;).

[Anonymous]

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

Same here and sometimes I see the warning: CsipSimple (process com.csipsimple).
This warning is shown also when the app is closed, I use csipsimple only for outgoing call.
In this version while on call the icon "Phone speaker is mute" is shown and after the error, it's still present.

[Anonymous]

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

The error (anr) appear while you are in call?
If so the fact that proximity sensor mode, ringer mode (silent : this is the signification of what you get in notification bar), but also probably wifi sleep mode are no reset to their previous value is just a side effect of the crash there is while in call (tear down of the sip call is never done)

So the good thing to solve is the cause of the anr you get. Since if everything is fine tear down (when call screen and audio are cleanly released) will release the proximity lock.
Unfortunately this logs are not old enough to show me what is happening before anr.
I would be interested in the codec actually in use when you get this anr.

[Anonymous]

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

I hope this log is usefull.
The error appear, before the call(gsm call too), when the app is not started, during the call and closing the call.
I use the gsm codec, the quality is good (3g and wifi).

[Anonymous]

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

In the first log the error appeared during the call.
In the second one, the error screen appeared after the call (so proximity sensor and ringer mode were ok)

[Anonymous]

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

Thanks for this log.
It will help me a lot.
I'll keep you in touch with my progress on this point.

[Anonymous]

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

https://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-36-NotAlsa.apk

Can you try this one and let me know if it helps. I changed when the proximityWakeLock is released. (You should probably uninstall previously installed version)

[Anonymous]

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

The app seems ready for the market :-)
I have not noticed differences about issue 211.
For my Legend with your default audio configuration and gsm codec on 3g or wifi, audio is good as in previous version.
Perhaps an occasional problem on specific configurations.

Thanks

[Anonymous]

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

(No comment was entered for this change.)

Status: NextRelease

[Anonymous]

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

(No comment was entered for this change.)

Status: Verified