Closed GoogleCodeExporter closed 9 years ago
This might be related to issue 625
http://code.google.com/p/sipdroid/issues/detail?id=625
Original comment by xavdouvi...@gmail.com
on 3 Sep 2010 at 1:58
Yes, might be related. I have additional objections: It looks like my Milestone
is consuming lots of traffic while Sipdroid is running. I had an upload of over
4 MB and download of 5 MB in 3 hours without any phone call.
Original comment by michael....@gmail.com
on 3 Sep 2010 at 2:14
I am seeing the same extreme battery draw after upgrading to 1.5.6. I'm using
a Samsung Vibrant (Galaxy S phone) on T-Mobile USA. Android 2.1
Original comment by jsiedli...@stf.com
on 3 Sep 2010 at 5:01
I am also seeing that Sipdroid is constantly re registering. Does not matter if
I'm using Wifi or 3G, every 20 seconds or so it will show the yellow
notification dot and register.
Original comment by jsiedli...@stf.com
on 3 Sep 2010 at 5:04
[deleted comment]
I noticed this problem as well yesterday and today but I thought it was because
this is the first time trying to configure VOIP calling on my Samsung Vibrant.
My Sip provider is SipGate. Also, what are some other reccomended Sip providers
to try because I have only data on my phone and I would like to make it so I
can make calls with VOIP/SIP/or Skype (fat chance in this working now). Thus
far, call quality has been below average due to the other party hearing
multiple echo's of what I'm saying and the 3-5 second delay between me talking
and the other party hearing me.
Original comment by BlackImp...@gmail.com
on 5 Sep 2010 at 12:43
Original comment by pmerl...@googlemail.com
on 6 Sep 2010 at 12:29
I see the same issue again after upgrading to 1.6.0
Original comment by michael....@gmail.com
on 15 Oct 2010 at 12:11
I am using a Samsung Vibrant in Canada on Bell and noticed today that Sipdroid
drained half the battery in a few hours time. The system is constantly
re-registering every 5 to 10 seconds whether I'm on wifi or 3G.
Original comment by merchant...@gmail.com
on 25 Oct 2010 at 9:23
Original issue reported on code.google.com by
michael....@gmail.com
on 2 Sep 2010 at 1:59