Closed GoogleCodeExporter closed 9 years ago
I am having the same issue, both on Wifi and 3G.
Original comment by christia...@gmail.com
on 3 Mar 2010 at 1:10
Me too...
...but it saves battery...
Original comment by erv...@gmail.com
on 4 Mar 2010 at 12:04
Does it really? The Wifi is in 'Never sleep' mode, so WiFi is on even if
SIPDroid is not.
Original comment by dennised...@gmail.com
on 4 Mar 2010 at 1:45
I logged this (as issue 333) several weeks ago and there's been no action on it
since. I downgraded to
3.12 for a while but re- upgraded to 3.14 since there are several bugs with
3.12 (Mic gain) that are worse
than setting my screen time out to half hour. Ideally I'd like to be able to
use 3.13 which worked well.
There may also be a microphone gain problem with 3.14 on the nexus one but
since I don't have 3.13 to
test against, I can't be sure...
Barry
Original comment by fixitisa...@gmail.com
on 7 Mar 2010 at 2:04
[deleted comment]
Issue 404 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 7 Apr 2010 at 11:18
Original comment by pmerl...@googlemail.com
on 1 May 2010 at 9:53
Original comment by pmerl...@googlemail.com
on 4 May 2010 at 2:07
After upgrading to the version that should include the fix, I still have the
error.
Can someone verify that it is indeed the case?
Original comment by christia...@gmail.com
on 4 May 2010 at 3:42
I have installed 1.5.1 beta on HTC Legend(Android 2.1) and there is still this
problem.
I am not using mobile internet, I have only wifi.
There are 3 parts on the problem:
1) Sipdroid is online - waiting for the calls.
2) Outgoing calls.
3) Incomming calls.
Disconnecting of wifi happens only in points 1 and 3. Incomming calls are
disconnected after few minutes.
Outgoing calls are never disconnected. You can talk even hours without problem.
I would say that Sipdroid use any trick or system call to disable disconnect of
the wifi during outgoing calls. The trick should be used also while incomming
calls or even better for whole live of sipdroid.
Cheers
Dusan
Original comment by dusan.kr...@gmail.com
on 10 Jun 2010 at 8:18
I'm having the same problem. So that makes two of us who have reported this
bug as "NOT FIXED".
Running sipdroid 2.0.1 beta.
Phones tested: T-Mobile G1 (Dream) and T-Mobile MyTouch 3G (Original,
Sapphire). Both are 32B phones.
Both phones are rooted, running Android 2.2.1 via the Cyanogen Mod 6.1. They
are both running the .0013d SPH with the latest .28 radio drivers.
The PBX is Asterisk. The problem happens on WiFi and on 3G too (I think... 80%
sure about 3G, need to test again). It also happens using either TCP or SIP as
the transport.
I'm not certain but I don't think I saw this when I was running my phones
through OpenVPN. Maybe OpenVPN was keeping the channel open for me... gotta
play with it some more.
TLDR;NOT FIXED.
Original comment by dereks...@gmail.com
on 20 Dec 2010 at 12:58
There is a reported workaround. I am testing it now but please try this.
Do NOT use the Sipdroid setting "Wireless > Control WiFi Power". Leave that
unchecked at all times. It's broke.
Then go into the phone's native settings, Home > Settings > Wireless & Networks
> Wi-Fi settings > Menu [Button] > Advanced > Wi-Fi sleep policy > Never. If
it's already set to Never then change it, save it, come back and put it to
Never. That should keep the Wi-Fi turned on all the time and, thus, able to
receive SIP calls.
However, there is more to this bug. According to bug #506 if you change any of
the Sipdroid network settings (such as "Use Wi-Fi", "Use 3G", or "Control Wi-Fi
Power") then Sipdroid will annoyingly re-set the Wi-Fi policy back to default,
meaning, go to sleep (and miss SIP calls). So, once you set the WiFi sleep
policy, don't touch the Sipdroid settings.
IMHO, a project admin should merge bugs #354, #506, and #409 into a single
issue called "Sipdroid Wi-Fi management is broke". They are all the same basic
problem, and probably in the same block of code. Bugs #354 and #506 have both
been incorrectly marked as "Fixed", and bug #498 has no owner. This has been
an open problem since March 2010.
(I'm am going to post this workaround to all three bugs. I apologize for the
duplication but I think anyone who Googled and got to any one of those bugs
would want to have this info. One commenter wasted a week troubleshooting his
missed calls due to this issue.)
P.S.> As an aside, I suspect that the 3G network proxies incoming TCP
connections for the phone. That's probably why 3G doesn't have this problem.
And, that's probably why the battery lasts 3x longer with TCP over UDP -- the
3G network will hold onto an incoming TCP connection on behalf of a phone, wake
it up from the cell tower, and then forward on the connection. Wi-Fi routers
don't do that.
Original comment by dereks...@gmail.com
on 20 Dec 2010 at 1:41
Original issue reported on code.google.com by
dennised...@gmail.com
on 3 Mar 2010 at 7:17