Android Question Fc upon app open and close

PFlores81

Active Member
Licensed User
Longtime User
  • Welp, the title says it all. I've had a few errors on a stupid soundboard that I threw together. Ever since my last compile with Android SDK ver18 I've have numerous reports of users getting an fc at load as well as some getting an fc after tapping the "yes" on the exit popup. Exact error code available upon request. Being I'm mobile right now, it makes it difficult.
B4X:
java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.hydr0warez.zombiesfree/com.hydr0warez.zombiesfree.main}: java.lang.ClassNotFoundException: com.hydr0warez.zombiesfree.main
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1989)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2090)
at android.app.ActivityThread.access$600(ActivityThread.java:136)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1201)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4802)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:813)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:580)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: com.hydr0warez.zombiesfree.main
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
at android.app.Instrumentation.newActivity(Instrumentation.java:1053)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1980)
... 11 more

That's one. This is the other.

B4X:
Build fingerprint: 'samsung/d2uc/d2att:4.0.4/IMM76D/I747UCALEM:user/release-keys'
Revision: '16'
pid: 4019, tid: 4019, name: rez.zombiesfree >>> com.hydr0warez.zombiesfree <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 43a03180
r0 00000001 r1 74791834 r2 74772550 r3 43a03180
r4 41e11760 r5 74791828 r6 00000000 r7 00000057
r8 41e117a8 r9 4014d9e1 sl 00000000 fp 4014d8ea
ip 40acfee8 sp beb37400 lr 40a4c7a0 pc 4014ae10 cpsr 28000010
d0 00720064006e0061 d1 002e00640069006f
d2 002e007000700061 d3 0074006300410049
d4 000002840000008e d5 000000d643560000
d6 4000000043bb0000 d7 000000003f800000
d8 41a000000000024e d9 43aa000044070000
d10 0000000044138000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 726479682e6d6f63 d17 7a2e7a6572617730
d18 0000000000000000 d19 0061007200470049
d20 0063006900680070 d21 0066006600750042
d22 0072005000720065 d23 006300750064006f
d24 3ff0000000000000 d25 0000000000000000
d26 0707070703030303 d27 0000000000000000
d28 4000000000000000 d29 4054000000000000
d30 026f009c026d009c d31 0273009d0271009d
scr 20000010

backtrace:
#00 pc 00019e10 /system/lib/libutils.so (android::Looper::pollInner(int)+736)
#01 pc 00019f0c /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+176)
#02 pc 00078df0 /system/lib/libandroid_runtime.so (android::NativeMessageQueue::pollOnce(_JNIEnv*, int)+44)
#03 pc 0001ddcc /system/lib/libdvm.so (dvmPlatformInvoke+112)
#04 pc 000570f0 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+612)
#05 pc 000271e0 /system/lib/libdvm.so
#06 pc 0002acfc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+252)
#07 pc 00072b8c /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+524)
#08 pc 0007ec08 /system/lib/libdvm.so
#09 pc 000271e0 /system/lib/libdvm.so
#10 pc 0002acfc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+252)
#11 pc 00072778 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+444)
#12 pc 000504a4 /system/lib/libdvm.so
#13 pc 0004c62c /system/lib/libandroid_runtime.so
#14 pc 0004d904 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+616)
#15 pc 00001d37 /system/bin/app_process
#16 pc 0000e110 /system/lib/libc.so (__libc_init+84)
#17 pc 00001904 /system/bin/app_process

code around pc:
4014adf0 1a000002 e1a00004 e1a01007 ebfffeef
4014ae00 e595300c e285100c e3530000 0a000004
4014ae10 e5930000 e510200c e0830002 ebffdca2
4014ae20 e585a00c e3e07001 e2866001 e5941050
4014ae30 e1560001 3affffdd e1a00007 e28ddf49
4014ae40 e8bd8ff0 00002d7d 00002cea 00002dbd
4014ae50 00002cc2 00002cbe 00002d40 e92d45f8
4014ae60 e1a04000 e1a08001 e1a05002 e1a06003
4014ae70 e3a00000 e59d7020 e3a0a014 ea000010
4014ae80 e594104c e2832001 e584205c e023139a
4014ae90 e593c008 e35c0000 ba000009 e5930004
4014aea0 e3550000 e5931000 e5932010 15850000
4014aeb0 e3560000 15861000 e3570000 15872000
4014aec0 ea000014 e594305c e5942050 e1530002
4014aed0 3affffea e3500000 0a000009 e3550000
4014aee0 13a03000 15853000 e3560000 13a03000

code around lr:
40a4c780 fffffe54 00066eb1 0006c589 e92d4010
40a4c790 e3a01007 e1a04000 e5900000 eb003ee1
40a4c7a0 e1a00004 e8bd8010 e1a03000 e92d4037
40a4c7b0 e1a04001 e59f5070 e1a0000d e1a01003
40a4c7c0 ebffffd0 e3540000 e08f5005 0a000013
40a4c7d0 e59f0058 e7955000 e2850fd7 e58d0004
40a4c7e0 ebff372b e2850fd1 e3a01000 e1a02004
40a4c7f0 ebff615f e3500000 1a000006 e59f1030
40a4c800 e3a00005 e59f202c e1a03004 e08f1001
40a4c810 e08f2002 ebff36ee e28d0004 ebffff50
40a4c820 e1a0000d ebffffd8 e8bd803e 000834ac
40a4c830 fffffe58 00066dfd 0006c516 e1a03000
40a4c840 e92d4037 e1a05001 e28d0004 e1a01003
40a4c850 e59f4030 ebffffab e59f002c e08f4004
40a4c860 e7941000 e28d0004 e5912008 e3520000
40a4c870 e5852000 13a04000 03e04000 ebffffc2
 
Last edited:

PFlores81

Active Member
Licensed User
Longtime User
The problem with the crash when exiting the app can be solved by applying THIS workaround.

On a separate note, check your scaling, THIS is how your app looks on my Nexus 7 tab.
Yeah I have yet to scale to certain devices. Being I have a multitude of android devices floating around here. I like to test the layouts prior to updating. Only problem is, my 7" tab shit the bed. Need to buy a new power port assembly.
 
Upvote 0

PFlores81

Active Member
Licensed User
Longtime User
On a side note, at least most of the users are happy. Lol. They just request way too much. I had to change the email associated with the app because they would flood my inbox. Scaling is something I'm going to work on at some point tomorrow if I have time. I'll just run the avd on my TV . makes it easier to view flaws in the layout.
 
Upvote 0

PFlores81

Active Member
Licensed User
Longtime User
I guess you are not using the designer scripts, otherwise, you wouldn't be having his issues.
Honestly, i had my buddy process layouts. It was his job to do just that. But since his schooling is starting up again, he has no time. I did mention to him the ability to use said scripts. But he preferred to do it by hand. I guess it is what it is. Since I'm going to be picking up the slack for him until his stuff settles down, I'm going to look into the scripting. Only thing is, I'm not too goodwith that sort of thing .
 
Upvote 0

PFlores81

Active Member
Licensed User
Longtime User
Using the designer scripts is the way to go, trust me.
Ill have to look into it. As I said, when it comes to those things, its like Greek to me. I can sit here and pentest networks and do my thing with that without issue. But that type of stuff. Yeah I'm lost lol
 
Upvote 0
Top