abdallahynajar / sipdroid

Free SIP/VoIP client for Android
GNU General Public License v3.0
0 stars 0 forks source link

Call not ended properly #152

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
Can't guarantee that this will reproduce the problem; but it happens to me
at least 5 times today.
1. Somehow using sipdroid that initiate a call through GSM (i.e. calling
the phone's voicemail through sipdroid)
2. Reject the GSM call (i.e. I hang up my phone so that I can access the
voicemail) while sipdroid still calling.
3. After finishing the sipdroid call (through the back button), strange
things happens: the notification bar froze; screen timeouts after a few
seconds (even though in my setting, timeout is 2 minutes); reactivating the
screen does NOT go through the lockscreen even though it normally should.
In short, the phone seems to be in a state where it is still on a phone call.
4. Only ways to fix it are 1) reboot the phone. 2) kill sipdroid, dialer,
and dialer storage through some kind of task manager, then things are
restored to normal (i.e. notification bar works, screen does not timeout
after a few secs, etc.)

What is the expected output? What do you see instead?
Phone call should be properly terminated and restore phone to a normal state.

What version of the product are you using? On what operating system?
sipdroid 1.1.1. Donut (cyanogen build). I don't have this problem before
upgrading from sipdroid version 25.

Which SIP server are you using? What happens with PBXes?
Gizmo.

Please provide any additional information below.

Original issue reported on code.google.com by xinl...@gmail.com on 4 Oct 2009 at 8:33

GoogleCodeExporter commented 8 years ago
I have the exact same issue - at end of call, screen goes blank and I can't 
hang up; power button gives me only option of changing, and that means I have 
to reboot the phone.

Original comment by ekan...@gmail.com on 14 Dec 2012 at 12:58