search

jinzigui / imsdroid

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

MultiLine GUI issues #153

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. start a new call during a call with multiline version
2. do any kind of gui stuff
3. watch it go stuck/wrong

What is the expected output? What do you see instead?
The expected output is a working GUI

What version of the product are you using? On what operating system?
The newest multiline

Please provide any additional information below.
I know this issue sounds a bit vague, but try it yourself, make a new call 
during a call, the gui will act strangly

Original issue reported on code.google.com by matthijs...@gmail.com on 13 Jan 2011 at 12:37

GoogleCodeExporter commented 9 years ago 
Could you please provided a screenshot?

Original comment by boss...@yahoo.fr on 13 Jan 2011 at 5:17

GoogleCodeExporter commented 9 years ago 
Here is one way to produce an error
1. Download imsdroid 356 and put it on 2 Nexus 1's
2. I have this setup: 701/702 for the 2 Nexus phones with imsdroid, 703 for an 
XLite softphone on Windows
3. Call with 701 to 702
4. Pickup the call with 702
5. press the back key on 701
6. press inside the call edit-box
7. nothing happens...

Another thing, how can I hang up the phone/put it on speaker after I press the 
back button on 701? There is no way to go back to the call-screen...

Here is another way to produce an error:
Repeat steps 1 - 4
5. Call 701 with the Xlite 703
6. press the answer call button on 701 a couple of times
7. See ims-droid crash with a dialog box

Further more, I don't really understand what imsdroid understands about the 
concept multi-line, there is no way to destinguish between 2 or more 
running/pending calls, how can I choose to place my call to 702 on hold, place 
701 on speaker etc... 

I hope this provided more detailed info, Matthijs

Original comment by matthijs...@gmail.com on 18 Jan 2011 at 10:24

GoogleCodeExporter commented 9 years ago 
On this note I mean:
7. nothing happens, what I want to happen is see a cursor so I can type a new 
number...

Original comment by matthijs...@gmail.com on 18 Jan 2011 at 11:15

GoogleCodeExporter commented 9 years ago 
First of all please provide information about your Android device, OS version 
and IMSDroid version.

1. In the previous version you had to press on the dialer button to go back to 
the call screen. In this version, as we support multi-line, pressing on the 
dialer button open the "dialer screen as it's allowed to make several calls.
To reopen the call screen you have to slide the "status bar" and click on the 
"in call" icon. Please see the attached image. 
If there is more than one pending call, then the "Pending calls" screen will be 
opened. Please see attached image. From the "pending call screen" you hold or 
resume any call when you select its entry.

2. The edit-box problem has no relation with multi-line. You can open another 
ticket in the tracker.

3. About the crash, you cannot say "See ims-droid crash with a dialog box" 
without sending any log file (I cannot reproduce). Amazing!
Off course if you never hang up your calls and repeat steps 1 - 4 several times 
there will be a problem (Memory issues).

4. "I don't really understand what imsdroid understands about the concept 
multi-line": You are right, we have a real problem :(
The concept is simple: When you are in call and receive/make another call then, 
the current call is put on hold and new one become the active call. At any time 
you can switch from one line to another via the "Pending calls screen". See 
attached image.

Original comment by boss...@yahoo.fr on 18 Jan 2011 at 12:33

Attachments:

GoogleCodeExporter commented 9 years ago 
Also don't forget to attach Wireshark trace if it's relevant.

Original comment by boss...@yahoo.fr on 18 Jan 2011 at 12:36

GoogleCodeExporter commented 9 years ago 
Hi, I managed to get a Wireshark trace from a tcpdump of an asterisk server.

This the situation:
Asterisk = 10.101.2.16
Opensips = 10.101.2.17

X-Lite on Windows      = 107@10.101.2.17
Imsdroid r366 on Nexus = 108@10.101.2.17
Imsdroid r366 on Nexus = 109@10.101.2.17

- 108 calls 109, 109 picks up, sound both ways
- 107 calls 108, 108 rings, still sound both ways between 108 and 109
But, the answer (green) button of 108 stays yellow for at least 5 seconds, and 
this is what I see in the DDMS Log in eclipse of the 108 phone: 
02-09 21:15:11.255: ERROR/AudioRecord(1102): Could not get audio input for 
record source 1
02-09 21:15:11.255: ERROR/AudioRecord-JNI(1102): Error creating AudioRecord 
instance: initialization check failed.
02-09 21:15:11.255: ERROR/AudioRecord-Java(1102): [ android.media.AudioRecord ] 
Error code -20 when initializing native AudioRecord object.
02-09 21:15:11.255: 
ERROR/org.doubango.imsdroid.media.MyProxyAudioProducer(1102): prepare() failed

After that (5 seconds) the call is established and 109 hears 'busy' music from 
asterisk.
Sound between 107 and 108 goes only 1 way: from 107 to 108. And not from 108 to 
107.

- 107 hangs up, call is terminated on 108. 109 still hears 'busy' music, so 
that is good I think.
- 108 resumes the call with 109, I slide down from the top and select Imsdroid, 
I see Call placed on hold. I press the menu button and select Resume. The call 
with 109 resumes but there is only sound 1 way: From 109 to 108, not from 108 
to 109.
- 108 hangs up, and on both phones the call is terminated correctly.

Original comment by matthijs...@gmail.com on 9 Feb 2011 at 2:44

Attachments:

GoogleCodeExporter commented 9 years ago 
Attached above is a txt file of the graph from wireshark.

Here is another example, it uses the same setup as the one above.
(108 and 109 are imsdroid and  107 is X-Lite)

so the same beginning as above,
- 109 calls 108
- 108 picks up and there is sounds both ways
- 107 calls 108 and 108 presses the answer (green) button, but now the button 
gets pressed a lot of times. After a while (6 seconds), this happens in DDMS on 
108:
02-09 21:46:38.445: ERROR/Sensors(85): CAPELLA_CM3602_IOCTL_ENABLE error (I/O 
error)
02-09 21:46:38.555: DEBUG/org.doubango.imsdroid.Screens.ScreenAV(1571): Can 
detect orientation
02-09 21:46:40.086: 
DEBUG/org.doubango.imsdroid.media.MyProxyAudioConsumer(1571): 
prepareCallback(20,8000,1)
02-09 21:46:40.086: 
DEBUG/org.doubango.imsdroid.media.MyProxyAudioConsumer(1571): startCallback
02-09 21:46:40.106: 
DEBUG/org.doubango.imsdroid.media.MyProxyAudioProducer(1571): 
prepareCallback(20,8000,1)
02-09 21:46:40.106: 
DEBUG/org.doubango.imsdroid.media.MyProxyAudioConsumer(1571): ===== Audio 
Player Thread (Start) =====
02-09 21:46:45.845: WARN/WindowManager(85): Key dispatching timed out sending 
to org.doubango.imsdroid/org.doubango.imsdroid.Main
02-09 21:46:45.855: WARN/WindowManager(85): Previous dispatch state: 
{{KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=72} to 
Window{44b50240 com.android.launcher2/com.android.launcher2.Launcher 
paused=false} @ 1297262752734 lw=Window{44b50240 
com.android.launcher2/com.android.launcher2.Launcher paused=false} 
lb=android.os.BinderProxy@44a54320 fin=false gfw=true ed=true tts=0 wf=false 
fp=false mcf=Window{44b50240 
com.android.launcher2/com.android.launcher2.Launcher paused=false}}}
02-09 21:46:45.855: WARN/WindowManager(85): Current dispatch state: {{null to 
Window{44b533e8 org.doubango.imsdroid/org.doubango.imsdroid.Main paused=false} 
@ 1297262805857 lw=Window{44b533e8 
org.doubango.imsdroid/org.doubango.imsdroid.Main paused=false} 
lb=android.os.BinderProxy@44c65490 fin=false gfw=true ed=true tts=0 wf=false 
fp=false mcf=Window{44b533e8 org.doubango.imsdroid/org.doubango.imsdroid.Main 
paused=false}}}
02-09 21:46:45.876: INFO/Process(85): Sending signal. PID: 1571 SIG: 3
02-09 21:46:45.876: INFO/dalvikvm(1571): threadid=3: reacting to signal 3
02-09 21:46:45.916: INFO/dalvikvm(1571): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:45.925: INFO/Process(85): Sending signal. PID: 85 SIG: 3
02-09 21:46:45.925: INFO/dalvikvm(85): threadid=3: reacting to signal 3
02-09 21:46:46.025: INFO/dalvikvm(85): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.025: INFO/Process(85): Sending signal. PID: 153 SIG: 3
02-09 21:46:46.035: INFO/dalvikvm(153): threadid=3: reacting to signal 3
02-09 21:46:46.045: INFO/dalvikvm(153): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.056: INFO/Process(85): Sending signal. PID: 161 SIG: 3
02-09 21:46:46.056: INFO/dalvikvm(161): threadid=3: reacting to signal 3
02-09 21:46:46.095: INFO/dalvikvm(161): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.095: INFO/Process(85): Sending signal. PID: 169 SIG: 3
02-09 21:46:46.095: INFO/dalvikvm(169): threadid=3: reacting to signal 3
02-09 21:46:46.106: INFO/dalvikvm(169): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.106: INFO/Process(85): Sending signal. PID: 499 SIG: 3
02-09 21:46:46.106: INFO/dalvikvm(499): threadid=3: reacting to signal 3
02-09 21:46:46.115: INFO/dalvikvm(499): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.115: INFO/Process(85): Sending signal. PID: 212 SIG: 3
02-09 21:46:46.115: INFO/dalvikvm(212): threadid=3: reacting to signal 3
02-09 21:46:46.146: INFO/dalvikvm(212): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.146: INFO/Process(85): Sending signal. PID: 191 SIG: 3
02-09 21:46:46.146: INFO/dalvikvm(191): threadid=3: reacting to signal 3
02-09 21:46:46.155: INFO/dalvikvm(191): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.155: INFO/Process(85): Sending signal. PID: 283 SIG: 3
02-09 21:46:46.155: INFO/dalvikvm(283): threadid=3: reacting to signal 3
02-09 21:46:46.165: INFO/dalvikvm(283): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.165: INFO/Process(85): Sending signal. PID: 443 SIG: 3
02-09 21:46:46.165: INFO/dalvikvm(443): threadid=3: reacting to signal 3
02-09 21:46:46.165: INFO/dalvikvm(443): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.176: INFO/Process(85): Sending signal. PID: 433 SIG: 3
02-09 21:46:46.176: INFO/dalvikvm(433): threadid=3: reacting to signal 3
02-09 21:46:46.176: INFO/dalvikvm(433): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.186: INFO/Process(85): Sending signal. PID: 309 SIG: 3
02-09 21:46:46.186: INFO/dalvikvm(309): threadid=3: reacting to signal 3
02-09 21:46:46.196: INFO/dalvikvm(309): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.196: INFO/Process(85): Sending signal. PID: 328 SIG: 3
02-09 21:46:46.196: INFO/dalvikvm(328): threadid=3: reacting to signal 3
02-09 21:46:46.205: INFO/dalvikvm(328): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.205: INFO/Process(85): Sending signal. PID: 1253 SIG: 3
02-09 21:46:46.205: INFO/dalvikvm(1253): threadid=3: reacting to signal 3
02-09 21:46:46.216: INFO/dalvikvm(1253): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.216: INFO/Process(85): Sending signal. PID: 171 SIG: 3
02-09 21:46:46.216: INFO/dalvikvm(171): threadid=3: reacting to signal 3
02-09 21:46:46.216: INFO/dalvikvm(171): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.225: INFO/Process(85): Sending signal. PID: 422 SIG: 3
02-09 21:46:46.225: INFO/dalvikvm(422): threadid=3: reacting to signal 3
02-09 21:46:46.225: INFO/dalvikvm(422): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.236: INFO/Process(85): Sending signal. PID: 1057 SIG: 3
02-09 21:46:46.236: INFO/dalvikvm(1057): threadid=3: reacting to signal 3
02-09 21:46:46.236: INFO/dalvikvm(1057): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.245: INFO/Process(85): Sending signal. PID: 1082 SIG: 3
02-09 21:46:46.245: INFO/dalvikvm(1082): threadid=3: reacting to signal 3
02-09 21:46:46.245: INFO/dalvikvm(1082): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.245: INFO/Process(85): Sending signal. PID: 388 SIG: 3
02-09 21:46:46.245: INFO/dalvikvm(388): threadid=3: reacting to signal 3
02-09 21:46:46.256: INFO/dalvikvm(388): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:46:46.266: ERROR/ActivityManager(85): ANR in org.doubango.imsdroid 
(org.doubango.imsdroid/.Main)
02-09 21:46:46.266: ERROR/ActivityManager(85): Reason: keyDispatchingTimedOut
02-09 21:46:46.266: ERROR/ActivityManager(85): Load: 2.22 / 2.18 / 2.24
02-09 21:46:46.266: ERROR/ActivityManager(85): CPU usage from 16443ms to 4407ms 
ago:
02-09 21:46:46.266: ERROR/ActivityManager(85):   zygote: 4% = 2% user + 1% 
kernel / faults: 41 minor
02-09 21:46:46.266: ERROR/ActivityManager(85):   mediaserver: 3% = 0% user + 2% 
kernel / faults: 6 minor
02-09 21:46:46.266: ERROR/ActivityManager(85):   akmd: 2% = 0% user + 2% kernel
02-09 21:46:46.266: ERROR/ActivityManager(85):   system_server: 2% = 1% user + 
0% kernel / faults: 61 minor
02-09 21:46:46.266: ERROR/ActivityManager(85):   dhd_dpc: 2% = 0% user + 2% 
kernel
02-09 21:46:46.266: ERROR/ActivityManager(85):   events/0: 0% = 0% user + 0% 
kernel
02-09 21:46:46.266: ERROR/ActivityManager(85):   droid.launcher2: 0% = 0% user 
+ 0% kernel
02-09 21:46:46.266: ERROR/ActivityManager(85):   synaptics_wq: 0% = 0% user + 
0% kernel
02-09 21:46:46.266: ERROR/ActivityManager(85):   wpa_supplicant: 0% = 0% user + 
0% kernel
02-09 21:46:46.266: ERROR/ActivityManager(85): TOTAL: 15% = 4% user + 9% kernel 
+ 0% softirq
02-09 21:46:47.305: INFO/WindowManager(85): Setting rotation to 1, animFlags=0
02-09 21:46:47.325: INFO/ActivityManager(85): Config changed: { scale=1.0 
imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 orien=2 layout=34 uiMode=17 
seq=17}
02-09 21:46:47.385: INFO/UsageStats(85): Unexpected resume of 
org.doubango.imsdroid while already resumed in org.doubango.imsdroid
02-09 21:46:49.305: WARN/WindowManager(85): Window freeze timeout expired.
02-09 21:46:49.305: WARN/WindowManager(85): Force clearing orientation change: 
Window{44b3fcb8 StatusBar paused=false}
02-09 21:46:49.305: WARN/WindowManager(85): Force clearing orientation change: 
Window{44a9da28 StatusBarExpanded paused=false}
02-09 21:46:49.315: WARN/WindowManager(85): Force clearing orientation change: 
Window{44b533e8 org.doubango.imsdroid/org.doubango.imsdroid.Main paused=false}
02-09 21:47:25.505: ERROR/AudioHardwareQSD(59): Cannot open /dev/msm_pcm_in 
errno: 16
02-09 21:47:25.505: INFO/AudioHardwareQSD(59): do input routing device 40000
02-09 21:47:25.505: INFO/AudioHardwareQSD(59): Routing audio to Handset
02-09 21:47:25.595: DEBUG/dalvikvm(85): GC_EXPLICIT freed 7098 objects / 360896 
bytes in 34281ms
02-09 21:47:25.605: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.626: INFO/Process(85): Sending signal. PID: 85 SIG: 3
02-09 21:47:25.626: INFO/dalvikvm(85): threadid=3: reacting to signal 3
02-09 21:47:25.635: DEBUG/AudioHardwareQSD(59): Switching audio device to 
02-09 21:47:25.635: DEBUG/AudioHardwareQSD(59): Handset
02-09 21:47:25.696: INFO/dalvikvm(85): Wrote stack traces to 
'/data/anr/traces.txt'
02-09 21:47:25.696: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.696: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.696: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.696: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.696: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 0
02-09 21:47:25.705: WARN/WindowManager(85): No window to dispatch pointer 
action 1
02-09 21:47:25.736: INFO/AudioHardwareQSD(59): AudioHardware PCM record is 
going to standby.
02-09 21:47:25.736: ERROR/AudioRecord(1571): Could not get audio input for 
record source 1
02-09 21:47:25.736: ERROR/AudioRecord-JNI(1571): Error creating AudioRecord 
instance: initialization check failed.
02-09 21:47:25.736: ERROR/AudioRecord-Java(1571): [ android.media.AudioRecord ] 
Error code -20 when initializing native AudioRecord object.
02-09 21:47:25.736: 
ERROR/org.doubango.imsdroid.media.MyProxyAudioProducer(1571): prepare() failed
02-09 21:47:25.736: 
DEBUG/org.doubango.imsdroid.media.MyProxyAudioProducer(1571): startCallback
02-09 21:47:25.745: DEBUG/org.doubango.imsdroid.Services.Impl.SipService(1571): 
OnDialogEvent (Dialog connected)
02-09 21:47:25.745: WARN/TimedEventQueue(59): Event 474 was not found in the 
queue, already cancelled?
02-09 21:47:25.836: DEBUG/dalvikvm(85): GC_EXTERNAL_ALLOC freed 1653 objects / 
113808 bytes in 106ms
02-09 21:47:25.836: DEBUG/org.doubango.imsdroid.sip.MyAVSession(1571): 
initializeConsumersAndProducers()
02-09 21:47:25.845: WARN/SurfaceFlinger(85): timeout expired mFreezeDisplay=0, 
mFreezeCount=2
02-09 21:47:25.966: ERROR/Sensors(85): CAPELLA_CM3602_IOCTL_ENABLE error (I/O 
error)
02-09 21:47:25.996: INFO/WindowManager(85): Setting rotation to 0, animFlags=0
02-09 21:47:26.016: INFO/ActivityManager(85): Config changed: { scale=1.0 
imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 orien=1 layout=34 uiMode=17 
seq=18}
02-09 21:47:26.016: INFO/UsageStats(85): Unexpected resume of 
org.doubango.imsdroid while already resumed in org.doubango.imsdroid
02-09 21:47:26.175: DEBUG/dalvikvm(1571): GC_FOR_MALLOC freed 3948 objects / 
164808 bytes in 203ms
02-09 21:47:26.375: DEBUG/org.doubango.imsdroid.Screens.ScreenAV(1571): Can 
detect orientation
02-09 21:47:26.526: DEBUG/AndroidRuntime(1571): Shutting down VM
02-09 21:47:26.526: WARN/dalvikvm(1571): threadid=1: thread exiting with 
uncaught exception (group=0x4001d7f0)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571): FATAL EXCEPTION: main
02-09 21:47:26.535: ERROR/AndroidRuntime(1571): 
java.lang.IllegalStateException: TimerTask is scheduled already
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
java.util.Timer.scheduleImpl(Timer.java:577)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
java.util.Timer.schedule(Timer.java:485)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
org.doubango.imsdroid.Screens.ScreenAV.updateState(ScreenAV.java:788)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
org.doubango.imsdroid.Screens.ScreenAV.updateState(ScreenAV.java:710)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
org.doubango.imsdroid.Screens.ScreenAV.access$20(ScreenAV.java:709)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
org.doubango.imsdroid.Screens.ScreenAV$AVInviteEventHandler$5.run(ScreenAV.java:
958)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
android.os.Handler.handleCallback(Handler.java:587)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
android.os.Handler.dispatchMessage(Handler.java:92)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
android.os.Looper.loop(Looper.java:123)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
android.app.ActivityThread.main(ActivityThread.java:4627)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
java.lang.reflect.Method.invokeNative(Native Method)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
java.lang.reflect.Method.invoke(Method.java:521)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
02-09 21:47:26.535: ERROR/AndroidRuntime(1571):     at 
dalvik.system.NativeStart.main(Native Method)
02-09 21:47:26.546: WARN/ActivityManager(85):   Force finishing activity 
org.doubango.imsdroid/.Main
02-09 21:47:27.055: WARN/ActivityManager(85): Activity pause timeout for 
HistoryRecord{44a4af18 org.doubango.imsdroid/.Main}

Together with a dialog box on 108 that says: The application IMSDRoid (process 
org.doubango.imsdroid) has stopped unexpectedly. Please try again.
Force close (button)

Original comment by matthijs...@gmail.com on 9 Feb 2011 at 2:51

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 5 Jun 2011 at 5:13