Open GoogleCodeExporter opened 9 years ago
Issue 735 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 15 Nov 2010 at 7:10
Issue 742 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 17 Nov 2010 at 12:46
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
"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
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
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
Issue 881 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 24 Mar 2011 at 7:18
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
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
Same issue on HTC Sensation 4G with ICS 4.0 rom
Original comment by alexleykin
on 23 Apr 2012 at 6:53
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
[deleted comment]
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
how can i download the sipdroid2.6 beta aversion?
Original comment by jagruti....@inextrix.com
on 30 Jul 2012 at 7:38
Original issue reported on code.google.com by
ctros...@gmail.com
on 9 Jan 2010 at 10:23