hudamalmsteen / csipsimple

Automatically exported from code.google.com/p/csipsimple
0 stars 0 forks source link

program crashes, when phone was sleeping #1313

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Sorry if this is a known problem. i read somth about it somewhere, but couldnt 
find it anymore. so better post it again:

What steps will reproduce the problem?
1.leave the phone for a while, until it goes to sleep
2.wake it up by disabling the keylock - i.e. drag a bar to the other side
3.the client will register. if i call this client from another phone the call 
will arrive at the mobile, the window will pop up but if i accept the call it 
will crash the client.

What is the expected output? What do you see instead?
the client should set the call up, but crashes instead. i have to start the 
program again. after that it works fine again.

What version of the product are you using? On what operating system?
I am using this nightly: CSipSimple-r1035-tls. This issue seems to be common in 
all of them.
I am using Android 2.3.3 on htc wildfire cyganomod 7.0.3 

Please provide any additional information below.

The phones are connected through the same wifi. I have added a logfile which 
shows the call.
thanks for your support :)

Original issue reported on code.google.com by automate...@gmail.com on 7 Oct 2011 at 3:23

Attachments:

GoogleCodeExporter commented 9 years ago
Hi thanks for feedback.

Version 1036 may fix a lot of issues, so worth to try it :).

However this one seems slightly different. It sounds it tries to launch an 
obsolete method. Can you check this setting and let me know which is the value 
on your device :
=> Settings > Media > Thread count. (Before, you have to switch to expert 
setting mode if not already done : Settings [press menu key of the phone] > 
Switch to expert mode).

I'll do a pass on tls build with new implementation of timers next week.

Original comment by r3gis...@gmail.com on 7 Oct 2011 at 5:08

GoogleCodeExporter commented 9 years ago
Will do :)
The value you asked for is: 3.

Original comment by automate...@gmail.com on 7 Oct 2011 at 5:41

GoogleCodeExporter commented 9 years ago
Set 0 instead. 
It should not be used anymore with the new timers approach. Did you changed 
that manually? Or did you use the restore feature? 

Restore feature should be safe regarding that but I could have missed 
something. 

Original comment by r3gis...@gmail.com on 7 Oct 2011 at 6:19

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1037.

Original comment by r3gis...@gmail.com on 8 Oct 2011 at 2:53

GoogleCodeExporter commented 9 years ago
Ok, will do. '3' was set by the program itself.
Maybe because i am installing the new build over the old one without 
uninstalling?

On the first try setting zero made it worse unfortunately. But will install the 
new revision first and the come back to this.

Original comment by automate...@gmail.com on 8 Oct 2011 at 9:31

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1039.

Original comment by r3gis...@gmail.com on 10 Oct 2011 at 8:19