Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid Application Crashes when exported
    primarykey
    data
    text
    <p>My android application is the customized version of the Cool reader. When I run the application from eclipse, or debug it on my phone, it runs fine. But when I sign it, export it, install it, and run it from my phone, it crashes.</p> <p>In the logcat, I see the following before the application crashes:</p> <pre><code>07-17 21:40:40.371: D/Zygote(1218): Process 3136 terminated by signal (11) 07-17 21:40:40.371: E/InputDispatcher(1331): channel '40b7d8a8 com.myCustomApp/org.coolreader.CoolReader (server)' ~ Consumer closed input channel or an error occurred. events=0x8 07-17 21:40:40.371: E/InputDispatcher(1331): channel '40b7d8a8 com.myCustomApp/org.coolreader.CoolReader (server)' ~ Channel is unrecoverably broken and will be disposed! 07-17 21:40:40.451: D/dalvikvm(1331): GC_FOR_MALLOC freed 758K, 35% free 9419K/14279K, external 2060K/2410K, paused 85ms 07-17 21:40:40.451: I/WindowManager(1331): WIN DEATH: Window{40b7d8a8 com.myCustomApp/org.coolreader.CoolReader paused=false} 07-17 21:40:40.451: I/ActivityManager(1331): Process com.myCustomApp (pid 3136) has died. 07-17 21:40:40.471: E/ActivityManager(1331): fail to set top app changed! </code></pre> <p><strong>Update:</strong> If you are not aware about CoolReader (the open source project I'm using), it jni code, has proGuard configuration, and uses ndk. It also has normal Java code. I'm don't have a lot of experience with jni/ndk, or any low level c\c++ code, so I'm not sure what I can do there.</p> <p>But again, the starngest thing is that it works fine when it runs from eclipse, but the exported version closes on its own.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload