search

RohitJPatil / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 1 forks source link

Garbled incoming when screen locks on Nexus One #268

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
NOTE: This form is only for reporting bugs. For problems, questions, or
comments, please visit:  http://groups.google.com/group/sipdroid-users
What steps will reproduce the problem?
1. Register with either Callcentric or Link2Voip, either directly or via
pbxes.org
2. Place a call to 1-425-296-4774+ (the local # version of GOOG 411... for
whatever reason the toll-free version does not show this issue)
3. Respond to the voice prompts in order to keep getting some incoming voice.
4. Don't touch the screen. Wait for it to lock.

What is the expected output? What do you see instead?
Expected output: Voice quality should continue sounding equally good during
the call.
Actual result: Once the screen locks, incoming audio becomes completely
garbled. If I press the unlock button then the audio snaps back to sounding
perfect. Once the screen fades it's garbled again.

What version of the product are you using? On what operating system?
Version 1.2.4 beta on Android 2.1, Google Nexus One

Which SIP server are you using? What happens with PBXes?
Callcentric or Link2VoIP. Same results directly or through PBXes.

Which type of network are you using?
Wi-fi

Please provide any additional information below.
If I keep my finger on the screen throughout the call to prevent it from
going into lock, the call quality remains good. No idea why this is happening.

Original issue reported on code.google.com by ctros...@gmail.com on 9 Jan 2010 at 10:23

GoogleCodeExporter commented 9 years ago 
Issue 735 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 15 Nov 2010 at 7:10

GoogleCodeExporter commented 9 years ago 
Issue 742 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 17 Nov 2010 at 12:46

GoogleCodeExporter commented 9 years ago 
Developers assume there was not user activity while the screen turned off. Thus 
wi-fi powre-save policy got more aggressive in this stage though it had no idea 
about upper-layer apps running. That's why network seemed "blocked" while 
screen off. 

Considering wifi is a greedy battery killer, the scheme is correct in my 
opinion. 
The exception is some apps (or the background service routine) which need 
stable wi-fi connection even in screen-off stage e.g. VoIP SipDroid.

Briefly a solution is to explicitly claim lock the wifi connection in the app 
(or service). And then the wifi driver can properly keep it ative accordingly.

Original comment by wan...@gmail.com on 2 Dec 2010 at 10:11

GoogleCodeExporter commented 9 years ago 
"Considering wifi is a greedy battery killer, the scheme is correct in my 
opinion."

I strongly disagree.

With only Sipdroid running in the background, there is no discernible 
difference in power consumption between PM_MAX (default power management on 
Nexus/Desire, i.e. PowerSave Polling) and PM_FAST (ConstantAwakeMode).

WiFi draws very little power when idling on current chipsets.

Original comment by simonbro...@gmail.com on 2 Dec 2010 at 10:18

GoogleCodeExporter commented 9 years ago 
Quick update: This issue seems to have disappeared on Gingerbread. No more 
problems on CyanogenMod7, at least...

Original comment by simonbro...@gmail.com on 5 Feb 2011 at 2:36

GoogleCodeExporter commented 9 years ago 
Issue is back - symptoms were just lessened greatly on Gingerbread (no dropouts 
any more, just stuttering every few seconds), but it looks like there's a 
solution in sight:

http://code.google.com/p/android/issues/detail?id=9781#c32

If this could also be added to Sipdroid, it'd be great... :)

Original comment by simonbro...@gmail.com on 7 Mar 2011 at 3:57

GoogleCodeExporter commented 9 years ago 
Issue 881 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 24 Mar 2011 at 7:18

GoogleCodeExporter commented 9 years ago 
I have a similar issue on my Evo running rooted stock sense version 2.3.3.  
While in a call the proximity sensor does not turn the screen off when I put 
the phone to my head, and if I press the standby button to turn off the screen 
the other party can hear me, but I cannot hear them.  Im running sipdroid 2.3 
beta with the default pbxes configuration to make calls with google voice.

Original comment by nat.g...@gmail.com on 18 Jul 2011 at 1:54

GoogleCodeExporter commented 9 years ago 
Still present on Galaxy Nexus GSM with 4.0.2 (stock) and 4.0.3 (AOKP).

No word on implementation of the link in my comment above (#106)?

Original comment by simonbro...@gmail.com on 28 Mar 2012 at 9:00

GoogleCodeExporter commented 9 years ago 
Same issue on HTC Sensation 4G with ICS 4.0 rom

Original comment by alexleykin on 23 Apr 2012 at 6:53

GoogleCodeExporter commented 9 years ago 
Thanks for comment #106, we have implemented it into Sipdroid 2.6. So under 
Android 4.0 the screen can be finally left off while talking over Wifi, and 
standby times under permanent Wifi have greatly improved.

Original comment by pmerl...@googlemail.com on 24 Apr 2012 at 7:17

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
After using Sipdroid 2.6 for a few days, I can confirm: The bug is completely 
and beautifully fixed. Great job, and thanks for the hard work!

Original comment by simonbro...@gmail.com on 30 Apr 2012 at 6:29

GoogleCodeExporter commented 9 years ago 
how can i download the sipdroid2.6 beta aversion?

Original comment by jagruti....@inextrix.com on 30 Jul 2012 at 7:38