Process android.process.acore is not responding

[GoogleCodeExporter]

NOTE: This form is only for reporting bugs. For problems, questions, or
comments, please visit:  http://groups.google.com/group/sipdroid-users

*************************************************
* Read the FAQ                                  *
*    Check if the bug has already been reported *
*        No doubles please                      *
*************************************************

Did you carefully read above and decide this means of communication is 
the
right for your notice? Don't just list an incompatible SIP server or
device, please. Try to look behind the scenes if you like to
contribute here. Thanks!

--
What steps will reproduce the problem?
1. Make or receive a call via sipdroid
2. When on a call, the proximity sensor should lock the screen
3.

What is the expected output? What do you see instead?
Expect to recieve or make a phone call with communications in both 
directions.
Instead, media is only bidirectional for 2 seconds, after which sipdroid
appears to stop transmitting packets.
Once phone call is terminated, either by hanging up sipdroid, or by the far 
end party hanging up, dialer application is no longer available.
Message: "Process android.process.acore is not responding> Force close or 
Wait"
Force close allows access to the home screen again, but the operation of 
the phone is affected. Calling my sim card number from another phone, I 
get no audible ringing, just vibration alert. The dialer is unavailable until a 
reboot of the phone.

Before upgrading to 1.3.13 or 1.3.14, sipdroid was working very well with 
PBXes.

Sipdroid affects the operation of the proximity sensor. Using sensors test, I 
find the proximity sensor fails to respond. When sipdroid is not installed, 
this is not the case.

What version of the product are you using? On what operating system?
Sipdroid 1.3.14, Android 1.5 on Samsung Galaxy i7500 Phone

Which SIP server are you using? What happens with PBXes?
I am using PBXes and have a sip trunk to PennyTel.

Which type of network are you using?
3G 900Mhz / 2100MHz  Network

Please provide any additional information below.

Original issue reported on code.google.com by timefan...@gmail.com on 20 Feb 2010 at 4:00

[GoogleCodeExporter]

I checked out r451(which is 1.3.11) from the svn today. I built and loaded this 
on to my 
phone, and I do not have the issues I listed above. It appears to work 
correctly now.
So there seems to be a regression introduced in one of the revisions after that.
Could you provide the official apk's for the other versions? It makes it easy 
to test each 
of the versions.

John

Original comment by timefan...@gmail.com on 20 Feb 2010 at 6:18

[GoogleCodeExporter]

Just to clarify, the proximity sensor problem didn't go away, but I noticed 
there was an 
issue listed earlier and an explanation as to why functionality is not present 
and I 
understand that. I also used the built in samsung command to test the sensors 
and they 
work, so I no longer think sipdroid is the culprit for that, since sensors work 
 when 
someone calls my SIM number and the regular phone stack handles the call.

I guess its something that has happened in the codec refactoring that is 
causing my 
issue.

Original comment by timefan...@gmail.com on 22 Feb 2010 at 9:47

[GoogleCodeExporter]

Which codec have you been using when you got the "not responding" message?

Original comment by pmerl...@googlemail.com on 30 Mar 2010 at 12:50

• Changed title: Process android.process.acore is not responding

[GoogleCodeExporter]

Running N1 with 2.2.1 unrooted.
1.5.7 Beta 

When I enable STUN SIPdroid not responding and eventually comes back after two 
waits.
Dialing with native dialer very slow to not working
Turn off stun, works fine and quick.

Original comment by br...@3dprinting.co.nz on 13 Oct 2010 at 7:12