--------- beginning of main

05-13 06:34:28.988 9177 9177 E com.mbwhatsapp: Not starting debugger since

process cannot load the jdwp agent.
05-13 06:34:29.716 9177 9177 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-13 06:34:29.717 9177 9177 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.Class.newInstance(Native Method)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-13 06:34:29.717 9177 9177 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7183)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
05-13 06:34:29.717 9177 9177 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-13 06:34:29.717 9177 9177 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-13 06:34:29.717 9177 9177 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-13 06:34:29.717 9177 9177 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8396)
05-13 06:34:29.717 9177 9177 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-13 06:34:29.717 9177 9177 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-13 06:34:29.717 9177 9177 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
05-13 06:34:29.734 9177 9177 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-13 06:34:30.466 9177 9177 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-13 06:34:30.466 9177 9177 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-13 06:34:30.529 9177 9177 W com.mbwhatsapp: type=1400 audit(0.0:7881): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="mmcblk0p42" ino=3041480 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 06:34:30.541 9177 9177 W com.mbwhatsapp: type=1400 audit(0.0:7882): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so"
dev="mmcblk0p42" ino=3041473 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 06:34:30.549 9177 9177 W com.mbwhatsapp: type=1400 audit(0.0:7884): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 06:34:30.665 9177 9177 W com.mbwhatsapp: type=1400 audit(0.0:7885): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 06:34:30.693 9177 9177 W com.mbwhatsapp: type=1400 audit(0.0:7886): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 06:34:30.859 9177 9290 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-13 06:34:30.859 9177 9290 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-13 06:34:30.859 9177 9290 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-13 06:34:32.218 9177 9360 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-13 06:34:32.218 9177 9360 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-13 07:27:27.635 22823 22823 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 07:27:28.113 22823 22823 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-13 07:27:28.765 22823 22823 W com.mbwhatsapp: type=1400 audit(0.0:9036): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 07:27:28.777 22823 22823 W com.mbwhatsapp: type=1400 audit(0.0:9037): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 07:27:28.852 22823 22878 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-13 07:27:28.852 22823 22878 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-13 07:27:28.852 22823 22878 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-13 08:27:45.496 8672 8672 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 08:27:46.150 8672 8672 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-13 08:27:47.427 8672 8672 W com.mbwhatsapp: type=1400 audit(0.0:10878): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 09:27:45.384 24296 24296 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 09:27:45.938 24296 24296 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-13 09:27:46.659 24296 24349 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-13 09:27:46.659 24296 24349 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-13 09:27:46.659 24296 24349 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-13 10:27:26.355 9176 9176 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 10:27:27.072 9176 9176 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-13 10:27:27.848 9176 9298 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-13 10:27:27.848 9176 9298 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-13 10:27:27.848 9176 9298 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-13 11:27:48.522 27523 27523 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 11:27:48.998 27523 27523 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-13 11:27:49.691 27523 27577 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-13 11:27:49.691 27523 27577 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-13 11:27:49.691 27523 27577 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-13 12:27:55.474 15941 15941 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 12:27:56.019 15941 15941 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-13 16:04:20.962 5892 5892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 16:04:21.770 5892 5892 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-13 16:05:25.352 8189 8189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 16:05:25.881 8189 8189 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-14 06:59:05.734 7913 7913 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 06:59:06.930 7913 7913 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-14 06:59:09.079 7913 7913 W com.mbwhatsapp: type=1400 audit(0.0:8220): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-14 07:03:02.778 13941 13941 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 07:03:03.123 13941 13941 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-14 07:03:03.727 13941 13941 W com.mbwhatsapp: type=1400 audit(0.0:8606): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 07:03:03.735 13941 13941 W com.mbwhatsapp: type=1400 audit(0.0:8607): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 07:03:03.735 13941 13941 W com.mbwhatsapp: type=1400 audit(0.0:8608): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 07:03:03.735 13941 13941 W com.mbwhatsapp: type=1400 audit(0.0:8609): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-14 07:37:04.146 21235 21235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 07:37:04.591 21235 21235 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-14 07:37:05.143 21235 21235 W com.mbwhatsapp: type=1400 audit(0.0:9131): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 07:37:05.151 21235 21235 W com.mbwhatsapp: type=1400 audit(0.0:9132): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 07:37:05.214 21235 21287 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 07:37:05.214 21235 21287 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 07:37:05.214 21235 21287 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-14 07:38:31.931 21680 21680 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 07:38:32.221 21680 21680 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-14 07:38:32.683 21680 21727 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 07:38:32.683 21680 21727 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 07:38:32.683 21680 21727 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-14 08:37:23.207 6266 6266 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 08:37:23.694 6266 6266 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-14 09:37:40.342 16855 16855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 09:37:40.754 16855 16855 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-14 10:37:47.291 2281 2281 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 10:37:48.123 2281 2281 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-14 11:37:04.070 20523 20523 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 11:37:04.448 20523 20523 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-14 12:37:04.100 7570 7570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 12:37:04.578 7570 7570 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-14 12:37:05.028 7570 7570 W com.mbwhatsapp: type=1400 audit(0.0:15519): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 12:37:05.028 7570 7570 W com.mbwhatsapp: type=1400 audit(0.0:15520): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-14 12:37:05.130 7570 7636 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 12:37:05.130 7570 7636 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 12:37:05.130 7570 7636 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-14 13:37:04.093 19471 19471 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 13:37:04.696 19471 19471 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 06:29:47.954 8998 8998 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 06:29:48.534 8998 8998 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-15 06:29:50.006 8998 8998 W com.mbwhatsapp: type=1400 audit(0.0:7392): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 06:29:50.034 8998 8998 W com.mbwhatsapp: type=1400 audit(0.0:7394): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 06:29:50.034 8998 8998 W com.mbwhatsapp: type=1400 audit(0.0:7395): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-15 07:20:59.387 23762 23762 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 07:21:00.157 23762 23762 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-15 07:21:00.788 23762 23911 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 07:21:00.788 23762 23911 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 07:21:00.788 23762 23911 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-15 07:22:39.184 24531 24531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 07:22:39.450 24531 24531 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 08:25:15.186 28477 28477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 08:25:15.439 28477 28477 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 09:21:48.293 4601 4601 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 09:21:48.795 4601 4601 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 09:26:21.784 5549 5549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 09:26:22.022 5549 5549 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 09:30:54.782 6291 6291 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 09:30:54.922 6291 6291 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 09:34:01.161 6839 6839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 09:34:01.484 6839 6839 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 10:22:21.992 21255 21255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 10:22:22.705 21255 21255 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 10:35:48.759 22764 22764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 10:35:49.214 22764 22764 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-15 10:35:49.214 22764 22764 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.Class.newInstance(Native Method)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-15 10:35:49.214 22764 22764 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7183)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
05-15 10:35:49.214 22764 22764 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-15 10:35:49.214 22764 22764 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-15 10:35:49.214 22764 22764 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-15 10:35:49.214 22764 22764 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8396)
05-15 10:35:49.214 22764 22764 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-15 10:35:49.214 22764 22764 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-15 10:35:49.214 22764 22764 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
05-15 10:35:49.227 22764 22764 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 10:51:59.112 27873 27873 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 10:51:59.562 27873 27873 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 11:21:05.018 32591 32591 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 11:21:05.510 32591 32591 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 11:53:49.208 6715 6715 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 11:53:49.725 6715 6715 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 12:21:15.257 18182 18182 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 12:21:15.773 18182 18182 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-15 12:57:15.999 28179 28179 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 12:57:16.649 28179 28179 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-15 12:57:17.962 28179 28352 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=da11761a-8541-4674-9980-b11f475e15fb, generation=0)
05-15 12:57:17.966 28179 28352 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=da11761a-8541-4674-9980-b11f475e15fb, generation=0)
--------- beginning of main
05-15 13:20:58.912 7022 7022 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 13:20:59.454 7022 7022 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 06:39:36.189 10899 10899 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 06:39:36.927 10899 10899 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-16 06:39:39.101 10899 11103 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-16 06:39:39.101 10899 11103 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-16 06:39:39.101 10899 11103 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-16 06:47:16.810 15335 15335 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 06:47:17.302 15335 15335 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-16 06:47:18.051 15335 15335 W com.mbwhatsapp: type=1400 audit(0.0:8349): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-16 06:54:50.574 16489 16489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 06:54:50.965 16489 16489 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 07:31:40.739 29820 29820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 07:31:41.377 29820 29820 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 07:35:11.610 31363 31363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 07:35:11.890 31363 31363 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 08:33:11.808 13214 13214 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 08:33:12.878 13214 13214 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 08:40:51.459 14932 14932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 08:40:51.912 14932 14932 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 08:44:19.581 15261 15261 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 08:44:19.774 15261 15261 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 09:44:55.589 19840 19840 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 09:44:56.407 19840 19840 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 11:11:33.987 21948 21948 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 11:11:34.474 21948 21948 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-16 11:11:34.474 21948 21948 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.Class.newInstance(Native Method)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-16 11:11:34.474 21948 21948 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7183)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
05-16 11:11:34.474 21948 21948 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-16 11:11:34.474 21948 21948 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-16 11:11:34.474 21948 21948 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-16 11:11:34.474 21948 21948 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8396)
05-16 11:11:34.474 21948 21948 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-16 11:11:34.474 21948 21948 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-16 11:11:34.474 21948 21948 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
05-16 11:11:34.489 21948 21948 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-16 11:11:34.702 21948 21948 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-16 11:11:34.703 21948 21948 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-16 11:11:34.727 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12576): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="mmcblk0p42" ino=3041480 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.739 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12577): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so"
dev="mmcblk0p42" ino=3041473 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.747 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12578): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.827 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12579): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.847 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12580): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.847 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12581): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.847 21948 21948 W com.mbwhatsapp: type=1400 audit(0.0:12582): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 11:11:34.947 21948 22049 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-16 11:11:34.947 21948 22049 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-16 11:11:34.947 21948 22049 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-16 12:32:54.508 2720 2720 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 12:32:54.974 2720 2720 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 12:36:52.542 3580 3580 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 12:36:52.830 3580 3580 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 12:39:08.454 4771 4771 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 12:39:08.896 4771 4771 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 12:44:40.080 5744 5744 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 12:49:43.726 6044 6044 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 12:49:44.191 6044 6044 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 13:32:21.965 10612 10612 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 13:32:22.502 10612 10612 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-16 16:35:46.198 14973 14973 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 16:35:46.658 14973 14973 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-17 07:17:26.942 17020 17020 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 07:17:28.868 17020 17020 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-17 08:13:16.870 32641 32641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 08:13:17.329 32641 32641 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-17 08:16:38.758 2520 2520 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 08:16:39.214 2520 2520 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-17 09:09:53.997 18467 18467 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 09:09:54.840 18467 18467 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-17 10:10:18.903 3545 3545 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 10:10:19.365 3545 3545 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-18 06:49:28.896 18932 18932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 06:49:29.708 18932 18932 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-18 06:51:39.157 21625 21625 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 06:51:39.554 21625 21625 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-19 17:26:10.621 9936 9936 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 17:26:12.010 9936 9936 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-19 17:26:14.465 9936 9936 W com.mbwhatsapp: type=1400 audit(0.0:8381): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 17:26:14.549 9936 9936 W com.mbwhatsapp: type=1400 audit(0.0:8382): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 17:26:14.553 9936 9936 W com.mbwhatsapp: type=1400 audit(0.0:8383): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 17:26:14.553 9936 9936 W com.mbwhatsapp: type=1400 audit(0.0:8384): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-20 06:56:34.631 8569 8569 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 06:56:35.956 8569 8569 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-20 06:58:31.927 14017 14017 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 06:58:32.444 14017 14017 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-20 08:02:03.216 32105 32105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 08:02:03.719 32105 32105 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-20 08:02:04.233 32105 32105 W com.mbwhatsapp: type=1400 audit(0.0:12566): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-20 08:02:04.241 32105 32105 W com.mbwhatsapp: type=1400 audit(0.0:12567): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-20 09:02:23.190 22270 22270 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 09:02:23.712 22270 22270 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-20 10:02:25.110 16302 16302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 10:02:25.656 16302 16302 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-20 12:05:16.495 28200 28200 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 12:05:16.990 28200 28200 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-20 12:05:16.991 28200 28200 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.Class.newInstance(Native Method)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-20 12:05:16.991 28200 28200 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7183)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
05-20 12:05:16.991 28200 28200 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-20 12:05:16.991 28200 28200 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-20 12:05:16.991 28200 28200 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-20 12:05:16.991 28200 28200 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8396)
05-20 12:05:16.991 28200 28200 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-20 12:05:16.991 28200 28200 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-20 12:05:16.991 28200 28200 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
05-20 12:05:17.016 28200 28200 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-20 12:05:17.502 28200 28200 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-20 12:05:17.503 28200 28200 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-20 12:05:17.551 28200 28200 W com.mbwhatsapp: type=1400 audit(0.0:15856): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="mmcblk0p42" ino=3041480 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-20 12:05:17.571 28200 28200 W com.mbwhatsapp: type=1400 audit(0.0:15857): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so"
dev="mmcblk0p42" ino=3041473 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-20 12:05:17.583 28200 28200 W com.mbwhatsapp: type=1400 audit(0.0:15858): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-20 12:05:17.671 28200 28200 W com.mbwhatsapp: type=1400 audit(0.0:15859): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-20 12:05:17.683 28200 28200 W com.mbwhatsapp: type=1400 audit(0.0:15860): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-20 12:05:17.799 28200 28289 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-20 12:05:17.799 28200 28289 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-20 12:05:17.799 28200 28289 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-20 14:07:09.535 30883 30883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 14:07:10.229 30883 30883 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-20 16:51:55.549 8975 8975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 16:51:56.199 8975 8975 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 07:19:54.201 8868 8868 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 07:19:55.135 8868 8868 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-21 07:19:55.135 8868 8868 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-21 07:19:55.135 8868 8868 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-21 07:19:55.135 8868 8868 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-21 07:19:55.135 8868 8868 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-21 07:19:55.135 8868 8868 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-21 07:19:55.135 8868 8868 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-21 07:19:55.135 8868 8868 W System.err: at
java.lang.Class.newInstance(Native Method)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-21 07:19:55.135 8868 8868 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7183)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
05-21 07:19:55.135 8868 8868 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-21 07:19:55.135 8868 8868 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-21 07:19:55.135 8868 8868 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-21 07:19:55.135 8868 8868 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8396)
05-21 07:19:55.136 8868 8868 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-21 07:19:55.136 8868 8868 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-21 07:19:55.136 8868 8868 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
05-21 07:19:55.171 8868 8868 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-21 07:19:56.473 8868 8868 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-21 07:19:56.473 8868 8868 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-21 07:19:56.615 8868 8868 W com.mbwhatsapp: type=1400 audit(0.0:7951): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="mmcblk0p42" ino=3041480 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 07:19:56.647 8868 8868 W com.mbwhatsapp: type=1400 audit(0.0:7952): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so"
dev="mmcblk0p42" ino=3041473 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 07:19:56.663 8868 8868 W com.mbwhatsapp: type=1400 audit(0.0:7953): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 07:19:56.835 8868 8868 W com.mbwhatsapp: type=1400 audit(0.0:7954): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 07:19:56.867 8868 8868 W com.mbwhatsapp: type=1400 audit(0.0:7955): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 07:19:57.174 8868 9028 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-21 07:19:57.174 8868 9028 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-21 07:19:57.174 8868 9028 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-21 07:19:58.872 8868 9138 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-21 07:19:58.872 8868 9138 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-21 07:23:30.332 14834 14834 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 07:23:30.672 14834 14834 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 07:25:19.967 16351 16351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 07:25:20.688 16351 16351 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 08:12:51.041 23703 23703 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 08:12:51.857 23703 23703 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 08:13:51.013 24155 24155 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 08:13:51.227 24155 24155 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 09:15:31.032 8461 8461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 09:15:31.677 8461 8461 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 10:16:12.741 24483 24483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 10:16:13.726 24483 24483 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 11:12:50.956 17366 17366 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 11:12:51.724 17366 17366 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 12:13:04.168 7949 7949 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 12:13:04.675 7949 7949 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-21 12:13:05.544 7949 7949 W com.mbwhatsapp: type=1400 audit(0.0:18574): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-21 13:13:34.139 20765 20765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 13:13:34.622 20765 20765 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 13:15:05.947 21412 21412 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 13:15:06.302 21412 21412 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 14:13:00.916 5393 5393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 14:13:01.645 5393 5393 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 16:32:21.587 7546 7546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 16:32:23.978 7546 7546 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-21 16:32:23.978 7546 7546 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-21 16:32:23.979 7546 7546 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-21 16:32:23.979 7546 7546 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-21 16:32:23.979 7546 7546 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-21 16:32:23.979 7546 7546 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-21 16:32:23.979 7546 7546 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-21 16:32:23.979 7546 7546 W System.err: at
java.lang.Class.newInstance(Native Method)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-21 16:32:23.979 7546 7546 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7183)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
05-21 16:32:23.979 7546 7546 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-21 16:32:23.979 7546 7546 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-21 16:32:23.979 7546 7546 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-21 16:32:23.979 7546 7546 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8396)
05-21 16:32:23.979 7546 7546 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-21 16:32:23.979 7546 7546 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-21 16:32:23.979 7546 7546 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
05-21 16:32:24.160 7546 7546 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-21 16:32:26.969 7546 7546 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-21 16:32:26.973 7546 7546 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-21 16:32:27.468 7546 7546 W com.mbwhatsapp: type=1400 audit(0.0:7608): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="mmcblk0p42" ino=3041475 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 16:32:27.528 7546 7546 W com.mbwhatsapp: type=1400 audit(0.0:7609): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 16:32:27.528 7546 7546 W com.mbwhatsapp: type=1400 audit(0.0:7610): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 16:32:27.528 7546 7546 W com.mbwhatsapp: type=1400 audit(0.0:7611): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="mmcblk0p42" ino=3041474 scontext=u:r:untrusted_app:s0:c145,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c145,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-21 16:32:27.921 7546 8241 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-21 16:32:27.921 7546 8241 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-21 16:32:27.921 7546 8241 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-21 16:32:28.743 7546 7554 W com.mbwhatsapp: Suspending all threads took:
15.955ms
05-21 17:43:38.584 24094 24094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 17:43:39.886 24094 24094 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
05-21 17:43:42.855 24094 24559 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-21 17:43:42.855 24094 24559 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-21 17:43:42.855 24094 24559 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-21 18:59:38.630 26349 26349 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 18:59:39.392 26349 26349 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-21 21:11:39.044 30823 30823 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 21:11:40.607 30823 30823 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-22 01:22:52.193 8876 8876 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 01:22:53.641 8876 8876 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-22 02:27:53.211 20824 20824 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 02:27:53.727 20824 20824 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-22 03:28:16.694 24479 24479 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 03:28:17.188 24479 24479 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.