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

04-28 21:29:49.414 6524 6524 E com.mbwhatsapp: Not starting debugger since

process cannot load the jdwp agent.
01-01 08:00:00.187 6524 6524 W main : type=1400 audit(0.0:8388608): avc:
granted { mounton } for path="/storage" dev="dm-5" ino=53 scontext=u:r:zygote:s0
tcontext=u:object_r:storage_file:s0 tclass=dir app=com.mbwhatsapp
04-28 21:29:52.330 6524 6524 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
04-28 21:29:52.337 6524 6524 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.Class.newInstance(Native Method)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-28 21:29:52.337 6524 6524 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
04-28 21:29:52.337 6524 6524 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-28 21:29:52.337 6524 6524 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
04-28 21:29:52.337 6524 6524 W System.err: at
android.os.Looper.loop(Looper.java:334)
04-28 21:29:52.337 6524 6524 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
04-28 21:29:52.337 6524 6524 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-28 21:29:52.337 6524 6524 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
04-28 21:29:52.337 6524 6524 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
04-28 21:29:52.755 6524 6524 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.
04-28 21:29:54.127 6524 6524 W com.mbwhatsapp: Class com.mbwhatsapp.yo.x1 failed
lock verification and will run slower.
04-28 21:29:54.127 6524 6524 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-28 21:29:54.127 6524 6524 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-28 21:29:56.572 6524 6524 W com.mbwhatsapp: Class com.mbwhatsapp.yo.r0 failed
lock verification and will run slower.
04-28 21:29:57.815 6524 6524 W com.mbwhatsapp: type=1400 audit(0.0:1920): avc:
granted { execute } for
path="/data/user/0/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app_29:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 21:29:57.862 6524 6524 W com.mbwhatsapp: type=1400 audit(0.0:1922): avc:
granted { execute } for
path="/data/user/0/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so"
dev="dm-10" ino=1256111 scontext=u:r:untrusted_app_29:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 21:29:57.908 6524 6524 W com.mbwhatsapp: type=1400 audit(0.0:1923): avc:
granted { execute } for
path="/data/user/0/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app_29:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 21:29:58.771 6524 6534 W com.mbwhatsapp: Suspending all threads took:
39.297ms
04-28 21:30:00.994 6524 7076 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
04-28 21:30:00.995 6524 7076 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
04-28 21:31:20.242 9807 9807 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 21:31:27.332 9807 9807 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.
04-28 22:07:57.584 9807 9807 E ArmVmp : Match on catch block at 0x18 in for 0x79
04-28 22:08:17.508 22618 22618 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 22:08:18.719 22618 22618 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.
04-28 23:16:00.739 27297 27297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 23:16:01.390 27297 27297 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.
04-28 23:16:02.789 27349 27349 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 23:16:03.198 27349 27349 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.
04-28 23:16:08.792 27349 27349 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-28 23:16:08.793 27349 27349 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
04-29 01:29:35.409 3694 3694 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 01:29:37.270 3694 3694 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
04-29 01:29:37.271 3694 3694 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.Class.newInstance(Native Method)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-29 01:29:37.271 3694 3694 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
04-29 01:29:37.271 3694 3694 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-29 01:29:37.271 3694 3694 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
04-29 01:29:37.271 3694 3694 W System.err: at
android.os.Looper.loop(Looper.java:334)
04-29 01:29:37.271 3694 3694 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
04-29 01:29:37.271 3694 3694 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-29 01:29:37.271 3694 3694 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
04-29 01:29:37.271 3694 3694 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
04-29 01:29:37.879 3694 3694 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
04-29 01:29:40.533 3694 3694 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-29 01:29:40.535 3694 3694 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
04-29 01:29:40.736 3694 3694 W com.mbwhatsapp: type=1400 audit(0.0:1089): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:29:40.749 3694 3694 W com.mbwhatsapp: type=1400 audit(0.0:1090): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:29:40.842 3694 3694 W com.mbwhatsapp: type=1400 audit(0.0:1091): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:29:41.056 3694 3694 W com.mbwhatsapp: type=1400 audit(0.0:1092): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:29:41.179 3694 3694 W com.mbwhatsapp: type=1400 audit(0.0:1093): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:29:42.215 3694 4154 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
04-29 01:29:42.215 3694 4154 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-29 01:29:42.215 3694 4154 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-29 01:30:14.216 5582 5582 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 01:30:14.759 5582 5582 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-29 01:30:14.759 5582 5582 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-29 01:30:14.760 5582 5582 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
04-29 01:30:14.760 5582 5582 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
04-29 01:30:14.760 5582 5582 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
04-29 01:30:14.760 5582 5582 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
04-29 01:30:14.760 5582 5582 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-29 01:30:14.760 5582 5582 W System.err: at
java.lang.Class.newInstance(Native Method)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-29 01:30:14.760 5582 5582 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
04-29 01:30:14.760 5582 5582 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-29 01:30:14.760 5582 5582 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
04-29 01:30:14.760 5582 5582 W System.err: at
android.os.Looper.loop(Looper.java:334)
04-29 01:30:14.760 5582 5582 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
04-29 01:30:14.760 5582 5582 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-29 01:30:14.760 5582 5582 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
04-29 01:30:14.760 5582 5582 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
04-29 01:30:14.950 5582 5582 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.
04-29 01:30:15.733 5582 5582 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-29 01:30:15.734 5582 5582 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
04-29 01:30:16.155 5582 5582 W com.mbwhatsapp: type=1400 audit(0.0:1557): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:30:16.192 5582 5582 W com.mbwhatsapp: type=1400 audit(0.0:1558): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:30:16.192 5582 5582 W com.mbwhatsapp: type=1400 audit(0.0:1559): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:30:16.192 5582 5582 W com.mbwhatsapp: type=1400 audit(0.0:1560): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-29 01:30:16.192 5582 5582 W com.mbwhatsapp: type=1400 audit(0.0:1561): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
04-29 01:30:16.514 5582 5707 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
04-29 01:30:16.514 5582 5707 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-29 01:30:16.514 5582 5707 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-29 01:31:45.188 8629 8629 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 01:31:46.258 8629 8629 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
04-29 01:54:04.677 15032 15032 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 01:54:05.313 15032 15032 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
04-29 17:49:43.740 7160 7160 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 17:49:44.609 7160 7160 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
04-29 18:24:41.149 14199 14199 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 18:24:41.822 14199 14199 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
04-29 18:35:42.232 16135 16135 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 18:35:42.680 16135 16135 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
04-29 22:08:36.787 11741 11741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 22:08:37.377 11741 11741 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.
04-29 22:08:38.469 11741 11807 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=9ecd65d2-6087-4065-a095-8e8b80af51e7, generation=0)
--------- beginning of main
04-30 02:01:35.918 26959 26959 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-30 02:01:36.492 26959 26959 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
04-30 22:10:07.800 28782 28782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-30 22:10:08.334 28782 28782 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-01 00:00:14.068 14438 14438 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 00:00:14.688 14438 14438 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-01 00:00:16.349 14438 14580 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-01 00:00:16.349 14438 14580 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-01 00:00:16.349 14438 14580 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-01 02:01:10.192 24268 24268 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 02:01:10.684 24268 24268 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-01 10:10:20.173 11692 11692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 10:10:21.279 11692 11692 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-01 10:10:22.357 11692 11692 W com.mbwhatsapp: type=1400 audit(0.0:2677): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 10:10:22.384 11692 11692 W com.mbwhatsapp: type=1400 audit(0.0:2678): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-01 10:23:59.889 5490 5490 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 10:24:01.736 5490 5490 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-01 10:24:01.739 5490 5490 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-01 10:24:01.739 5490 5490 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-01 10:24:01.739 5490 5490 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-01 10:24:01.740 5490 5490 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-01 10:24:01.740 5490 5490 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-01 10:24:01.740 5490 5490 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-01 10:24:01.740 5490 5490 W System.err: at
java.lang.Class.newInstance(Native Method)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-01 10:24:01.740 5490 5490 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-01 10:24:01.740 5490 5490 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-01 10:24:01.740 5490 5490 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-01 10:24:01.740 5490 5490 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-01 10:24:01.740 5490 5490 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-01 10:24:01.740 5490 5490 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-01 10:24:01.740 5490 5490 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-01 10:24:01.740 5490 5490 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-01 10:24:02.051 5490 5490 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-01 10:24:03.859 5490 5490 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-01 10:24:03.860 5490 5490 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-01 10:24:04.597 5490 5767 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-01 10:24:04.597 5490 5767 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-01 10:24:04.597 5490 5767 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-01 10:24:41.766 7130 7130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 10:24:42.651 7130 7130 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-01 10:24:42.652 7130 7130 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.Class.newInstance(Native Method)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-01 10:24:42.652 7130 7130 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-01 10:24:42.652 7130 7130 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-01 10:24:42.652 7130 7130 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-01 10:24:42.652 7130 7130 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-01 10:24:42.652 7130 7130 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-01 10:24:42.652 7130 7130 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-01 10:24:42.652 7130 7130 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-01 10:24:42.652 7130 7130 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-01 10:24:42.768 7130 7130 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-01 10:24:43.715 7130 7130 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-01 10:24:43.716 7130 7130 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-01 10:24:44.816 7130 7290 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-01 10:24:44.816 7130 7290 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-01 10:24:44.816 7130 7290 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-01 10:26:13.171 10156 10156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 10:26:13.932 10156 10156 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-01 12:12:51.552 8839 8839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 12:12:52.685 8839 8839 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-01 14:03:44.801 3793 3793 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 14:03:47.301 3793 3793 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-01 14:03:47.302 3793 3793 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.Class.newInstance(Native Method)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-01 14:03:47.302 3793 3793 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-01 14:03:47.302 3793 3793 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-01 14:03:47.302 3793 3793 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-01 14:03:47.302 3793 3793 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-01 14:03:47.302 3793 3793 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-01 14:03:47.302 3793 3793 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-01 14:03:47.302 3793 3793 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-01 14:03:47.302 3793 3793 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-01 14:03:47.638 3793 3793 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-01 14:03:50.487 3793 3793 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-01 14:03:50.488 3793 3793 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-01 14:03:51.936 3793 3793 W com.mbwhatsapp: type=1400 audit(0.0:1213): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 14:03:52.559 3793 3793 W com.mbwhatsapp: type=1400 audit(0.0:1214): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 14:03:52.559 3793 3793 W com.mbwhatsapp: type=1400 audit(0.0:1215): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 14:03:52.559 3793 3793 W com.mbwhatsapp: type=1400 audit(0.0:1216): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 14:03:52.559 3793 3793 W com.mbwhatsapp: type=1400 audit(0.0:1217): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
05-01 14:03:53.565 3793 4589 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-01 14:03:53.565 3793 4589 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-01 14:03:53.565 3793 4589 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-01 14:06:17.137 10358 10358 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 14:06:17.611 10358 10358 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-01 14:06:18.251 10358 10358 W com.mbwhatsapp: type=1400 audit(0.0:2637): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-01 14:58:12.111 15981 15981 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 14:58:12.652 15981 15981 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-01 15:58:12.189 20653 20653 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 15:58:12.636 20653 20653 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-01 16:58:14.827 25493 25493 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 16:58:15.351 25493 25493 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-01 17:24:20.107 1347 1347 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 17:24:21.292 1347 1347 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-01 17:24:22.904 1347 1347 W com.mbwhatsapp: type=1400 audit(0.0:7940): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 17:24:22.957 1347 1347 W com.mbwhatsapp: type=1400 audit(0.0:7941): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-01 17:24:22.957 1347 1347 W com.mbwhatsapp: type=1400 audit(0.0:7942): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-01 22:18:07.657 28074 28074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-01 22:18:08.320 28074 28074 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-02 02:00:11.254 8444 8444 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-02 02:00:12.009 8444 8444 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-02 17:12:06.514 15105 15105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-02 17:12:14.113 15105 15105 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-02 17:18:23.056 19322 19322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-02 17:18:23.644 19322 19322 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-02 22:32:16.403 9396 9396 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-02 22:32:17.443 9396 9396 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-02 22:32:18.613 9396 9396 W com.mbwhatsapp: type=1400 audit(0.0:2487): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-02 22:32:18.640 9396 9396 W com.mbwhatsapp: type=1400 audit(0.0:2488): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-03 08:18:24.349 5005 5005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 08:18:27.206 5005 5005 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-03 08:18:27.209 5005 5005 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-03 08:18:27.209 5005 5005 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-03 08:18:27.209 5005 5005 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-03 08:18:27.209 5005 5005 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-03 08:18:27.209 5005 5005 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-03 08:18:27.210 5005 5005 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-03 08:18:27.210 5005 5005 W System.err: at
java.lang.Class.newInstance(Native Method)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-03 08:18:27.210 5005 5005 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-03 08:18:27.210 5005 5005 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-03 08:18:27.210 5005 5005 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-03 08:18:27.210 5005 5005 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-03 08:18:27.210 5005 5005 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-03 08:18:27.210 5005 5005 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-03 08:18:27.210 5005 5005 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-03 08:18:27.210 5005 5005 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-03 08:18:27.369 5005 5005 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-03 08:18:30.261 5005 5005 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-03 08:18:30.262 5005 5005 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-03 08:18:32.731 5005 5358 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-03 08:18:32.731 5005 5358 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-03 08:18:32.731 5005 5358 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-03 08:18:34.746 5005 5017 W com.mbwhatsapp: Suspending all threads took:
5.152ms
05-03 08:20:19.293 8841 8841 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 08:20:20.363 8841 8841 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-03 08:22:14.833 13167 13167 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 08:22:18.120 13167 13167 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-03 08:52:45.591 20529 20529 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 08:52:46.118 20529 20529 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-03 08:52:46.890 20529 20529 W com.mbwhatsapp: type=1400 audit(0.0:4759): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-03 10:14:13.570 24111 24111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 10:14:16.614 24111 24111 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-03 10:14:17.313 24111 24111 W com.mbwhatsapp: type=1400 audit(0.0:5296): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-03 11:17:22.378 27139 27139 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 11:17:22.802 27139 27139 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-03 11:58:49.415 29538 29538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 11:58:50.137 29538 29538 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-03 22:32:20.506 17993 17993 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-03 22:32:21.313 17993 17993 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-03 22:32:23.050 17993 18042 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-03 22:32:23.050 17993 18042 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-03 22:32:23.050 17993 18042 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-04 02:00:06.240 22389 22389 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-04 02:00:06.680 22389 22389 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-04 08:11:28.762 4290 4290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-04 08:11:30.727 4290 4290 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-04 08:11:30.738 4290 4290 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.Class.newInstance(Native Method)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-04 08:11:30.738 4290 4290 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-04 08:11:30.738 4290 4290 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-04 08:11:30.738 4290 4290 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-04 08:11:30.738 4290 4290 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-04 08:11:30.738 4290 4290 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-04 08:11:30.738 4290 4290 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-04 08:11:30.738 4290 4290 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-04 08:11:30.738 4290 4290 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-04 08:11:30.926 4290 4290 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-04 08:11:33.702 4290 4290 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-04 08:11:33.703 4290 4290 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-04 08:11:36.772 4290 4290 W com.mbwhatsapp: type=1400 audit(0.0:1405): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-04 08:11:37.136 4290 4290 W com.mbwhatsapp: type=1400 audit(0.0:1406): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-04 08:11:37.366 4290 4290 W com.mbwhatsapp: type=1400 audit(0.0:1407): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-04 08:11:37.366 4290 4290 W com.mbwhatsapp: type=1400 audit(0.0:1408): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-04 08:11:37.366 4290 4290 W com.mbwhatsapp: type=1400 audit(0.0:1409): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-04 08:11:38.270 4290 4903 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-04 08:11:38.270 4290 4903 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-04 08:11:38.270 4290 4903 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-04 08:11:43.851 4290 5184 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-04 08:11:43.851 4290 5184 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-04 09:08:25.471 23555 23555 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-04 09:08:26.489 23555 23555 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-04 12:27:31.067 4483 4483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-04 12:27:33.260 4483 4483 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-04 12:29:04.006 7437 7437 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-04 12:29:05.325 7437 7437 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-04 13:08:16.875 20212 20212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-04 13:08:18.289 20212 20212 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-04 13:08:19.807 20212 20212 W com.mbwhatsapp: type=1400 audit(0.0:8803): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-04 13:08:19.844 20212 20212 W com.mbwhatsapp: type=1400 audit(0.0:8804): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-05 02:02:02.598 4387 4387 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-05 02:02:04.163 4387 4387 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-05 02:02:04.164 4387 4387 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.Class.newInstance(Native Method)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-05 02:02:04.164 4387 4387 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-05 02:02:04.164 4387 4387 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-05 02:02:04.164 4387 4387 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-05 02:02:04.164 4387 4387 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-05 02:02:04.164 4387 4387 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-05 02:02:04.164 4387 4387 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-05 02:02:04.164 4387 4387 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-05 02:02:04.165 4387 4387 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-05 02:02:04.332 4387 4387 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-05 02:02:05.049 4387 4491 W LibraryVersion: Failed to get app version for
libraryName: firebase-iid
05-05 02:02:06.400 4387 4387 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-05 02:02:06.401 4387 4387 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-05 02:02:07.444 4387 4680 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-05 02:02:07.444 4387 4680 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-05 02:02:07.444 4387 4680 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-05 02:02:08.378 4387 4734 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=531d8b59-e24b-46f1-bad2-b87f2b3378ea, generation=0)
05-05 02:02:08.569 4387 4736 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-05 02:02:08.569 4387 4736 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-05 02:03:38.530 7665 7665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-05 02:03:40.273 7665 7665 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-05 02:03:40.277 7665 7665 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-05 02:03:40.278 7665 7665 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-05 02:03:40.278 7665 7665 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-05 02:03:40.278 7665 7665 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-05 02:03:40.278 7665 7665 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-05 02:03:40.278 7665 7665 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-05 02:03:40.278 7665 7665 W System.err: at
java.lang.Class.newInstance(Native Method)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-05 02:03:40.278 7665 7665 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-05 02:03:40.278 7665 7665 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-05 02:03:40.278 7665 7665 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-05 02:03:40.278 7665 7665 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-05 02:03:40.278 7665 7665 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-05 02:03:40.278 7665 7665 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-05 02:03:40.278 7665 7665 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-05 02:03:40.278 7665 7665 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-05 02:03:40.381 7665 7665 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-05 02:03:43.981 7665 7665 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-05 02:03:43.982 7665 7665 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-05 02:03:46.537 7665 7913 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-05 02:03:46.537 7665 7913 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-05 02:03:46.537 7665 7913 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-05 02:58:22.286 20516 20516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-05 02:58:22.755 20516 20516 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-05 02:58:23.473 20516 20516 W com.mbwhatsapp: type=1400 audit(0.0:3894): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-05 02:58:23.497 20516 20516 W com.mbwhatsapp: type=1400 audit(0.0:3895): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-05 03:07:01.340 22355 22355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-05 03:07:01.602 22355 22355 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-05 11:56:13.101 26778 26778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-05 11:56:14.162 26778 26778 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-05 11:56:15.468 26778 26906 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-05 11:56:15.468 26778 26906 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-05 11:56:15.468 26778 26906 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-06 02:01:06.496 11931 11931 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-06 02:01:07.050 11931 11931 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-06 02:01:08.187 11931 12006 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-06 02:01:08.187 11931 12006 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-06 02:01:08.187 11931 12006 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-06 09:09:25.702 21911 21911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-06 09:09:26.143 21911 21911 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-07 01:56:14.738 7956 7956 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 01:56:15.751 7956 7956 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-07 02:44:07.738 24651 24651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 02:44:08.701 24651 24651 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-07 03:44:26.067 28148 28148 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 03:44:26.627 28148 28148 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-07 03:46:30.072 28265 28265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 03:46:30.325 28265 28265 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-07 04:43:56.068 30609 30609 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 04:43:56.377 30609 30609 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-07 05:43:39.031 904 904 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 05:43:39.840 904 904 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-07 05:55:42.160 4600 4600 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 05:55:42.708 4600 4600 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-07 05:55:43.038 4600 4600 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-07 05:55:43.039 4600 4600 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-07 05:55:43.069 4600 4600 W com.mbwhatsapp: type=1400 audit(0.0:7964): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-07 05:55:43.261 4600 4683 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-07 05:55:43.261 4600 4683 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-07 05:55:43.261 4600 4683 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-07 05:55:43.073 4600 4600 W com.mbwhatsapp: type=1400 audit(0.0:7965): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-07 06:44:27.343 10559 10559 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 06:44:27.823 10559 10559 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-07 07:43:44.756 12414 12414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 07:43:45.004 12414 12414 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-07 08:43:46.300 16285 16285 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 08:43:46.717 16285 16285 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-07 09:43:38.882 18410 18410 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-07 09:43:39.150 18410 18410 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-08 13:22:14.539 6257 6257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 13:22:16.957 6257 6257 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-08 13:27:20.666 14020 14020 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 13:27:21.708 14020 14020 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-08 14:15:55.209 28514 28514 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 14:15:56.085 28514 28514 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-08 14:15:57.432 28514 28514 W com.mbwhatsapp: type=1400 audit(0.0:8844): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-08 18:05:42.388 15291 15291 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 18:05:44.056 15291 15291 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-08 19:06:09.833 5726 5726 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 19:06:10.299 5726 5726 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-08 19:06:11.096 5726 5793 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-08 19:06:11.096 5726 5793 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-08 19:06:11.096 5726 5793 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-08 20:21:09.113 19706 19706 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 20:21:09.692 19706 19706 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-08 21:18:26.969 7519 7519 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 21:18:27.673 7519 7519 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-08 21:18:28.729 7519 7568 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-08 21:18:28.729 7519 7568 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-08 21:18:28.729 7519 7568 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-08 21:51:29.230 15086 15086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 21:51:30.687 15086 15086 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-08 23:20:59.866 28600 28600 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 23:21:00.525 28600 28600 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-09 00:22:29.580 6933 6933 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 00:22:29.956 6933 6933 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-09 00:22:30.696 6933 6988 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-09 00:22:30.696 6933 6988 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-09 00:22:30.696 6933 6988 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-09 00:51:23.038 16576 16576 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 00:51:23.604 16576 16576 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-09 02:00:47.131 25866 25866 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 02:00:47.626 25866 25866 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-09 03:18:52.598 6168 6168 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 03:18:57.412 6168 6168 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-09 04:16:56.891 8633 8633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 04:16:57.503 8633 8633 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-09 05:15:57.020 11063 11063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 05:15:57.641 11063 11063 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-09 06:15:57.227 14455 14455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 06:15:57.945 14455 14455 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-09 07:15:58.693 16816 16816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 07:15:59.436 16816 16816 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-09 08:15:57.032 19533 19533 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 08:15:57.607 19533 19533 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-09 09:20:55.177 22380 22380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 09:20:55.697 22380 22380 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-09 10:20:55.110 4644 4644 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 10:20:55.584 4644 4644 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-09 11:16:04.341 18882 18882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 11:16:05.004 18882 18882 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-09 11:16:06.163 18882 18882 W com.mbwhatsapp: type=1400 audit(0.0:77566): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-09 12:16:03.139 24714 24714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 12:16:03.633 24714 24714 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-09 14:15:59.206 8959 8959 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 14:15:59.683 8959 8959 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-09 14:27:02.340 12338 12338 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 14:27:03.636 12338 12338 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-09 16:19:30.921 2836 2836 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 16:19:31.944 2836 2836 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-09 17:18:31.141 13231 13231 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 17:18:31.668 13231 13231 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-09 18:21:04.650 19136 19136 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 18:21:05.286 19136 19136 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-09 19:02:08.983 26130 26130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 19:02:09.589 26130 26130 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-09 19:21:03.289 32071 32071 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 19:21:04.012 32071 32071 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-09 20:16:50.793 17273 17273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 20:16:54.323 17273 17273 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-09 21:21:33.372 24860 24860 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 21:21:33.832 24860 24860 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-09 22:19:39.403 6946 6946 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 22:19:40.097 6946 6946 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-09 22:39:42.347 13322 13322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 22:39:42.904 13322 13322 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-09 23:18:06.775 26054 26054 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 23:18:07.483 26054 26054 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-10 00:21:10.504 1360 1360 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 00:21:11.009 1360 1360 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-10 01:17:33.444 17600 17600 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 01:17:33.931 17600 17600 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-10 01:38:07.373 25190 25190 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 01:38:08.167 25190 25190 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-10 02:15:55.181 30550 30550 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 02:15:56.341 30550 30550 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-10 03:15:57.346 4495 4495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 03:15:57.975 4495 4495 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-10 04:17:29.106 7086 7086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 04:17:29.637 7086 7086 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-10 05:17:29.923 8711 8711 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 05:17:30.263 8711 8711 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-10 06:17:38.820 19572 19572 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 06:17:39.330 19572 19572 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-10 06:49:00.463 23461 23461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 06:49:01.407 23461 23461 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-10 07:17:22.295 31877 31877 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 07:17:22.922 31877 31877 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-10 08:16:09.920 14746 14746 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 08:16:10.421 14746 14746 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-10 08:36:45.419 20325 20325 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 08:36:45.902 20325 20325 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-10 09:16:55.436 28373 28373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 09:16:55.929 28373 28373 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-10 10:17:55.716 7196 7196 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 10:17:56.463 7196 7196 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-10 11:18:13.461 16280 16280 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 11:18:13.963 16280 16280 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-10 12:21:32.578 28132 28132 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 12:21:33.225 28132 28132 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-10 12:37:37.937 30438 30438 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 12:37:38.437 30438 30438 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-10 14:16:08.409 12220 12220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 14:16:08.908 12220 12220 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-10 14:36:23.028 13932 13932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 14:36:23.550 13932 13932 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-10 15:18:14.500 24983 24983 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 15:18:15.766 24983 24983 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-10 16:22:24.951 11869 11869 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 16:22:25.555 11869 11869 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-10 17:58:30.772 10883 10883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 17:58:32.635 10883 10883 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-10 19:02:09.228 17190 17190 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 19:02:09.976 17190 17190 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-10 20:16:28.755 2459 2459 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 20:16:29.383 2459 2459 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-10 20:16:30.789 2459 2527 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-10 20:16:30.789 2459 2527 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-10 21:18:46.254 16621 16621 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 21:18:47.333 16621 16621 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-10 22:01:43.488 10342 10342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 22:01:44.406 10342 10342 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-10 22:29:12.256 24323 24323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 22:29:13.142 24323 24323 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-10 22:29:13.966 24323 24323 W com.mbwhatsapp: type=1400 audit(0.0:9954): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-11 00:04:02.859 11785 11785 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 00:04:03.978 11785 11785 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-11 14:16:37.305 15704 15704 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 14:16:37.809 15704 15704 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-11 14:16:38.537 15704 15756 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-11 14:16:38.537 15704 15756 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-11 14:16:38.537 15704 15756 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-11 19:22:46.391 25830 25830 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 19:22:48.389 25830 25830 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-11 19:22:52.418 25830 26241 W com.mbwhatsapp: Verification of void
X.2rL.A03(java.lang.Integer) took 114.465ms (2149.12 bytecodes/s) (4968B
approximate peak alloc)
05-11 19:22:52.422 25830 26241 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-11 19:22:52.422 25830 26241 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-11 19:22:52.422 25830 26241 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-12 02:03:38.292 22652 22652 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 02:03:40.403 22652 22652 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-12 02:03:41.729 22652 22709 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-12 02:03:41.729 22652 22709 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-12 02:03:41.729 22652 22709 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-12 02:39:24.403 5103 5103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 02:39:25.362 5103 5103 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-12 02:39:25.363 5103 5103 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-12 02:39:25.364 5103 5103 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-12 02:39:25.364 5103 5103 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-12 02:39:25.364 5103 5103 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-12 02:39:25.364 5103 5103 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-12 02:39:25.364 5103 5103 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-12 02:39:25.364 5103 5103 W System.err: at
java.lang.Class.newInstance(Native Method)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-12 02:39:25.364 5103 5103 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-12 02:39:25.364 5103 5103 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-12 02:39:25.364 5103 5103 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-12 02:39:25.364 5103 5103 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-12 02:39:25.364 5103 5103 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-12 02:39:25.364 5103 5103 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-12 02:39:25.364 5103 5103 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-12 02:39:25.364 5103 5103 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-12 02:39:25.735 5103 5103 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-12 02:39:27.509 5103 5103 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-12 02:39:27.510 5103 5103 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-12 02:39:29.014 5103 5180 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-12 02:39:29.014 5103 5180 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-12 02:39:29.014 5103 5180 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-12 02:42:16.823 8998 8998 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 02:42:18.280 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.
--------- beginning of main
05-12 02:45:42.090 13414 13414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 02:45:43.533 13414 13414 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-12 05:52:22.892 17516 17516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 05:52:23.803 17516 17516 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-12 06:40:47.580 26215 26215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:40:48.859 26215 26215 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-12 14:23:43.717 10156 10156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 14:23:44.415 10156 10156 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-12 15:14:56.720 13519 13519 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 15:14:58.343 13519 13519 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-12 17:16:37.603 4585 4585 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 17:16:40.528 4585 4585 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-12 17:19:18.895 9942 9942 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 17:19:19.453 9942 9942 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-12 18:34:08.447 21854 21854 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 18:34:13.992 21854 21854 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-12 18:34:21.578 21854 21854 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-12 18:34:21.579 21854 21854 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-12 18:42:08.420 22398 22398 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 18:42:08.776 22398 22398 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-12 18:51:28.616 23990 23990 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 18:51:29.194 23990 23990 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-12 19:34:07.496 31070 31070 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 19:36:00.779 32426 32426 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 19:36:01.546 32426 32426 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-12 19:39:08.214 3178 3178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 19:39:08.777 3178 3178 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-12 19:42:39.429 5717 5717 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 19:42:40.070 5717 5717 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-12 19:54:11.480 8038 8038 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 19:54:12.151 8038 8038 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-12 20:42:11.556 9394 9394 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 20:42:12.106 9394 9394 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-12 21:03:12.309 11422 11422 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 21:03:13.236 11422 11422 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-12 21:06:48.134 12763 12763 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 21:06:48.909 12763 12763 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-12 21:48:17.109 17248 17248 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 21:48:18.155 17248 17248 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-12 22:04:16.123 19787 19787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 22:04:16.893 19787 19787 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-12 22:23:31.380 21586 21586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 22:23:32.259 21586 21586 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-12 22:33:12.633 22904 22904 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 22:33:13.250 22904 22904 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-12 22:43:13.820 27782 27782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 22:43:14.599 27782 27782 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-12 22:43:15.936 27782 27782 W com.mbwhatsapp: type=1400 audit(0.0:18245): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-12 23:33:50.462 9964 9964 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 23:33:51.422 9964 9964 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-12 23:33:52.813 9964 9964 W com.mbwhatsapp: type=1400 audit(0.0:24789): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-12 23:33:52.823 9964 9964 W com.mbwhatsapp: type=1400 audit(0.0:24790): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-12 23:38:48.837 11185 11185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 23:38:49.778 11185 11185 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 00:04:12.123 17932 17932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 00:04:12.919 17932 17932 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 00:07:59.278 18657 18657 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 00:07:59.914 18657 18657 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 00:10:30.693 19370 19370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 00:10:31.104 19370 19370 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 00:15:27.422 20290 20290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 00:15:28.268 20290 20290 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 00:15:29.461 20290 20290 W com.mbwhatsapp: type=1400 audit(0.0:26721): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 00:25:33.094 21608 21608 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 00:25:34.212 21608 21608 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 00:36:02.166 23430 23430 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 00:36:02.858 23430 23430 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 00:36:04.042 23430 23430 W com.mbwhatsapp: type=1400 audit(0.0:31847): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 00:36:04.068 23430 23430 W com.mbwhatsapp: type=1400 audit(0.0:31848): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 01:33:34.032 31497 31497 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 01:33:34.812 31497 31497 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 01:33:36.256 31497 31497 W com.mbwhatsapp: type=1400 audit(0.0:46031): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 01:33:36.272 31497 31497 W com.mbwhatsapp: type=1400 audit(0.0:46032): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 02:33:19.689 4742 4742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 02:33:20.402 4742 4742 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 02:33:21.592 4742 4742 W com.mbwhatsapp: type=1400 audit(0.0:46602): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 02:33:21.602 4742 4742 W com.mbwhatsapp: type=1400 audit(0.0:46603): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 03:33:42.327 10733 10733 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 03:33:43.060 10733 10733 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 04:33:12.266 13960 13960 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 04:33:13.042 13960 13960 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 04:33:14.230 13960 13960 W com.mbwhatsapp: type=1400 audit(0.0:48441): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 04:33:14.244 13960 13960 W com.mbwhatsapp: type=1400 audit(0.0:48442): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-13 04:33:14.277 13960 13960 W com.mbwhatsapp: type=1400 audit(0.0:48443): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 05:33:21.944 18966 18966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 05:33:23.367 18966 18966 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 06:33:41.283 22247 22247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 06:33:42.126 22247 22247 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 07:33:19.673 25905 25905 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 07:33:20.365 25905 25905 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:33:21.658 25905 25905 W com.mbwhatsapp: type=1400 audit(0.0:50040): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 08:33:12.192 28175 28175 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 08:33:12.729 28175 28175 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 09:33:12.202 4036 4036 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 09:33:12.909 4036 4036 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 10:33:12.175 7281 7281 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 10:33:13.009 7281 7281 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 11:33:19.639 11839 11839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 11:33:20.169 11839 11839 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 12:33:20.232 15701 15701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 12:33:20.840 15701 15701 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 12:42:21.240 18103 18103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 12:42:21.924 18103 18103 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 12:47:43.518 19832 19832 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 12:47:44.027 19832 19832 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 12:50:20.042 20662 20662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 12:50:20.608 20662 20662 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 13:03:12.225 21893 21893 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 13:03:12.775 21893 21893 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 13:06:27.880 22311 22311 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 13:06:28.261 22311 22311 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 13:16:40.455 23442 23442 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 13:16:41.451 23442 23442 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 13:37:31.234 29103 29103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 13:37:31.651 29103 29103 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 13:37:32.885 29103 29163 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-13 13:37:32.885 29103 29163 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-13 13:37:32.885 29103 29163 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-13 13:44:01.833 29756 29756 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 13:44:02.267 29756 29756 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 14:38:10.452 4043 4043 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 14:38:10.934 4043 4043 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 14:56:43.118 5841 5841 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 14:56:43.743 5841 5841 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 15:02:06.984 6466 6466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 15:02:07.284 6466 6466 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 15:10:10.561 6650 6650 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 15:10:10.815 6650 6650 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 15:22:54.468 7741 7741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 15:22:55.239 7741 7741 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 15:34:42.612 8149 8149 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 15:34:42.843 8149 8149 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 15:47:51.563 10370 10370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 15:47:52.207 10370 10370 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:33:34.361 17596 17596 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 16:33:34.841 17596 17596 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 17:33:21.059 32176 32176 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 17:33:23.191 32176 32176 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 17:33:25.473 32176 32176 W com.mbwhatsapp: type=1400 audit(0.0:90017): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-13 18:36:04.796 22329 22329 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 18:36:05.581 22329 22329 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 19:33:46.398 29025 29025 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 19:33:47.375 29025 29025 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 19:33:48.709 29025 29096 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=3156b2fd-bd3b-412b-84a8-e1e00c00dbad, generation=0)
--------- beginning of main
05-13 19:54:56.454 2889 2889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 19:54:56.948 2889 2889 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 20:32:48.523 6484 6484 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 20:32:49.277 6484 6484 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 21:33:47.949 27251 27251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 21:33:48.581 27251 27251 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 22:44:13.412 11402 11402 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 22:44:14.333 11402 11402 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 23:54:11.575 17957 17957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-13 23:54:12.361 17957 17957 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 01:06:11.868 20465 20465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 01:06:13.018 20465 20465 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 02:07:42.287 27303 27303 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 02:07:44.649 27303 27303 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 03:09:45.884 4516 4516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 03:09:46.406 4516 4516 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 03:44:13.946 14974 14974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 03:44:14.447 14974 14974 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 04:38:11.558 17219 17219 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 04:38:12.145 17219 17219 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 05:49:11.272 20920 20920 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 05:49:12.016 20920 20920 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 07:11:59.061 27569 27569 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 07:12:00.785 27569 27569 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 08:25:44.587 11201 11201 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 08:25:45.128 11201 11201 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 13:14:34.879 4206 4206 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 13:14:36.810 4206 4206 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-14 13:14:36.810 4206 4206 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-14 13:14:36.810 4206 4206 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-14 13:14:36.811 4206 4206 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-14 13:14:36.811 4206 4206 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-14 13:14:36.811 4206 4206 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-14 13:14:36.811 4206 4206 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-14 13:14:36.811 4206 4206 W System.err: at
java.lang.Class.newInstance(Native Method)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-14 13:14:36.811 4206 4206 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-14 13:14:36.811 4206 4206 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-14 13:14:36.811 4206 4206 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-14 13:14:36.811 4206 4206 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-14 13:14:36.811 4206 4206 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-14 13:14:36.811 4206 4206 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-14 13:14:36.811 4206 4206 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-14 13:14:36.811 4206 4206 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-14 13:14:37.364 4206 4206 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 13:14:40.368 4206 4206 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-14 13:14:40.369 4206 4206 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-14 13:14:44.557 4206 4790 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 13:14:44.557 4206 4790 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 13:14:44.557 4206 4790 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-14 13:14:47.900 4206 4983 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-14 13:14:47.901 4206 4983 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-14 13:16:54.900 9714 9714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 13:16:56.815 9714 9714 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 13:43:05.870 16928 16928 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 13:43:06.434 16928 16928 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 13:57:18.827 21638 21638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 13:57:19.512 21638 21638 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 16:08:32.159 12461 12461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 16:08:33.046 12461 12461 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 16:08:34.087 12461 12577 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 16:08:34.087 12461 12577 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 16:08:34.087 12461 12577 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-14 16:34:45.524 15623 15623 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 16:34:46.162 15623 15623 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 16:34:46.967 15623 15682 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 16:34:46.967 15623 15682 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 16:34:46.967 15623 15682 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-14 18:08:37.924 15279 15279 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 18:08:39.305 15279 15279 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 18:39:52.119 27197 27197 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 18:39:52.967 27197 27197 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 20:09:00.503 8189 8189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 20:09:01.150 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 21:11:04.310 15056 15056 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 21:11:05.852 15056 15056 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 21:11:07.290 15056 15165 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-14 21:11:07.290 15056 15165 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-14 21:11:07.290 15056 15165 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-14 22:09:33.725 29595 29595 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 22:09:34.921 29595 29595 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 23:22:39.954 8273 8273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-14 23:22:40.615 8273 8273 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:51:00.916 14902 14902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 06:51:02.541 14902 14902 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:51:06.380 14902 14902 W com.mbwhatsapp: type=1400 audit(0.0:298192): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-15 08:09:28.163 4637 4637 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 08:09:29.341 4637 4637 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-15 08:09:29.353 4637 4637 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.Class.newInstance(Native Method)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-15 08:09:29.353 4637 4637 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-15 08:09:29.353 4637 4637 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-15 08:09:29.353 4637 4637 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-15 08:09:29.353 4637 4637 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-15 08:09:29.353 4637 4637 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-15 08:09:29.353 4637 4637 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-15 08:09:29.353 4637 4637 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-15 08:09:29.353 4637 4637 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-15 08:09:29.649 4637 4637 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 08:09:32.335 4637 4637 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-15 08:09:32.335 4637 4637 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-15 08:09:33.545 4637 4637 W com.mbwhatsapp: type=1400 audit(0.0:1530): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 08:09:33.791 4637 4637 W com.mbwhatsapp: type=1400 audit(0.0:1531): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 08:09:33.791 4637 4637 W com.mbwhatsapp: type=1400 audit(0.0:1532): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 08:09:34.889 4637 5176 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 08:09:34.889 4637 5176 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 08:09:34.889 4637 5176 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-15 08:11:14.650 7791 7791 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 08:11:16.660 7791 7791 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:16:42.154 12363 12363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 08:16:44.025 12363 12363 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:41:23.619 18187 18187 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 08:41:24.355 18187 18187 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 08:41:31.589 18187 18187 W com.mbwhatsapp: type=1400 audit(0.0:9707): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-15 09:02:21.981 21848 21848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 09:02:23.006 21848 21848 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 16:35:07.959 5109 5109 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 16:35:10.673 5109 5109 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-15 16:35:10.674 5109 5109 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.Class.newInstance(Native Method)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-15 16:35:10.674 5109 5109 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-15 16:35:10.674 5109 5109 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-15 16:35:10.674 5109 5109 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-15 16:35:10.674 5109 5109 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-15 16:35:10.674 5109 5109 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-15 16:35:10.674 5109 5109 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-15 16:35:10.674 5109 5109 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-15 16:35:10.674 5109 5109 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-15 16:35:10.857 5109 5109 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 16:35:13.646 5109 5121 W com.mbwhatsapp: Suspending all threads took:
9.951ms
05-15 16:35:13.660 5109 5109 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-15 16:35:13.660 5109 5109 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-15 16:35:14.132 5109 5109 W com.mbwhatsapp: type=1400 audit(0.0:1379): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 16:35:14.189 5109 5109 W com.mbwhatsapp: type=1400 audit(0.0:1380): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 16:35:14.242 5109 5109 W com.mbwhatsapp: type=1400 audit(0.0:1381): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 16:35:14.675 5109 5109 W com.mbwhatsapp: type=1400 audit(0.0:1382): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 16:35:14.869 5109 5109 W com.mbwhatsapp: type=1400 audit(0.0:1383): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 16:35:18.170 5109 5544 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 16:35:18.170 5109 5544 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 16:35:18.170 5109 5544 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-15 16:35:18.713 5109 5121 W com.mbwhatsapp: Suspending all threads took:
25.958ms
05-15 16:37:55.446 10848 10848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 16:38:00.158 10848 10848 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 16:38:18.208 10848 11415 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 16:38:18.208 10848 11415 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 16:38:18.208 10848 11415 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-15 16:43:48.340 16145 16145 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 16:43:51.875 16145 16145 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 17:29:07.250 25395 25395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 17:29:07.973 25395 25395 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 19:03:00.893 6049 6049 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 19:03:01.694 6049 6049 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-15 19:03:01.695 6049 6049 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-15 19:03:01.695 6049 6049 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-15 19:03:01.695 6049 6049 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-15 19:03:01.695 6049 6049 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-15 19:03:01.695 6049 6049 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-15 19:03:01.695 6049 6049 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-15 19:03:01.695 6049 6049 W System.err: at
java.lang.Class.newInstance(Native Method)
05-15 19:03:01.695 6049 6049 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-15 19:03:01.696 6049 6049 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-15 19:03:01.696 6049 6049 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-15 19:03:01.696 6049 6049 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-15 19:03:01.696 6049 6049 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-15 19:03:01.696 6049 6049 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-15 19:03:01.696 6049 6049 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-15 19:03:01.696 6049 6049 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-15 19:03:01.696 6049 6049 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-15 19:03:01.696 6049 6049 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-15 19:03:01.696 6049 6049 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-15 19:03:01.696 6049 6049 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-15 19:03:01.696 6049 6049 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-15 19:03:01.696 6049 6049 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-15 19:03:01.754 6049 6049 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 19:03:02.346 6049 6049 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-15 19:03:02.347 6049 6049 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-15 19:03:02.715 6049 6187 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 19:03:02.715 6049 6187 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 19:03:02.715 6049 6187 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-15 19:39:19.081 5233 5233 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 19:39:20.387 5233 5233 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 19:39:23.952 5233 5233 W com.mbwhatsapp: type=1400 audit(0.0:1559): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 19:39:23.965 5233 5233 W com.mbwhatsapp: type=1400 audit(0.0:1560): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-15 19:40:01.112 6519 6519 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 19:40:01.392 6519 6519 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 19:57:12.126 20614 20614 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 19:57:13.485 20614 20614 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 19:57:16.175 20614 20665 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 19:57:16.175 20614 20665 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 19:57:16.175 20614 20665 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-15 20:57:39.075 3143 3143 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 20:57:40.024 3143 3143 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 20:57:41.710 3143 3245 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 20:57:41.710 3143 3245 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 20:57:41.710 3143 3245 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-15 21:57:04.825 15493 15493 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 21:57:05.688 15493 15493 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 21:57:07.405 15493 15580 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 21:57:07.405 15493 15580 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 21:57:07.405 15493 15580 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-15 22:10:18.980 5235 5235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 22:10:20.886 5235 5235 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-15 22:10:20.889 5235 5235 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.Class.newInstance(Native Method)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-15 22:10:20.889 5235 5235 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-15 22:10:20.889 5235 5235 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-15 22:10:20.889 5235 5235 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-15 22:10:20.889 5235 5235 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-15 22:10:20.889 5235 5235 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-15 22:10:20.889 5235 5235 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-15 22:10:20.889 5235 5235 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-15 22:10:20.889 5235 5235 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-15 22:10:21.108 5235 5235 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 22:10:23.204 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1389): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:10:22.925 5235 5235 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-15 22:10:22.927 5235 5235 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-15 22:10:23.264 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1390): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-15 22:10:23.421 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1391): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:10:23.964 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1393): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:10:24.528 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1394): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:10:24.528 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1395): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:10:24.528 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1396): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:10:24.528 5235 5235 W com.mbwhatsapp: type=1400 audit(0.0:1397): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
05-15 22:10:25.910 5235 5480 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-15 22:10:25.910 5235 5480 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-15 22:10:25.910 5235 5480 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-15 22:10:28.540 5235 5512 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-15 22:10:28.540 5235 5512 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-15 22:42:07.277 19346 19346 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-15 22:42:07.844 19346 19346 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 22:42:08.442 19346 19346 W com.mbwhatsapp: type=1400 audit(0.0:20430): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-15 22:42:08.462 19346 19346 W com.mbwhatsapp: type=1400 audit(0.0:20431): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-16 07:59:31.499 4505 4505 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 07:59:35.411 4505 4505 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-16 07:59:35.413 4505 4505 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-16 07:59:35.414 4505 4505 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-16 07:59:35.414 4505 4505 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-16 07:59:35.414 4505 4505 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-16 07:59:35.414 4505 4505 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-16 07:59:35.414 4505 4505 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-16 07:59:35.414 4505 4505 W System.err: at
java.lang.Class.newInstance(Native Method)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-16 07:59:35.414 4505 4505 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-16 07:59:35.414 4505 4505 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-16 07:59:35.414 4505 4505 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-16 07:59:35.414 4505 4505 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-16 07:59:35.414 4505 4505 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-16 07:59:35.414 4505 4505 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-16 07:59:35.414 4505 4505 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-16 07:59:35.414 4505 4505 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-16 07:59:35.725 4505 4505 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 07:59:38.361 4505 4505 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-16 07:59:38.361 4505 4505 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-16 07:59:38.756 4505 4505 W com.mbwhatsapp: type=1400 audit(0.0:1296): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 07:59:38.802 4505 4505 W com.mbwhatsapp: type=1400 audit(0.0:1297): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 07:59:38.856 4505 4505 W com.mbwhatsapp: type=1400 audit(0.0:1298): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 07:59:39.199 4505 4505 W com.mbwhatsapp: type=1400 audit(0.0:1299): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 07:59:39.322 4505 4505 W com.mbwhatsapp: type=1400 audit(0.0:1300): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 07:59:40.089 4505 4864 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-16 07:59:40.089 4505 4864 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-16 07:59:40.089 4505 4864 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-16 08:00:53.902 4505 7010 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-16 08:00:53.903 4505 7010 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-16 08:06:20.087 10988 10988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 08:06:22.242 10988 10988 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:11:33.370 15149 15149 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 08:11:40.730 15149 15149 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:09:30.921 24491 24491 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 09:09:31.479 24491 24491 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:07:55.898 13638 13638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 11:07:56.852 13638 13638 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:09:30.952 23605 23605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 12:09:31.670 23605 23605 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:09:30.884 30359 30359 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 13:09:31.321 30359 30359 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:22:44.581 1103 1103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 13:22:45.809 1103 1103 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:43:39.072 4910 4910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 13:43:39.369 4910 4910 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 14:50:44.186 17883 17883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 14:50:45.104 17883 17883 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 14:50:46.059 17883 17883 W com.mbwhatsapp: type=1400 audit(0.0:26320): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-16 14:50:46.059 17883 17883 W com.mbwhatsapp: type=1400 audit(0.0:26321): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-16 19:06:18.689 27163 27163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 19:06:19.277 27163 27163 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 23:07:23.660 31737 31737 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-16 23:07:24.787 31737 31737 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 23:07:27.565 31737 31737 W com.mbwhatsapp: type=1400 audit(0.0:31216): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-17 00:54:56.675 26513 26513 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 00:54:57.211 26513 26513 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-17 00:54:58.233 26513 26562 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-17 00:54:58.233 26513 26562 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-17 00:54:58.233 26513 26562 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-17 01:53:50.474 8782 8782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 01:53:51.342 8782 8782 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-17 01:53:53.094 8782 8833 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-17 01:53:53.094 8782 8833 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-17 01:53:53.094 8782 8833 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-17 02:53:44.071 15597 15597 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 02:53:44.616 15597 15597 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 04:53:44.915 22423 22423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 04:53:45.394 22423 22423 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:53:44.143 26138 26138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 10:53:45.236 26138 26138 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 12:01:54.627 4122 4122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 12:01:56.252 4122 4122 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-17 12:01:56.267 4122 4122 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-17 12:01:56.268 4122 4122 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-17 12:01:56.268 4122 4122 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-17 12:01:56.268 4122 4122 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-17 12:01:56.268 4122 4122 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-17 12:01:56.268 4122 4122 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-17 12:01:56.275 4122 4122 W System.err: at
java.lang.Class.newInstance(Native Method)
05-17 12:01:56.275 4122 4122 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-17 12:01:56.275 4122 4122 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-17 12:01:56.275 4122 4122 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-17 12:01:56.275 4122 4122 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-17 12:01:56.275 4122 4122 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-17 12:01:56.275 4122 4122 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-17 12:01:56.275 4122 4122 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-17 12:01:56.275 4122 4122 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-17 12:01:56.276 4122 4122 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-17 12:01:56.276 4122 4122 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-17 12:01:56.276 4122 4122 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-17 12:01:56.276 4122 4122 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-17 12:01:56.276 4122 4122 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-17 12:01:56.276 4122 4122 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-17 12:01:56.495 4122 4122 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-17 12:01:59.838 4122 4122 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-17 12:01:59.853 4122 4122 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-17 12:02:00.419 4122 4122 W com.mbwhatsapp: type=1400 audit(0.0:1288): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-17 12:02:00.465 4122 4122 W com.mbwhatsapp: type=1400 audit(0.0:1289): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-17 12:02:00.582 4122 4122 W com.mbwhatsapp: type=1400 audit(0.0:1290): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-17 13:30:38.170 4675 4675 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 13:30:39.249 4675 4675 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-17 13:30:39.250 4675 4675 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-17 13:30:39.250 4675 4675 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-17 13:30:39.250 4675 4675 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-17 13:30:39.250 4675 4675 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-17 13:30:39.250 4675 4675 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-17 13:30:39.250 4675 4675 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-17 13:30:39.250 4675 4675 W System.err: at
java.lang.Class.newInstance(Native Method)
05-17 13:30:39.250 4675 4675 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-17 13:30:39.250 4675 4675 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-17 13:30:39.250 4675 4675 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-17 13:30:39.250 4675 4675 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-17 13:30:39.250 4675 4675 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-17 13:30:39.250 4675 4675 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-17 13:30:39.250 4675 4675 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-17 13:30:39.250 4675 4675 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-17 13:30:39.250 4675 4675 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-17 13:30:39.250 4675 4675 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-17 13:30:39.251 4675 4675 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-17 13:30:39.251 4675 4675 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-17 13:30:39.251 4675 4675 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-17 13:30:39.251 4675 4675 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-17 13:30:39.477 4675 4675 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 13:30:41.122 4675 4675 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-17 13:30:41.123 4675 4675 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-17 13:30:42.643 4675 4975 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-17 13:30:42.643 4675 4975 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-17 13:30:42.643 4675 4975 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-17 13:34:08.050 11686 11686 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 13:34:08.777 11686 11686 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-17 13:34:09.834 11686 11686 W com.mbwhatsapp: type=1400 audit(0.0:2777): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-17 13:34:09.874 11686 11686 W com.mbwhatsapp: type=1400 audit(0.0:2778): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-17 13:37:39.926 14869 14869 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 13:37:43.470 14869 14869 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 14:10:56.476 26431 26431 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 14:10:57.457 26431 26431 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 18:55:28.989 5509 5509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 18:55:32.183 5509 5509 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-17 18:55:32.203 5509 5509 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.Class.newInstance(Native Method)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-17 18:55:32.203 5509 5509 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-17 18:55:32.203 5509 5509 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-17 18:55:32.203 5509 5509 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-17 18:55:32.203 5509 5509 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-17 18:55:32.203 5509 5509 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-17 18:55:32.203 5509 5509 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-17 18:55:32.203 5509 5509 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-17 18:55:32.203 5509 5509 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-17 18:55:32.982 5509 5509 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-17 18:55:37.248 5509 5509 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-17 18:55:37.249 5509 5509 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-17 18:55:40.971 5509 5905 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-17 18:55:40.971 5509 5905 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-17 18:55:40.971 5509 5905 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-17 18:55:44.502 5509 6011 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-17 18:55:44.502 5509 6011 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
05-17 19:12:34.321 19978 19978 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-17 19:12:35.094 19978 19978 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 02:11:08.698 6254 6254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 02:11:10.789 6254 6254 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-18 02:11:10.792 6254 6254 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.Class.newInstance(Native Method)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-18 02:11:10.792 6254 6254 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-18 02:11:10.792 6254 6254 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-18 02:11:10.792 6254 6254 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-18 02:11:10.792 6254 6254 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-18 02:11:10.792 6254 6254 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-18 02:11:10.792 6254 6254 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-18 02:11:10.792 6254 6254 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-18 02:11:10.792 6254 6254 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-18 02:11:11.012 6254 6254 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-18 02:11:12.443 6254 6254 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-18 02:11:12.443 6254 6254 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-18 02:18:40.898 14204 14204 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 02:18:44.355 14204 14204 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 03:03:43.491 23456 23456 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 03:03:44.190 23456 23456 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 03:06:03.490 23581 23581 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 03:06:03.713 23581 23581 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 03:08:52.877 23705 23705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 03:08:53.158 23705 23705 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 03:12:43.832 23889 23889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 03:12:44.087 23889 23889 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 04:08:54.545 27739 27739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 04:08:55.130 27739 27739 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 04:10:47.029 28471 28471 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 04:10:47.294 28471 28471 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 04:14:11.990 28726 28726 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 04:14:12.231 28726 28726 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 04:17:08.674 28892 28892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 04:17:08.874 28892 28892 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 05:03:49.127 32410 32410 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 05:03:49.701 32410 32410 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:03:41.268 8591 8591 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 06:03:42.034 8591 8591 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:15:53.038 13556 13556 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 06:15:56.215 13556 13556 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:33:41.000 24570 24570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 06:33:42.208 24570 24570 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 08:03:46.504 5639 5639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 08:03:47.322 5639 5639 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 09:03:40.969 12650 12650 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 09:03:42.007 12650 12650 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 10:03:40.998 19531 19531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 10:03:41.826 19531 19531 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-18 10:03:43.321 19531 19581 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-18 10:03:43.321 19531 19581 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-18 10:03:43.321 19531 19581 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-18 11:03:51.340 24975 24975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 11:03:52.133 24975 24975 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 11:09:50.898 25464 25464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 11:09:51.606 25464 25464 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 12:13:54.828 30882 30882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 12:13:56.015 30882 30882 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-18 12:13:57.531 30882 31012 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-18 12:13:57.531 30882 31012 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-18 12:13:57.531 30882 31012 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-18 12:20:11.651 843 843 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 12:20:13.728 843 843 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 12:21:49.674 3083 3083 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 12:21:50.306 3083 3083 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 12:23:58.468 4395 4395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 12:23:59.365 4395 4395 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 12:30:31.298 6882 6882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 12:30:32.036 6882 6882 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 13:03:41.084 15333 15333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 13:03:42.140 15333 15333 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 13:05:36.552 17011 17011 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 13:05:37.370 17011 17011 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 14:06:08.499 24422 24422 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 14:06:09.139 24422 24422 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 15:07:23.297 32376 32376 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 15:07:23.893 32376 32376 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 16:53:55.984 4223 4223 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 16:53:57.389 4223 4223 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 18:58:04.530 7501 7501 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 18:58:05.362 7501 7501 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 21:52:49.602 11085 11085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 21:52:52.370 11085 11085 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 21:54:04.324 12420 12420 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 21:54:04.622 12420 12420 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 23:09:37.879 22964 22964 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 23:09:39.757 22964 22964 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 23:12:17.195 23803 23803 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 23:12:19.892 23803 23803 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 23:16:45.756 26031 26031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 23:16:46.396 26031 26031 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 23:28:50.654 26742 26742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-18 23:28:51.429 26742 26742 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 00:46:06.769 4661 4661 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 00:46:08.651 4661 4661 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-19 00:46:08.652 4661 4661 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-19 00:46:08.653 4661 4661 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-19 00:46:08.653 4661 4661 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-19 00:46:08.653 4661 4661 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-19 00:46:08.653 4661 4661 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-19 00:46:08.653 4661 4661 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-19 00:46:08.653 4661 4661 W System.err: at
java.lang.Class.newInstance(Native Method)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-19 00:46:08.653 4661 4661 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-19 00:46:08.653 4661 4661 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-19 00:46:08.653 4661 4661 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-19 00:46:08.653 4661 4661 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-19 00:46:08.653 4661 4661 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-19 00:46:08.653 4661 4661 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-19 00:46:08.653 4661 4661 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-19 00:46:08.653 4661 4661 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-19 00:46:08.772 4661 4661 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 00:46:11.572 4661 4661 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-19 00:46:11.581 4661 4661 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-19 00:46:11.915 4661 4661 W com.mbwhatsapp: type=1400 audit(0.0:1337): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 00:46:11.935 4661 4661 W com.mbwhatsapp: type=1400 audit(0.0:1338): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 00:46:12.002 4661 4661 W com.mbwhatsapp: type=1400 audit(0.0:1339): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 00:46:12.295 4661 4661 W com.mbwhatsapp: type=1400 audit(0.0:1340): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 00:46:12.375 4661 4661 W com.mbwhatsapp: type=1400 audit(0.0:1341): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-19 00:46:12.943 4661 4670 W com.mbwhatsapp: Suspending all threads took:
10.928ms
--------- beginning of main
05-19 00:52:45.103 9342 9342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 00:52:49.292 9342 9342 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 00:52:54.942 9342 9503 W com.mbwhatsapp: Verification of void
X.2rL.A03(java.lang.Integer) took 125.768ms (1955.98 bytecodes/s) (4968B
approximate peak alloc)
05-19 00:52:54.990 9342 9503 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-19 00:52:54.990 9342 9503 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-19 00:52:54.990 9342 9503 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-19 06:25:11.663 22584 22584 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 06:25:12.429 22584 22584 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 07:01:15.785 29414 29414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 07:01:16.475 29414 29414 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 11:02:34.823 18378 18378 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 11:02:35.363 18378 18378 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 11:02:36.701 18378 18480 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-19 11:02:36.701 18378 18480 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-19 11:02:36.701 18378 18480 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-19 11:02:36.489 18378 18378 W com.mbwhatsapp: type=1400 audit(0.0:50500): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-19 15:04:02.781 32320 32320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 15:04:04.310 32320 32320 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 16:04:02.787 16878 16878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 16:04:03.612 16878 16878 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 18:06:32.213 5104 5104 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 18:06:32.771 5104 5104 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 20:40:39.410 7632 7632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-19 20:40:40.317 7632 7632 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 20:40:41.924 7632 7706 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-19 20:40:41.924 7632 7706 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-20 00:14:41.019 6364 6364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 00:14:42.431 6364 6364 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 00:15:27.886 7949 7949 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 00:15:28.699 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.
--------- beginning of main
05-20 00:54:43.999 18092 18092 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 00:54:44.665 18092 18092 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 00:54:45.525 18092 18092 W com.mbwhatsapp: type=1400 audit(0.0:10063): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-20 01:01:40.783 20039 20039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 01:01:41.487 20039 20039 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 01:28:35.253 24009 24009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 01:28:36.349 24009 24009 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 03:05:05.837 30253 30253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 03:05:06.245 30253 30253 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 04:08:57.971 31461 31461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 04:08:58.231 31461 31461 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 05:04:12.089 5819 5819 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 05:04:12.652 5819 5819 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 05:27:03.403 8094 8094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 05:27:04.844 8094 8094 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 07:04:36.353 16944 16944 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 07:04:36.889 16944 16944 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 07:04:37.708 16944 16997 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-20 07:04:37.708 16944 16997 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-20 07:04:37.708 16944 16997 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-20 08:10:30.145 19622 19622 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 08:10:31.321 19622 19622 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 13:04:27.194 30221 30221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 13:04:27.849 30221 30221 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 15:02:30.130 5015 5015 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 15:02:31.363 5015 5015 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:04:15.644 15212 15212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 16:04:16.382 15212 15212 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 16:04:18.337 15212 15260 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-20 16:04:18.337 15212 15260 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-20 16:04:18.337 15212 15260 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-20 17:04:18.546 19996 19996 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 17:04:20.401 19996 19996 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 18:06:19.613 31409 31409 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 18:06:20.821 31409 31409 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 19:06:03.840 11196 11196 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 19:06:06.129 11196 11196 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 19:08:21.305 13202 13202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 19:08:25.321 13202 13202 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 20:04:12.187 26932 26932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 20:04:13.049 26932 26932 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 20:04:14.441 26932 26981 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-20 20:04:14.441 26932 26981 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-20 20:04:14.441 26932 26981 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-20 21:13:42.787 31434 31434 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 21:13:43.861 31434 31434 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 22:04:26.444 5982 5982 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 22:04:27.663 5982 5982 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 23:10:30.087 19720 19720 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-20 23:10:31.032 19720 19720 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 01:04:37.486 29935 29935 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 01:04:38.173 29935 29935 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 02:00:19.072 5066 5066 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 02:00:19.920 5066 5066 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 02:04:38.667 5794 5794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 02:04:39.218 5794 5794 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 03:05:03.655 7977 7977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 03:05:04.250 7977 7977 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 04:04:47.976 9369 9369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 04:04:48.242 9369 9369 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 05:04:21.217 10968 10968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 05:04:21.492 10968 10968 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 06:04:13.381 13723 13723 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 06:04:21.969 13723 13723 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:05:16.467 22544 22544 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 07:05:17.093 22544 22544 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:05:34.040 22544 22592 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-21 07:05:34.040 22544 22592 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-21 07:05:34.040 22544 22592 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-21 13:20:51.904 11474 11474 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 13:20:53.020 11474 11474 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:04:41.220 29276 29276 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 16:04:42.093 29276 29276 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 17:04:28.022 9573 9573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 17:04:28.754 9573 9573 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:04:29.578 9573 9620 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-21 17:04:29.578 9573 9620 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-21 17:04:29.578 9573 9620 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-21 18:04:27.804 16248 16248 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 18:04:28.677 16248 16248 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 20:06:59.846 667 667 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 20:07:00.870 667 667 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 20:07:02.164 667 1010 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-21 20:07:02.164 667 1010 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-21 20:07:02.164 667 1010 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-21 21:04:39.734 9082 9082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 21:04:40.465 9082 9082 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:22:07.436 15477 15477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 21:22:10.863 15477 15477 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 22:04:12.132 26506 26506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 22:04:13.035 26506 26506 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 23:13:15.068 31452 31452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-21 23:13:16.203 31452 31452 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 00:04:28.495 17008 17008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 00:04:29.158 17008 17008 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 00:11:35.185 19152 19152 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 00:11:36.259 19152 19152 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:04:12.004 22838 22838 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 01:04:12.607 22838 22838 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:00:03.059 25862 25862 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 02:00:03.559 25862 25862 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:04:24.836 27854 27854 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 03:04:25.370 27854 27854 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 04:04:11.996 29567 29567 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 04:04:12.491 29567 29567 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 05:04:12.014 31421 31421 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 05:04:12.504 31421 31421 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 06:04:22.314 2972 2972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 06:04:23.080 2972 2972 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 07:04:12.084 5251 5251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 07:04:12.514 5251 5251 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 08:04:12.114 7085 7085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 08:04:12.426 7085 7085 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 08:33:17.716 9288 9288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 08:33:18.286 9288 9288 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 09:04:22.597 11164 11164 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 09:04:22.892 11164 11164 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 10:04:12.060 14322 14322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 10:04:12.536 14322 14322 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 11:09:16.372 17778 17778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 11:09:16.888 17778 17778 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 12:04:29.516 25363 25363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 12:04:30.730 25363 25363 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 13:04:12.548 32417 32417 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 13:04:14.900 32417 32417 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 14:04:24.044 12600 12600 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 14:04:25.094 12600 12600 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 15:04:13.178 24256 24256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 15:04:15.247 24256 24256 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-22 15:04:17.899 24256 24358 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-22 15:04:17.899 24256 24358 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-22 15:04:17.899 24256 24358 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-22 15:09:28.747 26466 26466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 15:09:29.946 26466 26466 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-22 15:09:32.159 26466 26641 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-22 15:09:32.159 26466 26641 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-22 15:09:32.159 26466 26641 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-22 16:10:28.993 1358 1358 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 16:10:29.649 1358 1358 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 17:04:30.500 10634 10634 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 17:04:31.654 10634 10634 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 17:34:30.777 25472 25472 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 17:34:31.441 25472 25472 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-22 17:34:32.680 25472 25541 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-22 17:34:32.680 25472 25541 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-22 18:04:30.044 1376 1376 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 18:04:31.167 1376 1376 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 19:01:52.276 22504 22504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 19:01:53.101 22504 22504 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-22 19:01:54.567 22504 22592 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-22 19:01:54.567 22504 22592 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-22 19:01:54.567 22504 22592 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-22 19:29:45.089 27779 27779 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 19:29:45.848 27779 27779 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-22 19:29:47.342 27779 27842 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-22 19:29:47.344 27779 27842 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-22 20:44:34.693 20137 20137 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 20:44:39.485 20137 20137 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-22 20:44:46.613 20137 20481 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-22 20:44:46.613 20137 20481 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-23 07:34:48.649 7069 7069 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:34:52.617 7069 7069 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-23 07:36:04.269 11527 11527 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:36:05.630 11527 11527 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-23 07:36:38.209 12918 12918 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:36:38.430 12918 12918 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-23 07:37:42.868 15527 15527 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:37:44.364 15527 15527 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-23 07:39:58.602 19284 19284 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:39:59.182 19284 19284 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-23 07:41:52.493 20229 20229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:41:52.749 20229 20229 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-23 07:44:32.490 20691 20691 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 07:44:32.701 20691 20691 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-23 08:07:10.393 22860 22860 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 08:07:11.746 22860 22860 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-23 18:19:51.955 16421 16421 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 18:19:53.959 16421 16421 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-23 19:58:08.782 6388 6388 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 19:58:09.452 6388 6388 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-23 21:00:30.404 18832 18832 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 21:00:30.947 18832 18832 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-23 21:00:32.284 18832 18989 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-23 21:00:32.284 18832 18989 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-23 21:00:32.284 18832 18989 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-23 21:14:36.456 19613 19613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 21:14:36.863 19613 19613 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-23 21:32:29.982 19786 19786 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 21:32:30.222 19786 19786 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-23 21:59:33.247 20932 20932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 21:59:33.777 20932 20932 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-23 22:01:34.064 21256 21256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 22:01:34.269 21256 21256 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-23 22:05:38.067 21528 21528 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 22:05:38.344 21528 21528 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-23 23:01:51.488 24583 24583 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-23 23:01:52.036 24583 24583 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-23 23:01:52.850 24583 24631 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-23 23:01:52.850 24583 24631 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-23 23:01:52.850 24583 24631 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-24 01:00:26.509 27169 27169 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 01:00:27.127 27169 27169 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-24 03:04:29.812 28613 28613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 03:04:30.754 28613 28613 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-24 05:00:04.693 8840 8840 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 05:00:06.871 8840 8840 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-24 05:06:51.236 9202 9202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 05:06:52.268 9202 9202 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-24 05:18:33.648 10940 10940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 05:18:34.798 10940 10940 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-24 05:34:11.908 11864 11864 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 05:34:12.737 11864 11864 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-24 06:08:06.340 14166 14166 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 06:08:07.407 14166 14166 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-24 06:36:28.527 17641 17641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 06:36:29.611 17641 17641 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-24 07:07:19.940 21289 21289 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 07:07:20.914 21289 21289 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-24 07:41:47.386 31515 31515 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 07:41:48.085 31515 31515 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-24 08:05:12.278 32255 32255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 08:05:12.484 32255 32255 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-24 08:22:59.249 32741 32741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 08:22:59.561 32741 32741 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-24 08:40:30.525 1371 1371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 08:40:30.797 1371 1371 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-24 09:49:49.193 4148 4148 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 09:49:49.586 4148 4148 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-24 13:52:02.005 6035 6035 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 13:52:07.130 6035 6035 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-24 13:52:07.131 6035 6035 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-24 13:52:07.131 6035 6035 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-24 13:52:07.131 6035 6035 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-24 13:52:07.131 6035 6035 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-24 13:52:07.131 6035 6035 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-24 13:52:07.131 6035 6035 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-24 13:52:07.131 6035 6035 W System.err: at
java.lang.Class.newInstance(Native Method)
05-24 13:52:07.131 6035 6035 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-24 13:52:07.131 6035 6035 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-24 13:52:07.131 6035 6035 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-24 13:52:07.131 6035 6035 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-24 13:52:07.131 6035 6035 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-24 13:52:07.131 6035 6035 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-24 13:52:07.131 6035 6035 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-24 13:52:07.132 6035 6035 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-24 13:52:07.132 6035 6035 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-24 13:52:07.132 6035 6035 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-24 13:52:07.132 6035 6035 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-24 13:52:07.132 6035 6035 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-24 13:52:07.132 6035 6035 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-24 13:52:07.132 6035 6035 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-24 13:52:07.352 6035 6035 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-24 13:52:09.857 6035 6035 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-24 13:52:09.860 6035 6035 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-24 13:52:11.865 6035 6035 W com.mbwhatsapp: type=1400 audit(0.0:1601): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-24 13:52:11.982 6035 6035 W com.mbwhatsapp: type=1400 audit(0.0:1602): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-24 13:52:11.982 6035 6035 W com.mbwhatsapp: type=1400 audit(0.0:1603): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-24 13:52:11.982 6035 6035 W com.mbwhatsapp: type=1400 audit(0.0:1604): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-24 13:52:11.982 6035 6035 W com.mbwhatsapp: type=1400 audit(0.0:1605): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
05-24 13:52:12.519 6035 6301 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-24 13:52:12.519 6035 6301 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-24 13:52:12.519 6035 6301 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-24 13:52:12.537 6035 6046 W com.mbwhatsapp: Suspending all threads took:
7.271ms
05-24 13:57:59.551 15304 15304 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 13:58:00.621 15304 15304 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-24 14:46:03.954 22990 22990 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 14:46:04.434 22990 22990 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-24 19:34:15.515 18312 18312 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 19:34:15.962 18312 18312 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-24 19:34:16.538 18312 18312 W com.mbwhatsapp: type=1400 audit(0.0:12869): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-24 19:34:16.674 18312 18444 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-24 19:34:16.674 18312 18444 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-24 19:34:16.674 18312 18444 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-24 19:34:16.558 18312 18312 W com.mbwhatsapp: type=1400 audit(0.0:12870): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-24 19:35:39.647 21183 21183 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 19:35:40.346 21183 21183 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-24 20:52:06.157 2948 2948 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 20:52:06.817 2948 2948 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-24 21:45:52.588 16944 16944 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 21:45:53.289 16944 16944 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-24 21:45:54.288 16944 17001 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-24 21:45:54.288 16944 17001 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-24 21:45:54.288 16944 17001 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-24 22:15:41.609 24046 24046 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-24 22:15:42.150 24046 24046 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-24 22:15:43.320 24046 24095 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-24 22:15:43.320 24046 24095 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-24 22:15:43.320 24046 24095 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-25 05:52:09.284 13543 13543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 05:52:10.214 13543 13543 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-25 07:46:39.082 32448 32448 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 07:46:39.996 32448 32448 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-25 09:02:43.963 8870 8870 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 09:02:44.302 8870 8870 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-25 09:02:45.380 8870 8943 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-25 09:02:45.380 8870 8943 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-25 09:02:45.380 8870 8943 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-25 11:48:07.378 13677 13677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 11:48:08.076 13677 13677 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-25 13:44:06.692 16632 16632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 13:44:09.354 16632 16632 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-25 14:05:11.859 20079 20079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 14:05:13.102 20079 20079 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-25 14:05:15.844 20079 20278 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-25 14:05:15.844 20079 20278 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-25 14:05:15.844 20079 20278 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-25 14:45:32.755 27340 27340 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 14:45:33.567 27340 27340 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-25 19:06:43.180 8753 8753 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 19:06:44.480 8753 8753 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-25 19:06:45.991 8753 8753 W com.mbwhatsapp: type=1400 audit(0.0:45121): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-25 20:24:33.468 13153 13153 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 20:24:34.102 13153 13153 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-25 20:45:34.320 21105 21105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 20:45:35.176 21105 21105 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-25 20:45:36.693 21105 21198 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-25 20:45:36.693 21105 21198 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-25 20:45:36.693 21105 21198 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-25 22:52:07.459 26765 26765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-25 22:52:08.300 26765 26765 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-26 00:08:52.461 4312 4312 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 00:08:53.673 4312 4312 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-26 00:08:53.675 4312 4312 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.Class.newInstance(Native Method)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-26 00:08:53.675 4312 4312 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-26 00:08:53.675 4312 4312 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-26 00:08:53.675 4312 4312 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-26 00:08:53.675 4312 4312 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-26 00:08:53.675 4312 4312 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-26 00:08:53.675 4312 4312 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-26 00:08:53.675 4312 4312 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-26 00:08:53.675 4312 4312 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-26 00:08:53.918 4312 4312 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-26 00:08:55.730 4312 4312 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-26 00:08:55.731 4312 4312 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-26 00:08:55.912 4312 4312 W com.mbwhatsapp: type=1400 audit(0.0:1625): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-26 00:08:55.948 4312 4312 W com.mbwhatsapp: type=1400 audit(0.0:1626): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-26 00:08:56.002 4312 4312 W com.mbwhatsapp: type=1400 audit(0.0:1627): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-26 00:08:56.402 4312 4312 W com.mbwhatsapp: type=1400 audit(0.0:1628): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-26 00:08:56.438 4312 4312 W com.mbwhatsapp: type=1400 audit(0.0:1629): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-26 00:08:57.430 4312 4817 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-26 00:08:57.430 4312 4817 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-26 00:08:57.430 4312 4817 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-26 00:11:14.804 10019 10019 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 00:11:18.818 10019 10019 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-26 07:03:26.699 10920 10920 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 07:03:27.089 10920 10920 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-26 07:03:27.959 10920 10920 W com.mbwhatsapp: type=1400 audit(0.0:9450): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-26 07:03:28.134 10920 11030 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-26 07:03:28.134 10920 11030 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-26 07:03:28.134 10920 11030 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-26 07:03:27.986 10920 10920 W com.mbwhatsapp: type=1400 audit(0.0:9451): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-26 09:23:18.465 17752 17752 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 09:23:18.892 17752 17752 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-26 15:37:06.817 9327 9327 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 15:37:07.385 9327 9327 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-26 15:37:08.396 9327 9375 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-26 15:37:08.396 9327 9375 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-26 15:37:08.396 9327 9375 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-26 17:37:25.437 32109 32109 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 17:37:26.328 32109 32109 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-26 17:46:42.649 3644 3644 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 17:46:43.538 3644 3644 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-26 23:41:24.138 24041 24041 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 23:41:24.836 24041 24041 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-27 05:47:48.426 2279 2279 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 05:47:49.352 2279 2279 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-27 10:59:36.961 7300 7300 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 10:59:38.776 7300 7300 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-27 10:59:38.782 7300 7300 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-27 10:59:38.785 7300 7300 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-27 10:59:38.786 7300 7300 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-27 10:59:38.786 7300 7300 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-27 10:59:38.786 7300 7300 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-27 10:59:38.786 7300 7300 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-27 10:59:38.786 7300 7300 W System.err: at
java.lang.Class.newInstance(Native Method)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-27 10:59:38.786 7300 7300 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-27 10:59:38.786 7300 7300 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-27 10:59:38.786 7300 7300 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-27 10:59:38.786 7300 7300 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-27 10:59:38.786 7300 7300 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-27 10:59:38.786 7300 7300 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-27 10:59:38.786 7300 7300 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-27 10:59:38.786 7300 7300 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-27 10:59:39.163 7300 7300 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-27 10:59:41.808 7300 7300 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-27 10:59:41.809 7300 7300 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-27 10:59:43.302 7300 7509 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-27 10:59:43.302 7300 7509 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-27 10:59:43.302 7300 7509 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-27 11:02:53.545 13403 13403 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 11:02:55.020 13403 13403 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-27 11:28:02.204 21243 21243 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 11:28:02.690 21243 21243 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-27 11:52:31.392 23902 23902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 11:52:32.018 23902 23902 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-27 12:52:41.789 29607 29607 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 12:52:42.468 29607 29607 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-27 13:52:31.364 6937 6937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 13:52:31.920 6937 6937 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-27 14:52:39.018 16346 16346 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 14:52:39.914 16346 16346 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-27 19:33:24.510 1102 1102 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-27 19:33:25.071 1102 1102 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-28 00:31:19.083 1422 1422 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 00:31:22.487 1422 1422 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-28 03:22:46.436 24962 24962 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 03:22:46.806 24962 24962 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-28 07:00:16.868 24962 25405 W ConnectivityManager.CallbackHandler: callback not
found for CALLBACK_CAP_CHANGED message
05-28 07:00:16.973 24962 25405 W ConnectivityManager.CallbackHandler: callback not
found for CALLBACK_CAP_CHANGED message
05-28 15:06:03.061 9902 9902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 15:06:04.108 9902 9902 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-28 15:06:05.350 9902 9902 W com.mbwhatsapp: type=1400 audit(0.0:34713): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-28 16:52:48.463 23723 23723 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 16:52:49.133 23723 23723 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-28 16:52:50.367 23723 23807 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-28 16:52:50.367 23723 23807 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-28 16:52:50.367 23723 23807 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-28 17:53:12.121 11902 11902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 17:53:12.911 11902 11902 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-28 18:06:50.439 16476 16476 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 18:06:51.035 16476 16476 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-28 18:57:23.437 29707 29707 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 18:57:23.986 29707 29707 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-28 18:57:24.882 29707 29766 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-28 18:57:24.882 29707 29766 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-28 18:57:24.882 29707 29766 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-28 21:09:11.556 23379 23379 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 21:09:13.058 23379 23379 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-28 21:09:14.833 23379 23431 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-28 21:09:14.833 23379 23431 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-28 21:09:14.833 23379 23431 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-28 21:11:54.716 25340 25340 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 21:11:56.569 25340 25340 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-28 23:09:11.602 21865 21865 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 23:09:14.098 21865 21865 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-29 01:52:38.605 31188 31188 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 01:52:40.117 31188 31188 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-29 02:53:09.717 364 364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 02:53:10.737 364 364 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-29 09:13:47.065 24637 24637 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 09:13:47.621 24637 24637 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-29 16:56:49.771 24212 24212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 16:56:50.528 24212 24212 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-29 16:56:51.439 24212 24321 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-29 16:56:51.439 24212 24321 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-29 16:56:51.439 24212 24321 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-29 18:05:13.920 6234 6234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 18:05:14.760 6234 6234 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-29 18:53:05.037 16301 16301 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 18:53:05.912 16301 16301 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-29 19:53:13.756 3235 3235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 19:53:14.575 3235 3235 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-29 20:53:04.063 19482 19482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 20:53:05.160 19482 19482 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-29 21:11:12.381 28168 28168 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 21:11:13.041 28168 28168 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-29 21:52:54.876 6145 6145 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 21:52:55.800 6145 6145 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-29 22:58:53.979 19095 19095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 22:58:54.557 19095 19095 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-29 23:52:31.366 27406 27406 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-29 23:52:31.937 27406 27406 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-30 00:52:47.173 2578 2578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 00:52:47.719 2578 2578 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-30 01:23:02.360 6357 6357 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 01:23:02.947 6357 6357 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-30 03:52:34.605 12867 12867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 03:52:35.008 12867 12867 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-30 05:52:31.310 18652 18652 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 05:52:31.853 18652 18652 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-30 06:55:54.181 29034 29034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 06:55:54.816 29034 29034 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-30 08:13:01.009 3125 3125 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 08:13:02.798 3125 3125 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-30 09:53:01.226 10940 10940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 09:53:02.199 10940 10940 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-30 11:18:25.481 15620 15620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 11:18:26.473 15620 15620 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-30 12:54:53.659 24938 24938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 12:54:54.537 24938 24938 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-30 15:54:55.237 11797 11797 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 15:54:55.901 11797 11797 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-30 18:01:55.616 24082 24082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 18:01:56.360 24082 24082 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-30 18:53:11.262 4336 4336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 18:53:12.312 4336 4336 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-30 18:53:14.047 4336 4508 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-30 18:53:14.047 4336 4508 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-30 18:53:14.047 4336 4508 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-30 19:11:43.404 12689 12689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 19:11:44.622 12689 12689 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-30 19:52:31.307 32532 32532 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 19:52:31.923 32532 32532 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-30 19:52:33.633 32532 32600 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-30 19:52:33.633 32532 32600 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-30 19:52:33.633 32532 32600 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-30 20:58:53.791 20810 20810 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 20:58:54.340 20810 20810 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-30 21:28:52.604 30849 30849 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 21:28:53.386 30849 30849 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-30 22:53:15.225 14118 14118 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 22:53:15.778 14118 14118 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-30 23:19:38.998 16599 16599 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 23:19:39.616 16599 16599 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
05-30 23:19:39.617 16599 16599 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
05-30 23:19:39.617 16599 16599 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
05-30 23:19:39.617 16599 16599 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
05-30 23:19:39.617 16599 16599 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
05-30 23:19:39.617 16599 16599 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
05-30 23:19:39.617 16599 16599 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
05-30 23:19:39.617 16599 16599 W System.err: at
java.lang.Class.newInstance(Native Method)
05-30 23:19:39.617 16599 16599 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
05-30 23:19:39.617 16599 16599 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
05-30 23:19:39.617 16599 16599 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
05-30 23:19:39.617 16599 16599 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
05-30 23:19:39.617 16599 16599 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
05-30 23:19:39.617 16599 16599 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
05-30 23:19:39.617 16599 16599 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
05-30 23:19:39.617 16599 16599 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
05-30 23:19:39.617 16599 16599 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
05-30 23:19:39.618 16599 16599 W System.err: at
android.os.Looper.loop(Looper.java:334)
05-30 23:19:39.618 16599 16599 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
05-30 23:19:39.618 16599 16599 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
05-30 23:19:39.618 16599 16599 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
05-30 23:19:39.618 16599 16599 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
05-30 23:19:39.667 16599 16599 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-30 23:19:40.436 16599 16599 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-30 23:19:40.436 16599 16599 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
05-30 23:19:40.483 16599 16599 W com.mbwhatsapp: type=1400 audit(0.0:264256): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-30 23:19:40.493 16599 16599 W com.mbwhatsapp: type=1400 audit(0.0:264257): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-30 23:19:40.770 16599 16667 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-30 23:19:40.770 16599 16667 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-30 23:19:40.770 16599 16667 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-30 23:19:41.142 16599 16682 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-30 23:19:41.143 16599 16682 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-30 23:46:52.604 21359 21359 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-30 23:46:53.141 21359 21359 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-31 00:52:54.395 31314 31314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 00:52:56.610 31314 31314 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-31 01:09:00.843 6489 6489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 01:09:01.713 6489 6489 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-31 01:38:53.619 9402 9402 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 01:38:54.210 9402 9402 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-31 01:38:55.513 9402 9532 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
05-31 01:38:55.514 9402 9532 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
05-31 03:30:04.810 11066 11066 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 03:30:05.526 11066 11066 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-31 06:18:09.174 6482 6482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 06:18:09.599 6482 6482 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-31 06:18:10.241 6482 6482 W com.mbwhatsapp: type=1400 audit(0.0:1728): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
05-31 06:18:10.258 6482 6482 W com.mbwhatsapp: type=1400 audit(0.0:1729): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-31 06:19:19.955 9572 9572 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 06:19:20.449 9572 9572 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-31 07:05:02.972 21052 21052 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 07:05:03.404 21052 21052 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-31 07:05:04.199 21052 21052 W com.mbwhatsapp: type=1400 audit(0.0:4754): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-31 07:17:04.941 22031 22031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 07:22:10.514 22149 22149 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 07:22:10.761 22149 22149 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-31 07:34:47.869 22342 22342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 07:34:48.058 22342 22342 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-31 07:51:32.150 23180 23180 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 07:51:32.494 23180 23180 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-31 08:08:57.594 24171 24171 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 08:08:57.792 24171 24171 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-31 09:19:32.370 25291 25291 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 09:19:32.708 25291 25291 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-31 09:19:33.358 25291 25461 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-31 09:19:33.358 25291 25461 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-31 09:19:33.358 25291 25461 W com.mbwhatsapp: and incorrect proguard
optimizations.
05-31 11:10:45.506 27143 27143 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 11:10:45.998 27143 27143 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-31 11:15:54.961 29874 29874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 11:15:55.570 29874 29874 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-31 11:23:31.090 30167 30167 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 11:23:31.296 30167 30167 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-31 13:04:59.485 11789 11789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 13:05:00.316 11789 11789 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-31 13:05:01.400 11789 11916 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-31 13:05:01.400 11789 11916 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-31 13:05:01.400 11789 11916 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-31 14:04:41.268 19926 19926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 14:04:41.838 19926 19926 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-31 14:22:43.761 22536 22536 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 14:22:44.344 22536 22536 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-31 15:05:03.727 27443 27443 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 15:05:04.370 27443 27443 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-31 15:09:23.056 29015 29015 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 15:09:23.683 29015 29015 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-31 15:30:46.579 6679 6679 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 15:30:47.461 6679 6679 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-31 16:04:42.969 10779 10779 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 16:04:43.672 10779 10779 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-31 16:04:44.775 10779 10826 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-31 16:04:44.775 10779 10826 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-31 16:04:44.775 10779 10826 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-31 17:05:01.667 16019 16019 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 17:05:02.394 16019 16019 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-31 17:05:03.466 16019 16110 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-31 17:05:03.466 16019 16110 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-31 17:05:03.466 16019 16110 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-31 18:13:33.785 27717 27717 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 18:13:35.111 27717 27717 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-31 18:13:36.202 27717 27806 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
05-31 18:13:36.202 27717 27806 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-31 18:13:36.202 27717 27806 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-31 20:06:42.642 11932 11932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 20:06:43.360 11932 11932 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-31 21:08:08.834 26378 26378 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 21:08:09.419 26378 26378 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-31 22:04:43.579 11285 11285 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 22:04:44.359 11285 11285 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-31 23:04:41.272 29348 29348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 23:04:41.919 29348 29348 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
06-01 00:20:06.682 12108 12108 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 00:20:07.293 12108 12108 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
06-01 00:43:18.368 8625 8625 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 00:43:19.159 8625 8625 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
06-01 00:44:13.752 10707 10707 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 00:44:14.556 10707 10707 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
06-01 04:28:55.011 30350 30350 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 04:28:55.948 30350 30350 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
06-01 15:05:07.066 28273 28273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 15:05:07.641 28273 28273 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.
06-01 15:05:08.615 28273 28323 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-01 15:05:08.615 28273 28323 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-01 15:05:08.615 28273 28323 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-01 16:04:59.401 11724 11724 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 16:05:00.231 11724 11724 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
06-01 16:27:05.790 13573 13573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 16:27:06.523 13573 13573 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
06-01 16:32:56.029 14726 14726 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 16:32:56.865 14726 14726 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.
06-01 16:32:59.360 14726 14772 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-01 16:32:59.360 14726 14772 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-01 16:32:59.360 14726 14772 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-01 16:45:29.603 16160 16160 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 16:45:30.972 16160 16160 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
06-01 18:33:43.626 3244 3244 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 18:33:44.440 3244 3244 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
06-01 20:09:33.855 23212 23212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 20:09:36.102 23212 23212 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
06-01 20:10:37.245 26249 26249 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 20:10:38.460 26249 26249 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
06-01 20:17:50.820 30944 30944 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 20:17:53.007 30944 30944 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
06-01 21:01:51.916 4613 4613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 21:01:52.592 4613 4613 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.
06-01 21:01:53.549 4613 4671 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-01 21:01:53.549 4613 4671 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-01 21:01:53.549 4613 4671 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-01 21:51:11.207 13854 13854 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 21:51:11.717 13854 13854 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
06-01 23:07:28.134 25189 25189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-01 23:07:28.508 25189 25189 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
06-02 06:01:48.960 6090 6090 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 06:01:49.742 6090 6090 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.
06-02 06:01:51.298 6090 6136 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-02 06:01:51.298 6090 6136 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-02 06:01:51.298 6090 6136 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-02 07:57:00.459 19384 19384 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 07:57:01.233 19384 19384 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
06-02 08:08:18.044 21932 21932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 08:08:18.532 21932 21932 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
06-02 16:44:51.606 9637 9637 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 16:44:52.446 9637 9637 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.
06-02 16:44:53.529 9637 9696 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-02 16:44:53.529 9637 9696 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-02 16:44:53.529 9637 9696 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-02 17:27:51.956 9637 9646 W com.mbwhatsapp: Reducing the number of considered
missed Gc histogram windows from 160 to 100
06-02 17:40:25.684 19114 19114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 17:40:26.435 19114 19114 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.
06-02 17:40:27.535 19114 19294 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-02 17:40:27.535 19114 19294 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-02 17:40:27.535 19114 19294 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-02 18:46:58.902 25254 25254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 18:46:59.362 25254 25254 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
06-02 21:48:14.134 13153 13153 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 21:48:14.716 13153 13153 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
06-02 22:48:37.910 27160 27160 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-02 22:48:38.487 27160 27160 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
06-03 02:00:12.204 5008 5008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 02:00:13.771 5008 5008 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.
06-03 02:00:15.715 5008 5061 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-03 02:00:15.715 5008 5061 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-03 02:00:15.715 5008 5061 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-03 06:02:28.554 13497 13497 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 06:02:29.101 13497 13497 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
06-03 08:02:09.759 21340 21340 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 08:02:10.292 21340 21340 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
06-03 08:24:32.115 26445 26445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 08:24:32.663 26445 26445 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
06-03 08:52:18.943 29798 29798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 08:52:21.908 29798 29798 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
06-03 17:15:44.613 11380 11380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 17:15:45.564 11380 11380 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
06-03 17:17:16.874 12483 12483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 17:17:18.139 12483 12483 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
06-03 18:01:53.026 27588 27588 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 18:01:54.143 27588 27588 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
06-03 18:31:39.875 4894 4894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 18:31:40.644 4894 4894 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
06-03 18:55:30.465 14730 14730 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 18:55:31.617 14730 14730 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.
06-03 18:55:33.938 14730 15023 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-03 18:55:33.938 14730 15023 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-03 18:55:33.938 14730 15023 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-03 19:01:46.727 18139 18139 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 19:01:48.339 18139 18139 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
06-03 21:15:45.551 5578 5578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 21:15:46.235 5578 5578 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.
06-03 21:15:47.584 5578 5625 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-03 21:15:47.584 5578 5625 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-03 21:15:47.584 5578 5625 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-03 22:15:45.584 15944 15944 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 22:15:46.678 15944 15944 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.
06-03 22:15:48.333 15944 16079 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-03 22:15:48.333 15944 16079 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-03 22:15:48.333 15944 16079 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-03 22:26:01.486 19816 19816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 22:26:02.428 19816 19816 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
06-03 23:11:47.729 1692 1692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-03 23:11:48.341 1692 1692 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
06-04 07:16:02.975 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.976 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.977 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.978 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 07:16:02.979 1692 1702 W System : A resource failed to call close.
06-04 08:15:44.977 19999 19999 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 08:15:45.731 19999 19999 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
06-04 09:01:13.976 31192 31192 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 09:01:14.698 31192 31192 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
06-04 18:47:28.553 31369 31369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 18:47:29.509 31369 31369 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
06-04 19:47:28.484 4836 4836 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 19:47:29.447 4836 4836 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
06-04 20:47:45.633 17144 17144 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 20:47:46.250 17144 17144 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.
06-04 20:47:47.557 17144 17208 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-04 20:47:47.557 17144 17208 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-04 20:47:47.557 17144 17208 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-04 21:47:45.610 23566 23566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 21:47:46.462 23566 23566 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.
06-04 21:47:47.680 23566 23611 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-04 21:47:47.680 23566 23611 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-04 21:47:47.680 23566 23611 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-04 22:02:13.782 28660 28660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 22:02:14.821 28660 28660 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
06-04 22:17:31.513 630 630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 22:17:32.536 630 630 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
06-04 22:47:45.553 7254 7254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 22:47:46.316 7254 7254 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.
06-04 22:47:47.719 7254 7301 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-04 22:47:47.719 7254 7301 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-04 22:47:47.719 7254 7301 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-04 22:49:23.310 7561 7561 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 22:49:23.688 7561 7561 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
06-04 23:14:43.738 10941 10941 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 23:14:44.403 10941 10941 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
06-04 23:49:43.345 13887 13887 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 23:49:44.127 13887 13887 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
06-04 23:55:49.250 16181 16181 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-04 23:55:53.067 16181 16181 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
06-05 04:14:13.602 936 936 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 04:14:14.765 936 936 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
06-05 05:03:40.288 8795 8795 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 05:03:40.987 8795 8795 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
06-05 07:11:51.491 24624 24624 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 07:11:52.630 24624 24624 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
06-05 07:54:36.416 30248 30248 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 07:54:36.864 30248 30248 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
06-05 09:45:45.968 13005 13005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 09:45:46.708 13005 13005 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
06-05 16:56:48.582 24479 24479 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 16:56:49.997 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.
06-05 16:56:51.910 24479 24533 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-05 16:56:51.910 24479 24533 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-05 16:56:51.910 24479 24533 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-05 17:39:45.569 2428 2428 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 17:39:46.703 2428 2428 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.
06-05 17:39:49.282 2428 2534 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-05 17:39:49.282 2428 2534 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-05 17:39:49.282 2428 2534 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-05 18:39:45.593 17855 17855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 18:39:46.529 17855 17855 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
06-05 18:47:30.558 21163 21163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 18:47:31.391 21163 21163 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
06-05 18:51:44.355 22739 22739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 18:51:45.050 22739 22739 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
06-05 19:02:26.733 26718 26718 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 19:02:27.438 26718 26718 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
06-05 19:40:07.399 3229 3229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 19:40:08.116 3229 3229 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.
06-05 19:40:09.570 3229 3275 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-05 19:40:09.570 3229 3275 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-05 19:40:09.570 3229 3275 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-05 19:43:45.669 6202 6202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 19:43:46.379 6202 6202 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
06-05 20:40:22.239 12017 12017 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 20:40:22.877 12017 12017 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
06-05 22:55:44.945 31282 31282 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 22:55:45.925 31282 31282 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
06-05 22:57:23.848 31968 31968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-05 22:57:25.004 31968 31968 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
06-06 08:11:00.622 31037 31037 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 08:11:01.324 31037 31037 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
06-06 11:59:44.388 5147 5147 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 11:59:45.078 5147 5147 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
06-06 15:03:44.435 7412 7412 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 15:03:44.853 7412 7412 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
06-06 17:01:48.133 22009 22009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 17:01:48.921 22009 22009 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.
06-06 17:01:50.348 22009 22094 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-06 17:01:50.348 22009 22094 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-06 17:01:50.348 22009 22094 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-06 18:07:02.248 28303 28303 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 18:07:03.103 28303 28303 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.
06-06 18:07:05.514 28303 28443 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-06 18:07:05.514 28303 28443 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-06 18:07:05.514 28303 28443 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-06 18:13:46.760 28838 28838 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 18:13:47.831 28838 28838 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
06-06 19:06:29.067 1640 1640 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 19:06:29.813 1640 1640 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
06-06 20:58:12.355 7636 7636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 20:58:15.817 7636 7636 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.
06-06 20:58:17.506 7636 7636 W com.mbwhatsapp: type=1400 audit(0.0:2310): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-06 20:58:17.533 7636 7636 W com.mbwhatsapp: type=1400 audit(0.0:2311): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-06 20:59:54.685 10578 10578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 20:59:55.695 10578 10578 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
06-06 22:02:06.221 16682 16682 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 22:02:07.699 16682 16682 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
06-06 22:18:21.013 17556 17556 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 22:18:21.394 17556 17556 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
06-06 22:21:29.510 18355 18355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 22:21:29.762 18355 18355 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
06-06 22:30:54.482 18586 18586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 22:30:54.800 18586 18586 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
06-06 22:45:36.050 19180 19180 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 22:45:36.392 19180 19180 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
06-06 23:01:22.086 20076 20076 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-06 23:01:22.383 20076 20076 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
06-07 03:11:44.927 25884 25884 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 03:11:46.317 25884 25884 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
06-07 07:05:27.542 28203 28203 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 07:05:29.789 28203 28203 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
06-07 07:16:41.921 30711 30711 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 07:23:44.680 30841 30841 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 07:23:45.158 30841 30841 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
06-07 07:31:01.945 31677 31677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 07:31:02.241 31677 31677 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
06-07 07:35:27.497 2095 2095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 07:35:28.453 2095 2095 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
06-07 09:01:53.578 17259 17259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 09:01:54.408 17259 17259 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.
06-07 09:01:56.020 17259 17325 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-07 09:01:56.020 17259 17325 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-07 09:01:56.020 17259 17325 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-07 10:01:57.015 21640 21640 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 10:01:57.801 21640 21640 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.
06-07 10:01:59.300 21640 21640 W com.mbwhatsapp: type=1400 audit(0.0:14484): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-07 10:04:47.789 21879 21879 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 10:04:48.088 21879 21879 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
06-07 11:01:49.102 24477 24477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 11:01:49.824 24477 24477 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
06-07 11:03:29.184 24630 24630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 11:03:29.560 24630 24630 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
06-07 12:11:43.523 27692 27692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 12:11:44.164 27692 27692 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
06-07 12:35:02.342 28938 28938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 12:35:03.628 28938 28938 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
06-07 13:01:49.352 32303 32303 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 13:01:49.981 32303 32303 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
06-07 13:30:59.587 3665 3665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 13:31:00.021 3665 3665 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
06-07 14:02:59.900 5917 5917 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 14:03:00.393 5917 5917 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
06-07 15:05:11.845 13004 13004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 15:05:12.678 13004 13004 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
06-07 15:16:46.486 14319 14319 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 15:16:47.216 14319 14319 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
06-07 16:56:33.291 17888 17888 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 16:56:34.398 17888 17888 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
06-07 18:07:44.786 10395 10395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 18:07:45.988 10395 10395 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
06-07 18:27:44.750 11358 11358 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 18:27:45.241 11358 11358 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
06-07 19:30:36.884 12244 12244 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 19:30:37.119 12244 12244 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
06-07 20:16:52.998 13502 13502 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 20:16:53.641 13502 13502 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
06-07 21:02:39.283 19208 19208 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 21:02:40.433 19208 19208 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.
06-07 21:02:43.527 19208 19208 W com.mbwhatsapp: type=1400 audit(0.0:32694): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-07 22:47:44.770 21100 21100 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 22:47:45.296 21100 21100 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
06-07 22:55:40.979 21859 21859 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-07 22:55:41.344 21859 21859 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
06-08 00:02:27.455 12949 12949 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 00:02:28.228 12949 12949 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
06-08 00:04:48.101 13714 13714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 00:04:49.079 13714 13714 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
06-08 00:08:32.667 15025 15025 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 00:08:33.114 15025 15025 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
06-08 01:59:43.516 29342 29342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 01:59:44.345 29342 29342 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
06-08 03:10:43.015 1107 1107 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 03:10:50.017 1107 1107 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.
06-08 03:10:52.354 1107 1107 W com.mbwhatsapp: type=1400 audit(0.0:51293): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-08 05:15:45.623 5351 5351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 05:15:46.980 5351 5351 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
06-08 09:13:48.986 9662 9662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 09:13:51.497 9662 9662 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
06-08 11:01:46.003 29410 29410 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 11:01:46.636 29410 29410 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
06-08 12:06:39.961 11339 11339 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:06:41.151 11339 11339 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.
06-08 12:06:42.662 11339 11400 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-08 12:06:42.662 11339 11400 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-08 12:06:42.662 11339 11400 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-08 12:12:54.127 12789 12789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:12:55.050 12789 12789 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
06-08 12:16:11.000 13758 13758 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:16:11.758 13758 13758 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
06-08 12:21:41.257 14761 14761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:21:42.581 14761 14761 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
06-08 12:27:46.260 17094 17094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:27:47.324 17094 17094 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
06-08 12:47:09.741 21251 21251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:50:46.586 23927 23927 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 12:50:47.429 23927 23927 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
06-08 13:01:01.620 27392 27392 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 13:01:02.345 27392 27392 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
06-08 13:03:10.534 27828 27828 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 13:03:11.777 27828 27828 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
06-08 13:06:10.719 28304 28304 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 13:06:11.093 28304 28304 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
06-08 14:42:20.612 11354 11354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 14:42:21.282 11354 11354 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.
06-08 14:42:22.258 11354 11408 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-08 14:42:22.258 11354 11408 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-08 14:42:22.258 11354 11408 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-08 14:47:43.573 14256 14256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 14:47:45.089 14256 14256 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
06-08 14:54:44.045 15479 15479 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 14:54:44.957 15479 15479 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
06-08 17:05:05.206 19008 19008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 17:05:06.664 19008 19008 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
06-08 17:15:16.018 21377 21377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-08 17:15:16.838 21377 21377 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
06-09 02:47:55.195 28142 28142 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 02:47:55.959 28142 28142 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.
06-09 02:47:57.300 28142 28189 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-09 02:47:57.300 28142 28189 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-09 02:47:57.300 28142 28189 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-09 03:47:56.003 4018 4018 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 03:47:56.797 4018 4018 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.
06-09 03:47:57.882 4018 4123 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-09 03:47:57.882 4018 4123 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-09 03:47:57.882 4018 4123 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-09 04:47:55.148 8009 8009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 04:47:55.842 8009 8009 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
06-09 05:48:06.548 10960 10960 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 05:48:06.867 10960 10960 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
06-09 06:02:38.668 14968 14968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 06:02:39.293 14968 14968 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
06-09 06:47:55.202 17228 17228 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 06:47:55.520 17228 17228 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
06-09 07:47:55.194 21834 21834 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 07:47:55.711 21834 21834 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
06-09 09:48:46.434 30111 30111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 09:48:47.017 30111 30111 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.
06-09 09:48:47.953 30111 30159 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-09 09:48:47.953 30111 30159 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-09 09:48:47.953 30111 30159 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-09 10:34:49.727 3493 3493 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 10:34:50.578 3493 3493 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
06-09 11:49:04.401 13357 13357 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 11:49:05.065 13357 13357 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.
06-09 11:49:06.098 13357 13357 W com.mbwhatsapp: type=1400 audit(0.0:151256): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-09 12:16:14.035 19948 19948 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 12:16:15.467 19948 19948 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.
06-09 12:16:17.406 19948 19948 W com.mbwhatsapp: type=1400 audit(0.0:154344): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-09 12:16:17.442 19948 19948 W com.mbwhatsapp: type=1400 audit(0.0:154345): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-09 12:47:50.189 26246 26246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 12:47:51.662 26246 26246 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
06-09 12:58:10.197 28302 28302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 12:58:11.736 28302 28302 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
06-09 13:26:41.529 6271 6271 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 13:26:42.956 6271 6271 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.
06-09 13:26:44.731 6271 6372 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-09 13:26:44.731 6271 6372 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-09 13:26:44.731 6271 6372 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-09 13:36:16.279 8609 8609 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 13:36:17.433 8609 8609 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
06-09 14:52:31.075 18784 18784 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 14:52:31.706 18784 18784 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
06-09 17:49:17.230 25138 25138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 17:49:18.316 25138 25138 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
06-09 20:51:59.192 4525 4525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 20:52:00.105 4525 4525 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.
06-09 20:52:01.087 4525 4583 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-09 20:52:01.087 4525 4583 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-09 20:52:01.087 4525 4583 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-09 23:49:21.921 17798 17798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-09 23:49:22.660 17798 17798 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.
06-09 23:49:23.927 17798 17853 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-09 23:49:23.927 17798 17853 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-09 23:49:23.927 17798 17853 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-10 01:27:39.308 2725 2725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 01:27:42.112 2725 2725 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
06-10 03:15:05.346 7257 7257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 03:15:06.701 7257 7257 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
06-10 04:57:17.154 10079 10079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 04:57:18.247 10079 10079 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
06-10 06:49:18.088 16182 16182 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 06:49:18.727 16182 16182 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
06-10 17:23:46.183 9503 9503 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 17:23:48.290 9503 9503 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.
06-10 17:23:53.414 9503 9503 W com.mbwhatsapp: type=1400 audit(0.0:7599): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-10 17:23:53.481 9503 9503 W com.mbwhatsapp: type=1400 audit(0.0:7600): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-10 17:25:21.411 12606 12606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 17:25:23.026 12606 12606 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
06-10 17:57:03.808 19004 19004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 17:57:04.480 19004 19004 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
06-10 18:16:37.463 22841 22841 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 18:16:38.410 22841 22841 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.
06-10 18:16:39.444 22841 22841 W com.mbwhatsapp: type=1400 audit(0.0:10906): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-10 18:39:00.697 26049 26049 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 18:39:01.548 26049 26049 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
06-10 19:24:24.020 7292 7292 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 19:24:24.907 7292 7292 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
06-10 23:25:57.608 9578 9578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-10 23:25:58.264 9578 9578 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.
06-10 23:25:59.397 9578 9635 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-10 23:25:59.397 9578 9635 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-10 23:25:59.397 9578 9635 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-11 17:05:57.668 15334 15334 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-11 17:05:58.397 15334 15334 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.
06-11 17:06:00.153 15334 15446 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-11 17:06:00.153 15334 15446 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-11 17:06:00.153 15334 15446 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-11 17:09:57.203 17215 17215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-11 17:09:58.115 17215 17215 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
06-11 18:05:57.691 29416 29416 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-11 18:05:58.878 29416 29416 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
06-11 19:05:57.813 9648 9648 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-11 19:05:58.620 9648 9648 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
06-11 20:09:06.500 14665 14665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-11 20:09:07.108 14665 14665 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
06-12 00:09:35.659 14938 14938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 00:09:36.519 14938 14938 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.
06-12 00:09:38.342 14938 14989 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-12 00:09:38.342 14938 14989 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-12 00:09:38.342 14938 14989 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-12 04:40:00.721 20415 20415 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 04:40:01.559 20415 20415 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
06-12 05:33:49.073 25464 25464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 05:33:50.584 25464 25464 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
06-12 06:41:28.110 5850 5850 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 06:41:28.753 5850 5850 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.
06-12 06:41:29.887 5850 5934 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-12 06:41:29.887 5850 5934 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-12 06:41:29.887 5850 5934 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-12 16:42:27.764 7846 7846 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 16:42:28.753 7846 7846 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
06-12 16:44:10.362 11867 11867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 16:44:11.000 11867 11867 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
06-12 16:48:53.308 14370 14370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 16:48:54.861 14370 14370 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
06-12 17:23:32.017 19384 19384 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 17:23:32.801 19384 19384 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
06-12 17:44:24.439 19973 19973 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 17:44:24.832 19973 19973 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
06-12 18:22:20.084 32664 32664 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 18:22:21.144 32664 32664 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.
06-12 18:22:22.575 32664 32664 W com.mbwhatsapp: type=1400 audit(0.0:13866): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-12 19:13:42.058 15609 15609 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-12 19:13:42.746 15609 15609 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
06-13 01:40:09.524 5384 5384 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 01:40:12.180 5384 5384 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-13 01:40:12.181 5384 5384 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-13 01:40:12.182 5384 5384 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-13 01:40:12.182 5384 5384 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-13 01:40:12.183 5384 5384 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-13 01:40:12.184 5384 5384 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-13 01:40:12.184 5384 5384 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-13 01:40:12.184 5384 5384 W System.err: at
java.lang.Class.newInstance(Native Method)
06-13 01:40:12.184 5384 5384 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-13 01:40:12.185 5384 5384 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-13 01:40:12.185 5384 5384 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-13 01:40:12.185 5384 5384 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-13 01:40:12.185 5384 5384 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-13 01:40:12.185 5384 5384 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-13 01:40:12.185 5384 5384 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-13 01:40:12.186 5384 5384 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-13 01:40:12.186 5384 5384 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-13 01:40:12.186 5384 5384 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-13 01:40:12.186 5384 5384 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-13 01:40:12.186 5384 5384 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-13 01:40:12.186 5384 5384 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-13 01:40:12.187 5384 5384 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-13 01:40:12.802 5384 5384 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.
06-13 01:40:14.434 5384 5384 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-13 01:40:14.435 5384 5384 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
06-13 01:40:16.026 5384 5645 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-13 01:40:16.026 5384 5645 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-13 01:40:16.026 5384 5645 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-13 01:40:19.707 5384 5392 W com.mbwhatsapp: Suspending all threads took:
7.698ms
06-13 01:40:20.484 5384 5981 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
06-13 01:40:20.485 5384 5981 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
06-13 02:00:00.096 18512 18512 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 02:00:01.000 18512 18512 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.
06-13 02:00:01.970 18512 18512 W com.mbwhatsapp: type=1400 audit(0.0:4363): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-13 02:00:02.136 18512 18512 W com.mbwhatsapp: type=1400 audit(0.0:4364): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-13 02:07:19.169 20522 20522 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 02:07:19.710 20522 20522 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
06-13 04:19:00.520 22712 22712 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 04:19:00.802 22712 22712 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
06-13 11:50:47.245 4807 4807 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 11:50:49.218 4807 4807 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-13 11:50:49.221 4807 4807 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-13 11:50:49.222 4807 4807 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-13 11:50:49.222 4807 4807 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-13 11:50:49.222 4807 4807 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-13 11:50:49.222 4807 4807 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-13 11:50:49.222 4807 4807 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-13 11:50:49.222 4807 4807 W System.err: at
java.lang.Class.newInstance(Native Method)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-13 11:50:49.222 4807 4807 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-13 11:50:49.222 4807 4807 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-13 11:50:49.222 4807 4807 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-13 11:50:49.222 4807 4807 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-13 11:50:49.222 4807 4807 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-13 11:50:49.222 4807 4807 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-13 11:50:49.222 4807 4807 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-13 11:50:49.222 4807 4807 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-13 11:50:49.623 4807 4807 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.
06-13 11:50:51.175 4807 4807 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-13 11:50:51.176 4807 4807 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-13 11:50:51.466 4807 4807 W com.mbwhatsapp: type=1400 audit(0.0:1297): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-13 11:50:51.512 4807 4807 W com.mbwhatsapp: type=1400 audit(0.0:1298): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-13 11:50:52.803 4807 4818 W com.mbwhatsapp: Suspending all threads took:
30.725ms
06-13 11:50:54.415 4807 5219 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-13 11:50:54.415 4807 5219 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-13 11:50:54.415 4807 5219 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-13 11:52:31.501 8536 8536 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 11:52:32.597 8536 8536 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-13 11:52:32.598 8536 8536 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-13 11:52:32.599 8536 8536 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-13 11:52:32.599 8536 8536 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-13 11:52:32.599 8536 8536 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-13 11:52:32.599 8536 8536 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-13 11:52:32.599 8536 8536 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-13 11:52:32.599 8536 8536 W System.err: at
java.lang.Class.newInstance(Native Method)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-13 11:52:32.599 8536 8536 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-13 11:52:32.599 8536 8536 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-13 11:52:32.599 8536 8536 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-13 11:52:32.599 8536 8536 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-13 11:52:32.599 8536 8536 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-13 11:52:32.599 8536 8536 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-13 11:52:32.599 8536 8536 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-13 11:52:32.599 8536 8536 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-13 11:52:32.847 8536 8536 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.
06-13 11:52:33.692 8536 8536 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-13 11:52:33.693 8536 8536 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
06-13 11:52:34.428 8536 8680 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-13 11:52:34.428 8536 8680 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-13 11:52:34.428 8536 8680 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-13 11:53:41.924 11041 11041 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 11:53:42.506 11041 11041 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
06-13 12:17:00.237 23894 23894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 12:17:00.984 23894 23894 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.
06-13 12:17:02.997 23894 23894 W com.mbwhatsapp: type=1400 audit(0.0:5117): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-13 12:18:55.793 25866 25866 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 12:18:57.106 25866 25866 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
06-13 15:55:30.383 13344 13344 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 15:55:31.181 13344 13344 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
06-13 19:39:25.973 12205 12205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 19:39:26.877 12205 12205 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.
06-13 19:39:28.000 12205 12205 W com.mbwhatsapp: type=1400 audit(0.0:106169): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-13 20:14:48.244 20446 20446 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 20:14:49.415 20446 20446 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
06-13 21:15:26.058 7106 7106 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 21:15:26.753 7106 7106 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.
06-13 21:15:28.205 7106 7163 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-13 21:15:28.205 7106 7163 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-13 21:15:28.205 7106 7163 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-13 22:22:15.008 14425 14425 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 22:22:15.941 14425 14425 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
06-13 22:27:27.041 16257 16257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 22:27:27.796 16257 16257 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
06-13 23:15:27.165 27375 27375 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 23:15:27.802 27375 27375 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
06-13 23:23:27.125 28048 28048 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-13 23:23:27.595 28048 28048 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
06-14 07:19:13.257 9074 9074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 07:19:13.987 9074 9074 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
06-14 08:04:54.799 18769 18769 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 08:04:56.429 18769 18769 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.
06-14 08:04:58.301 18769 18929 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-14 08:04:58.301 18769 18929 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-14 08:04:58.301 18769 18929 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-14 11:59:46.117 23353 23353 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 11:59:46.660 23353 23353 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.
06-14 11:59:47.764 23353 23404 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-14 11:59:47.764 23353 23404 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-14 11:59:47.764 23353 23404 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-14 15:58:31.139 8552 8552 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 15:58:33.687 8552 8552 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
06-14 16:05:02.633 17088 17088 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 16:05:06.861 17088 17088 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.
06-14 16:05:12.398 17088 17088 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-14 16:05:12.399 17088 17088 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-14 16:05:13.248 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3759): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 16:05:13.288 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3760): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 16:05:13.398 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3761): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-14 16:05:14.842 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3762): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 16:05:15.288 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3763): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 16:05:15.288 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3764): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 16:05:15.288 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3765): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 16:05:15.288 17088 17088 W com.mbwhatsapp: type=1400 audit(0.0:3766): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
06-14 16:05:19.212 17088 17096 W com.mbwhatsapp: Suspending all threads took:
63.334ms
06-14 16:05:19.795 17088 17096 W com.mbwhatsapp: Suspending all threads took:
75.598ms
06-14 16:44:57.544 26140 26140 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 16:44:58.573 26140 26140 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.
06-14 16:44:59.985 26140 26140 W com.mbwhatsapp: type=1400 audit(0.0:5670): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-14 18:03:23.408 7949 7949 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 18:03:24.517 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.
--------- beginning of main
06-14 19:14:18.648 5246 5246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-14 19:14:21.458 5246 5246 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-14 19:14:21.459 5246 5246 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-14 19:14:21.459 5246 5246 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-14 19:14:21.459 5246 5246 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-14 19:14:21.459 5246 5246 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-14 19:14:21.459 5246 5246 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-14 19:14:21.459 5246 5246 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-14 19:14:21.459 5246 5246 W System.err: at
java.lang.Class.newInstance(Native Method)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-14 19:14:21.460 5246 5246 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-14 19:14:21.460 5246 5246 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-14 19:14:21.460 5246 5246 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-14 19:14:21.460 5246 5246 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-14 19:14:21.460 5246 5246 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-14 19:14:21.460 5246 5246 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-14 19:14:21.460 5246 5246 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-14 19:14:21.460 5246 5246 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-14 19:14:22.056 5246 5246 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.
06-14 19:14:26.032 5246 5246 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-14 19:14:26.035 5246 5246 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-14 19:14:26.585 5246 5246 W com.mbwhatsapp: type=1400 audit(0.0:1471): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 19:14:26.609 5246 5246 W com.mbwhatsapp: type=1400 audit(0.0:1472): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 19:14:26.652 5246 5246 W com.mbwhatsapp: type=1400 audit(0.0:1473): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 19:14:26.955 5246 5246 W com.mbwhatsapp: type=1400 audit(0.0:1474): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 19:14:27.225 5246 5246 W com.mbwhatsapp: type=1400 audit(0.0:1475): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-14 19:14:27.225 5246 5246 W com.mbwhatsapp: type=1400 audit(0.0:1476): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-15 07:48:16.109 4907 4907 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 07:48:18.968 4907 4907 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-15 07:48:18.969 4907 4907 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.Class.newInstance(Native Method)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-15 07:48:18.969 4907 4907 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-15 07:48:18.969 4907 4907 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-15 07:48:18.969 4907 4907 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-15 07:48:18.969 4907 4907 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-15 07:48:18.969 4907 4907 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-15 07:48:18.969 4907 4907 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-15 07:48:18.969 4907 4907 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-15 07:48:18.969 4907 4907 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-15 07:48:19.944 4907 4907 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.
06-15 07:48:21.626 4907 4918 W com.mbwhatsapp: Suspending all threads took:
6.923ms
06-15 07:48:23.348 4907 4907 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-15 07:48:23.349 4907 4907 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
06-15 07:48:25.516 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1369): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:26.309 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1370): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:26.452 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1371): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:27.156 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1373): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:27.422 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1374): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:27.422 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1375): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:27.422 4907 4907 W com.mbwhatsapp: type=1400 audit(0.0:1376): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-15 07:48:28.387 4907 5349 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-15 07:48:28.387 4907 5349 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-15 07:48:28.387 4907 5349 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-15 07:48:33.287 4907 5531 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
06-15 07:48:33.288 4907 5531 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
06-15 07:51:44.345 10234 10234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 07:51:46.230 10234 10234 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
06-15 13:29:45.546 12235 12235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 13:29:47.177 12235 12235 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
06-15 13:31:51.666 17226 17226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 13:31:53.165 17226 17226 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
06-15 13:34:21.984 22236 22236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 13:34:26.617 22236 22236 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
06-15 13:54:00.992 28441 28441 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 13:54:02.011 28441 28441 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
06-15 15:14:22.543 10557 10557 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 15:14:23.564 10557 10557 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
06-15 15:43:06.576 17967 17967 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 15:43:07.307 17967 17967 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
06-15 18:45:35.684 14894 14894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 18:45:36.905 14894 14894 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
06-15 19:43:05.387 28773 28773 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 19:43:06.518 28773 28773 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.
06-15 19:43:08.279 28773 28904 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-15 19:43:08.279 28773 28904 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-15 19:43:08.279 28773 28904 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-15 20:48:12.606 3433 3433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 20:48:14.329 3433 3433 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.
06-15 20:48:16.929 3433 3433 W com.mbwhatsapp: type=1400 audit(0.0:25431): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-15 21:06:12.312 6176 6176 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 21:06:12.909 6176 6176 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
06-15 21:17:59.140 10054 10054 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 21:17:59.977 10054 10054 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
06-15 21:46:13.317 13586 13586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 21:46:14.129 13586 13586 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
06-15 22:43:01.003 22297 22297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-15 22:43:01.547 22297 22297 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
06-16 07:03:23.406 15833 15833 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-16 07:03:24.011 15833 15833 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
06-16 07:31:31.339 21028 21028 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-16 07:31:31.877 21028 21028 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
06-16 15:26:03.308 16789 16789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-16 15:26:03.940 16789 16789 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.
06-16 15:26:05.040 16789 16839 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-16 15:26:05.040 16789 16839 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-16 15:26:05.040 16789 16839 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-16 18:44:19.761 30651 30651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-16 18:44:20.746 30651 30651 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
06-16 22:27:07.980 12290 12290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-16 22:27:10.094 12290 12290 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
06-16 23:27:07.859 19586 19586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-16 23:27:08.637 19586 19586 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.
06-16 23:27:09.736 19586 19633 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-16 23:27:09.736 19586 19633 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-16 23:27:09.736 19586 19633 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-17 00:34:14.018 3087 3087 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 00:34:15.642 3087 3087 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.
06-17 00:34:18.272 3087 3178 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-17 00:34:18.272 3087 3178 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-17 00:34:18.272 3087 3178 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-17 00:42:11.720 6331 6331 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 00:42:12.371 6331 6331 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.
06-17 00:42:13.702 6331 6379 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-17 00:42:13.702 6331 6379 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-17 00:42:13.702 6331 6379 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-17 01:27:07.847 21629 21629 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 01:27:08.692 21629 21629 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
06-17 03:42:14.131 21629 21643 W com.mbwhatsapp: Reducing the number of considered
missed Gc histogram windows from 105 to 100
06-17 05:46:12.325 9054 9054 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 05:46:13.372 9054 9054 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
06-17 11:09:28.972 14869 14869 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 11:09:30.179 14869 14869 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.
06-17 11:09:31.875 14869 14953 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-17 11:09:31.875 14869 14953 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-17 11:09:31.875 14869 14953 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-17 12:40:34.749 30146 30146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 12:40:35.236 30146 30146 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
06-17 13:42:12.332 9130 9130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 13:42:13.099 9130 9130 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
06-17 14:41:02.029 26897 26897 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-17 14:41:02.552 26897 26897 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
06-18 02:36:04.751 9980 9980 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 02:36:07.136 9980 9980 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.
06-18 02:36:08.714 9980 9980 W com.mbwhatsapp: type=1400 audit(0.0:2499): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-18 02:36:08.787 9980 9980 W com.mbwhatsapp: type=1400 audit(0.0:2500): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-18 02:42:33.458 14496 14496 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 02:42:34.187 14496 14496 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
06-18 03:43:07.477 27390 27390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 03:43:08.185 27390 27390 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.
06-18 03:43:09.040 27390 27390 W com.mbwhatsapp: type=1400 audit(0.0:6242): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-18 03:43:09.063 27390 27390 W com.mbwhatsapp: type=1400 audit(0.0:6243): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-18 03:44:57.178 27688 27688 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 03:44:57.504 27688 27688 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.
06-18 03:44:58.025 27688 27741 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-18 03:44:58.025 27688 27741 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-18 03:44:58.025 27688 27741 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-18 04:42:47.196 3052 3052 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 04:42:47.935 3052 3052 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.
06-18 04:42:48.843 3052 3052 W com.mbwhatsapp: type=1400 audit(0.0:7878): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-18 05:42:38.075 31954 31954 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 05:42:38.397 31954 31954 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.
06-18 05:42:39.000 31954 32004 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-18 05:42:39.000 31954 32004 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-18 05:42:39.000 31954 32004 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-18 06:39:02.179 8314 8314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 06:39:03.121 8314 8314 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
06-18 07:42:53.159 22765 22765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 07:42:53.825 22765 22765 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.
06-18 07:42:55.044 22765 22815 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-18 07:42:55.044 22765 22815 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-18 07:42:55.044 22765 22815 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-18 08:21:54.690 25964 25964 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 08:21:55.199 25964 25964 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
06-18 08:33:49.555 28908 28908 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 08:33:51.052 28908 28908 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
06-18 08:43:33.580 30318 30318 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 08:43:34.207 30318 30318 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
06-18 09:42:44.265 6892 6892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 09:42:44.964 6892 6892 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
06-18 09:44:44.851 7087 7087 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 09:44:45.134 7087 7087 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
06-18 10:42:33.469 15019 15019 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 10:42:34.269 15019 15019 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
06-18 10:44:46.204 15457 15457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 10:44:46.570 15457 15457 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
06-18 11:46:21.888 23452 23452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 11:46:22.513 23452 23452 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
06-18 11:55:23.296 24419 24419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 11:55:24.034 24419 24419 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
06-18 11:57:41.529 24604 24604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 11:57:41.799 24604 24604 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
06-18 12:13:54.671 26738 26738 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 12:13:55.347 26738 26738 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
06-18 12:26:18.977 27745 27745 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 12:26:19.310 27745 27745 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
06-18 12:30:07.203 28802 28802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 12:30:07.615 28802 28802 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
06-18 12:35:03.550 32020 32020 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 12:35:04.900 32020 32020 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
06-18 12:43:14.075 6174 6174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 12:43:15.322 6174 6174 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
06-18 12:45:16.378 6726 6726 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 12:45:17.592 6726 6726 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
06-18 13:51:55.520 18233 18233 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 13:51:56.605 18233 18233 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.
06-18 13:51:58.671 18233 18339 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-18 13:51:58.671 18233 18339 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-18 13:51:58.671 18233 18339 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-18 13:58:04.738 20396 20396 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 13:58:05.702 20396 20396 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
06-18 14:01:16.900 20882 20882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 14:01:17.786 20882 20882 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
06-18 14:16:17.807 22794 22794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 14:16:18.504 22794 22794 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
06-18 14:24:44.394 23594 23594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 14:24:45.237 23594 23594 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
06-18 14:34:17.926 24962 24962 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 14:34:18.633 24962 24962 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
06-18 14:44:19.816 26065 26065 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 14:44:20.729 26065 26065 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
06-18 14:54:28.930 29369 29369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 14:54:29.901 29369 29369 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
06-18 15:23:36.767 31922 31922 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 15:23:38.605 31922 31922 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
06-18 16:02:05.792 2308 2308 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 16:02:06.832 2308 2308 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
06-18 17:02:25.246 3852 3852 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 17:02:27.062 3852 3852 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
06-18 18:41:26.790 10493 10493 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 18:41:28.645 10493 10493 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.
06-18 18:41:29.970 10493 10493 W com.mbwhatsapp: type=1400 audit(0.0:133901): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-18 18:41:29.993 10493 10493 W com.mbwhatsapp: type=1400 audit(0.0:133902): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-18 19:45:30.958 17092 17092 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 19:45:31.679 17092 17092 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
06-18 20:51:40.382 20501 20501 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 20:51:42.467 20501 20501 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
06-18 22:55:37.016 24929 24929 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-18 22:55:38.313 24929 24929 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
06-19 00:42:34.703 16014 16014 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 00:42:35.356 16014 16014 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
06-19 01:47:34.118 28485 28485 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 01:47:34.719 28485 28485 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.
06-19 01:47:35.946 28485 28537 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-19 01:47:35.946 28485 28537 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-19 01:47:35.946 28485 28537 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-19 02:31:46.341 5640 5640 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 02:31:47.997 5640 5640 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
06-19 02:43:16.778 8477 8477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 02:43:18.119 8477 8477 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
06-19 02:45:56.997 8850 8850 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 02:45:57.267 8850 8850 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
06-19 02:58:18.036 10298 10298 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 02:58:18.388 10298 10298 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.
06-19 02:58:18.682 10298 10298 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-19 02:58:18.682 10298 10298 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-19 02:58:18.909 10298 10355 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-19 02:58:18.909 10298 10355 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-19 02:58:18.909 10298 10355 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-19 03:02:10.457 10735 10735 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 03:02:10.939 10735 10735 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
06-19 03:06:38.602 11377 11377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 03:06:38.889 11377 11377 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
06-19 03:43:21.328 15446 15446 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 03:43:21.962 15446 15446 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
06-19 03:53:10.714 16453 16453 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 03:53:11.006 16453 16453 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
06-19 04:42:40.617 22405 22405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 04:42:41.402 22405 22405 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
06-19 06:43:14.047 13543 13543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 06:43:14.729 13543 13543 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.
06-19 06:43:15.837 13543 13602 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-19 06:43:15.837 13543 13602 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-19 06:43:15.837 13543 13602 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-19 06:46:47.942 14376 14376 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 06:46:48.743 14376 14376 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
06-19 06:49:53.986 14972 14972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 06:49:54.468 14972 14972 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
06-19 06:53:37.590 15819 15819 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 06:53:37.850 15819 15819 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
06-19 06:57:33.456 16256 16256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 06:57:33.724 16256 16256 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
06-19 07:45:07.033 19955 19955 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 07:45:07.707 19955 19955 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
06-19 07:52:09.208 22963 22963 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 07:52:12.729 22963 22963 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
06-19 08:03:34.131 25475 25475 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 08:03:35.186 25475 25475 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
06-19 08:44:03.819 2119 2119 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 08:44:04.784 2119 2119 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
06-19 08:48:45.351 3220 3220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 08:48:47.407 3220 3220 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
06-19 08:55:36.063 4643 4643 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 08:55:36.492 4643 4643 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
06-19 09:00:06.263 5404 5404 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 09:00:06.556 5404 5404 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
06-19 09:47:04.487 15993 15993 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 09:47:08.869 15993 15993 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.
06-19 09:47:10.167 15993 16041 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-19 09:47:10.167 15993 16041 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-19 09:47:10.167 15993 16041 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-19 10:51:37.845 20778 20778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 10:51:39.303 20778 20778 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
06-19 11:43:36.912 24591 24591 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 11:43:38.238 24591 24591 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
06-19 12:47:36.809 5564 5564 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 12:47:37.901 5564 5564 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
06-19 14:39:25.664 11292 11292 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 14:39:26.928 11292 11292 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.
06-19 14:39:28.403 11292 11292 W com.mbwhatsapp: type=1400 audit(0.0:190226): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-19 14:47:37.869 13252 13252 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 14:47:38.664 13252 13252 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
06-19 15:51:35.971 19596 19596 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 15:51:36.915 19596 19596 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
06-19 16:47:36.764 24333 24333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 16:47:37.062 24333 24333 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
06-19 17:47:36.233 6255 6255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 17:47:38.048 6255 6255 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
06-19 18:57:16.539 13900 13900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 18:57:17.400 13900 13900 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
06-19 19:10:05.096 15472 15472 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 19:10:05.909 15472 15472 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
06-19 19:47:14.208 30162 30162 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 19:47:15.735 30162 30162 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
06-19 20:07:21.354 6196 6196 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 20:07:22.355 6196 6196 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
06-19 20:43:37.034 15398 15398 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 20:43:39.536 15398 15398 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.
06-19 20:43:40.757 15398 15398 W com.mbwhatsapp: type=1400 audit(0.0:212631): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-19 21:42:33.511 1180 1180 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 21:42:34.278 1180 1180 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
06-19 22:42:55.495 6048 6048 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 22:42:56.609 6048 6048 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
06-19 23:57:30.044 18430 18430 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-19 23:57:31.852 18430 18430 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.
06-19 23:57:33.090 18430 18430 W com.mbwhatsapp: type=1400 audit(0.0:4581): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-19 23:57:33.110 18430 18430 W com.mbwhatsapp: type=1400 audit(0.0:4582): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-20 00:14:36.224 21157 21157 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 00:14:37.254 21157 21157 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
06-20 01:22:14.416 23871 23871 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 01:22:15.030 23871 23871 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
06-20 03:25:04.642 27452 27452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 03:25:05.137 27452 27452 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
06-20 05:01:30.046 31755 31755 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 05:01:30.408 31755 31755 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
06-20 05:18:11.973 1215 1215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 05:18:12.531 1215 1215 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
06-20 05:41:05.627 3457 3457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 05:41:06.008 3457 3457 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
06-20 06:08:11.930 5043 5043 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 06:08:12.831 5043 5043 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
06-20 06:28:09.554 5874 5874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 06:28:09.820 5874 5874 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
06-20 07:20:43.293 8623 8623 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 07:20:43.940 8623 8623 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
06-20 07:27:46.150 10352 10352 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 07:27:46.413 10352 10352 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
06-20 07:34:40.532 4814 4814 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 07:34:41.886 4814 4814 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-20 07:34:41.887 4814 4814 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-20 07:34:41.887 4814 4814 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-20 07:34:41.887 4814 4814 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-20 07:34:41.887 4814 4814 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-20 07:34:41.887 4814 4814 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-20 07:34:41.887 4814 4814 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-20 07:34:41.888 4814 4814 W System.err: at
java.lang.Class.newInstance(Native Method)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-20 07:34:41.888 4814 4814 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-20 07:34:41.888 4814 4814 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-20 07:34:41.888 4814 4814 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-20 07:34:41.888 4814 4814 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-20 07:34:41.888 4814 4814 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-20 07:34:41.889 4814 4814 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-20 07:34:41.889 4814 4814 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-20 07:34:41.889 4814 4814 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-20 07:34:42.411 4814 4814 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.
06-20 07:34:46.357 4814 4814 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-20 07:34:46.358 4814 4814 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-20 07:34:46.615 4814 4814 W com.mbwhatsapp: type=1400 audit(0.0:1462): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-20 07:34:46.639 4814 4814 W com.mbwhatsapp: type=1400 audit(0.0:1463): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-20 07:34:46.695 4814 4814 W com.mbwhatsapp: type=1400 audit(0.0:1464): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-20 07:34:47.165 4814 4814 W com.mbwhatsapp: type=1400 audit(0.0:1465): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-20 07:53:48.301 8557 8557 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 07:53:51.890 8557 8557 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.
06-20 07:53:55.831 8557 8557 W com.mbwhatsapp: type=1400 audit(0.0:2149): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-20 07:53:55.875 8557 8557 W com.mbwhatsapp: type=1400 audit(0.0:2150): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-20 07:53:55.965 8557 8557 W com.mbwhatsapp: type=1400 audit(0.0:2151): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-20 08:38:14.590 20579 20579 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 08:38:17.309 20579 20579 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
06-20 09:38:24.198 26185 26185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 09:38:24.973 26185 26185 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
06-20 10:36:01.232 29888 29888 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 10:36:01.843 29888 29888 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.
06-20 10:36:02.986 29888 29934 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-20 10:36:02.986 29888 29934 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-20 10:36:02.986 29888 29934 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-20 11:36:03.223 2050 2050 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 11:36:03.824 2050 2050 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
06-20 12:37:11.860 13484 13484 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 12:37:13.036 13484 13484 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.
06-20 12:37:14.704 13484 13537 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-20 12:37:14.704 13484 13537 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-20 12:37:14.704 13484 13537 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-20 13:36:51.362 22758 22758 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 13:36:54.051 22758 22758 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
06-20 14:39:25.577 29220 29220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 14:39:26.501 29220 29220 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.
06-20 14:39:27.634 29220 29311 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-20 14:39:27.634 29220 29311 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-20 14:39:27.634 29220 29311 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-20 16:24:35.013 7226 7226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 16:24:37.976 7226 7226 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
06-20 17:50:45.386 11166 11166 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 17:50:47.273 11166 11166 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
06-20 18:36:32.548 22548 22548 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 18:36:33.582 22548 22548 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
06-20 18:46:16.207 25201 25201 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 18:46:17.603 25201 25201 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
06-20 18:57:13.816 26769 26769 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 18:57:14.892 26769 26769 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.
06-20 18:57:16.345 26769 26769 W com.mbwhatsapp: type=1400 audit(0.0:238867): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-20 19:01:19.397 27780 27780 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 19:01:20.104 27780 27780 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
06-20 19:38:24.712 1040 1040 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 19:38:25.586 1040 1040 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
06-20 19:41:57.135 2853 2853 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 19:41:58.037 2853 2853 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
06-20 20:38:17.115 5106 5106 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 20:38:18.029 5106 5106 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
06-20 21:35:52.410 14294 14294 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 21:35:53.082 14294 14294 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
06-20 22:34:32.671 27595 27595 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 22:34:33.619 27595 27595 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
06-20 22:44:06.386 29824 29824 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 22:44:07.366 29824 29824 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
06-20 22:48:12.243 30491 30491 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 22:48:12.590 30491 30491 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
06-20 22:52:23.735 383 383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 22:52:24.818 383 383 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
06-20 23:39:25.589 7826 7826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-20 23:39:26.579 7826 7826 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
06-21 00:01:55.038 10230 10230 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 00:01:56.215 10230 10230 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.
06-21 00:01:57.672 10230 10230 W com.mbwhatsapp: type=1400 audit(0.0:298878): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-21 01:03:25.635 11676 11676 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 01:03:27.263 11676 11676 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
06-21 01:03:28.929 11676 11767 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-21 01:03:28.929 11676 11767 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-21 01:03:28.929 11676 11767 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-21 01:03:29.652 11676 11796 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
06-21 01:03:29.653 11676 11796 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
06-21 03:06:04.983 14962 14962 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 03:06:08.690 14962 14962 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
06-21 07:03:33.431 21678 21678 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 07:03:35.085 21678 21678 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
06-21 07:31:19.092 26551 26551 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 07:31:20.731 26551 26551 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
06-21 17:09:17.431 27522 27522 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 17:09:20.328 27522 27522 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.
06-21 17:09:23.269 27522 27522 W com.mbwhatsapp: type=1400 audit(0.0:15358): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-21 17:18:08.596 30719 30719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 17:18:10.410 30719 30719 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
06-21 18:42:35.341 13225 13225 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 18:42:36.129 13225 13225 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.
06-21 18:42:37.419 13225 13274 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-21 18:42:37.419 13225 13274 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-21 18:42:37.419 13225 13274 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-21 18:50:37.440 15963 15963 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 18:50:38.649 15963 15963 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
06-21 18:52:50.128 17464 17464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 18:52:51.682 17464 17464 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
06-21 18:56:03.534 18221 18221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 18:56:09.412 18221 18221 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
06-21 19:49:12.704 27100 27100 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 19:49:14.125 27100 27100 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
06-21 19:57:53.138 30653 30653 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 19:57:53.991 30653 30653 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
06-21 20:05:00.539 2605 2605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 20:05:01.768 2605 2605 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
06-21 20:42:33.987 16879 16879 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 20:42:35.110 16879 16879 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
06-21 21:06:04.809 24967 24967 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 21:06:06.102 24967 24967 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.
06-21 21:06:07.858 24967 24967 W com.mbwhatsapp: type=1400 audit(0.0:64264): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-21 21:43:05.840 2975 2975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 21:43:06.634 2975 2975 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.
06-21 21:45:17.685 3489 3489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 21:45:18.369 3489 3489 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
06-21 21:46:32.733 4743 4743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 21:46:33.589 4743 4743 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
06-21 21:49:44.050 5338 5338 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 21:49:44.312 5338 5338 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
06-21 22:42:32.798 13765 13765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 22:42:33.531 13765 13765 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
06-21 23:42:53.290 22886 22886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-21 23:42:54.335 22886 22886 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.
06-21 23:42:56.044 22886 22886 W com.mbwhatsapp: type=1400 audit(0.0:76395): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-22 01:09:21.884 28210 28210 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 01:09:24.021 28210 28210 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
06-22 03:11:43.148 32727 32727 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 03:11:46.188 32727 32727 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.
06-22 03:11:48.642 32727 32727 W com.mbwhatsapp: type=1400 audit(0.0:78359): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-22 07:00:00.614 9838 9838 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 07:00:03.389 9838 9838 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.
06-22 07:00:07.336 9838 9838 W com.mbwhatsapp: type=1400 audit(0.0:79818): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-22 13:55:19.986 10322 10322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 13:55:23.462 10322 10322 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
06-22 13:57:43.800 17135 17135 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 13:57:44.981 17135 17135 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
06-22 15:43:36.430 8633 8633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 15:43:37.084 8633 8633 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.
06-22 15:43:37.880 8633 8633 W com.mbwhatsapp: type=1400 audit(0.0:7119): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-22 16:44:51.191 23901 23901 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 16:44:51.893 23901 23901 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
06-22 16:51:02.534 24097 24097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 16:51:02.911 24097 24097 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
06-22 16:53:05.224 24247 24247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 16:53:05.637 24247 24247 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
06-22 16:57:01.699 24747 24747 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 16:57:02.266 24747 24747 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
06-22 17:06:35.612 26373 26373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 17:06:37.047 26373 26373 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
06-22 17:43:37.440 29893 29893 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 17:43:38.416 29893 29893 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
06-22 17:54:32.626 31684 31684 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 17:54:35.615 31684 31684 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
06-22 18:17:44.301 6236 6236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 18:17:45.358 6236 6236 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
06-22 18:57:47.319 16184 16184 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 18:57:48.575 16184 16184 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
06-22 19:47:03.117 26781 26781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 19:47:04.155 26781 26781 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.
06-22 19:47:07.276 26781 26781 W com.mbwhatsapp: type=1400 audit(0.0:387008): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-22 20:47:15.302 6465 6465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 20:47:15.981 6465 6465 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
06-22 21:48:28.865 19579 19579 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 21:48:29.873 19579 19579 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
06-22 22:50:45.593 2260 2260 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-22 22:50:46.198 2260 2260 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
06-23 00:45:26.266 14424 14424 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 00:45:27.807 14424 14424 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.
06-23 00:45:30.036 14424 14424 W com.mbwhatsapp: type=1400 audit(0.0:407143): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-23 02:48:44.986 20321 20321 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 02:48:47.812 20321 20321 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.
06-23 06:52:45.579 28952 28952 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 06:52:47.411 28952 28952 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
06-23 07:56:39.576 12570 12570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 07:56:40.516 12570 12570 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.
06-23 07:56:42.518 12570 12641 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-23 07:56:42.518 12570 12641 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-23 07:56:42.518 12570 12641 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-23 08:43:22.834 14926 14926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 08:43:23.631 14926 14926 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.
06-23 08:43:25.308 14926 14982 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-23 08:43:25.308 14926 14982 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-23 08:43:25.308 14926 14982 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-23 14:05:05.948 5004 5004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 14:05:09.319 5004 5004 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-23 14:05:09.324 5004 5004 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.Class.newInstance(Native Method)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-23 14:05:09.324 5004 5004 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-23 14:05:09.324 5004 5004 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-23 14:05:09.324 5004 5004 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-23 14:05:09.324 5004 5004 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-23 14:05:09.324 5004 5004 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-23 14:05:09.324 5004 5004 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-23 14:05:09.325 5004 5004 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-23 14:05:09.325 5004 5004 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-23 14:05:10.296 5004 5004 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.
06-23 14:05:12.674 5004 5004 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-23 14:05:12.675 5004 5004 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-23 14:05:13.149 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1469): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-23 14:05:13.216 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1470): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-23 14:05:13.462 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1471): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-23 14:05:13.589 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1472): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-23 14:05:13.589 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1473): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-23 14:05:13.589 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1474): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-23 14:05:13.589 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1475): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
06-23 14:05:15.089 5004 5013 W com.mbwhatsapp: Suspending all threads took:
232.194ms
06-23 14:05:15.465 5004 5594 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-23 14:05:15.465 5004 5594 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-23 14:05:15.465 5004 5594 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-23 14:05:17.300 5004 5013 W com.mbwhatsapp: Suspending all threads took:
35.565ms
06-23 14:07:14.172 10009 10009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 14:07:17.295 10009 10009 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.
06-23 14:07:18.165 10009 10009 W com.mbwhatsapp: type=1400 audit(0.0:2545): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-23 14:07:57.886 11867 11867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 14:07:58.618 11867 11867 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
06-23 14:59:46.281 16882 16882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 14:59:46.809 16882 16882 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
06-23 15:07:50.765 17568 17568 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 15:07:51.148 17568 17568 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
06-23 15:14:25.766 17959 17959 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 15:14:26.183 17959 17959 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
06-23 15:17:08.673 19001 19001 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 15:17:09.331 19001 19001 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
06-23 15:22:42.463 19713 19713 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 15:22:42.769 19713 19713 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
06-23 15:31:11.927 20781 20781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 15:31:12.221 20781 20781 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
06-23 15:58:21.419 23660 23660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 15:58:21.951 23660 23660 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
06-23 16:59:29.475 6943 6943 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 16:59:30.481 6943 6943 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
06-23 17:03:30.902 7925 7925 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 17:03:31.192 7925 7925 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
06-23 17:59:34.024 17226 17226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 17:59:34.966 17226 17226 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
06-23 18:21:57.041 24600 24600 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 18:22:02.621 24600 24600 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
06-23 18:59:30.446 8856 8856 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 18:59:31.277 8856 8856 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
06-23 19:07:38.775 13539 13539 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 19:07:39.824 13539 13539 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
06-23 19:11:03.983 14270 14270 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 19:11:04.633 14270 14270 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
06-23 20:07:18.919 25362 25362 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 20:07:19.570 25362 25362 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
06-23 21:00:39.383 31701 31701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 21:00:40.294 31701 31701 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
06-23 21:20:39.455 1376 1376 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 21:20:39.767 1376 1376 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
06-23 21:29:10.866 3651 3651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 21:29:11.231 3651 3651 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
06-23 21:45:12.891 7957 7957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 21:45:13.574 7957 7957 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
06-23 21:56:08.354 9114 9114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 21:56:09.502 9114 9114 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
06-23 21:59:30.341 10287 10287 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 21:59:30.826 10287 10287 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
06-23 23:10:31.224 18176 18176 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-23 23:10:32.162 18176 18176 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
06-24 01:16:39.421 24661 24661 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 01:16:40.506 24661 24661 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.
06-24 01:16:42.404 24661 24661 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-24 01:16:42.404 24661 24661 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
06-24 03:20:24.361 27719 27719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 03:20:28.376 27719 27719 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
06-24 07:08:18.328 6652 6652 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 07:08:22.618 6652 6652 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
06-24 08:59:31.219 12351 12351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 08:59:31.838 12351 12351 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
06-24 09:59:37.166 15109 15109 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 09:59:37.837 15109 15109 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
06-24 10:59:55.696 17647 17647 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 10:59:56.225 17647 17647 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
06-24 11:02:46.035 18554 18554 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 11:02:46.370 18554 18554 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
06-24 11:19:08.493 19685 19685 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 11:19:08.886 19685 19685 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
06-24 13:06:16.523 26400 26400 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 13:06:18.146 26400 26400 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
06-24 15:11:10.467 323 323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 15:11:12.800 323 323 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
06-24 15:15:04.235 4782 4782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 15:15:05.565 4782 4782 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
06-24 16:03:09.809 14476 14476 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 16:03:10.498 14476 14476 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
06-24 16:15:08.921 15676 15676 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 16:15:09.979 15676 15676 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
06-24 16:32:51.885 17452 17452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 16:32:52.376 17452 17452 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
06-24 16:38:58.732 20008 20008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 16:38:59.843 20008 20008 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
06-24 16:45:06.214 21559 21559 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 16:45:07.124 21559 21559 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
06-24 16:53:41.422 22857 22857 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 16:53:41.898 22857 22857 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
06-24 17:11:43.588 27223 27223 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 17:11:44.176 27223 27223 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.
06-24 17:11:45.387 27223 27313 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-24 17:11:45.387 27223 27313 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-24 17:11:45.387 27223 27313 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-24 17:25:55.932 29720 29720 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 17:25:56.336 29720 29720 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
06-24 17:59:33.770 5578 5578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 17:59:34.756 5578 5578 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
06-24 18:13:56.246 10202 10202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 18:13:56.891 10202 10202 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
06-24 18:59:40.950 27640 27640 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 18:59:42.105 27640 27640 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
06-24 19:17:52.459 31592 31592 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 19:17:53.273 31592 31592 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
06-24 19:58:34.216 12925 12925 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 19:58:35.091 12925 12925 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
06-24 21:10:58.097 22013 22013 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 21:10:58.819 22013 22013 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
06-24 22:09:13.785 4403 4403 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 22:09:14.793 4403 4403 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
06-24 22:26:49.955 7533 7533 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 22:26:50.838 7533 7533 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
06-24 23:00:55.833 14469 14469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 23:00:56.553 14469 14469 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
06-24 23:14:50.826 16151 16151 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 23:14:51.828 16151 16151 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
06-24 23:35:08.410 18355 18355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-24 23:35:09.055 18355 18355 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
06-25 00:54:58.116 21582 21582 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 00:55:00.322 21582 21582 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
06-25 02:58:45.102 25555 25555 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 02:58:47.474 25555 25555 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
06-25 07:03:14.201 3492 3492 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 07:03:18.481 3492 3492 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
06-25 08:59:28.581 23460 23460 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 08:59:29.313 23460 23460 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
06-25 09:28:14.268 27085 27085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 09:28:18.226 27085 27085 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
06-25 09:59:25.854 31028 31028 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 09:59:27.035 31028 31028 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
06-25 10:59:25.755 4234 4234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 10:59:26.421 4234 4234 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.
06-25 10:59:27.975 4234 4297 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-25 10:59:27.975 4234 4297 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-25 10:59:27.975 4234 4297 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-25 17:22:03.439 26177 26177 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 17:22:03.983 26177 26177 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.
06-25 17:22:04.856 26177 26177 W com.mbwhatsapp: type=1400 audit(0.0:676622): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-25 17:22:04.876 26177 26177 W com.mbwhatsapp: type=1400 audit(0.0:676623): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-25 18:59:25.822 15804 15804 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 18:59:27.051 15804 15804 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.
06-25 18:59:28.484 15804 15804 W com.mbwhatsapp: type=1400 audit(0.0:684837): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-25 19:01:29.072 16545 16545 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 19:01:30.105 16545 16545 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
06-25 19:14:43.856 19751 19751 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 19:14:45.171 19751 19751 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
06-25 19:20:51.443 22097 22097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 19:20:52.331 22097 22097 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
06-25 19:59:25.824 813 813 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 19:59:26.932 813 813 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
06-25 20:14:27.183 6327 6327 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 20:14:28.042 6327 6327 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
06-25 20:26:36.136 9469 9469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 20:26:37.174 9469 9469 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
06-25 21:00:00.509 17185 17185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 21:00:01.600 17185 17185 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
06-25 21:22:03.585 19708 19708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 21:22:04.829 19708 19708 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
06-25 21:58:15.041 27851 27851 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 21:58:16.183 27851 27851 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
06-25 21:59:36.272 28551 28551 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 21:59:36.628 28551 28551 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
06-25 23:07:02.805 9487 9487 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-25 23:07:03.518 9487 9487 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.
06-25 23:07:05.189 9487 9549 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-25 23:07:05.189 9487 9549 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-25 23:07:05.189 9487 9549 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-26 01:03:09.914 12499 12499 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 01:03:11.221 12499 12499 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.
06-26 03:06:39.109 16305 16305 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 07:11:09.069 19641 19641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 07:11:11.115 19641 19641 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
06-26 08:59:25.861 13115 13115 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 08:59:26.780 13115 13115 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.
06-26 08:59:28.559 13115 13167 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-26 08:59:28.559 13115 13167 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-26 08:59:28.559 13115 13167 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-26 09:02:27.173 13563 13563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 09:02:28.022 13563 13563 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
06-26 09:11:15.200 15542 15542 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 09:11:16.020 15542 15542 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
06-26 09:35:08.807 16374 16374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 09:35:09.478 16374 16374 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
06-26 10:24:13.247 24038 24038 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 10:24:14.556 24038 24038 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
06-26 11:43:59.136 13976 13976 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 11:44:01.070 13976 13976 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-26 11:44:01.071 13976 13976 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-26 11:44:01.071 13976 13976 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-26 11:44:01.071 13976 13976 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-26 11:44:01.071 13976 13976 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-26 11:44:01.071 13976 13976 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-26 11:44:01.071 13976 13976 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-26 11:44:01.071 13976 13976 W System.err: at
java.lang.Class.newInstance(Native Method)
06-26 11:44:01.071 13976 13976 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-26 11:44:01.071 13976 13976 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-26 11:44:01.071 13976 13976 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-26 11:44:01.071 13976 13976 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-26 11:44:01.072 13976 13976 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-26 11:44:01.072 13976 13976 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-26 11:44:01.072 13976 13976 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-26 11:44:01.072 13976 13976 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-26 11:44:01.072 13976 13976 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-26 11:44:01.072 13976 13976 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-26 11:44:01.072 13976 13976 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-26 11:44:01.072 13976 13976 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-26 11:44:01.072 13976 13976 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-26 11:44:01.072 13976 13976 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-26 11:44:01.590 13976 13976 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
06-26 11:47:57.168 16128 16128 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 11:47:58.039 16128 16128 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
06-26 11:59:17.732 16934 16934 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 11:59:18.746 16934 16934 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
06-26 12:07:54.931 18114 18114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 12:07:55.618 18114 18114 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
06-26 12:27:19.019 21742 21742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 12:27:20.008 21742 21742 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
06-26 13:44:45.203 2566 2566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 13:44:46.052 2566 2566 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
06-26 14:01:06.266 5127 5127 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 14:01:06.987 5127 5127 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
06-26 15:00:42.085 12999 12999 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 15:00:43.009 12999 12999 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
06-26 15:09:15.028 13396 13396 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 15:09:15.729 13396 13396 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
06-26 15:20:10.856 13623 13623 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 15:20:11.553 13623 13623 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
06-26 15:38:57.936 15826 15826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 15:38:59.798 15826 15826 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.
06-26 15:39:01.084 15826 15970 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-26 15:39:01.084 15826 15970 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-26 15:39:01.084 15826 15970 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-26 15:54:52.310 16110 16110 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 15:54:52.621 16110 16110 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
06-26 17:02:41.037 17092 17092 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 17:02:42.468 17092 17092 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
06-26 19:06:53.778 19324 19324 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 19:06:56.873 19324 19324 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
06-26 23:11:13.302 27348 27348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 23:11:14.102 27348 27348 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
06-26 23:22:16.787 30417 30417 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 23:22:17.736 30417 30417 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
06-26 23:38:50.844 5731 5731 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-26 23:38:51.650 5731 5731 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
06-27 00:15:08.650 8126 8126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 00:15:10.399 8126 8126 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
06-27 01:08:01.325 4470 4470 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 01:08:03.460 4470 4470 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-27 01:08:03.461 4470 4470 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-27 01:08:03.462 4470 4470 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-27 01:08:03.462 4470 4470 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-27 01:08:03.462 4470 4470 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-27 01:08:03.462 4470 4470 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-27 01:08:03.462 4470 4470 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-27 01:08:03.462 4470 4470 W System.err: at
java.lang.Class.newInstance(Native Method)
06-27 01:08:03.462 4470 4470 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-27 01:08:03.462 4470 4470 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-27 01:08:03.462 4470 4470 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-27 01:08:03.463 4470 4470 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-27 01:08:03.463 4470 4470 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-27 01:08:03.463 4470 4470 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-27 01:08:03.463 4470 4470 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-27 01:08:03.463 4470 4470 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-27 01:08:03.463 4470 4470 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-27 01:08:03.463 4470 4470 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-27 01:08:03.463 4470 4470 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-27 01:08:03.463 4470 4470 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-27 01:08:03.463 4470 4470 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-27 01:08:03.463 4470 4470 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-27 01:08:03.990 4470 4470 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
06-27 01:08:06.568 4470 4470 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-27 01:08:06.568 4470 4470 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
06-27 01:08:06.832 4470 4470 W com.mbwhatsapp: type=1400 audit(0.0:1247): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-27 01:08:06.869 4470 4470 W com.mbwhatsapp: type=1400 audit(0.0:1248): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-27 01:08:07.252 4470 4470 W com.mbwhatsapp: type=1400 audit(0.0:1249): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-27 01:08:07.616 4470 4470 W com.mbwhatsapp: type=1400 audit(0.0:1250): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-27 01:08:07.712 4470 4470 W com.mbwhatsapp: type=1400 audit(0.0:1251): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-27 01:08:08.584 4470 4952 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-27 01:08:08.584 4470 4952 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-27 01:08:08.584 4470 4952 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-27 01:08:10.532 4470 5009 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
06-27 01:08:10.532 4470 5009 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
06-27 01:09:02.331 7086 7086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 01:09:03.093 7086 7086 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
06-27 01:09:03.094 7086 7086 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
06-27 01:09:03.094 7086 7086 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
06-27 01:09:03.094 7086 7086 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
06-27 01:09:03.094 7086 7086 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
06-27 01:09:03.094 7086 7086 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
06-27 01:09:03.095 7086 7086 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
06-27 01:09:03.095 7086 7086 W System.err: at
java.lang.Class.newInstance(Native Method)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
06-27 01:09:03.095 7086 7086 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
06-27 01:09:03.095 7086 7086 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
06-27 01:09:03.095 7086 7086 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
06-27 01:09:03.095 7086 7086 W System.err: at
android.os.Looper.loop(Looper.java:334)
06-27 01:09:03.095 7086 7086 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
06-27 01:09:03.095 7086 7086 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
06-27 01:09:03.095 7086 7086 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
06-27 01:09:03.095 7086 7086 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
06-27 01:09:03.280 7086 7086 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.
06-27 01:09:03.954 7086 7086 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-27 01:09:03.954 7086 7086 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
06-27 01:09:04.481 7086 7148 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-27 01:09:04.481 7086 7148 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-27 01:09:04.481 7086 7148 W com.mbwhatsapp: and incorrect proguard
optimizations.
06-27 01:24:28.624 16794 16794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 01:24:31.236 16794 16794 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
06-27 02:02:34.989 24530 24530 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 02:02:35.588 24530 24530 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
06-27 02:02:39.440 24659 24659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 02:02:39.874 24659 24659 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
06-27 02:07:54.047 25258 25258 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 02:07:54.456 25258 25258 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
06-27 03:06:47.029 29112 29112 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 03:06:47.717 29112 29112 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.
06-27 03:06:48.841 29112 29166 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-27 03:06:48.841 29112 29166 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-27 03:06:48.841 29112 29166 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-27 03:08:20.456 29810 29810 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 03:08:20.744 29810 29810 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
06-27 03:11:55.158 30111 30111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 03:11:55.405 30111 30111 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
06-27 04:07:08.664 31387 31387 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 04:07:08.895 31387 31387 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
06-27 04:10:03.180 31521 31521 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 04:10:03.425 31521 31521 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
06-27 04:15:20.109 32068 32068 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 04:15:20.334 32068 32068 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
06-27 04:29:00.877 32397 32397 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 04:29:01.090 32397 32397 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
06-27 05:02:28.452 1945 1945 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 05:02:28.699 1945 1945 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
06-27 05:14:29.227 4402 4402 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 05:14:29.520 4402 4402 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
06-27 05:30:37.896 7608 7608 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 05:30:38.204 7608 7608 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
06-27 06:02:24.705 9611 9611 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 06:02:25.009 9611 9611 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
06-27 07:02:24.715 12975 12975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 07:02:25.031 12975 12975 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
06-27 08:02:45.538 16188 16188 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 08:02:45.840 16188 16188 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
06-27 09:02:30.691 20030 20030 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 09:02:30.988 20030 20030 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
06-27 09:32:24.719 22507 22507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 09:32:25.178 22507 22507 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
06-27 11:02:31.792 27128 27128 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:02:32.464 27128 27128 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
06-27 11:03:40.618 27628 27628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:03:40.900 27628 27628 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
06-27 11:07:33.809 28345 28345 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:07:34.180 28345 28345 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
06-27 11:08:26.507 28910 28910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:08:27.485 28910 28910 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
06-27 11:13:59.100 30380 30380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:13:59.724 30380 30380 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
06-27 11:17:18.524 30851 30851 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:17:18.782 30851 30851 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
06-27 11:27:37.456 31098 31098 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 11:27:37.679 31098 31098 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
06-27 12:40:44.085 13031 13031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 12:40:45.876 13031 13031 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
06-27 13:03:42.387 18989 18989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 13:03:43.153 18989 18989 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.
06-27 13:03:44.640 18989 19037 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-27 13:03:44.640 18989 19037 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-27 13:03:44.640 18989 19037 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-27 13:08:20.849 19800 19800 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 13:08:21.710 19800 19800 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
06-27 14:02:24.836 1380 1380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 14:02:25.532 1380 1380 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
06-27 14:12:21.314 5414 5414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 14:12:21.934 5414 5414 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
06-27 14:16:09.448 6348 6348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 14:16:09.701 6348 6348 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
06-27 14:39:37.073 10189 10189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 14:39:38.352 10189 10189 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
06-27 14:55:38.570 10429 10429 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 14:55:39.558 10429 10429 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
06-27 15:15:38.381 11601 11601 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 15:15:39.455 11601 11601 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
06-27 15:39:10.704 12844 12844 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 15:39:11.147 12844 12844 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
06-27 16:59:37.432 14217 14217 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 16:59:38.698 14217 14217 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
06-27 18:25:32.064 15654 15654 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 18:25:32.591 15654 15654 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
06-27 18:28:59.633 18005 18005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 18:29:00.269 18005 18005 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
06-27 18:31:30.365 18510 18510 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 18:31:30.673 18510 18510 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
06-27 18:36:20.095 20774 20774 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 18:36:21.810 20774 20774 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.
06-27 18:36:23.676 20774 20835 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-27 18:36:23.676 20774 20835 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-27 18:36:23.676 20774 20835 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-27 19:03:38.429 27096 27096 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 19:03:39.204 27096 27096 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
06-27 19:15:37.604 27580 27580 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 19:15:38.529 27580 27580 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
06-27 19:33:12.726 29307 29307 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 19:33:13.515 29307 29307 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
06-27 21:03:37.501 30794 30794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 21:03:38.782 30794 30794 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
06-27 22:02:34.634 4726 4726 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 22:02:36.047 4726 4726 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
06-27 23:02:45.195 13464 13464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-27 23:02:45.755 13464 13464 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.
06-27 23:02:46.666 13464 13515 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-27 23:02:46.666 13464 13515 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-27 23:02:46.666 13464 13515 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-28 01:09:13.528 7351 7351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 01:09:14.628 7351 7351 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.
06-28 01:09:16.451 7351 7351 W com.mbwhatsapp: type=1400 audit(0.0:87706): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-28 01:09:16.646 7351 7488 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-28 01:09:16.646 7351 7488 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-28 01:09:16.646 7351 7488 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-28 01:10:53.810 8283 8283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 01:10:55.467 8283 8283 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
06-28 03:02:41.241 17632 17632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 03:02:42.013 17632 17632 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
06-28 03:03:34.900 17768 17768 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 03:03:35.191 17768 17768 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
06-28 04:02:24.841 23502 23502 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 04:02:25.476 23502 23502 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
06-28 05:02:34.120 27252 27252 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 05:02:35.100 27252 27252 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
06-28 06:02:32.435 31987 31987 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 06:02:33.729 31987 31987 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
06-28 07:07:21.449 10991 10991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 07:07:23.824 10991 10991 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
06-28 07:09:11.502 11853 11853 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 07:09:11.822 11853 11853 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
06-28 07:12:19.222 12320 12320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 07:12:20.456 12320 12320 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
06-28 07:23:38.364 13103 13103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 07:23:38.820 13103 13103 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
06-28 08:14:26.891 16046 16046 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 08:14:27.545 16046 16046 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
06-28 09:14:40.910 17656 17656 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 09:14:42.143 17656 17656 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
06-28 11:15:37.121 18966 18966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 11:15:38.414 18966 18966 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
06-28 12:02:12.431 20796 20796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 12:02:13.628 20796 20796 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
06-28 12:14:22.198 24188 24188 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 12:14:22.904 24188 24188 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
06-28 12:15:34.688 25567 25567 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 12:15:36.304 25567 25567 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
06-28 13:02:25.862 812 812 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 13:02:26.681 812 812 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
06-28 13:10:19.297 4638 4638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 13:10:19.813 4638 4638 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
06-28 13:22:51.388 4886 4886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 13:22:51.830 4886 4886 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
06-28 14:03:38.558 7503 7503 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 14:03:39.468 7503 7503 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
06-28 15:07:20.816 9059 9059 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 15:07:22.331 9059 9059 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.
06-28 15:07:24.154 9059 9132 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-28 15:07:24.154 9059 9132 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-28 15:07:24.154 9059 9132 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-28 16:03:06.883 18542 18542 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 16:03:07.578 18542 18542 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
06-28 16:46:58.933 24301 24301 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 16:47:00.794 24301 24301 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
06-28 17:02:24.804 28061 28061 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 17:02:25.774 28061 28061 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
06-28 20:27:14.741 13632 13632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 20:27:21.353 13632 13632 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
06-28 22:19:05.983 30419 30419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 22:19:08.112 30419 30419 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
06-28 23:03:10.741 7857 7857 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 23:03:11.532 7857 7857 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
06-28 23:10:52.168 9616 9616 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 23:10:52.953 9616 9616 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
06-28 23:13:34.222 10380 10380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 23:13:35.516 10380 10380 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
06-28 23:16:22.753 10895 10895 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-28 23:16:23.616 10895 10895 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
06-29 00:02:24.843 21964 21964 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 00:02:25.773 21964 21964 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
06-29 00:08:23.310 24642 24642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 00:08:24.105 24642 24642 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
06-29 00:19:24.069 26709 26709 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 00:19:24.800 26709 26709 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
06-29 01:08:09.089 6573 6573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 01:08:10.399 6573 6573 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
06-29 02:02:50.758 15248 15248 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 02:02:51.294 15248 15248 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.
06-29 02:02:52.245 15248 15248 W com.mbwhatsapp: type=1400 audit(0.0:3614): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
06-29 02:02:52.398 15248 15347 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-29 02:02:52.398 15248 15347 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-29 02:02:52.398 15248 15347 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-29 02:06:24.058 15757 15757 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 02:06:24.327 15757 15757 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
06-29 02:08:24.706 15893 15893 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 02:08:24.992 15893 15893 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
06-29 02:12:26.202 16305 16305 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 02:12:26.467 16305 16305 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
06-29 03:02:40.924 19943 19943 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 03:02:41.552 19943 19943 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
06-29 03:09:48.136 20289 20289 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 03:09:48.391 20289 20289 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
06-29 03:18:53.677 20473 20473 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 03:18:53.941 20473 20473 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
06-29 04:02:38.587 22493 22493 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 04:02:38.877 22493 22493 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
06-29 05:02:40.162 24482 24482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 05:02:40.432 24482 24482 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
06-29 05:43:45.978 26875 26875 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 05:43:46.282 26875 26875 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
06-29 07:02:45.113 3772 3772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 07:02:45.678 3772 3772 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
06-29 07:37:30.802 7275 7275 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 07:37:31.302 7275 7275 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
06-29 08:12:23.492 8163 8163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 08:12:24.387 8163 8163 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
06-29 08:36:23.588 8798 8798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 08:36:23.856 8798 8798 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
06-29 09:38:44.586 9990 9990 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 09:38:45.664 9990 9990 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
06-29 11:02:34.061 19217 19217 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 11:02:34.963 19217 19217 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
06-29 11:08:46.197 19555 19555 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 11:08:46.475 19555 19555 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
06-29 11:15:25.923 19865 19865 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 11:15:26.195 19865 19865 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
06-29 11:28:00.007 20486 20486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 11:28:00.334 20486 20486 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
06-29 11:33:17.379 20944 20944 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 11:33:17.646 20944 20944 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
06-29 11:41:55.440 21796 21796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 11:41:55.711 21796 21796 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
06-29 12:04:23.393 22398 22398 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 12:04:23.743 22398 22398 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
06-29 13:44:23.673 24293 24293 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 13:44:25.394 24293 24293 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
06-29 13:55:54.395 25181 25181 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 15:02:40.440 3479 3479 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 15:02:41.443 3479 3479 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
06-29 16:03:34.473 7355 7355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 16:03:35.520 7355 7355 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.
06-29 16:03:38.892 7355 7555 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-29 16:03:38.892 7355 7555 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-29 16:03:38.892 7355 7555 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-29 17:06:11.784 8815 8815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 17:06:13.222 8815 8815 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
06-29 18:26:11.637 10212 10212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 18:26:13.115 10212 10212 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
06-29 19:02:56.500 18100 18100 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 19:02:57.230 18100 18100 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
06-29 19:33:53.658 18606 18606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 19:33:54.772 18606 18606 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
06-29 20:36:11.747 19951 19951 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 20:36:13.544 19951 19951 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
06-29 22:40:23.586 21393 21393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 22:40:25.472 21393 21393 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.
06-29 22:40:27.291 21393 21393 W com.mbwhatsapp: type=1400 audit(0.0:432282): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-30 01:00:20.257 15940 15940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 01:00:21.553 15940 15940 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.
06-30 01:00:25.095 15940 16274 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-30 01:00:25.095 15940 16274 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-30 01:00:25.095 15940 16274 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-30 01:01:29.718 16911 16911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 01:01:30.697 16911 16911 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
06-30 02:03:06.736 23070 23070 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 02:03:07.727 23070 23070 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
06-30 02:05:07.347 23227 23227 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 02:05:07.643 23227 23227 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
06-30 02:08:08.396 23461 23461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 02:08:08.753 23461 23461 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
06-30 03:02:43.430 30630 30630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 03:02:48.117 30630 30630 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
06-30 03:04:31.223 30906 30906 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 03:04:31.585 30906 30906 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
06-30 03:07:14.584 31132 31132 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 03:07:14.889 31132 31132 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
06-30 04:03:06.499 2529 2529 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 04:03:07.122 2529 2529 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
06-30 04:13:28.420 3195 3195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 04:13:28.685 3195 3195 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
06-30 05:02:24.811 6357 6357 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 05:02:25.409 6357 6357 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.
06-30 05:02:26.454 6357 6407 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-30 05:02:26.454 6357 6407 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-30 05:02:26.454 6357 6407 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-30 05:06:35.969 6598 6598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 05:06:36.271 6598 6598 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
06-30 06:02:44.303 10638 10638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 06:02:45.019 10638 10638 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
06-30 06:05:45.313 10935 10935 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 06:05:45.625 10935 10935 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
06-30 06:08:46.315 11167 11167 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 06:08:46.632 11167 11167 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
06-30 07:02:24.767 15906 15906 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 07:02:25.460 15906 15906 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.
06-30 07:02:26.924 15906 15957 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-30 07:02:26.924 15906 15957 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-30 07:02:26.924 15906 15957 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-30 07:04:18.131 16085 16085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 07:04:18.441 16085 16085 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
06-30 08:03:53.640 19672 19672 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 08:03:54.284 19672 19672 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.
06-30 08:03:55.855 19672 19746 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-30 08:03:55.855 19672 19746 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-30 08:03:55.855 19672 19746 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-30 08:18:35.067 20548 20548 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 08:18:35.704 20548 20548 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
06-30 09:08:23.573 23126 23126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 09:08:24.425 23126 23126 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
06-30 09:32:22.427 23689 23689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 09:32:22.807 23689 23689 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
06-30 10:48:36.887 24725 24725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 10:48:37.938 24725 24725 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
06-30 12:03:08.405 5416 5416 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 12:03:08.988 5416 5416 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.
06-30 12:03:10.118 5416 5473 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-30 12:03:10.118 5416 5473 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-30 12:03:10.118 5416 5473 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-30 13:20:35.527 14978 14978 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 13:20:39.157 14978 14978 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.
06-30 13:20:41.486 14978 15404 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
06-30 13:20:41.486 14978 15404 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
06-30 13:20:41.486 14978 15404 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
06-30 14:11:38.048 20495 20495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 14:11:38.660 20495 20495 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
06-30 15:03:45.334 7449 7449 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 15:03:46.050 7449 7449 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
06-30 15:10:16.360 8043 8043 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 15:10:16.925 8043 8043 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
06-30 15:24:22.436 8647 8647 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 15:24:22.961 8647 8647 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
06-30 17:05:33.184 12817 12817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 17:05:36.722 12817 12817 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.
06-30 17:05:38.945 12817 12817 W com.mbwhatsapp: type=1400 audit(0.0:720535): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
06-30 19:07:39.706 14124 14124 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 19:07:43.989 14124 14124 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.
06-30 19:07:49.108 14124 14124 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
06-30 19:07:49.109 14124 14124 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
06-30 23:10:45.303 20442 20442 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-30 23:10:51.267 20442 20442 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
07-01 01:48:24.643 10013 10013 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 01:48:27.160 10013 10013 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
07-01 03:02:56.640 13351 13351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 03:02:57.390 13351 13351 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
07-01 04:50:04.721 16464 16464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 04:50:06.096 16464 16464 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
07-01 04:58:51.379 16844 16844 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 04:58:51.671 16844 16844 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
07-01 05:10:15.669 17747 17747 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 05:10:16.782 17747 17747 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
07-01 06:08:06.619 19900 19900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 06:08:07.406 19900 19900 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
07-01 07:05:22.085 29080 29080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 07:05:23.081 29080 29080 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
07-01 07:08:20.382 29761 29761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 07:08:21.197 29761 29761 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
07-01 07:16:23.415 29970 29970 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 07:16:23.717 29970 29970 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
07-01 08:08:23.411 30446 30446 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 08:08:23.747 30446 30446 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
07-01 09:08:45.901 32516 32516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 09:08:48.047 32516 32516 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
07-01 09:11:41.904 1920 1920 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 09:11:42.391 1920 1920 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
07-01 09:15:05.315 4184 4184 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 09:15:05.955 4184 4184 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
07-01 10:09:38.441 14005 14005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 10:09:39.301 14005 14005 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.
07-01 10:09:41.048 14005 14113 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-01 10:09:41.048 14005 14113 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-01 10:09:41.048 14005 14113 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-01 10:27:40.460 16177 16177 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 10:27:41.162 16177 16177 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
07-01 11:36:25.501 17133 17133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 11:36:27.737 17133 17133 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.
07-01 11:36:33.693 17133 17133 W com.mbwhatsapp: type=1400 audit(0.0:760122): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-01 13:04:53.884 19618 19618 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 13:04:54.540 19618 19618 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
07-01 13:14:57.011 22114 22114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 13:14:57.809 22114 22114 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
07-01 13:26:11.922 23893 23893 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 13:26:12.501 23893 23893 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
07-01 13:47:15.413 26226 26226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 13:47:15.953 26226 26226 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
07-01 14:07:37.623 26889 26889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 14:07:37.994 26889 26889 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
07-01 15:04:13.868 29391 29391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 15:04:15.037 29391 29391 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
07-01 15:07:37.741 30859 30859 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 15:07:38.140 30859 30859 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
07-01 15:48:23.448 8705 8705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 15:48:24.105 8705 8705 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
07-01 16:51:03.998 25470 25470 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 16:51:04.843 25470 25470 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
07-01 17:36:43.913 3886 3886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 17:36:46.326 3886 3886 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-01 17:36:46.327 3886 3886 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-01 17:36:46.327 3886 3886 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-01 17:36:46.327 3886 3886 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-01 17:36:46.327 3886 3886 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-01 17:36:46.327 3886 3886 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-01 17:36:46.327 3886 3886 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-01 17:36:46.327 3886 3886 W System.err: at
java.lang.Class.newInstance(Native Method)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-01 17:36:46.328 3886 3886 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-01 17:36:46.328 3886 3886 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-01 17:36:46.328 3886 3886 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-01 17:36:46.328 3886 3886 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-01 17:36:46.328 3886 3886 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-01 17:36:46.328 3886 3886 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-01 17:36:46.328 3886 3886 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-01 17:36:46.328 3886 3886 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-01 17:36:46.966 3886 3886 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.
07-01 17:36:49.762 3886 3886 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-01 17:36:49.763 3886 3886 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
07-01 17:36:50.002 3886 3886 W com.mbwhatsapp: type=1400 audit(0.0:1162): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-01 17:36:50.049 3886 3886 W com.mbwhatsapp: type=1400 audit(0.0:1163): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-01 17:36:50.079 3886 3886 W com.mbwhatsapp: type=1400 audit(0.0:1164): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-01 17:36:50.472 3886 3886 W com.mbwhatsapp: type=1400 audit(0.0:1165): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-01 17:36:50.722 3886 3886 W com.mbwhatsapp: type=1400 audit(0.0:1166): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-01 17:36:51.622 3886 3894 W com.mbwhatsapp: Suspending all threads took:
11.131ms
07-01 17:36:51.637 3886 4393 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-01 17:36:51.637 3886 4393 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-01 17:36:51.637 3886 4393 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-01 17:36:55.242 3886 4445 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-01 17:36:55.242 3886 4445 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-01 17:37:26.271 6113 6113 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 17:37:27.569 6113 6113 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-01 17:37:27.570 6113 6113 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.Class.newInstance(Native Method)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-01 17:37:27.570 6113 6113 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-01 17:37:27.570 6113 6113 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-01 17:37:27.570 6113 6113 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-01 17:37:27.570 6113 6113 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-01 17:37:27.570 6113 6113 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-01 17:37:27.570 6113 6113 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-01 17:37:27.570 6113 6113 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-01 17:37:27.570 6113 6113 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-01 17:37:30.760 6113 6113 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.
07-01 17:37:33.040 6113 6113 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-01 17:37:33.041 6113 6113 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-01 17:37:33.380 6113 6121 W com.mbwhatsapp: Suspending all threads took:
8.366ms
07-01 17:37:34.784 6113 6389 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-01 17:37:34.784 6113 6389 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-01 17:37:34.784 6113 6389 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-01 17:37:39.488 6113 6425 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-01 17:37:39.494 6113 6425 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-01 18:03:17.535 20079 20079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 18:03:20.460 20079 20079 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.
07-01 18:03:24.658 20079 20079 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-01 18:03:24.659 20079 20079 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-01 18:19:31.029 27817 27817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 18:19:32.799 27817 27817 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
07-01 19:02:38.107 15296 15296 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 19:02:39.088 15296 15296 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
07-01 20:20:17.430 22584 22584 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 20:20:18.527 22584 22584 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
07-01 21:03:57.037 25522 25522 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 21:03:58.246 25522 25522 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
07-01 21:12:11.113 28297 28297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 21:12:11.812 28297 28297 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
07-01 22:02:33.801 8458 8458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 22:02:34.719 8458 8458 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
07-01 23:05:05.416 25226 25226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-01 23:05:06.486 25226 25226 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.
07-01 23:05:08.253 25226 25277 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-01 23:05:08.253 25226 25277 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-01 23:05:08.253 25226 25277 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-02 00:02:25.733 31336 31336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 00:02:26.541 31336 31336 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
07-02 00:06:14.644 32306 32306 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 00:06:15.679 32306 32306 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
07-02 00:13:53.305 3822 3822 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 00:13:54.532 3822 3822 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.
07-02 00:13:55.892 3822 3901 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-02 00:13:55.892 3822 3901 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-02 00:13:55.892 3822 3901 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-02 06:35:27.051 10900 10900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 06:35:27.834 10900 10900 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
07-02 08:08:21.914 18264 18264 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 08:08:22.791 18264 18264 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
07-02 09:24:22.028 19484 19484 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 09:24:24.290 19484 19484 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
07-02 09:25:18.469 19788 19788 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 09:25:18.749 19788 19788 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
07-02 09:30:19.763 20868 20868 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 11:32:22.071 21593 21593 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-02 11:32:22.663 21593 21593 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
07-04 01:07:28.675 26530 26530 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 01:07:31.362 26530 26530 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
07-04 01:10:36.988 29871 29871 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 01:10:37.525 29871 29871 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
07-04 01:12:34.539 30349 30349 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 01:12:34.825 30349 30349 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
07-04 03:03:00.981 7165 7165 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 03:03:01.613 7165 7165 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.
07-04 03:03:02.554 7165 7219 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-04 03:03:02.554 7165 7219 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-04 03:03:02.554 7165 7219 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-04 04:02:35.187 9016 9016 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 04:02:35.571 9016 9016 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
07-04 05:02:23.962 14619 14619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 05:02:24.355 14619 14619 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
07-04 06:02:23.340 18135 18135 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 06:02:23.687 18135 18135 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
07-04 07:02:18.862 20061 20061 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 07:02:19.086 20061 20061 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
07-04 20:24:49.267 5261 5261 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 20:24:51.733 5261 5261 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-04 20:24:51.735 5261 5261 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.Class.newInstance(Native Method)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-04 20:24:51.735 5261 5261 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-04 20:24:51.735 5261 5261 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-04 20:24:51.735 5261 5261 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-04 20:24:51.735 5261 5261 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-04 20:24:51.735 5261 5261 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-04 20:24:51.735 5261 5261 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-04 20:24:51.735 5261 5261 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-04 20:24:51.735 5261 5261 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-04 20:24:52.068 5261 5261 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.
07-04 20:24:58.398 5261 5261 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-04 20:24:58.403 5261 5261 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-04 20:25:02.215 5261 5479 W com.mbwhatsapp: Verification of void
X.2rL.A04(byte[], int, int) took 147.941ms (419.08 bytecodes/s) (1624B approximate
peak alloc)
07-04 20:25:02.215 5261 5479 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-04 20:25:02.215 5261 5479 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-04 20:25:02.215 5261 5479 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-04 20:25:06.482 5261 5532 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=9fc2b5e8-367a-48ae-9c48-fc3838e5e18a, generation=0)
07-04 20:25:21.576 5261 5493 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-04 20:25:21.576 5261 5493 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-04 20:53:23.380 22561 22561 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-04 20:53:24.157 22561 22561 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
07-05 07:57:59.934 4610 4610 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 07:58:04.764 4610 4610 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-05 07:58:04.775 4610 4610 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-05 07:58:04.775 4610 4610 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-05 07:58:04.775 4610 4610 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-05 07:58:04.775 4610 4610 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-05 07:58:04.775 4610 4610 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-05 07:58:04.775 4610 4610 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-05 07:58:04.775 4610 4610 W System.err: at
java.lang.Class.newInstance(Native Method)
07-05 07:58:04.775 4610 4610 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-05 07:58:04.775 4610 4610 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-05 07:58:04.775 4610 4610 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-05 07:58:04.775 4610 4610 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-05 07:58:04.775 4610 4610 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-05 07:58:04.775 4610 4610 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-05 07:58:04.775 4610 4610 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-05 07:58:04.775 4610 4610 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-05 07:58:04.775 4610 4610 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-05 07:58:04.775 4610 4610 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-05 07:58:04.776 4610 4610 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-05 07:58:04.776 4610 4610 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-05 07:58:04.776 4610 4610 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-05 07:58:04.776 4610 4610 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-05 07:58:05.204 4610 4610 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.
07-05 07:58:07.432 4610 4610 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-05 07:58:07.433 4610 4610 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-05 07:58:08.032 4610 4610 W com.mbwhatsapp: type=1400 audit(0.0:1359): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-05 07:58:08.086 4610 4610 W com.mbwhatsapp: type=1400 audit(0.0:1360): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-05 07:58:08.202 4610 4610 W com.mbwhatsapp: type=1400 audit(0.0:1361): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-05 07:58:08.522 4610 4610 W com.mbwhatsapp: type=1400 audit(0.0:1362): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-05 07:58:10.630 4610 5041 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-05 07:58:10.630 4610 5041 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-05 07:58:10.630 4610 5041 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-05 07:58:14.896 4610 5149 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-05 07:58:14.897 4610 5149 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-05 08:03:25.687 14220 14220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 08:03:26.333 14220 14220 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.
07-05 08:03:27.266 14220 14220 W com.mbwhatsapp: type=1400 audit(0.0:9318): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-05 08:03:27.306 14220 14220 W com.mbwhatsapp: type=1400 audit(0.0:9319): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-05 08:53:10.985 23616 23616 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 08:53:13.180 23616 23616 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
07-05 09:52:41.003 4062 4062 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 09:52:43.540 4062 4062 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
07-05 10:23:00.267 9251 9251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 10:23:01.001 9251 9251 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
07-05 10:52:17.861 12642 12642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 10:52:18.495 12642 12642 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
07-05 21:05:38.471 8092 8092 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-05 21:05:41.809 8092 8092 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.
07-05 21:05:50.041 8092 8092 W com.mbwhatsapp: type=1400 audit(0.0:130162): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-05 21:05:50.107 8092 8092 W com.mbwhatsapp: type=1400 audit(0.0:130163): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-06 14:04:03.979 6200 6200 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 14:04:08.832 6200 6200 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-06 14:04:08.835 6200 6200 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-06 14:04:08.835 6200 6200 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-06 14:04:08.835 6200 6200 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-06 14:04:08.835 6200 6200 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-06 14:04:08.835 6200 6200 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-06 14:04:08.835 6200 6200 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-06 14:04:08.835 6200 6200 W System.err: at
java.lang.Class.newInstance(Native Method)
07-06 14:04:08.835 6200 6200 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-06 14:04:08.835 6200 6200 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-06 14:04:08.835 6200 6200 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-06 14:04:08.835 6200 6200 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-06 14:04:08.835 6200 6200 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-06 14:04:08.835 6200 6200 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-06 14:04:08.835 6200 6200 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-06 14:04:08.835 6200 6200 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-06 14:04:08.835 6200 6200 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-06 14:04:08.835 6200 6200 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-06 14:04:08.836 6200 6200 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-06 14:04:08.836 6200 6200 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-06 14:04:08.836 6200 6200 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-06 14:04:08.836 6200 6200 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-06 14:04:09.378 6200 6200 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.
07-06 14:04:12.198 6200 6200 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-06 14:04:12.199 6200 6200 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-06 14:04:14.157 6200 6779 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 14:04:14.157 6200 6779 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 14:04:14.157 6200 6779 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-06 14:04:14.381 6200 6211 W com.mbwhatsapp: Suspending all threads took:
8.388ms
07-06 14:04:17.051 6200 6891 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=4c2b6baf-b14f-4646-99df-4c6dafc092a3, generation=0)
07-06 14:04:18.419 6200 6211 W com.mbwhatsapp: Suspending all threads took:
15.621ms
07-06 14:09:38.838 12363 12363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 14:09:40.900 12363 12363 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
07-06 15:18:47.424 29363 29363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 15:18:48.660 29363 29363 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.
07-06 15:18:50.194 29363 29452 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 15:18:50.194 29363 29452 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 15:18:50.194 29363 29452 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-06 15:58:04.956 3708 3708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 15:58:05.803 3708 3708 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.
07-06 15:58:07.267 3708 3774 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 15:58:07.267 3708 3774 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 15:58:07.267 3708 3774 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-06 17:10:16.100 16463 16463 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 17:10:17.861 16463 16463 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.
07-06 17:10:19.360 16463 16700 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 17:10:19.360 16463 16700 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 17:10:19.360 16463 16700 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-06 17:40:19.594 22018 22018 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 17:40:20.108 22018 22018 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
07-06 21:07:47.900 4506 4506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 21:07:49.545 4506 4506 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
07-06 21:11:54.201 5601 5601 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 21:11:56.560 5601 5601 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-06 21:11:56.560 5601 5601 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-06 21:11:56.560 5601 5601 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-06 21:11:56.560 5601 5601 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-06 21:11:56.560 5601 5601 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-06 21:11:56.560 5601 5601 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-06 21:11:56.560 5601 5601 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-06 21:11:56.560 5601 5601 W System.err: at
java.lang.Class.newInstance(Native Method)
07-06 21:11:56.560 5601 5601 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-06 21:11:56.560 5601 5601 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-06 21:11:56.560 5601 5601 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-06 21:11:56.560 5601 5601 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-06 21:11:56.560 5601 5601 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-06 21:11:56.560 5601 5601 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-06 21:11:56.560 5601 5601 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-06 21:11:56.561 5601 5601 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-06 21:11:56.561 5601 5601 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-06 21:11:56.561 5601 5601 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-06 21:11:56.561 5601 5601 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-06 21:11:56.561 5601 5601 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-06 21:11:56.561 5601 5601 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-06 21:11:56.561 5601 5601 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-06 21:11:56.948 5601 5601 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.
07-06 21:12:01.898 5601 5601 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-06 21:12:01.901 5601 5601 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
07-06 21:12:02.159 5601 5601 W com.mbwhatsapp: type=1400 audit(0.0:4220): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-06 21:12:02.185 5601 5601 W com.mbwhatsapp: type=1400 audit(0.0:4221): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-06 21:12:02.269 5601 5601 W com.mbwhatsapp: type=1400 audit(0.0:4222): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-06 21:12:02.745 5601 5601 W com.mbwhatsapp: type=1400 audit(0.0:4223): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-06 21:12:03.029 5601 5601 W com.mbwhatsapp: type=1400 audit(0.0:4224): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-06 21:12:04.539 5601 6057 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 21:12:04.539 5601 6057 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 21:12:04.539 5601 6057 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-06 21:12:41.487 7602 7602 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 21:12:42.277 7602 7602 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-06 21:12:42.278 7602 7602 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.Class.newInstance(Native Method)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-06 21:12:42.278 7602 7602 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-06 21:12:42.278 7602 7602 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-06 21:12:42.278 7602 7602 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-06 21:12:42.278 7602 7602 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-06 21:12:42.278 7602 7602 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-06 21:12:42.278 7602 7602 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-06 21:12:42.278 7602 7602 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-06 21:12:42.278 7602 7602 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-06 21:12:42.399 7602 7602 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.
07-06 21:12:43.169 7602 7602 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-06 21:12:43.173 7602 7602 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-06 21:12:43.951 7602 7747 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 21:12:43.951 7602 7747 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 21:12:43.951 7602 7747 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-06 21:52:31.685 23152 23152 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-06 21:52:32.384 23152 23152 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.
07-06 21:52:33.729 23152 23203 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-06 21:52:33.729 23152 23203 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-06 21:52:33.729 23152 23203 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-07 02:30:24.237 29730 29730 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 02:30:26.016 29730 29730 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
07-07 03:04:24.128 4118 4118 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 03:04:25.530 4118 4118 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-07 03:04:25.531 4118 4118 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-07 03:04:25.532 4118 4118 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-07 03:04:25.532 4118 4118 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-07 03:04:25.532 4118 4118 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-07 03:04:25.532 4118 4118 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-07 03:04:25.532 4118 4118 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-07 03:04:25.532 4118 4118 W System.err: at
java.lang.Class.newInstance(Native Method)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-07 03:04:25.532 4118 4118 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-07 03:04:25.532 4118 4118 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-07 03:04:25.532 4118 4118 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-07 03:04:25.532 4118 4118 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-07 03:04:25.532 4118 4118 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-07 03:04:25.532 4118 4118 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-07 03:04:25.532 4118 4118 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-07 03:04:25.532 4118 4118 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-07 03:04:25.674 4118 4118 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.
07-07 03:04:28.621 4118 4118 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-07 03:04:28.627 4118 4118 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-07 10:43:26.377 4286 4286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 10:43:27.725 4286 4286 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-07 10:43:27.728 4286 4286 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-07 10:43:27.728 4286 4286 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-07 10:43:27.728 4286 4286 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-07 10:43:27.728 4286 4286 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-07 10:43:27.728 4286 4286 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-07 10:43:27.728 4286 4286 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-07 10:43:27.728 4286 4286 W System.err: at
java.lang.Class.newInstance(Native Method)
07-07 10:43:27.728 4286 4286 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-07 10:43:27.728 4286 4286 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-07 10:43:27.728 4286 4286 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-07 10:43:27.728 4286 4286 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-07 10:43:27.728 4286 4286 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-07 10:43:27.728 4286 4286 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-07 10:43:27.728 4286 4286 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-07 10:43:27.729 4286 4286 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-07 10:43:27.729 4286 4286 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-07 10:43:27.729 4286 4286 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-07 10:43:27.729 4286 4286 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-07 10:43:27.729 4286 4286 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-07 10:43:27.729 4286 4286 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-07 10:43:27.729 4286 4286 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-07 10:43:27.962 4286 4286 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.
07-07 10:43:30.895 4286 4286 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-07 10:43:30.897 4286 4286 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-07 10:43:32.620 4286 4782 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-07 10:43:32.620 4286 4782 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-07 10:43:32.620 4286 4782 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-07 10:44:18.292 6571 6571 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 10:44:20.120 6571 6571 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-07 10:44:20.121 6571 6571 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.Class.newInstance(Native Method)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-07 10:44:20.121 6571 6571 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-07 10:44:20.121 6571 6571 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-07 10:44:20.121 6571 6571 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-07 10:44:20.121 6571 6571 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-07 10:44:20.121 6571 6571 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-07 10:44:20.121 6571 6571 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-07 10:44:20.121 6571 6571 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-07 10:44:20.121 6571 6571 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-07 10:44:20.296 6571 6571 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.
07-07 10:44:22.704 6571 6571 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-07 10:44:22.705 6571 6571 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-07 10:44:27.123 6571 6852 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-07 10:44:27.123 6571 6852 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-07 10:44:27.123 6571 6852 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-07 10:49:16.501 12741 12741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 10:49:18.332 12741 12741 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.
07-07 10:49:22.843 12741 12741 W com.mbwhatsapp: type=1400 audit(0.0:3366): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-07 10:49:23.003 12741 12741 W com.mbwhatsapp: type=1400 audit(0.0:3367): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-07 11:37:53.469 23437 23437 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 11:37:54.245 23437 23437 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.
07-07 11:37:55.496 23437 23525 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-07 11:37:55.496 23437 23525 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-07 11:37:55.496 23437 23525 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-07 12:11:19.913 27390 27390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 12:11:20.721 27390 27390 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
07-07 13:38:06.745 11282 11282 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 13:38:07.387 11282 11282 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
07-07 14:04:50.230 14681 14681 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 14:04:50.713 14681 14681 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
07-07 14:37:46.672 17950 17950 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 14:37:47.422 17950 17950 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
07-07 14:55:23.379 23516 23516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-07 14:55:24.032 23516 23516 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
07-09 00:33:13.333 19614 19614 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 00:33:24.064 19614 19614 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.
07-09 00:33:28.946 19614 19614 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-09 00:33:28.949 19614 19614 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-09 01:42:31.872 8154 8154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 01:42:32.735 8154 8154 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.
07-09 01:42:34.295 8154 8154 W com.mbwhatsapp: type=1400 audit(0.0:22109): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-09 01:42:34.365 8154 8154 W com.mbwhatsapp: type=1400 audit(0.0:22110): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-09 02:37:45.413 11995 11995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 02:37:45.957 11995 11995 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
07-09 03:33:05.319 15433 15433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 03:33:05.987 15433 15433 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
07-09 04:06:02.344 18613 18613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 04:06:03.476 18613 18613 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
07-09 04:37:50.062 21523 21523 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 04:37:50.617 21523 21523 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.
07-09 04:37:51.648 21523 21523 W com.mbwhatsapp: type=1400 audit(0.0:23886): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-09 05:34:13.388 25124 25124 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-09 05:34:14.908 25124 25124 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
07-10 00:39:52.591 18343 18343 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-10 00:39:56.913 18343 18343 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
07-10 00:48:30.272 21697 21697 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-10 00:48:31.660 21697 21697 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
07-10 02:37:45.535 9345 9345 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-10 02:37:46.549 9345 9345 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
07-10 03:33:16.594 14616 14616 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-10 03:33:17.575 14616 14616 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
07-10 04:37:50.073 18847 18847 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-10 04:37:50.918 18847 18847 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
07-10 05:37:25.885 22014 22014 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-10 05:37:26.693 22014 22014 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
07-11 00:56:23.958 14337 14337 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 00:56:25.739 14337 14337 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.
07-11 00:56:28.228 14337 14337 W com.mbwhatsapp: type=1400 audit(0.0:4752): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-11 04:19:47.335 7458 7458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 04:19:49.581 7458 7458 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.
07-11 04:19:53.725 7458 7458 W com.mbwhatsapp: type=1400 audit(0.0:47127): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-11 04:19:53.865 7458 7458 W com.mbwhatsapp: type=1400 audit(0.0:47128): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-11 04:19:53.865 7458 7458 W com.mbwhatsapp: type=1400 audit(0.0:47129): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-11 04:19:53.865 7458 7458 W com.mbwhatsapp: type=1400 audit(0.0:47130): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-11 04:22:26.357 9339 9339 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 04:22:27.363 9339 9339 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
07-11 05:42:31.492 17290 17290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 05:42:32.273 17290 17290 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
07-11 06:42:22.001 20934 20934 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 06:42:22.657 20934 20934 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
07-11 09:41:37.278 16384 16384 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 09:41:41.123 16384 16384 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
07-11 11:05:51.439 26443 26443 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 11:05:53.675 26443 26443 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.
07-11 11:05:57.166 26443 26443 W com.mbwhatsapp: type=1400 audit(0.0:119728): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-11 11:05:57.183 26443 26443 W com.mbwhatsapp: type=1400 audit(0.0:119729): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-11 11:05:57.239 26443 26443 W com.mbwhatsapp: type=1400 audit(0.0:119730): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-11 12:45:03.462 14589 14589 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 12:45:05.774 14589 14589 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.
07-11 12:45:07.937 14589 14589 W com.mbwhatsapp: type=1400 audit(0.0:143715): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-11 20:47:57.220 24922 24922 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 20:48:01.912 24922 24922 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
07-11 20:48:46.249 25649 25649 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-11 20:48:52.504 25649 25649 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
07-12 08:41:26.361 4325 4325 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 08:41:30.048 4325 4325 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
07-12 09:42:29.756 15237 15237 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 09:42:30.961 15237 15237 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
07-12 09:44:29.829 15662 15662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 09:44:30.207 15662 15662 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
07-12 10:42:30.812 17930 17930 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 10:42:32.093 17930 17930 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
07-12 10:45:31.036 18336 18336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 10:45:31.410 18336 18336 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
07-12 10:54:23.845 18566 18566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 10:54:24.188 18566 18566 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
07-12 11:45:51.626 19840 19840 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 11:45:52.062 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
07-12 11:47:35.813 20212 20212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 11:47:36.118 20212 20212 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
07-12 12:42:55.731 22381 22381 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 12:42:56.895 22381 22381 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
07-12 13:42:45.630 28112 28112 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 13:42:46.582 28112 28112 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
07-12 14:42:17.721 29921 29921 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 14:42:18.589 29921 29921 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
07-12 15:42:45.654 1404 1404 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 15:42:46.485 1404 1404 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
07-12 16:42:28.595 4517 4517 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-12 16:42:29.249 4517 4517 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
07-13 03:05:43.032 15466 15466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-13 03:05:45.609 15466 15466 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.
07-13 03:05:51.210 15466 15466 W com.mbwhatsapp: type=1400 audit(0.0:644971): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-13 03:05:51.233 15466 15466 W com.mbwhatsapp: type=1400 audit(0.0:644972): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-13 04:42:15.646 30622 30622 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-13 04:42:16.333 30622 30622 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
07-13 06:55:54.191 12318 12318 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-13 06:55:54.868 12318 12318 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
07-13 10:56:26.214 3247 3247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-13 10:56:28.322 3247 3247 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
07-13 11:20:20.509 9004 9004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-13 11:20:21.842 9004 9004 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
07-15 02:28:45.984 5115 5115 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-15 02:28:48.769 5115 5115 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-15 02:28:48.775 5115 5115 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.Class.newInstance(Native Method)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-15 02:28:48.775 5115 5115 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-15 02:28:48.775 5115 5115 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-15 02:28:48.775 5115 5115 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-15 02:28:48.775 5115 5115 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-15 02:28:48.775 5115 5115 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-15 02:28:48.775 5115 5115 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-15 02:28:48.775 5115 5115 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-15 02:28:48.775 5115 5115 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-15 02:28:49.437 5115 5115 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.
07-15 02:28:54.007 5115 5123 W com.mbwhatsapp: Suspending all threads took:
26.339ms
--------- beginning of main
07-15 02:44:17.281 3910 3910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-15 02:44:20.685 3910 3910 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-15 02:44:20.685 3910 3910 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-15 02:44:20.685 3910 3910 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-15 02:44:20.686 3910 3910 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-15 02:44:20.686 3910 3910 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-15 02:44:20.686 3910 3910 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-15 02:44:20.686 3910 3910 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-15 02:44:20.686 3910 3910 W System.err: at
java.lang.Class.newInstance(Native Method)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-15 02:44:20.686 3910 3910 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-15 02:44:20.686 3910 3910 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-15 02:44:20.686 3910 3910 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-15 02:44:20.686 3910 3910 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-15 02:44:20.686 3910 3910 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-15 02:44:20.686 3910 3910 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-15 02:44:20.686 3910 3910 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-15 02:44:20.686 3910 3910 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-15 02:44:21.818 3910 3910 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.
07-15 02:44:26.489 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1248): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-15 02:44:26.215 3910 3910 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-15 02:44:26.509 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1249): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-15 02:44:26.572 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1250): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-15 02:44:27.096 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1271): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-15 02:44:27.096 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1272): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-15 02:44:27.817 3910 3925 W com.mbwhatsapp: Suspending all threads took:
11.232ms
07-15 02:44:27.096 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1273): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-15 02:44:27.099 3910 3910 W com.mbwhatsapp: type=1400 audit(0.0:1274): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
07-15 02:44:29.911 3910 4748 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-15 02:44:29.911 3910 4748 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-15 02:44:29.911 3910 4748 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-15 02:44:33.916 3910 5046 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=582fcbde-5cb5-499a-a189-ae07b6618c0d, generation=0)
07-15 09:45:18.718 28373 28373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-15 09:45:20.590 28373 28373 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.
07-15 09:45:25.105 28373 28373 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-15 09:45:25.106 28373 28373 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-15 11:27:37.068 9653 9653 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-15 11:27:38.478 9653 9653 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.
07-15 11:27:40.457 9653 9653 W com.mbwhatsapp: type=1400 audit(0.0:45625): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-15 12:04:31.998 16299 16299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-15 12:04:35.556 16299 16299 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.
07-15 12:04:42.698 16299 16299 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-15 12:04:42.699 16299 16299 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-16 01:17:48.434 15855 15855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-16 01:17:50.904 15855 15855 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
07-16 06:08:15.434 31883 31883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-16 06:08:16.912 31883 31883 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
07-16 23:44:22.330 23855 23855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-16 23:44:24.175 23855 23855 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
07-17 01:06:05.679 478 478 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 01:06:07.610 478 478 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
07-17 01:57:56.698 15496 15496 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 01:57:57.409 15496 15496 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
07-17 02:07:22.524 16333 16333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 02:07:22.797 16333 16333 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
07-17 02:12:33.629 16910 16910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 02:12:33.857 16910 16910 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
07-17 02:15:33.837 18139 18139 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 02:15:34.470 18139 18139 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
07-17 02:57:36.865 21250 21250 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 02:57:38.574 21250 21250 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
07-17 03:02:47.223 22241 22241 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 03:02:47.845 22241 22241 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
07-17 03:55:40.814 25677 25677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 03:55:41.670 25677 25677 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
07-17 03:56:40.829 25956 25956 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 03:56:41.114 25956 25956 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
07-17 03:59:28.331 26099 26099 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 03:59:28.588 26099 26099 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
07-17 04:06:23.488 26376 26376 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 04:06:23.736 26376 26376 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
07-17 04:14:33.904 26657 26657 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 04:14:34.196 26657 26657 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
07-17 04:26:32.118 26977 26977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 04:26:32.422 26977 26977 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
07-17 04:45:50.075 27500 27500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-17 04:45:50.383 27500 27500 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
07-18 01:13:51.488 4645 4645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-18 01:13:53.785 4645 4645 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
07-18 01:14:33.502 7246 7246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-18 01:14:34.804 7246 7246 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
07-18 02:00:17.956 19464 19464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-18 02:00:18.670 19464 19464 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
07-19 01:30:54.867 7541 7541 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-19 01:30:57.024 7541 7541 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-19 01:30:57.032 7541 7541 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.Class.newInstance(Native Method)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-19 01:30:57.032 7541 7541 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-19 01:30:57.032 7541 7541 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-19 01:30:57.032 7541 7541 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-19 01:30:57.032 7541 7541 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-19 01:30:57.032 7541 7541 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-19 01:30:57.032 7541 7541 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-19 01:30:57.032 7541 7541 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-19 01:30:57.032 7541 7541 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-19 01:30:57.541 7541 7541 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.
07-19 01:31:02.419 7541 7541 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-19 01:31:02.420 7541 7541 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-19 01:31:04.404 7541 7897 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-19 01:31:04.404 7541 7897 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-19 01:31:04.404 7541 7897 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-19 01:31:05.499 7541 8002 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=9ec0cb33-4c20-4852-8c04-78cbfd8b2a3e, generation=0)
07-19 01:31:05.502 7541 8002 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=9ec0cb33-4c20-4852-8c04-78cbfd8b2a3e, generation=0)
07-19 01:31:05.698 7541 8012 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-19 01:31:05.699 7541 8012 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-19 02:00:21.640 19284 19284 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-19 02:00:22.325 19284 19284 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.
07-19 02:00:23.568 19284 19331 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-19 02:00:23.568 19284 19331 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-19 02:00:23.568 19284 19331 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-19 02:36:11.794 26364 26364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-19 02:36:12.546 26364 26364 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
07-19 14:48:54.378 13905 13905 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-19 14:48:57.928 13905 13905 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.
07-19 14:49:01.116 13905 13905 W com.mbwhatsapp: type=1400 audit(0.0:3620): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-20 08:24:40.734 14738 14738 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-20 08:24:45.803 14738 14738 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.
07-20 08:24:48.573 14738 14738 W com.mbwhatsapp: type=1400 audit(0.0:7510): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-20 08:59:45.026 18590 18590 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-20 08:59:45.584 18590 18590 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.
07-20 08:59:47.124 18590 18651 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-20 08:59:47.124 18590 18651 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-20 08:59:47.124 18590 18651 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-20 09:59:43.655 24485 24485 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-20 09:59:44.085 24485 24485 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
07-20 10:59:44.490 30236 30236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-20 10:59:45.066 30236 30236 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
07-20 11:59:49.856 6153 6153 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-20 11:59:50.352 6153 6153 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
07-20 12:59:52.177 11082 11082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-20 12:59:52.764 11082 11082 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.
07-20 12:59:53.991 11082 11135 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-20 12:59:53.991 11082 11135 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-20 12:59:53.991 11082 11135 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-21 09:44:58.780 24146 24146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-21 09:44:59.996 24146 24146 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.
07-21 09:45:05.926 24146 24154 W com.mbwhatsapp: Suspending all threads took:
8.040ms
--------- beginning of main
07-21 11:00:30.745 7413 7413 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-21 11:00:31.648 7413 7413 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
07-21 12:00:09.055 10707 10707 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-21 12:00:09.802 10707 10707 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.
07-21 12:00:11.156 10707 10764 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-21 12:00:11.156 10707 10764 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-21 12:00:11.156 10707 10764 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-21 12:59:49.473 22508 22508 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-21 12:59:53.349 22508 22508 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
07-21 13:59:43.825 10126 10126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-21 13:59:44.621 10126 10126 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.
07-21 13:59:46.192 10126 10241 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-21 13:59:46.192 10126 10241 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-21 13:59:46.192 10126 10241 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-23 00:08:54.865 18589 18589 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 00:08:58.056 18589 18589 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
07-23 01:43:12.174 18120 18120 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 01:43:12.901 18120 18120 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
07-23 02:00:17.279 22514 22514 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 02:00:18.260 22514 22514 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
07-23 03:05:36.447 30890 30890 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 03:05:37.201 30890 30890 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
07-23 03:10:36.741 31739 31739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 03:10:37.015 31739 31739 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
07-23 04:00:00.240 6530 6530 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 04:00:01.038 6530 6530 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
07-23 04:02:00.772 6658 6658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 04:02:01.041 6658 6658 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
07-23 04:05:41.121 6802 6802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 04:05:41.475 6802 6802 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
07-23 04:08:41.290 7154 7154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 04:08:41.551 7154 7154 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
07-23 04:13:50.337 7656 7656 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 04:13:50.630 7656 7656 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
07-23 05:00:08.170 9742 9742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 05:00:08.950 9742 9742 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
07-23 05:59:45.164 14956 14956 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 05:59:45.821 14956 14956 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
07-23 06:59:43.474 18118 18118 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 06:59:44.008 18118 18118 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
07-23 07:59:43.532 22223 22223 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 07:59:43.859 22223 22223 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
07-23 09:59:59.691 2312 2312 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 10:00:00.603 2312 2312 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
07-23 13:25:43.800 30741 30741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-23 13:25:46.715 30741 30741 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.
07-23 13:25:49.400 30741 31036 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-23 13:25:49.400 30741 31036 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-23 13:25:49.400 30741 31036 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-24 02:03:45.349 4500 4500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-24 02:03:48.694 4500 4500 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.
07-24 02:03:54.191 4500 4500 W com.mbwhatsapp: type=1400 audit(0.0:591333): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-24 02:03:54.334 4500 4500 W com.mbwhatsapp: type=1400 audit(0.0:591334): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-24 12:42:08.959 32122 32122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-24 12:42:10.154 32122 32122 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.
07-24 12:42:12.781 32122 32245 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-24 12:42:12.781 32122 32245 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-24 12:42:12.781 32122 32245 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-24 14:00:30.283 13006 13006 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-24 14:00:30.995 13006 13006 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
07-24 14:02:50.470 13212 13212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-24 14:02:50.806 13212 13212 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
07-24 14:59:45.926 19163 19163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-24 14:59:46.766 19163 19163 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
07-24 15:59:49.607 22533 22533 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-24 15:59:50.223 22533 22533 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
07-25 03:56:43.736 2503 2503 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 03:56:44.972 2503 2503 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
07-25 12:52:38.399 12663 12663 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 12:52:40.574 12663 12663 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
07-25 14:03:45.537 31181 31181 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 14:03:46.113 31181 31181 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
07-25 14:05:31.839 32126 32126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 14:05:33.168 32126 32126 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
07-25 14:59:43.649 6508 6508 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 14:59:44.933 6508 6508 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
07-25 15:59:55.017 11057 11057 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 15:59:55.588 11057 11057 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
07-25 16:12:58.087 11358 11358 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 16:12:58.479 11358 11358 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
07-25 21:09:45.961 21018 21018 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 21:09:46.601 21018 21018 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
07-25 21:12:13.378 21719 21719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 21:12:13.668 21719 21719 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
07-25 22:59:44.861 17338 17338 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 22:59:45.605 17338 17338 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
07-25 23:12:58.114 17830 17830 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-25 23:12:58.897 17830 17830 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
07-26 00:08:59.198 19123 19123 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 00:08:59.999 19123 19123 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
07-26 01:12:59.921 19735 19735 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 01:13:01.646 19735 19735 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.
07-26 03:14:12.765 21437 21437 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 03:14:14.081 21437 21437 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
07-26 07:06:43.674 24745 24745 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 07:06:45.141 24745 24745 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
07-26 07:08:57.498 25780 25780 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 07:08:58.022 25780 25780 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
07-26 07:30:25.011 26927 26927 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 07:30:25.296 26927 26927 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
07-26 09:00:12.367 29207 29207 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 09:00:13.442 29207 29207 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
07-26 16:05:20.367 5817 5817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 16:05:23.913 5817 5817 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-26 16:05:23.913 5817 5817 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-26 16:05:23.913 5817 5817 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-26 16:05:23.913 5817 5817 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-26 16:05:23.913 5817 5817 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-26 16:05:23.913 5817 5817 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-26 16:05:23.913 5817 5817 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-26 16:05:23.913 5817 5817 W System.err: at
java.lang.Class.newInstance(Native Method)
07-26 16:05:23.913 5817 5817 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-26 16:05:23.913 5817 5817 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-26 16:05:23.913 5817 5817 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-26 16:05:23.913 5817 5817 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-26 16:05:23.913 5817 5817 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-26 16:05:23.913 5817 5817 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-26 16:05:23.913 5817 5817 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-26 16:05:23.914 5817 5817 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-26 16:05:23.914 5817 5817 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-26 16:05:23.914 5817 5817 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-26 16:05:23.914 5817 5817 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-26 16:05:23.914 5817 5817 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-26 16:05:23.914 5817 5817 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-26 16:05:23.914 5817 5817 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-26 16:05:27.723 5817 5817 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.
07-26 16:05:32.225 5817 5817 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-26 16:05:33.012 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1593): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-26 16:05:33.085 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1594): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-26 16:05:33.199 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1595): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-26 16:05:34.642 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1615): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-26 16:05:35.565 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1616): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-26 16:05:35.565 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1617): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-26 16:05:35.565 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1618): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-26 16:05:35.565 5817 5817 W com.mbwhatsapp: type=1400 audit(0.0:1619): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
07-26 16:05:37.834 5817 6472 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 16:05:37.834 5817 6472 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 16:05:37.834 5817 6472 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-26 16:05:38.792 5817 5825 W com.mbwhatsapp: Suspending all threads took:
8.800ms
07-26 16:05:43.308 5817 5825 W com.mbwhatsapp: Suspending all threads took:
14.748ms
07-26 16:05:43.424 5817 6668 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=d68bb438-92b1-479b-9d14-d6d361c64eda, generation=0)
07-26 16:05:44.758 5817 6715 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-26 16:05:44.759 5817 6715 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-26 16:12:19.357 13979 13979 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 16:12:20.286 13979 13979 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.
07-26 16:12:21.776 13979 13979 W com.mbwhatsapp: type=1400 audit(0.0:10690): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-26 16:59:50.624 19061 19061 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 16:59:51.473 19061 19061 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
07-26 17:59:15.406 26066 26066 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 17:59:16.477 26066 26066 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
07-26 19:00:02.041 6220 6220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 19:00:02.863 6220 6220 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.
07-26 19:00:04.142 6220 6274 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 19:00:04.142 6220 6274 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 19:00:04.142 6220 6274 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-26 19:59:25.517 17897 17897 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 19:59:26.430 17897 17897 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.
07-26 19:59:27.806 17897 17945 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 19:59:27.806 17897 17945 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 19:59:27.806 17897 17945 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-26 20:11:00.582 19570 19570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 20:11:01.247 19570 19570 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.
07-26 20:11:02.225 19570 19653 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 20:11:02.225 19570 19653 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 20:11:02.225 19570 19653 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-26 20:14:01.800 20573 20573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 20:14:02.545 20573 20573 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
07-26 20:17:56.244 21252 21252 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 20:17:56.764 21252 21252 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
07-26 20:59:19.170 26096 26096 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 20:59:19.849 26096 26096 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.
07-26 20:59:20.871 26096 26152 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 20:59:20.871 26096 26152 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 20:59:20.871 26096 26152 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-26 21:07:56.986 26344 26344 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 21:07:58.450 26344 26344 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
07-26 21:59:26.124 7071 7071 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 21:59:27.145 7071 7071 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.
07-26 21:59:28.953 7071 7136 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 21:59:28.953 7071 7136 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 21:59:28.953 7071 7136 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-26 23:02:52.586 18405 18405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 23:02:53.188 18405 18405 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.
07-26 23:02:54.593 18405 18456 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-26 23:02:54.593 18405 18456 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-26 23:02:54.593 18405 18456 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-26 23:20:24.652 18761 18761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-26 23:20:24.923 18761 18761 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
07-27 00:53:28.033 20033 20033 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 00:53:29.382 20033 20033 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
07-27 02:56:24.809 21114 21114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 02:56:26.710 21114 21114 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
07-27 10:25:51.782 4800 4800 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 10:25:54.297 4800 4800 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-27 10:25:54.298 4800 4800 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.Class.newInstance(Native Method)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-27 10:25:54.298 4800 4800 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-27 10:25:54.298 4800 4800 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-27 10:25:54.298 4800 4800 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-27 10:25:54.298 4800 4800 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-27 10:25:54.298 4800 4800 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-27 10:25:54.298 4800 4800 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-27 10:25:54.298 4800 4800 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-27 10:25:54.298 4800 4800 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-27 10:25:54.641 4800 4800 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.
07-27 10:25:56.175 4800 4800 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-27 10:25:56.177 4800 4800 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
07-27 10:25:58.751 4800 5047 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-27 10:25:58.751 4800 5047 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-27 10:25:58.751 4800 5047 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-27 10:25:59.200 4800 4812 W com.mbwhatsapp: Suspending all threads took:
8.797ms
07-27 10:26:04.912 4800 5192 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
07-27 10:26:04.913 4800 5192 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
07-27 10:27:34.205 4800 4833 W FastPrintWriter: Write failure
07-27 10:27:34.205 4800 4833 W FastPrintWriter: java.io.IOException: write
failed: EPIPE (Broken pipe)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.IoBridge.write(IoBridge.java:654)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
java.io.FileOutputStream.write(FileOutputStream.java:401)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.flushBytesLocked(FastPrintWriter.java:354
)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.flushLocked(FastPrintWriter.java:377)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.appendLocked(FastPrintWriter.java:322)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.print(FastPrintWriter.java:499)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
java.io.PrintWriter.println(PrintWriter.java:739)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.util.PrintWriterPrinter.println(PrintWriterPrinter.java:38)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.util.PrefixPrinter.println(PrefixPrinter.java:48)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteConnection$PreparedStatementCache.dump(SQLiteConnecti
on.java:1494)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteConnection.dumpUnsafe(SQLiteConnection.java:1298)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteConnection.dump(SQLiteConnection.java:1270)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteConnectionPool.dump(SQLiteConnectionPool.java:1149)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteDatabase.dump(SQLiteDatabase.java:2338)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteDatabase.dumpAll(SQLiteDatabase.java:2321)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.database.sqlite.SQLiteDebug.dump(SQLiteDebug.java:218)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.dumpDatabaseInfo(ActivityThread.java:1
761)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.dumpDbInfo(ActivityThread.java:1792)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.app.IApplicationThread$Stub.onTransact(IApplicationThread.java:1314)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.onTransact(ActivityThread.java:1970)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.os.Binder.execTransactInternal(Binder.java:1184)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
android.os.Binder.execTransact(Binder.java:1143)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: Caused by:
android.system.ErrnoException: write failed: EPIPE (Broken pipe)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.Linux.writeBytes(Native Method)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.Linux.write(Linux.java:296)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.ForwardingOs.write(ForwardingOs.java:951)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.BlockGuardOs.write(BlockGuardOs.java:447)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.ForwardingOs.write(ForwardingOs.java:951)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: at
libcore.io.IoBridge.write(IoBridge.java:649)
07-27 10:27:34.205 4800 4833 W FastPrintWriter: ... 21 more
07-27 11:20:09.370 19903 19903 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 11:20:10.054 19903 19903 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.
07-27 11:20:11.061 19903 19903 W com.mbwhatsapp: type=1400 audit(0.0:22896): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-27 11:20:11.081 19903 19903 W com.mbwhatsapp: type=1400 audit(0.0:22897): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-27 11:20:53.950 20371 20371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 11:20:54.231 20371 20371 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
07-27 18:53:01.807 5795 5795 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 18:53:05.483 5795 5795 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
07-27 19:02:15.647 12558 12558 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:02:16.452 12558 12558 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
07-27 19:04:16.516 13536 13536 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:04:17.098 13536 13536 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
07-27 19:07:40.126 14215 14215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:07:40.571 14215 14215 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
07-27 19:10:44.880 14947 14947 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:10:45.377 14947 14947 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
07-27 19:19:42.299 16756 16756 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:19:44.791 16756 16756 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
07-27 19:40:23.814 20444 20444 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:40:25.017 20444 20444 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
07-27 19:58:10.188 26565 26565 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 19:58:11.090 26565 26565 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
07-27 20:34:36.353 7830 7830 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 20:34:39.267 7830 7830 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
07-27 20:37:08.781 8308 8308 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 20:37:09.113 8308 8308 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
07-27 21:50:02.903 29877 29877 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 21:50:03.562 29877 29877 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.
07-27 21:50:05.050 29877 29937 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-27 21:50:05.050 29877 29937 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-27 21:50:05.050 29877 29937 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-27 22:51:53.169 9669 9669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 22:51:54.002 9669 9669 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.
07-27 22:51:55.751 9669 9851 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-27 22:51:55.751 9669 9851 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-27 22:51:55.751 9669 9851 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-27 23:52:27.964 14726 14726 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-27 23:52:28.596 14726 14726 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
07-28 00:37:07.046 17171 17171 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 00:37:07.621 17171 17171 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.
07-28 00:37:08.653 17171 17229 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 00:37:08.653 17171 17229 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 00:37:08.653 17171 17229 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-28 01:37:23.441 20465 20465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 01:37:23.996 20465 20465 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.
07-28 01:37:24.966 20465 20516 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 01:37:24.966 20465 20516 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 01:37:24.966 20465 20516 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-28 02:37:08.110 23165 23165 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 02:37:08.717 23165 23165 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.
07-28 02:37:09.699 23165 23229 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 02:37:09.699 23165 23229 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 02:37:09.699 23165 23229 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-28 03:37:34.717 25908 25908 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 03:37:35.295 25908 25908 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.
07-28 03:37:36.381 25908 25959 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 03:37:36.381 25908 25959 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 03:37:36.381 25908 25959 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-28 03:52:41.988 26714 26714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 03:52:42.222 26714 26714 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
07-28 04:37:08.177 28324 28324 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 04:37:08.442 28324 28324 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
07-28 05:37:29.410 30995 30995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 05:37:30.675 30995 30995 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
07-28 06:37:24.843 3154 3154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 06:37:25.259 3154 3154 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.
07-28 06:37:26.305 3154 3205 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 06:37:26.305 3154 3205 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 06:37:26.305 3154 3205 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-28 07:38:09.427 6459 6459 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 07:38:10.501 6459 6459 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
07-28 08:38:06.497 8313 8313 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 08:38:07.153 8313 8313 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.
07-28 08:51:44.147 9445 9445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 08:51:45.074 9445 9445 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
07-28 11:19:35.014 6364 6364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 11:19:35.986 6364 6364 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
07-28 12:04:13.298 17632 17632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 12:04:14.178 17632 17632 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
07-28 13:04:03.591 7901 7901 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 13:04:04.413 7901 7901 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
07-28 13:04:04.414 7901 7901 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.Class.newInstance(Native Method)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
07-28 13:04:04.414 7901 7901 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
07-28 13:04:04.414 7901 7901 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
07-28 13:04:04.414 7901 7901 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
07-28 13:04:04.414 7901 7901 W System.err: at
android.os.Looper.loop(Looper.java:334)
07-28 13:04:04.414 7901 7901 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
07-28 13:04:04.414 7901 7901 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
07-28 13:04:04.414 7901 7901 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
07-28 13:04:04.414 7901 7901 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
07-28 13:04:04.663 7901 7901 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.
07-28 13:04:05.719 7901 7901 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
07-28 13:04:05.720 7901 7901 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
07-28 13:04:05.828 7901 7901 W com.mbwhatsapp: type=1400 audit(0.0:2093): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-28 13:04:05.838 7901 7901 W com.mbwhatsapp: type=1400 audit(0.0:2094): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-28 13:04:05.852 7901 7901 W com.mbwhatsapp: type=1400 audit(0.0:2095): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-28 13:04:06.235 7901 8049 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 13:04:06.235 7901 8049 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 13:04:06.235 7901 8049 W com.mbwhatsapp: and incorrect proguard
optimizations.
07-28 13:04:06.961 7901 8115 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=9b5dcb85-36b5-4224-b3e3-791cf265cd1b, generation=0)
07-28 13:04:06.964 7901 8064 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=9b5dcb85-36b5-4224-b3e3-791cf265cd1b, generation=0)
07-28 13:05:10.267 10113 10113 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 13:05:11.205 10113 10113 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
07-28 14:04:04.002 18009 18009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 14:04:04.640 18009 18009 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.
07-28 14:04:05.985 18009 18059 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-28 14:04:05.985 18009 18059 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-28 14:04:05.985 18009 18059 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-28 19:05:54.018 31314 31314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 19:05:56.325 31314 31314 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.
07-28 19:06:02.560 31314 31314 W com.mbwhatsapp: type=1400 audit(0.0:20930): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-28 19:06:02.730 31314 31314 W com.mbwhatsapp: type=1400 audit(0.0:20931): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-28 19:06:02.734 31314 31314 W com.mbwhatsapp: type=1400 audit(0.0:20932): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-28 19:06:02.734 31314 31314 W com.mbwhatsapp: type=1400 audit(0.0:20933): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-28 19:06:02.734 31314 31314 W com.mbwhatsapp: type=1400 audit(0.0:20934): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
07-28 23:11:49.116 4662 4662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-28 23:11:50.678 4662 4662 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.
07-28 23:11:52.631 4662 4662 W com.mbwhatsapp: type=1400 audit(0.0:21676): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-29 12:13:11.274 10852 10852 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 12:13:12.207 10852 10852 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.
07-29 12:13:14.422 10852 10852 W com.mbwhatsapp: type=1400 audit(0.0:11419): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-29 12:13:14.508 10852 10852 W com.mbwhatsapp: type=1400 audit(0.0:11420): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-29 14:08:10.140 22594 22594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 14:08:11.213 22594 22594 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.
07-29 14:08:12.949 22594 22594 W com.mbwhatsapp: type=1400 audit(0.0:40644): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-29 14:08:12.986 22594 22594 W com.mbwhatsapp: type=1400 audit(0.0:40645): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-29 14:08:22.378 22892 22892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 14:08:22.696 22892 22892 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
07-29 15:08:16.965 8147 8147 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 15:08:17.816 8147 8147 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
07-29 15:19:01.646 8385 8385 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 15:19:01.946 8385 8385 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
07-29 15:38:38.066 8787 8787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 15:38:38.317 8787 8787 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
07-29 15:59:57.029 9046 9046 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 15:59:57.314 9046 9046 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
07-29 17:00:19.182 9445 9445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 17:00:19.932 9445 9445 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
07-29 19:08:08.079 13739 13739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 19:08:09.514 13739 13739 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
07-29 19:10:35.633 15314 15314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 19:10:36.139 15314 15314 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
07-29 23:05:04.949 18598 18598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:05:06.949 18598 18598 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
07-29 23:07:16.338 20514 20514 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:07:16.873 20514 20514 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
07-29 23:10:47.420 20679 20679 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:10:47.657 20679 20679 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
07-29 23:13:48.491 21544 21544 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:13:48.765 21544 21544 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
07-29 23:18:31.869 22263 22263 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:18:32.143 22263 22263 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
07-29 23:27:37.816 24411 24411 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:27:38.096 24411 24411 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
07-29 23:39:24.102 27770 27770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:39:24.408 27770 27770 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
07-29 23:56:20.013 32187 32187 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:56:20.527 32187 32187 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
07-29 23:56:59.744 32300 32300 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-29 23:57:00.035 32300 32300 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
07-30 00:08:38.757 4354 4354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 00:08:39.708 4354 4354 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
07-30 01:08:14.071 14731 14731 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:08:14.665 14731 14731 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.
07-30 01:08:16.116 14731 14897 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-30 01:08:16.116 14731 14897 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-30 01:08:16.116 14731 14897 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-30 01:10:38.860 15392 15392 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:10:39.347 15392 15392 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
07-30 01:18:12.007 17154 17154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:18:15.038 17154 17154 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.
07-30 01:18:16.052 17154 17154 W com.mbwhatsapp: type=1400 audit(0.0:5542): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-30 01:28:38.946 20548 20548 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:28:39.491 20548 20548 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
07-30 01:29:18.888 21283 21283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:29:19.167 21283 21283 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
07-30 01:41:20.416 23178 23178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:41:20.729 23178 23178 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
07-30 01:46:58.562 23300 23300 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 01:46:58.848 23300 23300 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
07-30 02:15:01.015 27539 27539 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 02:15:02.517 27539 27539 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
07-30 02:36:16.565 28816 28816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 02:36:17.016 28816 28816 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
07-30 03:30:23.308 30941 30941 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 03:30:24.052 30941 30941 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
07-30 12:06:35.486 30240 30240 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 12:06:38.004 30240 30240 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.
07-30 12:06:39.987 30240 30240 W com.mbwhatsapp: type=1400 audit(0.0:21661): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
07-30 12:06:40.000 30240 30240 W com.mbwhatsapp: type=1400 audit(0.0:21662): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-30 13:08:05.714 17408 17408 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 13:08:06.476 17408 17408 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
07-30 14:08:04.652 27630 27630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 14:08:05.756 27630 27630 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
07-30 14:09:27.187 27954 27954 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 14:09:27.523 27954 27954 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
07-30 15:20:46.596 6114 6114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 15:20:47.448 6114 6114 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
07-30 16:54:52.716 8051 8051 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 16:54:53.299 8051 8051 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
07-30 19:00:47.044 8887 8887 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 19:00:47.441 8887 8887 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
07-30 23:10:15.632 13355 13355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-30 23:10:16.609 13355 13355 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
07-31 00:08:42.382 24010 24010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 00:08:43.269 24010 24010 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
07-31 01:14:16.331 14936 14936 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 01:14:18.361 14936 14936 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
07-31 02:08:05.310 26716 26716 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 02:08:05.987 26716 26716 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
07-31 11:10:05.185 799 799 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 11:10:06.342 799 799 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
07-31 12:08:06.315 9542 9542 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 12:08:07.908 9542 9542 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
07-31 12:08:47.026 9865 9865 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 12:08:47.537 9865 9865 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
07-31 12:11:52.629 10972 10972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 12:11:53.376 10972 10972 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
07-31 13:08:20.512 17205 17205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 13:08:21.603 17205 17205 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.
07-31 13:08:24.185 17205 17256 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-31 13:08:24.185 17205 17256 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-31 13:08:24.185 17205 17256 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-31 14:08:46.526 22477 22477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 14:08:47.147 22477 22477 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.
07-31 14:08:48.503 22477 22528 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
07-31 14:08:48.503 22477 22528 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
07-31 14:08:48.503 22477 22528 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
07-31 14:22:27.328 23623 23623 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 14:22:27.699 23623 23623 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
07-31 14:25:01.145 24989 24989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 14:25:04.317 24989 24989 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
07-31 14:29:34.671 26104 26104 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 14:29:35.713 26104 26104 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
07-31 15:08:46.455 4130 4130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 15:08:47.307 4130 4130 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
07-31 17:04:17.693 6630 6630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 17:04:18.855 6630 6630 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
07-31 19:05:29.042 8868 8868 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 19:05:29.772 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.
07-31 19:05:33.614 8868 8868 W com.mbwhatsapp: type=1400 audit(0.0:171657): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
07-31 23:08:46.784 12607 12607 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
07-31 23:08:48.002 12607 12607 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.
08-01 00:14:03.769 30769 30769 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 00:14:04.398 30769 30769 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
08-01 00:32:46.585 32227 32227 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 00:32:47.353 32227 32227 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.
08-01 00:32:48.486 32227 32295 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-01 00:32:48.486 32227 32295 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-01 00:32:48.486 32227 32295 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-01 01:11:01.757 1119 1119 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 01:11:03.648 1119 1119 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
08-01 02:24:50.391 7686 7686 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 02:24:53.500 7686 7686 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
08-01 02:25:53.356 9819 9819 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 02:25:54.482 9819 9819 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
08-01 02:25:59.815 10090 10090 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 02:26:01.810 10090 10090 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
08-01 03:08:31.804 22857 22857 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 03:08:32.570 22857 22857 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
08-01 04:08:33.953 29798 29798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 04:08:34.555 29798 29798 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
08-01 05:11:14.167 2323 2323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 05:11:14.884 2323 2323 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.
08-01 05:11:16.148 2323 2525 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-01 05:11:16.148 2323 2525 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-01 05:11:16.148 2323 2525 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-01 06:08:13.104 6215 6215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 06:08:13.743 6215 6215 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
08-01 07:10:59.258 10883 10883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 07:10:59.799 10883 10883 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.
08-01 07:11:01.304 10883 10942 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-01 07:11:01.304 10883 10942 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-01 07:11:01.304 10883 10942 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-01 07:53:56.945 14067 14067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 07:53:57.900 14067 14067 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
08-01 08:12:50.306 15350 15350 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 08:12:51.333 15350 15350 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
08-01 09:11:41.949 17974 17974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 09:11:43.197 17974 17974 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
08-01 09:15:17.620 18266 18266 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 09:15:17.957 18266 18266 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
08-01 09:18:28.949 18687 18687 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 09:18:29.375 18687 18687 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
08-01 10:09:58.675 21966 21966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 10:09:59.415 21966 21966 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.
08-01 10:10:00.733 21966 21966 W com.mbwhatsapp: type=1400 audit(0.0:57164): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-01 10:10:00.757 21966 21966 W com.mbwhatsapp: type=1400 audit(0.0:57165): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-01 10:22:37.935 23040 23040 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 10:22:38.276 23040 23040 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
08-01 10:29:25.103 25155 25155 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 10:29:26.294 25155 25155 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
08-01 11:08:14.236 28205 28205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 11:08:15.222 28205 28205 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
08-01 11:10:52.353 29649 29649 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 11:10:53.236 29649 29649 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
08-01 11:15:54.800 30437 30437 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 11:15:55.724 30437 30437 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
08-01 11:18:38.479 30881 30881 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 11:18:38.763 30881 30881 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
08-01 12:08:11.053 7966 7966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 12:08:11.943 7966 7966 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.
08-01 12:08:13.315 7966 8117 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-01 12:08:13.315 7966 8117 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-01 12:08:13.315 7966 8117 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-01 12:10:40.523 9577 9577 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 12:10:41.526 9577 9577 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
08-01 12:13:08.301 10042 10042 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 12:13:09.593 10042 10042 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
08-01 13:09:38.452 16251 16251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 13:09:39.454 16251 16251 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.
08-01 13:09:41.772 16251 16251 W com.mbwhatsapp: type=1400 audit(0.0:98025): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-01 13:17:58.095 18221 18221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 13:17:58.697 18221 18221 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
08-01 14:13:54.462 24492 24492 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 14:13:55.209 24492 24492 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
08-01 14:21:58.202 24701 24701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 14:21:58.512 24701 24701 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
08-01 15:08:07.899 30578 30578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 15:08:08.691 30578 30578 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
08-01 16:13:59.188 4620 4620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 16:14:00.631 4620 4620 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.
08-01 16:14:01.965 4620 4822 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-01 16:14:01.965 4620 4822 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-01 16:14:01.965 4620 4822 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-01 17:13:36.159 7265 7265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 17:13:36.726 7265 7265 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
08-01 18:08:18.610 11435 11435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 18:08:19.268 11435 11435 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
08-01 19:08:30.955 20241 20241 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 19:08:31.894 20241 20241 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
08-01 21:33:16.534 15615 15615 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 21:33:19.175 15615 15615 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
08-01 21:40:34.248 18974 18974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 21:40:35.474 18974 18974 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
08-01 21:41:49.426 19765 19765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 21:41:50.009 19765 19765 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
08-01 22:32:39.019 22378 22378 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 22:32:39.864 22378 22378 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
08-01 23:27:12.763 24860 24860 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 23:27:13.697 24860 24860 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
08-01 23:40:15.686 25224 25224 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-01 23:40:15.963 25224 25224 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
08-02 00:00:05.201 25554 25554 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 00:00:05.574 25554 25554 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
08-02 00:00:06.220 25554 25653 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-02 00:00:06.220 25554 25653 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-02 00:00:06.220 25554 25653 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-02 00:20:18.079 26615 26615 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 00:20:18.463 26615 26615 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
08-02 01:24:40.828 27605 27605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 01:24:41.291 27605 27605 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
08-02 03:32:39.143 30406 30406 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 03:32:40.326 30406 30406 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
08-02 10:30:42.727 4324 4324 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 10:30:44.877 4324 4324 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-02 10:30:44.878 4324 4324 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.Class.newInstance(Native Method)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-02 10:30:44.878 4324 4324 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-02 10:30:44.878 4324 4324 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-02 10:30:44.878 4324 4324 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-02 10:30:44.878 4324 4324 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-02 10:30:44.878 4324 4324 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-02 10:30:44.878 4324 4324 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-02 10:30:44.878 4324 4324 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-02 10:30:44.878 4324 4324 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-02 10:30:45.310 4324 4324 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.
08-02 10:30:47.220 4324 4324 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-02 10:30:47.220 4324 4324 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-02 10:30:50.280 4324 4942 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-02 10:30:50.280 4324 4942 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-02 10:30:50.280 4324 4942 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-02 10:30:53.009 4324 4333 W com.mbwhatsapp: Suspending all threads took:
11.351ms
08-02 10:30:54.349 4324 5210 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-02 10:30:54.349 4324 5210 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-02 10:33:04.233 10139 10139 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 10:33:05.747 10139 10139 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.
08-02 10:33:07.408 10139 10139 W com.mbwhatsapp: type=1400 audit(0.0:2420): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-02 10:35:48.285 14554 14554 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 10:35:51.286 14554 14554 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
08-02 11:25:10.024 20844 20844 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 11:25:10.847 20844 20844 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.
08-02 11:25:12.343 20844 20898 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-02 11:25:12.343 20844 20898 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-02 11:25:12.343 20844 20898 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-02 12:28:46.170 25236 25236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 12:28:47.257 25236 25236 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
08-02 13:25:34.746 29323 29323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 13:25:35.259 29323 29323 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
08-02 14:24:59.557 2533 2533 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 14:25:00.324 2533 2533 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
08-02 15:24:59.498 8083 8083 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 15:25:00.449 8083 8083 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
08-02 16:32:39.258 10391 10391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 16:32:39.645 10391 10391 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
08-02 17:24:59.466 15232 15232 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 17:25:00.427 15232 15232 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
08-02 17:26:47.378 15372 15372 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 17:26:47.900 15372 15372 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
08-02 18:24:59.485 23087 23087 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 18:25:00.503 23087 23087 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.
08-02 18:25:02.627 23087 23139 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-02 18:25:02.627 23087 23139 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-02 18:25:02.627 23087 23139 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-02 18:26:28.704 23750 23750 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 18:26:29.024 23750 23750 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
08-02 19:24:59.540 29465 29465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 19:25:00.788 29465 29465 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
08-02 19:26:53.556 29867 29867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 19:26:53.898 29867 29867 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
08-02 19:38:38.001 31527 31527 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 19:38:38.779 31527 31527 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
08-02 19:40:19.565 32595 32595 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 19:40:19.873 32595 32595 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
08-02 19:42:45.349 724 724 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 19:42:45.636 724 724 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
08-02 20:25:35.859 8783 8783 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 20:25:36.485 8783 8783 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.
08-02 20:25:37.473 8783 8847 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-02 20:25:37.473 8783 8847 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-02 20:25:37.473 8783 8847 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-02 20:36:12.681 9707 9707 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 20:36:13.377 9707 9707 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
08-02 20:37:49.024 10433 10433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 20:37:53.259 10433 10433 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
08-02 21:26:41.078 23022 23022 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 21:26:43.271 23022 23022 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
08-02 21:28:03.517 24480 24480 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 21:28:04.937 24480 24480 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
08-02 21:35:44.651 26252 26252 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 21:35:45.964 26252 26252 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
08-02 22:25:19.527 7550 7550 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 22:25:20.147 7550 7550 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
08-02 22:27:45.168 8328 8328 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 22:27:45.673 8328 8328 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
08-02 22:29:55.418 8539 8539 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 22:29:55.653 8539 8539 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
08-02 22:33:19.100 9500 9500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 22:42:13.198 9800 9800 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 22:42:14.359 9800 9800 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
08-02 23:42:14.296 12380 12380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-02 23:42:15.315 12380 12380 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
08-03 01:06:15.100 15047 15047 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 01:06:17.972 15047 15047 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.
08-03 01:06:19.836 15047 15047 W com.mbwhatsapp: type=1400 audit(0.0:99638): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-03 03:10:13.397 17218 17218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 03:10:15.001 17218 17218 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
08-03 07:08:10.309 20354 20354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 07:08:11.116 20354 20354 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
08-03 08:25:48.080 28823 28823 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 08:25:49.436 28823 28823 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
08-03 09:29:35.371 3872 3872 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 09:29:37.310 3872 3872 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
08-03 10:25:40.130 18025 18025 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 10:25:40.708 18025 18025 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
08-03 11:32:41.212 23979 23979 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 11:32:43.752 23979 23979 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
08-03 12:34:15.286 25383 25383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 12:34:17.018 25383 25383 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
08-03 13:32:25.813 26572 26572 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 13:32:26.223 26572 26572 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
08-03 14:25:19.557 32701 32701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 14:25:20.284 32701 32701 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.
08-03 14:25:21.575 32701 349 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-03 14:25:21.575 32701 349 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-03 14:25:21.575 32701 349 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-03 15:24:59.513 10694 10694 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 15:25:00.168 10694 10694 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.
08-03 15:25:01.231 10694 10740 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-03 15:25:01.231 10694 10740 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-03 15:25:01.231 10694 10740 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-03 16:30:13.193 16771 16771 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 16:30:13.878 16771 16771 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
08-03 16:37:47.977 17595 17595 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 16:37:48.473 17595 17595 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
08-03 17:34:13.148 24469 24469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 17:34:13.761 24469 24469 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
08-03 18:25:39.261 4039 4039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 18:25:40.230 4039 4039 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.
08-03 18:25:42.274 4039 4089 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-03 18:25:42.274 4039 4089 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-03 18:25:42.274 4039 4089 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-03 19:25:14.601 17286 17286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:25:15.341 17286 17286 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.
08-03 19:25:16.655 17286 17334 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-03 19:25:16.655 17286 17334 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-03 19:25:16.655 17286 17334 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-03 19:26:44.580 17467 17467 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:26:44.916 17467 17467 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
08-03 19:32:41.591 18898 18898 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:32:42.400 18898 18898 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
08-03 19:37:13.637 20034 20034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:37:14.716 20034 20034 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
08-03 19:41:49.444 21615 21615 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:41:51.916 21615 21615 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
08-03 19:52:02.370 22446 22446 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:52:03.044 22446 22446 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
08-03 19:55:00.191 23178 23178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 19:55:00.496 23178 23178 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
08-03 20:40:08.518 29253 29253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 20:40:09.193 29253 29253 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
08-03 20:54:59.512 30662 30662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 20:55:00.938 30662 30662 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
08-03 21:26:14.102 3957 3957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 21:26:14.833 3957 3957 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
08-03 22:26:13.123 17111 17111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 22:26:13.765 17111 17111 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.
08-03 22:26:14.895 17111 17167 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-03 22:26:14.895 17111 17167 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-03 22:26:14.895 17111 17167 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-03 23:34:13.170 25086 25086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-03 23:34:13.847 25086 25086 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
08-04 01:11:55.568 26647 26647 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 01:11:57.385 26647 26647 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
08-04 03:14:16.186 29420 29420 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 03:14:18.244 29420 29420 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
08-04 07:04:57.523 1246 1246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 07:04:59.403 1246 1246 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
08-04 07:05:07.784 1246 1333 W com.mbwhatsapp: Suspending all threads took:
6.971ms
08-04 07:05:08.457 1246 2500 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-04 07:05:08.457 1246 2500 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-04 07:08:30.744 4433 4433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 07:08:31.468 4433 4433 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
08-04 07:10:57.996 5760 5760 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 07:10:58.265 5760 5760 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
08-04 07:26:13.104 7425 7425 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 07:26:13.787 7425 7425 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
08-04 08:25:02.119 16140 16140 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 08:25:03.301 16140 16140 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.
08-04 08:25:05.865 16140 16208 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-04 08:25:05.865 16140 16208 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-04 08:25:05.865 16140 16208 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-04 09:24:59.514 21462 21462 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 09:25:00.854 21462 21462 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.
08-04 09:25:04.837 21462 21462 W com.mbwhatsapp: type=1400 audit(0.0:229808): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-04 09:25:04.837 21462 21462 W com.mbwhatsapp: type=1400 audit(0.0:229809): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-04 09:25:04.837 21462 21462 W com.mbwhatsapp: type=1400 audit(0.0:229810): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-04 09:36:23.183 22838 22838 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 09:36:24.105 22838 22838 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
08-04 09:40:04.549 23808 23808 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 09:40:05.654 23808 23808 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
08-04 10:29:07.131 29218 29218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 10:29:08.060 29218 29218 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
08-04 10:42:12.493 30437 30437 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 10:42:14.083 30437 30437 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
08-04 12:24:48.704 6509 6509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 12:24:49.989 6509 6509 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
08-04 13:25:40.739 9197 9197 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 13:34:13.142 9255 9255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 13:34:14.210 9255 9255 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
08-04 14:24:59.669 18234 18234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 14:25:01.437 18234 18234 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
08-04 14:38:09.300 19632 19632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 14:38:10.162 19632 19632 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.
08-04 14:38:11.843 19632 19683 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-04 14:38:11.843 19632 19683 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-04 14:38:11.843 19632 19683 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-04 14:46:13.102 19815 19815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 14:46:13.381 19815 19815 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
08-04 15:38:13.203 24631 24631 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 15:38:14.270 24631 24631 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
08-04 15:38:18.188 24631 24768 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-04 15:38:18.188 24631 24768 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-04 15:38:18.188 24631 24768 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-04 17:12:08.188 26534 26534 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 17:12:09.173 26534 26534 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
08-04 19:14:14.259 30063 30063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 19:14:15.345 30063 30063 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
08-04 23:10:45.155 4842 4842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 23:10:46.997 4842 4842 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
08-04 23:14:42.578 6034 6034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-04 23:14:43.259 6034 6034 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
08-05 00:27:22.084 10154 10154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 00:27:22.870 10154 10154 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
08-05 01:29:49.365 13572 13572 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 01:29:52.480 13572 13572 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
08-05 02:25:29.309 18234 18234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 02:25:30.308 18234 18234 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.
08-05 02:25:31.756 18234 18290 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-05 02:25:31.756 18234 18290 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-05 02:25:31.756 18234 18290 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-05 02:36:18.234 20495 20495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 02:36:19.386 20495 20495 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
08-05 02:41:19.730 21403 21403 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 02:41:23.338 21403 21403 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
08-05 02:55:16.621 22264 22264 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 02:55:17.100 22264 22264 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
08-05 03:15:33.601 23407 23407 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 03:15:34.667 23407 23407 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
08-05 03:54:10.315 25219 25219 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 03:54:11.428 25219 25219 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.
08-05 03:54:13.362 25219 25267 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-05 03:54:13.362 25219 25267 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-05 03:54:13.362 25219 25267 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-05 03:58:10.156 26056 26056 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 03:58:10.528 26056 26056 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
08-05 04:24:59.519 28107 28107 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 04:25:00.065 28107 28107 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
08-05 05:44:51.234 31332 31332 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 05:44:52.498 31332 31332 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
08-05 07:13:33.299 1075 1075 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 07:13:33.968 1075 1075 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
08-05 10:21:48.004 6773 6773 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 10:21:48.765 6773 6773 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.
08-05 10:21:49.711 6773 6773 W com.mbwhatsapp: type=1400 audit(0.0:1676): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-05 10:24:21.513 10264 10264 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 10:24:32.136 10264 10264 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
08-05 10:52:27.986 17482 17482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 10:52:29.182 17482 17482 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
08-05 12:21:02.412 26638 26638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 12:21:03.315 26638 26638 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.
08-05 12:21:04.295 26638 26638 W com.mbwhatsapp: type=1400 audit(0.0:22924): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-05 13:23:19.048 29220 29220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 13:23:20.579 29220 29220 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
08-05 14:21:44.752 9111 9111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 14:21:46.101 9111 9111 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.
08-05 14:21:47.837 9111 9366 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-05 14:21:47.837 9111 9366 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-05 14:21:47.837 9111 9366 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-05 14:26:16.967 10189 10189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 14:26:17.879 10189 10189 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
08-05 14:42:23.461 12034 12034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 14:42:24.231 12034 12034 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
08-05 14:57:38.439 13070 13070 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 14:57:39.133 13070 13070 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
08-05 15:28:05.091 14029 14029 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 15:28:08.220 14029 14029 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
08-05 17:13:56.710 15891 15891 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 17:13:59.925 15891 15891 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
08-05 19:17:10.077 18388 18388 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 19:17:11.216 18388 18388 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
08-05 23:06:59.232 21802 21802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-05 23:07:01.379 21802 21802 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
08-06 00:12:45.387 32506 32506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 00:12:46.082 32506 32506 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
08-06 00:27:00.947 4573 4573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 00:27:01.748 4573 4573 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
08-06 01:12:48.628 10892 10892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 01:12:49.273 10892 10892 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
08-06 02:13:18.935 13469 13469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 02:13:19.945 13469 13469 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.
08-06 02:13:21.289 13469 13596 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-06 02:13:21.289 13469 13596 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-06 02:13:21.289 13469 13596 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-06 03:12:23.444 17200 17200 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 03:12:24.322 17200 17200 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
08-06 03:26:28.261 19196 19196 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 03:26:29.080 19196 19196 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
08-06 03:49:52.038 21162 21162 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 03:49:53.262 21162 21162 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
08-06 13:21:44.577 4989 4989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 13:21:46.322 4989 4989 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-06 13:21:46.329 4989 4989 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-06 13:21:46.329 4989 4989 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-06 13:21:46.329 4989 4989 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-06 13:21:46.329 4989 4989 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-06 13:21:46.329 4989 4989 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-06 13:21:46.329 4989 4989 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-06 13:21:46.329 4989 4989 W System.err: at
java.lang.Class.newInstance(Native Method)
08-06 13:21:46.329 4989 4989 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-06 13:21:46.329 4989 4989 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-06 13:21:46.329 4989 4989 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-06 13:21:46.329 4989 4989 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-06 13:21:46.329 4989 4989 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-06 13:21:46.329 4989 4989 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-06 13:21:46.329 4989 4989 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-06 13:21:46.329 4989 4989 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-06 13:21:46.329 4989 4989 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-06 13:21:46.329 4989 4989 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-06 13:21:46.330 4989 4989 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-06 13:21:46.330 4989 4989 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-06 13:21:46.330 4989 4989 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-06 13:21:46.330 4989 4989 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-06 13:21:47.274 4989 4989 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.
08-06 13:21:50.895 4989 4989 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-06 13:21:50.896 4989 4989 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
08-06 13:21:52.016 4989 5000 W com.mbwhatsapp: Suspending all threads took:
5.721ms
--------- beginning of main
08-06 13:21:52.628 4989 5564 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-06 13:21:52.628 4989 5564 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-06 13:21:52.628 4989 5564 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-06 13:21:53.653 4989 5700 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=07efc641-b4c0-4dea-b755-555c5cb021d9, generation=0)
08-06 13:22:26.207 6789 6789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 13:22:26.629 6789 6789 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-06 13:22:26.629 6789 6789 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-06 13:22:26.629 6789 6789 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-06 13:22:26.629 6789 6789 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-06 13:22:26.629 6789 6789 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-06 13:22:26.629 6789 6789 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-06 13:22:26.629 6789 6789 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-06 13:22:26.630 6789 6789 W System.err: at
java.lang.Class.newInstance(Native Method)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-06 13:22:26.630 6789 6789 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-06 13:22:26.630 6789 6789 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-06 13:22:26.630 6789 6789 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-06 13:22:26.630 6789 6789 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-06 13:22:26.630 6789 6789 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-06 13:22:26.630 6789 6789 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-06 13:22:26.630 6789 6789 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-06 13:22:26.630 6789 6789 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-06 13:22:26.803 6789 6789 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.
08-06 13:22:28.081 6789 6789 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-06 13:22:28.081 6789 6789 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-06 13:22:28.385 6789 6789 W com.mbwhatsapp: type=1400 audit(0.0:1758): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-06 13:22:28.422 6789 6789 W com.mbwhatsapp: type=1400 audit(0.0:1759): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-06 13:22:28.508 6789 6789 W com.mbwhatsapp: type=1400 audit(0.0:1761): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-06 13:22:28.958 6789 6789 W com.mbwhatsapp: type=1400 audit(0.0:1762): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-06 13:22:29.966 6789 7007 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-06 13:22:29.966 6789 7007 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-06 13:22:29.966 6789 7007 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-06 13:22:31.743 6789 6809 W com.mbwhatsapp: Suspending all threads took:
15.901ms
08-06 14:15:10.474 21458 21458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 14:15:11.361 21458 21458 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.
08-06 14:15:12.408 21458 21458 W com.mbwhatsapp: type=1400 audit(0.0:14749): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-06 14:16:01.979 21991 21991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 14:16:02.656 21991 21991 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
08-06 19:08:23.985 8749 8749 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 19:08:25.745 8749 8749 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.
08-06 19:09:02.681 10114 10114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 19:09:03.961 10114 10114 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
08-06 20:34:39.390 12832 12832 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 20:34:42.343 12832 12832 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
08-06 20:39:55.651 14816 14816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 20:39:56.096 14816 14816 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
08-06 20:54:10.068 15157 15157 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 20:54:10.357 15157 15157 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
08-06 22:15:51.095 22342 22342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-06 22:15:51.770 22342 22342 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
08-07 13:44:19.048 8586 8586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 13:44:20.033 8586 8586 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.
08-07 13:44:21.461 8586 8642 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-07 13:44:21.461 8586 8642 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-07 13:44:21.461 8586 8642 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-07 13:56:12.955 9763 9763 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 13:56:14.223 9763 9763 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
08-07 15:24:23.956 20900 20900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 15:24:25.493 20900 20900 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.
08-07 15:24:30.446 20900 20900 W com.mbwhatsapp: type=1400 audit(0.0:112702): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-07 16:15:46.285 26094 26094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 16:15:47.059 26094 26094 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
08-07 17:28:08.676 27935 27935 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 17:28:09.330 27935 27935 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
08-07 17:47:27.503 28427 28427 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 17:47:27.911 28427 28427 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
08-07 17:48:57.456 29142 29142 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 17:48:57.761 29142 29142 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
08-07 17:52:20.865 29276 29276 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 17:52:21.239 29276 29276 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
08-07 18:00:23.958 29445 29445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 18:00:24.266 29445 29445 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
08-07 18:16:12.892 29942 29942 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 18:16:13.281 29942 29942 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
08-07 19:20:23.880 7848 7848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 19:20:24.543 7848 7848 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.
08-07 19:20:25.651 7848 7905 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-07 19:20:25.651 7848 7905 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-07 19:20:25.651 7848 7905 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-07 20:15:14.226 20443 20443 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 20:15:15.018 20443 20443 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.
08-07 20:15:16.441 20443 20496 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-07 20:15:16.441 20443 20496 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-07 20:15:16.441 20443 20496 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-07 22:33:04.640 21592 21592 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 22:33:06.544 21592 21592 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.
08-07 22:33:08.161 21592 21592 W com.mbwhatsapp: type=1400 audit(0.0:185275): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-07 22:37:53.701 23393 23393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-07 22:37:54.550 23393 23393 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
08-08 00:24:29.149 6744 6744 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 00:24:30.309 6744 6744 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
08-08 02:09:25.744 9163 9163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 02:09:27.818 9163 9163 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
08-08 04:12:25.731 10152 10152 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 04:12:27.456 10152 10152 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
08-08 07:22:03.992 12188 12188 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 07:22:07.675 12188 12188 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
08-08 09:30:27.760 6130 6130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 09:30:29.920 6130 6130 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-08 09:30:29.927 6130 6130 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-08 09:30:29.927 6130 6130 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-08 09:30:29.927 6130 6130 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-08 09:30:29.927 6130 6130 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-08 09:30:29.928 6130 6130 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-08 09:30:29.928 6130 6130 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-08 09:30:29.928 6130 6130 W System.err: at
java.lang.Class.newInstance(Native Method)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-08 09:30:29.928 6130 6130 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-08 09:30:29.928 6130 6130 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-08 09:30:29.928 6130 6130 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-08 09:30:29.928 6130 6130 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-08 09:30:29.928 6130 6130 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-08 09:30:29.928 6130 6130 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-08 09:30:29.928 6130 6130 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-08 09:30:29.928 6130 6130 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-08 09:30:30.447 6130 6130 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.
08-08 09:30:32.462 6130 6130 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-08 09:30:32.462 6130 6130 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-08 09:30:32.892 6130 6130 W com.mbwhatsapp: type=1400 audit(0.0:1630): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-08 09:30:32.915 6130 6130 W com.mbwhatsapp: type=1400 audit(0.0:1631): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-08 09:30:32.945 6130 6130 W com.mbwhatsapp: type=1400 audit(0.0:1632): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-08 09:30:33.155 6130 6130 W com.mbwhatsapp: type=1400 audit(0.0:1633): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-08 09:30:33.205 6130 6130 W com.mbwhatsapp: type=1400 audit(0.0:1634): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-08 09:30:33.811 6130 6500 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-08 09:30:33.811 6130 6500 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-08 09:30:33.811 6130 6500 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-08 10:24:26.841 20971 20971 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 10:24:27.999 20971 20971 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.
08-08 10:24:33.431 20971 20971 W com.mbwhatsapp: type=1400 audit(0.0:37874): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-08 10:24:33.467 20971 20971 W com.mbwhatsapp: type=1400 audit(0.0:37875): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-08 11:25:01.920 24874 24874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 11:25:03.067 24874 24874 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
08-08 11:28:13.191 25536 25536 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 11:28:13.603 25536 25536 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
08-08 11:30:07.314 26085 26085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 11:30:07.678 26085 26085 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
08-08 11:33:09.089 26419 26419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 11:33:09.501 26419 26419 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
08-08 12:24:11.908 28671 28671 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 12:24:13.401 28671 28671 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
08-08 13:33:25.133 1708 1708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 13:33:26.876 1708 1708 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
08-08 13:53:26.081 3977 3977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 13:53:26.567 3977 3977 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.
08-08 13:53:27.646 3977 4251 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-08 13:53:27.646 3977 4251 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-08 13:53:27.646 3977 4251 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-08 14:24:28.180 7553 7553 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 14:24:29.705 7553 7553 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.
08-08 14:24:31.496 7553 7553 W com.mbwhatsapp: type=1400 audit(0.0:42077): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-08 15:24:19.627 14604 14604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 15:24:21.170 14604 14604 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
08-08 15:27:24.005 15449 15449 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 15:27:25.257 15449 15449 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
08-08 15:29:41.699 16955 16955 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 15:29:42.810 16955 16955 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
08-08 15:32:35.958 18468 18468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 15:32:36.800 18468 18468 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
08-08 15:42:03.761 21003 21003 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 15:42:04.585 21003 21003 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
08-08 15:54:25.660 26016 26016 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 15:54:27.067 26016 26016 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
08-08 16:13:25.928 31204 31204 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 16:13:26.816 31204 31204 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
08-08 16:27:35.803 31667 31667 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 16:27:36.160 31667 31667 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
08-08 16:47:00.885 32265 32265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 16:47:01.282 32265 32265 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
08-08 17:25:23.924 2607 2607 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 17:25:24.884 2607 2607 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
08-08 17:47:06.968 3902 3902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 17:47:07.395 3902 3902 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
08-08 18:24:31.047 18993 18993 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 18:24:32.573 18993 18993 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
08-08 19:24:16.913 29547 29547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 19:24:22.647 29547 29547 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.
08-08 19:24:28.077 29547 29547 W com.mbwhatsapp: type=1400 audit(0.0:75165): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-08 19:27:39.718 30573 30573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 19:27:41.121 30573 30573 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
08-08 20:30:37.277 11322 11322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 20:30:38.172 11322 11322 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
08-08 21:25:21.723 26665 26665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 21:25:22.963 26665 26665 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
08-08 21:29:14.358 28380 28380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 21:29:15.164 28380 28380 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
08-08 21:45:25.835 29518 29518 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 21:45:26.477 29518 29518 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.
08-08 21:45:27.610 29518 29567 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-08 21:45:27.610 29518 29567 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-08 21:45:27.610 29518 29567 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-08 22:01:25.139 30113 30113 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 22:01:28.514 30113 30113 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
08-08 22:12:27.166 30754 30754 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 22:12:27.912 30754 30754 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
08-08 22:21:25.865 31835 31835 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 22:21:26.209 31835 31835 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
08-08 22:37:02.664 2345 2345 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 22:37:03.522 2345 2345 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
08-08 22:40:22.535 2911 2911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 22:40:22.768 2911 2911 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
08-08 22:43:24.868 3276 3276 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 23:39:58.515 8858 8858 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-08 23:40:01.220 8858 8858 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
08-09 00:01:25.990 11222 11222 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 00:01:27.213 11222 11222 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
08-09 01:10:47.232 12556 12556 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 01:10:51.004 12556 12556 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
08-09 03:13:26.320 15377 15377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 03:13:29.494 15377 15377 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.
08-09 03:13:33.725 15377 15377 W com.mbwhatsapp: type=1400 audit(0.0:115041): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-09 07:07:51.013 18885 18885 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 07:07:53.751 18885 18885 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.
08-09 07:07:56.847 18885 18885 W com.mbwhatsapp: type=1400 audit(0.0:115787): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-09 07:22:53.355 24098 24098 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 07:22:54.131 24098 24098 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
08-09 07:54:05.575 31280 31280 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 07:54:06.988 31280 31280 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
08-09 08:33:25.910 5953 5953 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 08:33:26.610 5953 5953 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
08-09 08:53:26.906 7092 7092 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 08:53:27.231 7092 7092 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
08-09 10:06:29.475 14292 14292 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 10:06:30.160 14292 14292 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.
08-09 10:06:31.324 14292 14351 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-09 10:06:31.324 14292 14351 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-09 10:06:31.324 14292 14351 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-09 10:24:27.490 18270 18270 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 10:24:28.411 18270 18270 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.
08-09 10:24:30.122 18270 18326 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-09 10:24:30.122 18270 18326 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-09 10:24:30.122 18270 18326 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-09 11:24:17.167 24861 24861 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 11:24:18.162 24861 24861 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
08-09 12:10:53.906 27322 27322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 12:10:54.672 27322 27322 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
08-09 13:33:25.846 3094 3094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 13:33:26.519 3094 3094 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
08-09 14:25:26.074 4684 4684 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 14:25:27.573 4684 4684 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
08-09 14:32:05.215 5719 5719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 14:32:05.807 5719 5719 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
08-09 14:44:59.922 6228 6228 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 14:45:00.216 6228 6228 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
08-09 15:29:16.476 13217 13217 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 15:29:17.689 13217 13217 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.
08-09 15:29:19.476 13217 13282 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-09 15:29:19.476 13217 13282 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-09 15:29:19.476 13217 13282 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-09 15:35:36.429 14474 14474 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 15:35:37.426 14474 14474 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
08-09 15:45:24.147 15447 15447 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 15:45:24.855 15447 15447 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
08-09 16:29:23.925 20215 20215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 16:29:27.323 20215 20215 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.
08-09 16:29:28.744 20215 20469 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-09 16:29:28.744 20215 20469 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-09 16:29:28.744 20215 20469 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-09 17:40:04.253 25120 25120 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 17:40:06.120 25120 25120 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
08-09 18:01:30.084 27358 27358 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 18:01:34.427 27358 27358 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.
08-09 18:01:35.699 27358 27445 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-09 18:01:35.699 27358 27445 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-09 18:01:35.699 27358 27445 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-09 18:11:58.842 27685 27685 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 18:11:59.132 27685 27685 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
08-09 18:25:27.146 28039 28039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 18:25:27.582 28039 28039 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
08-09 18:39:23.079 31367 31367 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 18:39:23.811 31367 31367 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
08-09 19:05:24.098 4355 4355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 19:05:24.794 4355 4355 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
08-09 19:24:55.824 6229 6229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 19:24:56.842 6229 6229 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
08-09 20:02:08.826 19288 19288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 20:02:10.571 19288 19288 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
08-09 21:09:12.038 29099 29099 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 21:09:13.851 29099 29099 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
08-09 22:10:34.921 15828 15828 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 22:10:35.809 15828 15828 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
08-09 22:24:18.739 18500 18500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 22:24:19.402 18500 18500 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
08-09 23:36:57.024 21470 21470 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-09 23:36:57.863 21470 21470 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.
08-09 23:36:59.205 21470 21558 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-09 23:36:59.205 21470 21558 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-09 23:36:59.205 21470 21558 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-10 00:57:31.392 23219 23219 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 00:57:40.937 23430 23430 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 00:57:42.147 23430 23430 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
08-10 07:01:26.242 29012 29012 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 07:01:28.244 29012 29012 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.
08-10 07:01:31.582 29012 29012 W com.mbwhatsapp: type=1400 audit(0.0:318195): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-10 08:24:13.242 12297 12297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 08:24:14.066 12297 12297 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
08-10 09:21:25.066 18816 18816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 09:21:26.446 18816 18816 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
08-10 09:41:25.937 20641 20641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 09:41:26.762 20641 20641 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
08-10 10:48:08.218 21698 21698 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 10:48:09.545 21698 21698 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
08-10 12:53:27.686 24153 24153 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 12:53:30.035 24153 24153 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
08-10 14:28:22.937 28234 28234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 14:28:23.445 28234 28234 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.
08-10 14:28:24.622 28234 28290 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-10 14:28:24.622 28234 28290 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-10 14:28:24.622 28234 28290 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-10 14:48:03.511 29457 29457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 14:48:04.187 29457 29457 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
08-10 15:37:25.944 5293 5293 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 15:37:26.684 5293 5293 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
08-10 17:21:27.363 8709 8709 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 17:21:30.533 8709 8709 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
08-10 19:24:27.011 13959 13959 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 19:24:29.050 13959 13959 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
08-10 19:24:51.113 15390 15390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 19:24:52.361 15390 15390 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
08-10 23:10:40.574 17449 17449 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 23:10:44.250 17449 17449 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.
08-10 23:10:47.190 17449 17449 W com.mbwhatsapp: type=1400 audit(0.0:339530): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-10 23:10:47.240 17449 17449 W com.mbwhatsapp: type=1400 audit(0.0:339531): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-10 23:10:47.307 17449 17449 W com.mbwhatsapp: type=1400 audit(0.0:339532): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-10 23:13:15.281 19210 19210 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 23:13:15.942 19210 19210 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
08-10 23:13:17.141 19210 19264 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-10 23:13:17.141 19210 19264 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-10 23:13:17.141 19210 19264 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-10 23:28:07.935 20948 20948 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-10 23:28:09.707 20948 20948 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
08-11 00:24:41.867 32364 32364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 00:24:42.820 32364 32364 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.
08-11 00:24:44.860 32364 32427 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-11 00:24:44.860 32364 32427 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-11 00:24:44.860 32364 32427 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-11 00:45:25.923 639 639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 00:45:27.446 639 639 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
08-11 00:56:36.992 4666 4666 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 00:56:38.305 4666 4666 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
08-11 01:21:25.968 6665 6665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 01:21:29.799 6665 6665 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
08-11 01:41:26.869 8178 8178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 01:41:29.306 8178 8178 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
08-11 02:32:30.150 14362 14362 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 02:32:31.775 14362 14362 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
08-11 09:36:11.737 22757 22757 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 09:36:15.264 22757 22757 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.
08-11 09:36:24.091 22757 22757 W com.mbwhatsapp: type=1400 audit(0.0:369474): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-11 11:29:04.283 26721 26721 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 11:29:06.352 26721 26721 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
08-11 11:30:15.501 28218 28218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 11:30:16.529 28218 28218 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
08-11 11:57:36.435 2333 2333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 11:57:37.298 2333 2333 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.
08-11 11:57:39.052 2333 2419 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-11 11:57:39.052 2333 2419 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-11 11:57:39.052 2333 2419 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-11 12:24:18.808 8782 8782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 12:24:19.645 8782 8782 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
08-11 13:53:07.004 20354 20354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 13:53:08.999 20354 20354 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
08-11 14:25:00.534 25854 25854 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 14:25:01.595 25854 25854 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.
08-11 14:25:03.714 25854 25977 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-11 14:25:03.714 25854 25977 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-11 14:25:03.714 25854 25977 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-11 14:35:15.717 28896 28896 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 14:35:16.661 28896 28896 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.
08-11 14:35:18.447 28896 28948 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-11 14:35:18.447 28896 28948 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-11 14:35:18.447 28896 28948 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-11 14:39:55.592 30654 30654 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 14:39:57.778 30654 30654 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.
08-11 14:40:00.678 30654 30730 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-11 14:40:00.678 30654 30730 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-11 14:40:00.678 30654 30730 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-11 15:24:18.048 4409 4409 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 15:24:19.108 4409 4409 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
08-11 17:04:44.990 7658 7658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 17:04:48.500 7658 7658 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.
08-11 17:04:56.113 7658 7684 W com.mbwhatsapp: Suspending all threads took:
549.622ms
--------- beginning of main
08-11 19:05:24.175 11126 11126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 19:05:26.347 11126 11126 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
08-11 23:08:26.465 14617 14617 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-11 23:08:30.490 14617 14617 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.
08-11 23:08:34.538 14617 14617 W com.mbwhatsapp: type=1400 audit(0.0:404291): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-12 00:24:24.236 5428 5428 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 00:24:25.100 5428 5428 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
08-12 02:11:20.389 5371 5371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 02:11:22.605 5371 5371 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-12 02:11:22.606 5371 5371 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.Class.newInstance(Native Method)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-12 02:11:22.606 5371 5371 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-12 02:11:22.606 5371 5371 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-12 02:11:22.606 5371 5371 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-12 02:11:22.606 5371 5371 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-12 02:11:22.606 5371 5371 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-12 02:11:22.606 5371 5371 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-12 02:11:22.606 5371 5371 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-12 02:11:22.606 5371 5371 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-12 02:11:23.074 5371 5371 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
08-12 02:11:26.401 5371 5371 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-12 02:11:26.402 5371 5371 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
08-12 02:11:29.700 5371 5751 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-12 02:11:29.700 5371 5751 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-12 02:11:29.700 5371 5751 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-12 02:11:30.846 5371 5379 W com.mbwhatsapp: Suspending all threads took:
5.452ms
08-12 02:17:53.356 14644 14644 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 02:17:54.335 14644 14644 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
08-12 10:10:21.867 27809 27809 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 10:10:31.278 27809 27809 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.
08-12 10:11:01.084 28467 28467 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 10:11:12.502 28467 28467 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.
08-12 12:05:46.318 26391 26391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 12:05:47.122 26391 26391 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
08-12 12:08:14.883 27993 27993 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 12:08:19.921 27993 27993 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.
08-12 12:08:30.303 27993 27993 W com.mbwhatsapp: type=1400 audit(0.0:45036): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-12 13:05:21.723 7319 7319 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 13:05:22.535 7319 7319 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.
08-12 13:05:24.147 7319 7388 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-12 13:05:24.147 7319 7388 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-12 13:05:24.147 7319 7388 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-12 14:05:45.784 17371 17371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 14:05:46.786 17371 17371 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
08-12 15:06:26.864 29050 29050 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 15:06:27.857 29050 29050 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
08-12 15:34:27.437 30830 30830 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 15:34:28.618 30830 30830 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
08-12 17:02:27.225 32500 32500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 19:06:27.844 5864 5864 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 19:06:32.913 5864 5864 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
08-12 23:03:55.742 10257 10257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-12 23:03:59.814 10257 10257 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
08-12 23:04:40.827 10257 11385 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-12 23:04:40.827 10257 11385 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-13 00:05:13.273 27137 27137 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 00:05:15.916 27137 27137 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.
08-13 00:05:19.362 27137 27137 W com.mbwhatsapp: type=1400 audit(0.0:249716): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-13 00:05:19.378 27137 27137 W com.mbwhatsapp: type=1400 audit(0.0:249717): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-13 01:05:14.583 14399 14399 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 01:05:15.479 14399 14399 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
08-13 07:01:44.297 29674 29674 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 07:01:44.780 29674 29674 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.
08-13 07:01:45.949 29674 29733 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-13 07:01:45.949 29674 29733 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-13 07:01:45.949 29674 29733 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-13 07:10:26.771 29859 29859 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 07:10:27.021 29859 29859 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
08-13 09:06:25.878 31704 31704 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 09:06:27.124 31704 31704 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
08-13 11:10:27.130 32590 32590 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 11:10:27.721 32590 32590 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
08-13 14:22:10.258 4341 4341 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 14:22:13.428 4341 4341 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
08-13 16:06:58.611 11356 11356 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 16:06:59.747 11356 11356 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
08-13 16:09:56.027 13049 13049 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 16:09:56.749 13049 13049 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
08-13 16:20:00.898 14316 14316 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 16:20:01.671 14316 14316 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
08-13 17:05:36.887 26671 26671 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 17:05:37.838 26671 26671 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.
08-13 17:05:39.346 26671 26724 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-13 17:05:39.346 26671 26724 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-13 17:05:39.346 26671 26724 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-13 18:10:04.001 31366 31366 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 18:10:05.436 31366 31366 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
08-13 18:15:13.416 3004 3004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 18:15:14.493 3004 3004 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
08-13 18:20:17.667 4431 4431 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 18:20:18.689 4431 4431 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
08-13 18:57:52.856 9732 9732 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 18:57:53.746 9732 9732 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
08-13 19:35:53.933 15700 15700 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 19:35:54.660 15700 15700 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
08-13 20:50:27.189 20599 20599 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 20:50:29.021 20599 20599 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
08-13 21:14:26.949 21940 21940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 21:14:27.745 21940 21940 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
08-13 22:05:15.509 30284 30284 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 22:05:16.100 30284 30284 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
08-13 22:06:15.450 30724 30724 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 22:06:15.671 30724 30724 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
08-13 23:05:30.219 6432 6432 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-13 23:05:31.000 6432 6432 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
08-14 00:05:57.188 19100 19100 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 00:05:58.055 19100 19100 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
08-14 06:36:33.781 22043 22043 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 06:36:36.463 22043 22043 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.
08-14 06:36:38.992 22043 22043 W com.mbwhatsapp: type=1400 audit(0.0:495165): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-14 09:10:26.898 32132 32132 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 09:10:29.388 32132 32132 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
08-14 17:28:48.731 4847 4847 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 17:28:51.291 4847 4847 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-14 17:28:51.292 4847 4847 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.Class.newInstance(Native Method)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-14 17:28:51.292 4847 4847 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-14 17:28:51.292 4847 4847 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-14 17:28:51.292 4847 4847 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-14 17:28:51.292 4847 4847 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-14 17:28:51.292 4847 4847 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-14 17:28:51.292 4847 4847 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-14 17:28:51.292 4847 4847 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-14 17:28:51.292 4847 4847 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-14 17:28:51.773 4847 4847 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.
08-14 17:28:57.508 4847 4847 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-14 17:28:57.509 4847 4847 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-14 17:29:02.852 4847 5445 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-14 17:29:02.852 4847 5445 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-14 17:29:02.852 4847 5445 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-14 17:30:34.318 4847 5562 W FastPrintWriter: Write failure
08-14 17:30:34.318 4847 5562 W FastPrintWriter: java.io.IOException: write
failed: EPIPE (Broken pipe)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.IoBridge.write(IoBridge.java:654)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
java.io.FileOutputStream.write(FileOutputStream.java:401)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.flushBytesLocked(FastPrintWriter.java:354
)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.flushLocked(FastPrintWriter.java:377)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.appendLocked(FastPrintWriter.java:322)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.print(FastPrintWriter.java:499)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
java.io.PrintWriter.println(PrintWriter.java:739)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.util.PrintWriterPrinter.println(PrintWriterPrinter.java:38)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.database.sqlite.SQLiteConnectionPool.dump(SQLiteConnectionPool.java:1131)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.database.sqlite.SQLiteDatabase.dump(SQLiteDatabase.java:2338)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.database.sqlite.SQLiteDatabase.dumpAll(SQLiteDatabase.java:2321)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.database.sqlite.SQLiteDebug.dump(SQLiteDebug.java:218)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.dumpDatabaseInfo(ActivityThread.java:1
761)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.dumpDbInfo(ActivityThread.java:1792)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.app.IApplicationThread$Stub.onTransact(IApplicationThread.java:1314)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.onTransact(ActivityThread.java:1970)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.os.Binder.execTransactInternal(Binder.java:1184)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
android.os.Binder.execTransact(Binder.java:1143)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: Caused by:
android.system.ErrnoException: write failed: EPIPE (Broken pipe)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.Linux.writeBytes(Native Method)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.Linux.write(Linux.java:296)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.ForwardingOs.write(ForwardingOs.java:951)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.BlockGuardOs.write(BlockGuardOs.java:447)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.ForwardingOs.write(ForwardingOs.java:951)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: at
libcore.io.IoBridge.write(IoBridge.java:649)
08-14 17:30:34.318 4847 5562 W FastPrintWriter: ... 17 more
08-14 17:35:54.871 16782 16782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 17:35:57.640 16782 16782 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
08-14 17:38:54.293 20661 20661 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 17:38:55.864 20661 20661 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
08-14 18:24:17.663 30754 30754 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 18:24:19.184 30754 30754 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
08-14 18:33:28.927 31620 31620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 18:33:29.218 31620 31620 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
08-14 18:36:14.544 31857 31857 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 18:36:14.836 31857 31857 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
08-14 18:42:00.641 32307 32307 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 18:42:01.304 32307 32307 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
08-14 18:44:48.729 1826 1826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 18:44:49.008 1826 1826 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
08-14 18:53:30.085 3265 3265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 18:53:31.304 3265 3265 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
08-14 20:08:18.542 13546 13546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:08:19.788 13546 13546 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
08-14 20:26:26.409 14666 14666 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:26:26.801 14666 14666 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
08-14 20:30:05.681 15195 15195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:30:06.470 15195 15195 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
08-14 20:33:04.612 15759 15759 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:33:05.072 15759 15759 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
08-14 20:35:21.685 16075 16075 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:35:22.014 16075 16075 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
08-14 20:40:35.955 16291 16291 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:40:36.220 16291 16291 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
08-14 20:46:38.857 16985 16985 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:46:39.150 16985 16985 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
08-14 20:54:10.285 17153 17153 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 20:54:10.554 17153 17153 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
08-14 22:09:06.539 4258 4258 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 22:09:07.681 4258 4258 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-14 22:09:07.682 4258 4258 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-14 22:09:07.682 4258 4258 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-14 22:09:07.682 4258 4258 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-14 22:09:07.682 4258 4258 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-14 22:09:07.682 4258 4258 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-14 22:09:07.683 4258 4258 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-14 22:09:07.683 4258 4258 W System.err: at
java.lang.Class.newInstance(Native Method)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-14 22:09:07.683 4258 4258 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-14 22:09:07.683 4258 4258 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-14 22:09:07.683 4258 4258 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-14 22:09:07.683 4258 4258 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-14 22:09:07.683 4258 4258 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-14 22:09:07.683 4258 4258 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-14 22:09:07.683 4258 4258 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-14 22:09:07.683 4258 4258 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-14 22:09:08.075 4258 4258 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.
08-14 22:09:09.726 4258 4258 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-14 22:09:09.726 4258 4258 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-14 22:09:10.966 4258 4628 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-14 22:09:10.966 4258 4628 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-14 22:09:10.966 4258 4628 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-14 22:09:14.016 4258 4646 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-14 22:09:14.016 4258 4646 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-14 22:09:14.264 4258 4276 W com.mbwhatsapp: Suspending all threads took:
23.222ms
08-14 22:13:30.679 13039 13039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-14 22:13:32.842 13039 13039 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.
08-14 22:13:35.357 13039 13039 W com.mbwhatsapp: type=1400 audit(0.0:3711): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-15 16:10:56.963 669 669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 16:10:58.478 669 669 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.
08-15 16:11:01.175 669 1805 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=72b59cf2-2e28-4c83-aa71-beed56bec3a5, generation=0)
--------- beginning of main
08-15 16:24:41.775 3156 3156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 16:24:42.701 3156 3156 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
08-15 16:44:42.217 4365 4365 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 16:44:43.415 4365 4365 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
08-15 17:00:13.764 4933 4933 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 17:00:14.226 4933 4933 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
08-15 17:07:16.041 5295 5295 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 17:07:16.364 5295 5295 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
08-15 17:20:18.441 5716 5716 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 17:20:18.757 5716 5716 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
08-15 18:04:26.767 13273 13273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 18:04:27.759 13273 13273 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
08-15 18:11:49.919 14566 14566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 18:11:50.847 14566 14566 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
08-15 18:24:41.804 15494 15494 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 18:24:42.117 15494 15494 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
08-15 18:30:05.192 15808 15808 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 18:30:05.519 15808 15808 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
08-15 18:52:41.830 17504 17504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 18:52:42.927 17504 17504 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
08-15 19:08:41.916 17894 17894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 19:08:42.430 17894 17894 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
08-15 19:26:14.450 18683 18683 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-15 19:26:17.902 18683 18683 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
08-17 07:38:03.877 6314 6314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 07:38:05.060 6314 6314 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.
08-17 07:38:10.175 6314 6314 W com.mbwhatsapp: type=1400 audit(0.0:1654): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-17 07:38:10.238 6314 6314 W com.mbwhatsapp: type=1400 audit(0.0:1655): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-17 12:22:46.935 29611 29611 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 12:22:47.475 29611 29611 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.
08-17 12:22:48.604 29611 29663 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-17 12:22:48.604 29611 29663 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-17 12:22:48.604 29611 29663 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-17 12:27:01.299 29782 29782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 12:27:01.622 29782 29782 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
08-17 12:27:02.358 29782 29832 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-17 12:27:02.358 29782 29832 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-17 12:27:02.358 29782 29832 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-17 14:32:32.336 8988 8988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 14:32:33.996 8988 8988 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
08-17 14:36:06.513 10339 10339 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 14:36:07.121 10339 10339 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
08-17 14:39:02.532 10445 10445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 14:39:02.790 10445 10445 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
08-17 14:39:35.399 10540 10540 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 14:39:36.057 10540 10540 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
08-17 15:30:43.707 13687 13687 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 15:30:44.466 13687 13687 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
08-17 15:36:34.510 14158 14158 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 15:37:34.280 14405 14405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 15:37:34.558 14405 14405 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
08-17 15:39:13.831 14743 14743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 15:39:14.129 14743 14743 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
08-17 16:43:04.732 27296 27296 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 16:43:05.807 27296 27296 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
08-17 17:42:41.224 31583 31583 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 17:42:41.943 31583 31583 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
08-17 18:28:50.158 9184 9184 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 18:28:51.454 9184 9184 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.
08-17 18:28:53.313 9184 9233 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-17 18:28:53.313 9184 9233 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-17 18:28:53.313 9184 9233 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-17 18:29:19.708 9302 9302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 18:29:19.971 9302 9302 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
08-17 19:29:37.598 21475 21475 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 19:29:38.407 21475 21475 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
08-17 21:13:12.915 7563 7563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-17 21:13:14.079 7563 7563 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.
08-17 21:13:15.880 7563 7823 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-17 21:13:15.880 7563 7823 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-17 21:13:15.880 7563 7823 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-18 02:55:48.359 20859 20859 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-18 02:55:49.090 20859 20859 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
08-18 02:57:40.760 22048 22048 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-18 02:57:41.532 22048 22048 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
08-18 03:02:31.853 23323 23323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-18 03:02:32.513 23323 23323 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
08-18 03:12:56.289 24095 24095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-18 03:12:56.962 24095 24095 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
08-20 22:28:55.450 27211 27211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-20 22:28:58.170 27211 27211 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.
08-20 22:29:02.044 27211 27825 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=931e7736-5716-4d31-bfda-9271034fbc8f, generation=0)
--------- beginning of main
08-20 22:31:03.164 28636 28636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-20 22:31:03.572 28636 28636 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
08-21 08:03:24.438 6124 6124 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-21 08:03:32.887 6124 6124 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-21 08:03:32.892 6124 6124 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-21 08:03:32.892 6124 6124 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-21 08:03:32.892 6124 6124 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-21 08:03:32.892 6124 6124 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-21 08:03:32.892 6124 6124 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-21 08:03:32.892 6124 6124 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-21 08:03:32.892 6124 6124 W System.err: at
java.lang.Class.newInstance(Native Method)
08-21 08:03:32.892 6124 6124 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-21 08:03:32.892 6124 6124 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-21 08:03:32.892 6124 6124 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-21 08:03:32.892 6124 6124 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-21 08:03:32.892 6124 6124 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-21 08:03:32.893 6124 6124 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-21 08:03:32.893 6124 6124 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-21 08:03:32.893 6124 6124 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-21 08:03:32.893 6124 6124 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-21 08:03:32.893 6124 6124 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-21 08:03:32.893 6124 6124 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-21 08:03:32.893 6124 6124 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-21 08:03:32.893 6124 6124 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-21 08:03:32.893 6124 6124 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-21 08:03:33.382 6124 6124 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.
08-21 08:03:35.268 6124 6124 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-21 08:03:35.269 6124 6124 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-22 14:28:48.805 6681 6681 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 14:28:53.490 6681 6681 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-22 14:28:53.490 6681 6681 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-22 14:28:53.490 6681 6681 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-22 14:28:53.490 6681 6681 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-22 14:28:53.490 6681 6681 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-22 14:28:53.490 6681 6681 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-22 14:28:53.490 6681 6681 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-22 14:28:53.490 6681 6681 W System.err: at
java.lang.Class.newInstance(Native Method)
08-22 14:28:53.490 6681 6681 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-22 14:28:53.490 6681 6681 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-22 14:28:53.490 6681 6681 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-22 14:28:53.490 6681 6681 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-22 14:28:53.490 6681 6681 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-22 14:28:53.490 6681 6681 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-22 14:28:53.490 6681 6681 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-22 14:28:53.490 6681 6681 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-22 14:28:53.490 6681 6681 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-22 14:28:53.490 6681 6681 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-22 14:28:53.491 6681 6681 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-22 14:28:53.491 6681 6681 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-22 14:28:53.491 6681 6681 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-22 14:28:53.491 6681 6681 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-22 14:28:54.044 6681 6681 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.
08-22 14:28:57.062 6681 6681 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-22 14:28:57.063 6681 6681 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-22 14:28:59.111 6681 6702 W com.mbwhatsapp: Suspending all threads took:
83.699ms
08-22 14:28:59.972 6681 7043 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-22 14:28:59.972 6681 7043 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-22 14:28:59.972 6681 7043 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-22 14:29:02.567 6681 7143 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=bd7ea442-f480-4317-8ab2-c68cb7d41ad1, generation=0)
08-22 14:30:18.727 8805 8805 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 14:30:24.990 8805 8805 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.
08-22 14:30:28.598 8805 8805 W com.mbwhatsapp: type=1400 audit(0.0:2141): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-22 14:30:28.601 8805 8805 W com.mbwhatsapp: type=1400 audit(0.0:2142): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-22 14:30:28.601 8805 8805 W com.mbwhatsapp: type=1400 audit(0.0:2143): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-22 14:30:28.604 8805 8805 W com.mbwhatsapp: type=1400 audit(0.0:2144): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
08-22 14:33:23.130 13382 13382 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 14:33:24.646 13382 13382 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
08-22 15:29:52.895 26850 26850 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 15:29:53.831 26850 26850 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
08-22 15:46:43.226 28216 28216 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 15:46:43.608 28216 28216 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
08-22 17:07:15.654 31079 31079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 17:07:17.880 31079 31079 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
08-22 19:14:05.780 32738 32738 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 19:14:07.837 32738 32738 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
08-22 19:16:33.065 3669 3669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 19:16:33.573 3669 3669 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
08-22 22:45:48.665 7530 7530 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-22 22:45:51.653 7530 7530 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
08-23 00:23:12.174 18643 18643 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 00:29:46.270 18856 18856 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 00:29:46.722 18856 18856 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
08-23 01:22:10.669 30988 30988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 01:22:11.559 30988 30988 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
08-23 01:24:01.555 31680 31680 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 01:24:02.465 31680 31680 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
08-23 02:00:07.092 8513 8513 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 02:00:07.977 8513 8513 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
08-23 04:33:07.074 14517 14517 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 04:33:14.354 14517 14517 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
08-23 06:43:15.336 17328 17328 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 06:43:17.897 17328 17328 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.
08-23 10:17:07.183 23993 23993 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 10:17:11.254 23993 23993 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
08-23 10:17:42.464 25302 25302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 10:17:43.179 25302 25302 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
08-23 12:10:53.889 31635 31635 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 12:10:55.864 31635 31635 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
08-23 12:17:14.531 4174 4174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 12:17:16.010 4174 4174 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
08-23 12:17:17.399 4174 4252 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-23 12:17:17.399 4174 4252 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-23 12:17:17.399 4174 4252 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-23 13:39:15.436 9924 9924 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 13:39:18.102 9924 9924 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
08-23 14:27:17.891 12524 12524 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 14:27:20.096 12524 12524 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
08-23 16:31:54.024 6417 6417 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 16:31:55.415 6417 6417 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
08-23 16:34:32.057 11509 11509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 16:34:34.480 11509 11509 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
08-23 17:18:44.562 4557 4557 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 17:18:47.322 4557 4557 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-23 17:18:47.323 4557 4557 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-23 17:18:47.324 4557 4557 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-23 17:18:47.324 4557 4557 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-23 17:18:47.324 4557 4557 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-23 17:18:47.324 4557 4557 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-23 17:18:47.324 4557 4557 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-23 17:18:47.324 4557 4557 W System.err: at
java.lang.Class.newInstance(Native Method)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-23 17:18:47.324 4557 4557 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-23 17:18:47.324 4557 4557 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-23 17:18:47.324 4557 4557 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-23 17:18:47.324 4557 4557 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-23 17:18:47.324 4557 4557 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-23 17:18:47.324 4557 4557 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-23 17:18:47.324 4557 4557 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-23 17:18:47.324 4557 4557 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-23 17:18:48.148 4557 4557 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.
08-23 17:18:49.697 4557 4557 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-23 17:18:49.698 4557 4557 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-23 17:18:51.402 4557 5049 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-23 17:18:51.402 4557 5049 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-23 17:18:51.402 4557 5049 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-23 17:18:56.418 4557 5241 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-23 17:18:56.418 4557 5241 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-23 17:19:35.768 6906 6906 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 17:19:36.087 6906 6906 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-23 17:19:36.089 6906 6906 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.Class.newInstance(Native Method)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-23 17:19:36.089 6906 6906 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-23 17:19:36.089 6906 6906 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-23 17:19:36.089 6906 6906 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-23 17:19:36.089 6906 6906 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-23 17:19:36.089 6906 6906 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-23 17:19:36.089 6906 6906 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-23 17:19:36.089 6906 6906 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-23 17:19:36.089 6906 6906 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-23 17:19:36.354 6906 6906 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.
08-23 17:19:37.065 6906 6906 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-23 17:19:37.066 6906 6906 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-23 17:19:37.785 6906 7014 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-23 17:19:37.785 6906 7014 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-23 17:19:37.785 6906 7014 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-23 17:21:34.985 10689 10689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 17:21:35.856 10689 10689 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
08-23 18:14:16.989 25822 25822 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 18:14:17.826 25822 25822 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
08-23 18:25:06.209 29459 29459 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 18:25:06.797 29459 29459 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
08-23 18:28:32.171 31283 31283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 18:28:32.996 31283 31283 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
08-23 19:13:08.432 9138 9138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 19:13:09.920 9138 9138 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
08-23 20:32:34.363 5658 5658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 20:32:36.040 5658 5658 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-23 20:32:36.041 5658 5658 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-23 20:32:36.041 5658 5658 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-23 20:32:36.041 5658 5658 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-23 20:32:36.041 5658 5658 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-23 20:32:36.041 5658 5658 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-23 20:32:36.041 5658 5658 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-23 20:32:36.045 5658 5658 W System.err: at
java.lang.Class.newInstance(Native Method)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-23 20:32:36.045 5658 5658 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-23 20:32:36.045 5658 5658 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-23 20:32:36.045 5658 5658 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-23 20:32:36.045 5658 5658 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-23 20:32:36.045 5658 5658 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-23 20:32:36.045 5658 5658 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-23 20:32:36.045 5658 5658 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-23 20:32:36.045 5658 5658 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-23 20:32:36.676 5658 5658 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.
08-23 20:32:39.800 5658 5658 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-23 20:32:39.806 5658 5658 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
08-23 20:32:39.845 5658 5669 W com.mbwhatsapp: Suspending all threads took:
6.118ms
--------- beginning of main
08-23 20:32:42.627 5658 6243 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-23 20:32:42.627 5658 6243 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-23 20:32:42.627 5658 6243 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-23 20:32:46.472 5658 6243 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-23 20:32:46.473 5658 6243 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-23 20:34:42.276 10415 10415 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 20:34:44.103 10415 10415 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
08-23 20:37:36.998 15417 15417 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 20:37:37.896 15417 15417 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
08-23 20:41:24.623 16653 16653 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 20:41:25.415 16653 16653 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
08-23 20:46:04.494 17951 17951 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 20:46:05.337 17951 17951 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
08-23 20:55:56.853 20105 20105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 20:55:57.646 20105 20105 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
08-23 21:19:14.103 25988 25988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 21:19:14.902 25988 25988 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
08-23 21:26:47.833 27242 27242 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 21:26:49.095 27242 27242 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
08-23 22:26:43.254 11267 11267 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 22:26:44.491 11267 11267 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
08-23 23:26:57.439 32654 32654 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-23 23:26:58.443 32654 32654 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.
08-23 23:27:00.071 32654 421 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-23 23:27:00.071 32654 421 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-23 23:27:00.071 32654 421 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-24 00:26:22.367 22399 22399 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 00:26:23.349 22399 22399 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
08-24 00:43:11.979 24540 24540 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 00:43:12.677 24540 24540 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
08-24 00:59:39.411 5727 5727 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 00:59:40.425 5727 5727 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
08-24 01:01:12.697 9140 9140 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 01:01:14.638 9140 9140 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
08-24 01:26:23.619 17743 17743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 01:26:25.449 17743 17743 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
08-24 01:28:32.205 18236 18236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 01:28:32.672 18236 18236 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
08-24 02:32:56.684 20499 20499 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 02:32:57.020 20499 20499 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
08-24 03:42:15.753 21289 21289 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 03:42:16.251 21289 21289 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
08-24 05:46:15.850 22340 22340 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 05:46:16.295 22340 22340 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
08-24 07:34:42.972 24818 24818 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 07:34:45.703 24818 24818 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
08-24 07:36:59.222 25573 25573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 07:36:59.706 25573 25573 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
08-24 09:38:15.772 27969 27969 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 09:38:16.405 27969 27969 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
08-24 11:26:22.499 21913 21913 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 11:26:23.615 21913 21913 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
08-24 11:30:43.239 23392 23392 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 11:30:44.069 23392 23392 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
08-24 12:26:33.339 390 390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 12:26:34.022 390 390 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
08-24 13:26:45.380 9393 9393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 13:26:45.984 9393 9393 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.
08-24 13:26:47.000 9393 9393 W com.mbwhatsapp: type=1400 audit(0.0:184245): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-24 13:28:32.258 10016 10016 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 13:28:32.630 10016 10016 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
08-24 13:33:10.225 10674 10674 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 13:33:10.577 10674 10674 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
08-24 14:26:24.929 17322 17322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 14:26:25.665 17322 17322 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
08-24 14:30:14.503 18482 18482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 14:30:15.507 18482 18482 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
08-24 14:39:19.581 21397 21397 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 14:39:20.859 21397 21397 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
08-24 14:40:19.987 21712 21712 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 14:40:20.427 21712 21712 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
08-24 15:00:04.225 23969 23969 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 15:00:07.958 23969 23969 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.
08-24 15:00:10.733 23969 23969 W com.mbwhatsapp: type=1400 audit(0.0:193850): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-24 15:13:04.499 26294 26294 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 15:13:05.357 26294 26294 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
08-24 15:33:03.688 26654 26654 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 15:33:04.469 26654 26654 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
08-24 16:45:04.897 28230 28230 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 16:45:09.299 28230 28230 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.
08-24 18:53:04.952 29616 29616 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 18:53:06.951 29616 29616 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
08-24 19:40:07.559 31905 31905 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 19:40:08.529 31905 31905 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
08-24 19:45:33.814 2484 2484 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 19:45:34.591 2484 2484 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
08-24 20:05:03.609 6193 6193 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 20:05:04.557 6193 6193 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
08-24 20:35:17.354 7390 7390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 20:35:18.002 7390 7390 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
08-24 21:37:03.484 8993 8993 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 21:37:04.205 8993 8993 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
08-24 21:57:04.600 9261 9261 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-24 21:57:05.311 9261 9261 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
08-25 01:52:54.948 4379 4379 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-25 01:52:56.752 4379 4379 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-25 01:52:56.755 4379 4379 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-25 01:52:56.755 4379 4379 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-25 01:52:56.755 4379 4379 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-25 01:52:56.755 4379 4379 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-25 01:52:56.755 4379 4379 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-25 01:52:56.755 4379 4379 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-25 01:52:56.756 4379 4379 W System.err: at
java.lang.Class.newInstance(Native Method)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-25 01:52:56.756 4379 4379 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-25 01:52:56.756 4379 4379 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-25 01:52:56.756 4379 4379 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-25 01:52:56.756 4379 4379 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-25 01:52:56.756 4379 4379 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-25 01:52:56.756 4379 4379 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-25 01:52:56.756 4379 4379 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-25 01:52:56.756 4379 4379 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-25 01:52:57.255 4379 4379 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.
08-25 01:52:59.360 4379 4379 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-25 01:52:59.361 4379 4379 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-25 01:53:01.019 4379 4710 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-25 01:53:01.019 4379 4710 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-25 01:53:01.019 4379 4710 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-25 01:53:06.335 4379 4862 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
08-25 01:53:06.335 4379 4862 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
08-25 01:56:13.566 12216 12216 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-25 01:56:14.733 12216 12216 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
08-25 12:57:59.876 11665 11665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-25 12:58:08.432 11665 11665 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
08-26 10:17:10.097 4979 4979 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-26 10:17:12.993 4979 4979 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-26 10:17:13.002 4979 4979 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.Class.newInstance(Native Method)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-26 10:17:13.002 4979 4979 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-26 10:17:13.002 4979 4979 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-26 10:17:13.002 4979 4979 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-26 10:17:13.002 4979 4979 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-26 10:17:13.002 4979 4979 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-26 10:17:13.002 4979 4979 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-26 10:17:13.002 4979 4979 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-26 10:17:13.002 4979 4979 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-26 10:17:13.725 4979 4979 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.
08-26 10:17:18.240 4979 4979 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-26 10:17:18.240 4979 4979 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-26 10:17:18.669 4979 4979 W com.mbwhatsapp: type=1400 audit(0.0:1394): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-26 10:17:18.715 4979 4979 W com.mbwhatsapp: type=1400 audit(0.0:1395): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-26 10:17:21.887 4979 5489 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-26 10:17:21.887 4979 5489 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-26 10:17:21.887 4979 5489 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-26 10:17:27.549 4979 4987 W com.mbwhatsapp: Suspending all threads took:
733.703ms
08-26 10:17:29.722 4979 5767 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=605e9163-5fba-48c5-8f15-754025bef745, generation=0)
08-26 10:54:51.234 24431 24431 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-26 10:54:52.547 24431 24431 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
08-26 11:50:03.145 27688 27688 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-26 11:50:05.014 27688 27688 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
08-26 12:22:51.535 32746 32746 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-26 12:22:52.095 32746 32746 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
08-26 13:00:02.178 4579 4579 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-26 13:00:02.740 4579 4579 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
08-27 16:53:13.985 11402 11402 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-27 16:53:19.815 11402 11402 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.
08-27 16:53:22.379 11402 11402 W com.mbwhatsapp: type=1400 audit(0.0:199536): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-27 20:52:49.261 27926 27926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-27 20:52:54.307 27926 27926 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
08-27 21:13:22.128 9386 9386 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-27 21:13:22.877 9386 9386 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
08-27 21:24:48.209 16274 16274 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-27 21:24:49.419 16274 16274 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
08-27 22:28:40.196 32079 32079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-27 22:28:41.473 32079 32079 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
08-28 15:01:58.794 3633 3633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-28 15:02:01.137 3633 3633 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.
08-28 15:02:05.145 3633 3633 W com.mbwhatsapp: type=1400 audit(0.0:358407): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-28 15:02:05.355 3633 3633 W com.mbwhatsapp: type=1400 audit(0.0:358408): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-28 16:11:23.240 17564 17564 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-28 16:11:24.029 17564 17564 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.
08-28 16:11:25.798 17564 17626 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-28 16:11:25.798 17564 17626 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-28 16:11:25.798 17564 17626 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-28 21:18:58.064 29692 29692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-28 21:19:03.881 29692 29692 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
08-30 01:12:41.138 5134 5134 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-30 01:12:44.003 5134 5134 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-30 01:12:44.005 5134 5134 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-30 01:12:44.005 5134 5134 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-30 01:12:44.005 5134 5134 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-30 01:12:44.005 5134 5134 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-30 01:12:44.005 5134 5134 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-30 01:12:44.005 5134 5134 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-30 01:12:44.005 5134 5134 W System.err: at
java.lang.Class.newInstance(Native Method)
08-30 01:12:44.005 5134 5134 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-30 01:12:44.005 5134 5134 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-30 01:12:44.005 5134 5134 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-30 01:12:44.005 5134 5134 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-30 01:12:44.005 5134 5134 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-30 01:12:44.005 5134 5134 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-30 01:12:44.005 5134 5134 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-30 01:12:44.005 5134 5134 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-30 01:12:44.005 5134 5134 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-30 01:12:44.005 5134 5134 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-30 01:12:44.006 5134 5134 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-30 01:12:44.006 5134 5134 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-30 01:12:44.006 5134 5134 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-30 01:12:44.006 5134 5134 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-30 01:12:44.473 5134 5134 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.
08-30 01:12:47.491 5134 5134 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-30 01:12:47.491 5134 5134 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-30 01:12:51.133 5134 5817 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-30 01:12:51.133 5134 5817 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-30 01:12:51.133 5134 5817 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-30 01:12:57.157 5134 6101 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=3b9b2b55-5126-4597-ac26-a110ae68cf2c, generation=0)
08-30 01:13:41.169 7660 7660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-30 01:13:43.852 7660 7660 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-30 01:13:43.853 7660 7660 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-30 01:13:43.853 7660 7660 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-30 01:13:43.853 7660 7660 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-30 01:13:43.853 7660 7660 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-30 01:13:43.853 7660 7660 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-30 01:13:43.853 7660 7660 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-30 01:13:43.853 7660 7660 W System.err: at
java.lang.Class.newInstance(Native Method)
08-30 01:13:43.853 7660 7660 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-30 01:13:43.853 7660 7660 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-30 01:13:43.853 7660 7660 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-30 01:13:43.853 7660 7660 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-30 01:13:43.853 7660 7660 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-30 01:13:43.854 7660 7660 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-30 01:13:43.854 7660 7660 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-30 01:13:43.854 7660 7660 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-30 01:13:43.854 7660 7660 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-30 01:13:43.854 7660 7660 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-30 01:13:43.854 7660 7660 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-30 01:13:43.854 7660 7660 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-30 01:13:43.854 7660 7660 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-30 01:13:43.854 7660 7660 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-30 01:13:44.484 7660 7660 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
08-30 01:13:48.125 7660 7660 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-30 01:13:48.126 7660 7660 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
08-30 01:13:50.185 7660 7964 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-30 01:13:50.185 7660 7964 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-30 01:13:50.185 7660 7964 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-30 01:13:51.607 7660 7670 W com.mbwhatsapp: Suspending all threads took:
13.203ms
08-30 11:15:03.504 10996 10996 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-30 11:15:05.928 10996 10996 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
08-30 23:43:22.825 3885 3885 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-30 23:43:27.201 3885 3885 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
08-30 23:43:27.202 3885 3885 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.Class.newInstance(Native Method)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
08-30 23:43:27.202 3885 3885 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
08-30 23:43:27.202 3885 3885 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
08-30 23:43:27.202 3885 3885 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
08-30 23:43:27.202 3885 3885 W System.err: at
android.os.Looper.loop(Looper.java:334)
08-30 23:43:27.202 3885 3885 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
08-30 23:43:27.202 3885 3885 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
08-30 23:43:27.202 3885 3885 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
08-30 23:43:27.202 3885 3885 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
08-30 23:43:28.457 3885 3885 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.
08-30 23:43:32.108 3885 3885 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
08-30 23:43:32.109 3885 3885 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
08-30 23:43:34.119 3885 4830 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-30 23:43:34.119 3885 4830 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-30 23:43:34.119 3885 4830 W com.mbwhatsapp: and incorrect proguard
optimizations.
08-30 23:45:55.211 10053 10053 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-30 23:45:58.285 10053 10053 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.
08-30 23:45:59.025 10053 10053 W com.mbwhatsapp: type=1400 audit(0.0:2460): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
08-30 23:45:59.051 10053 10053 W com.mbwhatsapp: type=1400 audit(0.0:2461): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
08-30 23:59:02.785 17748 17748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-30 23:59:03.331 17748 17748 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
08-31 00:50:02.438 3574 3574 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-31 00:50:03.890 3574 3574 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
08-31 01:38:05.878 13097 13097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-31 01:38:06.763 13097 13097 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.
08-31 01:38:08.199 13097 13195 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
08-31 01:38:08.199 13097 13195 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
08-31 01:38:08.199 13097 13195 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
08-31 02:37:51.089 18712 18712 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-31 02:37:51.963 18712 18712 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
08-31 03:43:37.711 24792 24792 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-31 03:43:39.045 24792 24792 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
08-31 05:38:10.923 31798 31798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
08-31 05:38:12.016 31798 31798 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
09-01 19:31:13.232 5295 5295 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-01 19:31:18.113 5295 5295 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
09-01 23:07:00.753 22604 22604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-01 23:07:02.993 22604 22604 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
09-02 00:41:07.588 24537 24537 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 00:41:09.156 24537 24537 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.
09-02 00:41:11.036 24537 24537 W com.mbwhatsapp: type=1400 audit(0.0:10416): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-02 02:38:03.645 18597 18597 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 02:38:06.018 18597 18597 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
09-02 03:38:07.232 25950 25950 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 03:38:07.879 25950 25950 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
09-02 03:39:56.867 26332 26332 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 03:39:57.106 26332 26332 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
09-02 03:42:37.684 26867 26867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 03:42:37.956 26867 26867 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
09-02 03:46:47.987 27362 27362 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 03:46:48.234 27362 27362 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
09-02 04:38:32.678 2024 2024 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 04:38:33.291 2024 2024 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
09-02 05:37:51.464 10218 10218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 05:37:51.984 10218 10218 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
09-02 06:38:51.202 16810 16810 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 06:38:51.898 16810 16810 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
09-02 07:37:59.010 23350 23350 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 07:37:59.848 23350 23350 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
09-02 08:37:51.184 28359 28359 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 08:37:51.727 28359 28359 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
09-02 09:37:51.042 3472 3472 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 09:37:51.618 3472 3472 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
09-02 10:37:51.032 9815 9815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-02 10:37:51.773 9815 9815 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
09-03 10:29:11.579 4626 4626 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 10:29:13.827 4626 4626 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-03 10:29:13.828 4626 4626 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-03 10:29:13.828 4626 4626 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-03 10:29:13.828 4626 4626 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-03 10:29:13.828 4626 4626 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-03 10:29:13.828 4626 4626 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-03 10:29:13.828 4626 4626 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-03 10:29:13.828 4626 4626 W System.err: at
java.lang.Class.newInstance(Native Method)
09-03 10:29:13.828 4626 4626 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-03 10:29:13.828 4626 4626 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-03 10:29:13.828 4626 4626 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-03 10:29:13.828 4626 4626 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-03 10:29:13.828 4626 4626 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-03 10:29:13.828 4626 4626 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-03 10:29:13.828 4626 4626 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-03 10:29:13.828 4626 4626 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-03 10:29:13.837 4626 4626 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-03 10:29:13.837 4626 4626 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-03 10:29:13.837 4626 4626 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-03 10:29:13.837 4626 4626 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-03 10:29:13.837 4626 4626 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-03 10:29:13.837 4626 4626 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-03 10:29:14.660 4626 4626 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.
09-03 10:29:19.085 4626 4626 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-03 10:29:19.089 4626 4626 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-03 10:29:21.128 4626 5220 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-03 10:29:21.128 4626 5220 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-03 10:29:21.128 4626 5220 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-03 10:29:23.582 4626 5329 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=09bcf889-9142-4439-99bc-b74e6e30e159, generation=0)
09-03 10:29:23.954 4626 5334 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-03 10:29:23.955 4626 5334 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-03 10:34:28.974 12795 12795 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 10:34:30.744 12795 12795 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
09-03 10:44:46.427 16405 16405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 10:44:47.314 16405 16405 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
09-03 11:23:36.833 18421 18421 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 11:23:37.212 18421 18421 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
09-03 12:23:44.768 21367 21367 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 12:23:45.218 21367 21367 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
09-03 13:23:42.817 29911 29911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 13:23:43.381 29911 29911 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
09-03 14:23:33.340 6115 6115 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-03 14:23:33.755 6115 6115 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
09-04 17:34:02.515 8478 8478 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-04 17:34:04.420 8478 8478 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.
09-04 17:34:09.903 8478 9057 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=17b6d027-32bd-4144-b491-54188ec13afd, generation=0)
--------- beginning of main
09-05 15:45:02.367 5254 5254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-05 15:45:04.437 5254 5254 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.
09-05 15:45:11.047 5254 5951 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-05 15:45:11.047 5254 5951 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-05 15:45:11.047 5254 5951 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-05 15:45:09.981 5254 5254 W com.mbwhatsapp: type=1400 audit(0.0:16557): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-05 18:54:13.645 5669 5669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-05 18:54:15.968 5669 5669 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-05 18:54:15.973 5669 5669 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.Class.newInstance(Native Method)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-05 18:54:15.973 5669 5669 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-05 18:54:15.973 5669 5669 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-05 18:54:15.973 5669 5669 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-05 18:54:15.973 5669 5669 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-05 18:54:15.973 5669 5669 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-05 18:54:15.973 5669 5669 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-05 18:54:15.973 5669 5669 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-05 18:54:15.973 5669 5669 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-05 18:54:16.185 5669 5669 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.
09-05 18:54:17.726 5669 5669 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-05 18:54:17.727 5669 5669 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-05 18:54:18.465 5669 5669 W com.mbwhatsapp: type=1400 audit(0.0:1615): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-05 18:54:18.465 5669 5669 W com.mbwhatsapp: type=1400 audit(0.0:1616): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-05 18:54:18.465 5669 5669 W com.mbwhatsapp: type=1400 audit(0.0:1617): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-05 18:54:18.465 5669 5669 W com.mbwhatsapp: type=1400 audit(0.0:1618): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
09-05 18:54:19.294 5669 5953 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-05 18:54:19.294 5669 5953 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-05 18:54:19.294 5669 5953 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-05 18:54:20.217 5669 5968 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-05 18:54:20.217 5669 5968 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-05 18:55:36.693 9205 9205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-05 18:55:36.973 9205 9205 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-05 18:55:36.974 9205 9205 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.Class.newInstance(Native Method)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-05 18:55:36.974 9205 9205 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-05 18:55:36.974 9205 9205 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-05 18:55:36.974 9205 9205 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-05 18:55:36.974 9205 9205 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-05 18:55:36.974 9205 9205 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-05 18:55:36.974 9205 9205 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-05 18:55:36.974 9205 9205 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-05 18:55:36.974 9205 9205 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-05 18:55:36.984 9205 9205 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.
09-05 18:55:37.258 9205 9205 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-05 18:55:37.259 9205 9205 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-05 18:55:37.358 9205 9205 W com.mbwhatsapp: type=1400 audit(0.0:2428): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-05 18:55:37.358 9205 9205 W com.mbwhatsapp: type=1400 audit(0.0:2429): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-05 18:55:37.358 9205 9205 W com.mbwhatsapp: type=1400 audit(0.0:2430): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-05 18:55:37.358 9205 9205 W com.mbwhatsapp: type=1400 audit(0.0:2431): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
09-05 18:55:37.428 9205 9275 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-05 18:55:37.428 9205 9275 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-05 18:55:37.428 9205 9275 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-05 18:55:37.780 9205 9294 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-05 18:55:37.780 9205 9294 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-05 19:48:06.673 2513 2513 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-05 19:48:07.294 2513 2513 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.
09-05 19:48:08.899 2513 2652 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-05 19:48:08.899 2513 2652 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-05 19:48:08.899 2513 2652 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-06 08:54:08.537 3839 3839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 08:54:10.230 3839 3839 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-06 08:54:10.231 3839 3839 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-06 08:54:10.231 3839 3839 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-06 08:54:10.231 3839 3839 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-06 08:54:10.231 3839 3839 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-06 08:54:10.231 3839 3839 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-06 08:54:10.231 3839 3839 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-06 08:54:10.231 3839 3839 W System.err: at
java.lang.Class.newInstance(Native Method)
09-06 08:54:10.231 3839 3839 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-06 08:54:10.231 3839 3839 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-06 08:54:10.231 3839 3839 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-06 08:54:10.231 3839 3839 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-06 08:54:10.232 3839 3839 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-06 08:54:10.232 3839 3839 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-06 08:54:10.232 3839 3839 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-06 08:54:10.232 3839 3839 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-06 08:54:10.232 3839 3839 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-06 08:54:10.232 3839 3839 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-06 08:54:10.232 3839 3839 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-06 08:54:10.232 3839 3839 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-06 08:54:10.232 3839 3839 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-06 08:54:10.232 3839 3839 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-06 08:54:10.775 3839 3839 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.
09-06 08:54:12.909 3839 3839 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-06 08:54:12.914 3839 3839 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-06 08:54:13.276 3839 3839 W com.mbwhatsapp: type=1400 audit(0.0:1215): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-06 08:54:13.352 3839 3839 W com.mbwhatsapp: type=1400 audit(0.0:1216): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-06 08:54:13.549 3839 3839 W com.mbwhatsapp: type=1400 audit(0.0:1217): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-06 08:54:13.902 3839 3839 W com.mbwhatsapp: type=1400 audit(0.0:1218): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-06 08:54:13.972 3839 3839 W com.mbwhatsapp: type=1400 audit(0.0:1219): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-06 08:54:16.727 3839 4428 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-06 08:54:16.727 3839 4428 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-06 08:54:16.727 3839 4428 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-06 08:54:26.417 3839 4836 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=55c17212-d6cd-462c-89d8-6a3abb39574b, generation=0)
09-06 08:56:22.472 8642 8642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 08:56:25.344 8642 8642 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
09-06 09:19:37.969 18261 18261 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 09:19:38.854 18261 18261 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
09-06 09:52:32.780 28962 28962 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 09:52:34.201 28962 28962 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
09-06 10:15:49.777 3855 3855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 10:15:50.642 3855 3855 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
09-06 19:52:18.791 21386 21386 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 19:52:19.733 21386 21386 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
09-06 21:49:11.347 12226 12226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 21:49:11.997 12226 12226 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
09-06 22:48:57.961 16729 16729 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-06 22:48:58.694 16729 16729 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
09-08 01:13:59.617 26354 26354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 01:14:03.299 26354 26354 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.
09-08 01:14:05.707 26354 26568 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=39b429c0-6d59-4000-a570-5449dbf99bbd, generation=0)
--------- beginning of main
09-08 02:49:30.948 13063 13063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 02:49:31.675 13063 13063 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.
09-08 02:49:33.087 13063 13143 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=2b30872a-b770-4b3f-8e64-7c1c4c1459bf, generation=0)
09-08 02:49:33.089 13063 13131 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=2b30872a-b770-4b3f-8e64-7c1c4c1459bf, generation=0)
--------- beginning of main
09-08 02:51:11.093 13432 13432 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 02:51:11.401 13432 13432 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
09-08 02:53:52.728 13659 13659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 02:53:53.033 13659 13659 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
09-08 03:49:36.055 16723 16723 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 03:49:36.356 16723 16723 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
09-08 03:51:36.124 16882 16882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 03:51:36.421 16882 16882 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
09-08 04:48:41.050 18445 18445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 04:48:41.672 18445 18445 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
09-08 05:48:41.050 23277 23277 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-08 05:48:41.569 23277 23277 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
09-09 09:48:13.255 18732 18732 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-09 09:48:13.990 18732 18732 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.
09-09 09:48:16.034 18732 18827 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=4b7ce6b6-0a22-4924-8199-d0228d213eb7, generation=0)
--------- beginning of main
09-09 14:04:34.136 5378 5378 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-09 14:04:37.400 5378 5378 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-09 14:04:37.405 5378 5378 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-09 14:04:37.405 5378 5378 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-09 14:04:37.405 5378 5378 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-09 14:04:37.405 5378 5378 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-09 14:04:37.405 5378 5378 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-09 14:04:37.405 5378 5378 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-09 14:04:37.405 5378 5378 W System.err: at
java.lang.Class.newInstance(Native Method)
09-09 14:04:37.405 5378 5378 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-09 14:04:37.405 5378 5378 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-09 14:04:37.405 5378 5378 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-09 14:04:37.406 5378 5378 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-09 14:04:37.406 5378 5378 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-09 14:04:37.406 5378 5378 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-09 14:04:37.406 5378 5378 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-09 14:04:37.406 5378 5378 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-09 14:04:37.406 5378 5378 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-09 14:04:37.406 5378 5378 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-09 14:04:37.406 5378 5378 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-09 14:04:37.406 5378 5378 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-09 14:04:37.406 5378 5378 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-09 14:04:37.406 5378 5378 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-09 14:04:37.640 5378 5378 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.
09-09 14:04:42.214 5378 5378 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-09 14:04:42.215 5378 5378 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-09 14:04:47.846 5378 6112 W com.mbwhatsapp: Verification of void
X.2rL.A04(byte[], int, int) took 192.764ms (321.64 bytecodes/s) (1624B approximate
peak alloc)
09-09 14:04:47.847 5378 6112 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-09 14:04:47.847 5378 6112 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-09 14:04:47.847 5378 6112 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-09 14:04:52.477 5378 6325 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-09 14:04:52.478 5378 6325 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-09 14:04:53.875 5378 5391 W com.mbwhatsapp: Suspending all threads took:
26.385ms
09-09 14:13:26.042 16761 16761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-09 14:13:29.151 16761 16761 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
09-09 17:48:18.833 11138 11138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-09 17:48:21.561 11138 11138 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.
09-09 17:48:23.382 11138 11485 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-09 17:48:23.382 11138 11485 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-09 17:48:23.382 11138 11485 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-10 08:10:40.974 16902 16902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-10 08:10:42.293 16902 16902 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.
09-10 08:10:45.406 16902 17316 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-10 08:10:45.406 16902 17316 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-10 08:10:45.406 16902 17316 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-10 09:51:24.073 6224 6224 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-10 09:51:25.861 6224 6224 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-10 09:51:25.862 6224 6224 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-10 09:51:25.862 6224 6224 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-10 09:51:25.863 6224 6224 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-10 09:51:25.863 6224 6224 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-10 09:51:25.863 6224 6224 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-10 09:51:25.863 6224 6224 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-10 09:51:25.863 6224 6224 W System.err: at
java.lang.Class.newInstance(Native Method)
09-10 09:51:25.863 6224 6224 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-10 09:51:25.863 6224 6224 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-10 09:51:25.863 6224 6224 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-10 09:51:25.863 6224 6224 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-10 09:51:25.863 6224 6224 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-10 09:51:25.863 6224 6224 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-10 09:51:25.863 6224 6224 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-10 09:51:25.863 6224 6224 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-10 09:51:25.863 6224 6224 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-10 09:51:25.864 6224 6224 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-10 09:51:25.864 6224 6224 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-10 09:51:25.864 6224 6224 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-10 09:51:25.864 6224 6224 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-10 09:51:25.864 6224 6224 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-10 09:51:26.385 6224 6224 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
09-10 09:51:29.218 6224 6224 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-10 09:51:29.220 6224 6224 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-10 09:51:30.362 6224 6224 W com.mbwhatsapp: type=1400 audit(0.0:1705): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-10 09:51:30.729 6224 6224 W com.mbwhatsapp: type=1400 audit(0.0:1706): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-10 09:51:30.729 6224 6224 W com.mbwhatsapp: type=1400 audit(0.0:1707): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-10 09:51:30.729 6224 6224 W com.mbwhatsapp: type=1400 audit(0.0:1708): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-10 09:51:30.729 6224 6224 W com.mbwhatsapp: type=1400 audit(0.0:1709): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
09-10 09:51:32.410 6224 6600 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-10 09:51:32.410 6224 6600 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-10 09:51:32.410 6224 6600 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-10 09:51:34.969 6224 6243 W com.mbwhatsapp: Suspending all threads took:
411.302ms
09-10 09:51:39.994 6224 6809 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-10 09:51:39.995 6224 6809 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-10 10:27:43.768 17543 17543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-10 10:27:44.310 17543 17543 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.
09-10 10:27:45.850 17543 17593 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-10 10:27:45.850 17543 17593 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-10 10:27:45.850 17543 17593 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-10 17:05:41.830 30729 30729 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-10 17:05:43.990 30729 30729 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.
09-10 17:05:47.434 30729 30729 W com.mbwhatsapp: type=1400 audit(0.0:21150): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-11 08:28:49.229 4931 4931 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 08:28:50.765 4931 4931 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-11 08:28:50.767 4931 4931 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-11 08:28:50.767 4931 4931 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-11 08:28:50.767 4931 4931 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-11 08:28:50.767 4931 4931 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-11 08:28:50.767 4931 4931 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-11 08:28:50.768 4931 4931 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-11 08:28:50.768 4931 4931 W System.err: at
java.lang.Class.newInstance(Native Method)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-11 08:28:50.768 4931 4931 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-11 08:28:50.768 4931 4931 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-11 08:28:50.768 4931 4931 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-11 08:28:50.768 4931 4931 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-11 08:28:50.768 4931 4931 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-11 08:28:50.768 4931 4931 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-11 08:28:50.768 4931 4931 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-11 08:28:50.768 4931 4931 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-11 08:28:50.909 4931 4931 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.
09-11 08:28:53.231 4931 4931 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-11 08:28:53.235 4931 4931 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-11 08:28:53.422 4931 4931 W com.mbwhatsapp: type=1400 audit(0.0:1341): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-11 08:28:53.466 4931 4931 W com.mbwhatsapp: type=1400 audit(0.0:1342): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-11 08:28:53.516 4931 4931 W com.mbwhatsapp: type=1400 audit(0.0:1343): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-11 08:28:53.832 4931 4931 W com.mbwhatsapp: type=1400 audit(0.0:1344): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-11 08:28:53.946 4931 4931 W com.mbwhatsapp: type=1400 audit(0.0:1345): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-11 08:28:54.874 4931 5189 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-11 08:28:54.874 4931 5189 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-11 08:28:54.874 4931 5189 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-11 08:28:55.767 4931 5271 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=b2968efe-7569-4a52-bea3-b31aa8881efc, generation=0)
09-11 08:41:02.374 14348 14348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 08:41:04.524 14348 14348 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
09-11 09:23:31.252 18002 18002 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 09:23:32.229 18002 18002 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
09-11 10:23:02.153 25174 25174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 10:23:02.976 25174 25174 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
09-11 10:47:04.426 29966 29966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 10:47:04.861 29966 29966 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
09-11 11:23:01.153 32342 32342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 11:23:01.851 32342 32342 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
09-11 12:23:34.437 6067 6067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 12:23:34.911 6067 6067 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
09-11 13:23:34.914 10575 10575 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-11 13:23:35.357 10575 10575 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
09-13 15:25:14.051 4850 4850 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-13 15:25:20.163 4850 4850 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-13 15:25:20.163 4850 4850 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-13 15:25:20.164 4850 4850 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-13 15:25:20.164 4850 4850 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-13 15:25:20.164 4850 4850 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-13 15:25:20.164 4850 4850 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-13 15:25:20.164 4850 4850 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-13 15:25:20.164 4850 4850 W System.err: at
java.lang.Class.newInstance(Native Method)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-13 15:25:20.164 4850 4850 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-13 15:25:20.164 4850 4850 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-13 15:25:20.164 4850 4850 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-13 15:25:20.164 4850 4850 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-13 15:25:20.164 4850 4850 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-13 15:25:20.164 4850 4850 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-13 15:25:20.164 4850 4850 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-13 15:25:20.164 4850 4850 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-13 15:25:20.646 4850 4850 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.
09-13 15:25:21.455 4850 5070 W LibraryVersion: Failed to get app version for
libraryName: firebase-iid
09-13 15:25:24.988 4850 4850 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-13 15:25:24.989 4850 4850 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-13 15:25:26.479 4850 5347 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-13 15:25:26.479 4850 5347 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-13 15:25:26.479 4850 5347 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-13 15:25:27.795 4850 5407 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=1a2352d8-6e5b-4c04-a148-eddaa9d3d041, generation=0)
09-13 15:25:28.169 4850 5415 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-13 15:25:28.170 4850 5415 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-13 16:32:50.315 4452 4452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-13 16:32:54.540 4452 4452 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
09-13 18:06:37.920 5133 5133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-13 18:06:40.758 5133 5133 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-13 18:06:40.759 5133 5133 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-13 18:06:40.759 5133 5133 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-13 18:06:40.759 5133 5133 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-13 18:06:40.759 5133 5133 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-13 18:06:40.759 5133 5133 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-13 18:06:40.759 5133 5133 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-13 18:06:40.759 5133 5133 W System.err: at
java.lang.Class.newInstance(Native Method)
09-13 18:06:40.759 5133 5133 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-13 18:06:40.759 5133 5133 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-13 18:06:40.759 5133 5133 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-13 18:06:40.760 5133 5133 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-13 18:06:40.760 5133 5133 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-13 18:06:40.760 5133 5133 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-13 18:06:40.760 5133 5133 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-13 18:06:40.760 5133 5133 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-13 18:06:40.760 5133 5133 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-13 18:06:40.760 5133 5133 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-13 18:06:40.760 5133 5133 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-13 18:06:40.760 5133 5133 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-13 18:06:40.760 5133 5133 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-13 18:06:40.760 5133 5133 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-13 18:06:41.058 5133 5133 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
09-13 18:06:45.213 5133 5133 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-13 18:06:45.213 5133 5133 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-13 18:06:47.115 5133 5133 W com.mbwhatsapp: type=1400 audit(0.0:1489): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-13 18:06:47.442 5133 5133 W com.mbwhatsapp: type=1400 audit(0.0:1490): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-13 18:06:47.442 5133 5133 W com.mbwhatsapp: type=1400 audit(0.0:1491): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-13 18:06:47.442 5133 5133 W com.mbwhatsapp: type=1400 audit(0.0:1492): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-13 18:06:47.442 5133 5133 W com.mbwhatsapp: type=1400 audit(0.0:1493): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
09-13 18:06:48.763 5133 5669 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-13 18:06:48.763 5133 5669 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-13 18:06:48.763 5133 5669 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-13 18:06:52.185 5133 5780 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-13 18:06:52.185 5133 5780 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-13 18:08:02.712 7396 7396 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-13 18:08:03.259 7396 7396 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-13 18:08:03.259 7396 7396 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-13 18:08:03.259 7396 7396 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-13 18:08:03.259 7396 7396 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-13 18:08:03.259 7396 7396 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-13 18:08:03.260 7396 7396 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-13 18:08:03.260 7396 7396 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-13 18:08:03.260 7396 7396 W System.err: at
java.lang.Class.newInstance(Native Method)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-13 18:08:03.260 7396 7396 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-13 18:08:03.260 7396 7396 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-13 18:08:03.260 7396 7396 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-13 18:08:03.260 7396 7396 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-13 18:08:03.260 7396 7396 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-13 18:08:03.260 7396 7396 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-13 18:08:03.260 7396 7396 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-13 18:08:03.260 7396 7396 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-13 18:08:03.331 7396 7396 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.
09-13 18:08:03.925 7396 7396 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-13 18:08:03.926 7396 7396 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-13 18:08:04.444 7396 7493 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-13 18:08:04.444 7396 7493 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-13 18:08:04.444 7396 7493 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-13 18:18:34.665 17428 17428 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-13 18:18:35.462 17428 17428 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
09-13 21:12:04.109 9599 9599 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-13 21:12:06.391 9599 9599 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
09-14 14:16:43.605 5970 5970 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-14 14:16:45.600 5970 5970 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-14 14:16:45.601 5970 5970 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-14 14:16:45.601 5970 5970 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-14 14:16:45.601 5970 5970 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-14 14:16:45.601 5970 5970 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-14 14:16:45.601 5970 5970 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-14 14:16:45.601 5970 5970 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-14 14:16:45.601 5970 5970 W System.err: at
java.lang.Class.newInstance(Native Method)
09-14 14:16:45.601 5970 5970 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-14 14:16:45.601 5970 5970 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-14 14:16:45.601 5970 5970 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-14 14:16:45.601 5970 5970 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-14 14:16:45.602 5970 5970 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-14 14:16:45.602 5970 5970 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-14 14:16:45.602 5970 5970 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-14 14:16:45.602 5970 5970 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-14 14:16:45.602 5970 5970 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-14 14:16:45.602 5970 5970 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-14 14:16:45.602 5970 5970 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-14 14:16:45.602 5970 5970 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-14 14:16:45.602 5970 5970 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-14 14:16:45.602 5970 5970 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-14 14:16:45.885 5970 5970 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.
09-14 14:16:47.301 5970 5970 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-14 14:16:47.302 5970 5970 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-14 14:16:48.265 5970 5970 W com.mbwhatsapp: type=1400 audit(0.0:1576): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-14 14:16:48.265 5970 5970 W com.mbwhatsapp: type=1400 audit(0.0:1577): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-14 14:16:48.265 5970 5970 W com.mbwhatsapp: type=1400 audit(0.0:1578): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-14 14:16:48.265 5970 5970 W com.mbwhatsapp: type=1400 audit(0.0:1579): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
09-14 14:16:49.617 5970 6316 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-14 14:16:49.617 5970 6316 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-14 14:16:49.617 5970 6316 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-14 14:16:51.866 5970 6553 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=b41eb732-d02b-4b7e-a419-ebcb9be6b050, generation=0)
09-14 14:24:17.589 14121 14121 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-14 14:24:18.221 14121 14121 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.
09-14 14:24:19.465 14121 14168 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-14 14:24:19.465 14121 14168 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-14 14:24:19.465 14121 14168 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-14 15:10:42.507 24222 24222 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-14 15:10:43.239 24222 24222 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
09-14 19:14:51.958 7024 7024 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-14 19:14:52.979 7024 7024 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.
09-14 19:14:55.345 7024 7231 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-14 19:14:55.345 7024 7231 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-14 19:14:55.345 7024 7231 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-16 06:27:51.040 4350 4350 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 06:27:52.511 4350 4350 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
09-16 06:52:40.211 11915 11915 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 06:52:40.903 11915 11915 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
09-16 16:10:58.599 5185 5185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 16:11:02.105 5185 5185 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-16 16:11:02.108 5185 5185 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-16 16:11:02.108 5185 5185 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-16 16:11:02.108 5185 5185 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-16 16:11:02.109 5185 5185 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-16 16:11:02.109 5185 5185 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-16 16:11:02.109 5185 5185 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-16 16:11:02.109 5185 5185 W System.err: at
java.lang.Class.newInstance(Native Method)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-16 16:11:02.109 5185 5185 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-16 16:11:02.109 5185 5185 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-16 16:11:02.109 5185 5185 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-16 16:11:02.109 5185 5185 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-16 16:11:02.109 5185 5185 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-16 16:11:02.109 5185 5185 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-16 16:11:02.109 5185 5185 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-16 16:11:02.109 5185 5185 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-16 16:11:02.396 5185 5185 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
09-16 16:11:09.019 5185 5185 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-16 16:11:09.031 5185 5185 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-16 16:11:10.552 5185 5185 W com.mbwhatsapp: type=1400 audit(0.0:1631): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-16 16:11:10.552 5185 5185 W com.mbwhatsapp: type=1400 audit(0.0:1632): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-16 16:11:13.353 5185 6077 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-16 16:11:13.353 5185 6077 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-16 16:11:13.353 5185 6077 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-16 16:11:16.723 5185 6266 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=33695352-9d30-4140-aea6-f3aff997d290, generation=0)
09-16 16:11:18.243 5185 6273 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-16 16:11:18.244 5185 6273 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-16 16:12:09.563 8246 8246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 16:12:10.663 8246 8246 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-16 16:12:10.664 8246 8246 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-16 16:12:10.664 8246 8246 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-16 16:12:10.665 8246 8246 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-16 16:12:10.665 8246 8246 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-16 16:12:10.665 8246 8246 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-16 16:12:10.665 8246 8246 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-16 16:12:10.665 8246 8246 W System.err: at
java.lang.Class.newInstance(Native Method)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-16 16:12:10.665 8246 8246 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-16 16:12:10.665 8246 8246 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-16 16:12:10.665 8246 8246 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-16 16:12:10.665 8246 8246 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-16 16:12:10.665 8246 8246 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-16 16:12:10.665 8246 8246 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-16 16:12:10.665 8246 8246 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-16 16:12:10.665 8246 8246 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-16 16:12:10.849 8246 8246 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.
09-16 16:12:12.177 8246 8246 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-16 16:12:12.178 8246 8246 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-16 18:17:00.890 6311 6311 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 18:17:01.619 6311 6311 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-16 18:17:01.619 6311 6311 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-16 18:17:01.619 6311 6311 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-16 18:17:01.620 6311 6311 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-16 18:17:01.620 6311 6311 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-16 18:17:01.620 6311 6311 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-16 18:17:01.620 6311 6311 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-16 18:17:01.620 6311 6311 W System.err: at
java.lang.Class.newInstance(Native Method)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-16 18:17:01.620 6311 6311 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-16 18:17:01.620 6311 6311 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-16 18:17:01.620 6311 6311 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-16 18:17:01.620 6311 6311 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-16 18:17:01.620 6311 6311 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-16 18:17:01.620 6311 6311 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-16 18:17:01.620 6311 6311 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-16 18:17:01.620 6311 6311 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-16 18:17:01.707 6311 6311 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.
09-16 18:17:02.673 6311 6311 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-16 18:17:02.674 6311 6311 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-16 18:17:02.797 6311 6311 W com.mbwhatsapp: type=1400 audit(0.0:1792): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-16 18:17:02.817 6311 6311 W com.mbwhatsapp: type=1400 audit(0.0:1793): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-16 18:17:02.840 6311 6311 W com.mbwhatsapp: type=1400 audit(0.0:1794): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-16 18:17:03.033 6311 6311 W com.mbwhatsapp: type=1400 audit(0.0:1795): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-16 18:17:03.083 6311 6311 W com.mbwhatsapp: type=1400 audit(0.0:1796): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-16 18:17:03.337 6311 6539 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-16 18:17:03.337 6311 6539 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-16 18:17:03.337 6311 6539 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-16 18:17:04.504 6311 6565 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-16 18:17:04.505 6311 6565 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-16 18:17:52.315 9179 9179 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 18:17:52.792 9179 9179 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
09-16 18:18:37.726 11702 11702 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 18:18:39.189 11702 11702 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
09-16 23:23:04.414 24672 24672 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 23:23:05.975 24672 24672 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.
09-16 23:23:08.957 24672 24672 W com.mbwhatsapp: type=1400 audit(0.0:47023): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-16 23:25:29.482 25737 25737 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 23:25:30.053 25737 25737 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
09-16 23:39:55.418 27121 27121 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-16 23:39:55.938 27121 27121 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
09-17 01:22:47.729 11049 11049 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 01:22:51.161 11049 11049 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
09-17 02:10:26.131 14587 14587 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 02:10:26.795 14587 14587 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
09-17 06:32:54.577 16466 16466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 06:33:00.965 16466 16466 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
09-17 08:23:50.926 5782 5782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 08:23:52.079 5782 5782 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-17 08:23:52.083 5782 5782 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-17 08:23:52.084 5782 5782 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-17 08:23:52.084 5782 5782 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-17 08:23:52.084 5782 5782 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-17 08:23:52.084 5782 5782 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-17 08:23:52.084 5782 5782 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-17 08:23:52.084 5782 5782 W System.err: at
java.lang.Class.newInstance(Native Method)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-17 08:23:52.084 5782 5782 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-17 08:23:52.084 5782 5782 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-17 08:23:52.084 5782 5782 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-17 08:23:52.084 5782 5782 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-17 08:23:52.084 5782 5782 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-17 08:23:52.084 5782 5782 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-17 08:23:52.084 5782 5782 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-17 08:23:52.084 5782 5782 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-17 08:23:52.309 5782 5782 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.
09-17 08:23:53.709 5782 5782 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-17 08:23:53.710 5782 5782 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-17 08:23:54.072 5782 5782 W com.mbwhatsapp: type=1400 audit(0.0:1630): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-17 08:23:54.328 5782 5782 W com.mbwhatsapp: type=1400 audit(0.0:1631): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-17 08:23:54.382 5782 5782 W com.mbwhatsapp: type=1400 audit(0.0:1632): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-17 08:23:54.382 5782 5782 W com.mbwhatsapp: type=1400 audit(0.0:1633): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-17 08:23:55.472 5782 6030 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-17 08:23:55.472 5782 6030 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-17 08:23:55.472 5782 6030 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-17 08:39:07.036 12952 12952 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 08:39:07.590 12952 12952 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
09-17 09:18:08.946 15656 15656 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 09:18:09.535 15656 15656 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
09-17 10:09:36.823 18710 18710 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 10:09:37.146 18710 18710 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
09-17 11:17:10.842 23350 23350 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 11:17:11.215 23350 23350 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
09-17 12:17:15.004 10118 10118 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 12:17:15.456 10118 10118 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
09-17 13:17:10.858 14371 14371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 13:17:11.370 14371 14371 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.
09-17 13:17:12.503 14371 14419 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-17 13:17:12.503 14371 14419 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-17 13:17:12.503 14371 14419 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-17 14:16:40.823 18770 18770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-17 14:16:41.170 18770 18770 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
09-18 09:37:54.938 19566 19566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-18 09:37:58.420 19566 19566 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
09-18 10:04:20.158 29610 29610 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-18 10:04:21.459 29610 29610 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
09-19 01:25:16.770 16216 16216 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-19 01:25:20.946 16216 16216 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.
09-19 01:25:31.410 16216 16216 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-19 01:25:31.418 16216 16216 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
09-19 01:25:31.889 16216 16226 W com.mbwhatsapp: Suspending all threads took:
187.365ms
--------- beginning of main
09-19 02:53:27.195 23991 23991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-19 02:53:28.117 23991 23991 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
09-19 03:51:25.846 27414 27414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-19 03:51:26.554 27414 27414 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
09-19 04:51:17.508 29609 29609 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-19 04:51:18.140 29609 29609 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
09-19 10:04:29.266 14725 14725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-19 10:04:29.959 14725 14725 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
09-20 02:00:16.099 23205 23205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 02:00:17.038 23205 23205 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
09-20 03:01:46.322 10666 10666 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 03:01:51.894 10666 10666 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
09-20 03:02:04.841 10666 10683 W com.mbwhatsapp: Suspending all threads took:
255.188ms
09-20 03:02:05.034 10666 10683 W com.mbwhatsapp: Suspending all threads took:
29.172ms
09-20 03:02:09.584 10666 12147 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-20 03:02:09.585 10666 12147 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-20 03:02:14.315 10666 10683 W com.mbwhatsapp: Suspending all threads took:
6.036ms
09-20 03:52:06.032 20743 20743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 03:52:06.786 20743 20743 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
09-20 04:51:57.616 27251 27251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 04:51:58.415 27251 27251 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
09-20 05:51:26.180 30521 30521 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 05:51:26.882 30521 30521 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
09-20 06:51:23.199 3945 3945 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 06:51:23.808 3945 3945 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
09-20 08:51:21.427 10937 10937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 08:51:22.264 10937 10937 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
09-20 09:51:27.027 15461 15461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 09:51:27.720 15461 15461 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
09-20 19:54:39.519 9795 9795 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-20 19:54:40.806 9795 9795 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
09-22 16:11:23.883 8740 8740 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 16:11:26.189 8740 8740 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
09-22 16:17:15.464 14725 14725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 16:17:15.918 14725 14725 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
09-22 17:01:42.192 24701 24701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 17:01:43.927 24701 24701 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.
09-22 17:01:49.344 24701 24701 W com.mbwhatsapp: type=1400 audit(0.0:18452): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-22 17:01:49.484 24701 24701 W com.mbwhatsapp: type=1400 audit(0.0:18453): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-22 17:01:49.771 24701 24701 W com.mbwhatsapp: type=1400 audit(0.0:18454): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-22 17:01:49.917 24701 24701 W com.mbwhatsapp: type=1400 audit(0.0:18455): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-22 17:01:49.924 24701 24701 W com.mbwhatsapp: type=1400 audit(0.0:18456): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
09-22 17:53:51.009 9410 9410 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 17:53:52.268 9410 9410 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
09-22 17:55:31.279 13772 13772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 17:55:32.433 13772 13772 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
09-22 20:41:52.581 3878 3878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 20:41:54.953 3878 3878 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-22 20:41:54.953 3878 3878 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-22 20:41:54.954 3878 3878 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-22 20:41:54.954 3878 3878 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-22 20:41:54.954 3878 3878 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-22 20:41:54.954 3878 3878 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-22 20:41:54.954 3878 3878 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-22 20:41:54.954 3878 3878 W System.err: at
java.lang.Class.newInstance(Native Method)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-22 20:41:54.954 3878 3878 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-22 20:41:54.954 3878 3878 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-22 20:41:54.954 3878 3878 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-22 20:41:54.954 3878 3878 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-22 20:41:54.954 3878 3878 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-22 20:41:54.954 3878 3878 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-22 20:41:54.954 3878 3878 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-22 20:41:54.954 3878 3878 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-22 20:41:55.215 3878 3878 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.
09-22 20:41:57.892 3878 3878 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-22 20:41:57.894 3878 3878 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-22 20:42:01.110 3878 4583 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-22 20:42:01.110 3878 4583 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-22 20:42:01.110 3878 4583 W com.mbwhatsapp: and incorrect proguard
optimizations.
09-22 20:42:05.008 3878 4595 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-22 20:42:05.009 3878 4595 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
09-22 20:45:35.302 9799 9799 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 20:45:40.553 9799 9799 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
09-22 20:53:16.042 17800 17800 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 20:53:18.532 17800 17800 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
09-22 23:48:56.866 18670 18670 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-22 23:48:59.238 18670 18670 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
09-24 01:49:21.282 6263 6263 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 01:49:23.846 6263 6263 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
09-24 02:16:33.231 15641 15641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 02:16:33.729 15641 15641 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.
09-24 02:16:34.911 15641 15690 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-24 02:16:34.911 15641 15690 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-24 02:16:34.911 15641 15690 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-24 09:47:49.519 23320 23320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 09:47:50.453 23320 23320 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
09-24 11:42:05.282 6118 6118 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 11:42:05.868 6118 6118 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
09-24 11:43:25.360 6200 6200 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 11:43:25.652 6200 6200 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
09-24 11:47:05.723 6376 6376 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 11:47:06.002 6376 6376 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
09-24 11:50:46.005 6556 6556 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 11:50:46.270 6556 6556 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
09-24 12:42:10.331 10619 10619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 12:42:10.931 10619 10619 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
09-24 12:47:10.831 10926 10926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-24 12:47:11.127 10926 10926 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
09-25 01:29:58.406 9048 9048 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 01:30:03.442 9048 9048 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
09-25 01:47:36.258 14770 14770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 01:47:36.988 14770 14770 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
09-25 02:45:29.480 23538 23538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 02:45:30.239 23538 23538 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
09-25 02:47:37.347 23873 23873 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 02:47:37.630 23873 23873 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
09-25 02:50:13.829 24197 24197 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 02:50:14.198 24197 24197 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
09-25 03:44:54.575 28856 28856 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 03:44:55.308 28856 28856 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
09-25 04:44:41.226 1805 1805 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 04:44:41.814 1805 1805 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
09-25 05:42:30.904 6604 6604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-25 05:42:31.803 6604 6604 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
09-26 12:54:08.632 13034 13034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-26 12:54:10.499 13034 13034 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
09-26 13:13:59.870 21612 21612 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-26 13:14:00.519 21612 21612 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.
09-26 13:14:01.439 21612 21668 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-26 13:14:01.439 21612 21668 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-26 13:14:01.439 21612 21668 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-26 13:39:57.601 24011 24011 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-26 13:39:58.120 24011 24011 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
09-26 14:40:04.365 29736 29736 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-26 14:40:04.982 29736 29736 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
09-27 00:46:04.452 6290 6290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 00:46:07.016 6290 6290 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
09-27 00:47:00.099 9202 9202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 00:47:02.905 9202 9202 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
09-27 01:58:14.280 4242 4242 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 01:58:16.851 4242 4242 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
09-27 01:58:50.906 6248 6248 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 01:58:51.324 6248 6248 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
09-27 01:59:54.733 9272 9272 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 01:59:55.459 9272 9272 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
09-27 02:05:25.451 14995 14995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 02:05:26.104 14995 14995 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
09-27 02:54:00.635 19284 19284 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 02:54:01.465 19284 19284 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
09-27 03:53:51.155 22504 22504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 03:53:51.541 22504 22504 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
09-27 04:53:59.912 26136 26136 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 04:54:00.757 26136 26136 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
09-27 05:53:59.832 29903 29903 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 05:54:00.213 29903 29903 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
09-27 06:53:57.217 3468 3468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 06:53:57.823 3468 3468 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
09-27 09:14:27.250 13277 13277 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 09:14:28.438 13277 13277 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
09-27 09:48:19.419 17525 17525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 09:48:20.569 17525 17525 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
09-27 10:49:25.779 21328 21328 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 10:49:26.075 21328 21328 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
09-28 10:33:27.501 4468 4468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-28 10:33:30.577 4468 4468 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
09-28 10:33:30.604 4468 4468 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
09-28 10:33:30.604 4468 4468 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
09-28 10:33:30.604 4468 4468 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
09-28 10:33:30.604 4468 4468 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-28 10:33:30.604 4468 4468 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
09-28 10:33:30.604 4468 4468 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
09-28 10:33:30.604 4468 4468 W System.err: at
java.lang.Class.newInstance(Native Method)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
09-28 10:33:30.604 4468 4468 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
09-28 10:33:30.604 4468 4468 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
09-28 10:33:30.604 4468 4468 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
09-28 10:33:30.604 4468 4468 W System.err: at
android.os.Looper.loop(Looper.java:334)
09-28 10:33:30.604 4468 4468 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
09-28 10:33:30.605 4468 4468 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
09-28 10:33:30.605 4468 4468 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
09-28 10:33:30.605 4468 4468 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
09-28 10:33:30.975 4468 4468 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.
09-28 10:33:31.773 4468 4821 W LibraryVersion: Failed to get app version for
libraryName: firebase-iid
09-28 10:33:35.792 4468 4468 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
09-28 10:33:35.793 4468 4468 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
09-28 19:31:25.368 19016 19016 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-28 19:31:27.459 19016 19016 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.
09-28 19:31:30.679 19016 19334 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-28 19:31:30.679 19016 19334 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-28 19:31:30.679 19016 19334 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-28 19:55:10.355 26178 26178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-28 19:55:11.251 26178 26178 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
09-29 09:45:29.030 659 659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-29 09:45:30.926 659 659 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.
09-29 09:45:34.805 659 1975 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-29 09:45:34.805 659 1975 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-29 09:45:34.805 659 1975 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
09-29 11:28:00.495 17871 17871 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-29 11:28:01.313 17871 17871 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
09-29 12:27:33.779 26028 26028 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-29 12:27:34.546 26028 26028 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
09-29 13:27:30.423 30886 30886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-29 13:27:30.982 30886 30886 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
10-01 08:41:25.396 6208 6208 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 08:41:27.076 6208 6208 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-01 08:41:27.081 6208 6208 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-01 08:41:27.083 6208 6208 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-01 08:41:27.083 6208 6208 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-01 08:41:27.084 6208 6208 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-01 08:41:27.084 6208 6208 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-01 08:41:27.084 6208 6208 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-01 08:41:27.084 6208 6208 W System.err: at
java.lang.Class.newInstance(Native Method)
10-01 08:41:27.084 6208 6208 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-01 08:41:27.086 6208 6208 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-01 08:41:27.086 6208 6208 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-01 08:41:27.087 6208 6208 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-01 08:41:27.088 6208 6208 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-01 08:41:27.091 6208 6208 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-01 08:41:27.092 6208 6208 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-01 08:41:27.092 6208 6208 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-01 08:41:27.092 6208 6208 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-01 08:41:27.092 6208 6208 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-01 08:41:27.093 6208 6208 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-01 08:41:27.093 6208 6208 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-01 08:41:27.093 6208 6208 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-01 08:41:27.093 6208 6208 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-01 08:41:31.263 6208 6208 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.
10-01 08:41:33.690 6208 6208 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-01 08:41:33.690 6208 6208 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-01 08:41:33.912 6208 6208 W com.mbwhatsapp: type=1400 audit(0.0:1687): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-01 08:41:33.942 6208 6208 W com.mbwhatsapp: type=1400 audit(0.0:1689): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-01 08:41:33.992 6208 6208 W com.mbwhatsapp: type=1400 audit(0.0:1690): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-01 08:41:34.302 6208 6208 W com.mbwhatsapp: type=1400 audit(0.0:1691): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-01 08:41:35.096 6208 6554 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-01 08:41:35.096 6208 6554 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-01 08:41:35.096 6208 6554 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-01 08:41:36.173 6208 6218 W com.mbwhatsapp: Suspending all threads took:
6.195ms
10-01 08:41:37.695 6208 6671 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=76676dce-be90-4410-8390-684c91634ea1, generation=0)
10-01 08:41:37.870 6208 6674 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-01 08:41:37.870 6208 6674 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-01 09:34:59.082 24138 24138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 09:34:59.946 24138 24138 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.
10-01 09:35:01.139 24138 24253 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-01 09:35:01.139 24138 24253 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-01 09:35:01.139 24138 24253 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-01 10:35:32.207 29215 29215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 10:35:32.983 29215 29215 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
10-01 10:37:43.238 29564 29564 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 10:37:43.513 29564 29564 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
10-01 10:40:44.091 30487 30487 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 10:40:44.358 30487 30487 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
10-01 10:48:06.519 1413 1413 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 10:48:06.954 1413 1413 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
10-01 11:35:10.442 10159 10159 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-01 11:35:11.167 10159 10159 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
10-02 13:24:44.074 31581 31581 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-02 13:24:45.656 31581 31581 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.
10-02 13:24:49.785 31581 31952 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-02 13:24:49.786 31581 31952 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-02 13:42:58.350 10412 10412 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-02 13:42:59.037 10412 10412 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
10-02 20:10:19.071 14147 14147 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-02 20:10:21.131 14147 14147 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
10-02 20:23:42.705 17893 17893 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-02 20:23:43.596 17893 17893 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.
10-02 20:23:45.140 17893 17968 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-02 20:23:45.140 17893 17968 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-02 21:35:31.303 30957 30957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-02 21:35:32.100 30957 30957 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
10-03 02:37:16.371 21108 21108 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-03 02:37:17.927 21108 21108 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
10-03 13:10:25.527 24665 24665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-03 13:10:28.635 24665 24665 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
10-03 13:42:59.906 5921 5921 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-03 13:43:01.009 5921 5921 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
10-05 01:49:11.993 27326 27326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-05 01:49:14.003 27326 27326 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
10-06 15:58:57.869 6341 6341 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-06 15:58:59.855 6341 6341 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-06 15:58:59.857 6341 6341 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-06 15:58:59.857 6341 6341 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-06 15:58:59.857 6341 6341 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-06 15:58:59.857 6341 6341 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-06 15:58:59.857 6341 6341 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-06 15:58:59.857 6341 6341 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-06 15:58:59.857 6341 6341 W System.err: at
java.lang.Class.newInstance(Native Method)
10-06 15:58:59.857 6341 6341 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-06 15:58:59.857 6341 6341 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-06 15:58:59.857 6341 6341 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-06 15:58:59.857 6341 6341 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-06 15:58:59.857 6341 6341 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-06 15:58:59.857 6341 6341 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-06 15:58:59.857 6341 6341 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-06 15:58:59.857 6341 6341 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-06 15:58:59.857 6341 6341 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-06 15:58:59.857 6341 6341 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-06 15:58:59.858 6341 6341 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-06 15:58:59.858 6341 6341 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-06 15:58:59.858 6341 6341 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-06 15:58:59.858 6341 6341 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-06 15:59:00.101 6341 6341 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.
10-06 15:59:00.786 6341 6448 W LibraryVersion: Failed to get app version for
libraryName: firebase-iid
10-06 15:59:01.977 6341 6341 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-06 15:59:01.981 6341 6341 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-06 15:59:02.318 6341 6341 W com.mbwhatsapp: type=1400 audit(0.0:1739): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-06 15:59:02.348 6341 6341 W com.mbwhatsapp: type=1400 audit(0.0:1740): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-06 15:59:02.418 6341 6341 W com.mbwhatsapp: type=1400 audit(0.0:1741): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-06 15:59:03.285 6341 6599 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-06 15:59:03.285 6341 6599 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-06 15:59:03.285 6341 6599 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-06 15:59:04.723 6341 6721 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=20845848-ba0e-4c9e-8a03-5f9fa208e8e6, generation=0)
10-06 15:59:05.342 6341 6728 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-06 15:59:05.343 6341 6728 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-06 16:05:32.182 14674 14674 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-06 16:05:32.897 14674 14674 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
10-06 16:12:48.872 19736 19736 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-06 16:12:49.508 19736 19736 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
10-07 01:35:59.387 4090 4090 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 01:36:03.065 4090 4090 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-07 01:36:03.066 4090 4090 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-07 01:36:03.066 4090 4090 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-07 01:36:03.066 4090 4090 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-07 01:36:03.067 4090 4090 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-07 01:36:03.067 4090 4090 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-07 01:36:03.067 4090 4090 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-07 01:36:03.067 4090 4090 W System.err: at
java.lang.Class.newInstance(Native Method)
10-07 01:36:03.067 4090 4090 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-07 01:36:03.067 4090 4090 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-07 01:36:03.067 4090 4090 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-07 01:36:03.068 4090 4090 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-07 01:36:03.068 4090 4090 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-07 01:36:03.068 4090 4090 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-07 01:36:03.068 4090 4090 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-07 01:36:03.068 4090 4090 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-07 01:36:03.068 4090 4090 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-07 01:36:03.068 4090 4090 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-07 01:36:03.068 4090 4090 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-07 01:36:03.068 4090 4090 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-07 01:36:03.068 4090 4090 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-07 01:36:03.068 4090 4090 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-07 01:36:03.473 4090 4090 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.
10-07 01:36:05.009 4090 4090 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-07 01:36:05.028 4090 4090 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-07 01:36:06.703 4090 4593 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-07 01:36:06.703 4090 4593 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-07 01:36:06.703 4090 4593 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-07 01:36:09.640 4090 4781 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=7b43b61d-36e7-4db6-9121-f8a5ee319e13, generation=0)
10-07 01:36:09.650 4090 4680 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=7b43b61d-36e7-4db6-9121-f8a5ee319e13, generation=0)
10-07 01:36:09.858 4090 4782 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-07 01:36:09.858 4090 4782 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-07 01:38:36.047 10802 10802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 01:38:37.920 10802 10802 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.
10-07 01:38:39.043 10802 11034 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-07 01:38:39.043 10802 11034 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-07 01:38:39.043 10802 11034 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-07 01:44:51.799 14566 14566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 01:44:53.304 14566 14566 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
10-07 01:54:14.858 16305 16305 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 01:54:15.239 16305 16305 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
10-07 02:32:29.230 19431 19431 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 02:32:30.087 19431 19431 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.
10-07 02:32:31.169 19431 19542 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-07 02:32:31.169 19431 19542 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-07 02:32:31.169 19431 19542 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-07 03:31:02.035 23355 23355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 03:31:02.988 23355 23355 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
10-07 04:34:55.485 25999 25999 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 04:34:56.302 25999 25999 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
10-07 05:34:55.567 28912 28912 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 05:34:56.013 28912 28912 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
10-07 06:32:32.632 31850 31850 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 06:32:33.141 31850 31850 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
10-07 07:34:58.411 2378 2378 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 07:34:59.055 2378 2378 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
10-07 08:31:30.027 6701 6701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-07 08:31:30.988 6701 6701 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
10-08 08:26:27.298 10857 10857 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-08 08:26:30.176 10857 10857 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.
10-08 08:26:34.241 10857 10857 W com.mbwhatsapp: type=1400 audit(0.0:85176): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-08 10:19:17.627 31911 31911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-08 10:19:18.817 31911 31911 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
10-09 02:02:19.004 11748 11748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 02:02:32.680 11748 11748 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
10-09 02:03:18.347 13743 13743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 02:03:20.284 13743 13743 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
10-09 02:04:26.914 15828 15828 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 02:04:27.699 15828 15828 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.
10-09 02:04:37.627 15828 15828 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-09 02:04:37.628 15828 15828 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-09 02:05:18.154 17084 17084 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 02:05:18.648 17084 17084 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
10-09 02:19:34.337 20465 20465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 02:19:34.962 20465 20465 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
10-09 04:30:43.549 5254 5254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 04:30:44.996 5254 5254 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.
10-09 04:30:51.228 5254 5824 W com.mbwhatsapp: Verification of void
X.2rL.A04(byte[], int, int) took 103.569ms (598.63 bytecodes/s) (1624B approximate
peak alloc)
10-09 04:30:51.229 5254 5824 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-09 04:30:51.229 5254 5824 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-09 04:30:51.229 5254 5824 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-09 06:19:43.870 24573 24573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 06:19:44.429 24573 24573 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
10-09 14:18:17.382 6455 6455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 14:18:19.491 6455 6455 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
10-09 14:20:03.785 10309 10309 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 14:20:04.835 10309 10309 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
10-09 14:22:56.682 13456 13456 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 14:22:57.553 13456 13456 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
10-09 19:10:43.455 16685 16685 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-09 19:10:45.779 16685 16685 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.
10-09 19:10:47.700 16685 16685 W com.mbwhatsapp: type=1400 audit(0.0:3640): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-10 09:41:02.973 17546 17546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-10 09:41:05.127 17546 17546 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
10-10 09:53:15.343 25911 25911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-10 09:53:15.956 25911 25911 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
10-10 11:02:01.101 6555 6555 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-10 11:02:02.181 6555 6555 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
10-10 12:17:09.010 18343 18343 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-10 12:17:10.231 18343 18343 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
10-10 13:01:32.156 22130 22130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-10 13:01:32.821 22130 22130 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
10-11 08:35:52.198 16212 16212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-11 08:35:56.691 16212 16212 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.
10-11 08:36:05.274 16212 16212 W com.mbwhatsapp: type=1400 audit(0.0:114791): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-12 09:33:42.445 15483 15483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-12 09:33:44.823 15483 15483 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.
10-12 09:33:49.382 15483 16032 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=15ee7f48-9b48-4202-a656-c2e4c9f6926f, generation=0)
10-12 09:33:49.769 15483 16034 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-12 09:33:49.770 15483 16034 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-12 22:26:03.386 7565 7565 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-12 22:26:04.391 7565 7565 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.
10-12 22:26:05.525 7565 7782 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-12 22:26:05.525 7565 7782 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-12 22:26:05.525 7565 7782 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-12 22:26:05.971 7565 7821 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=458e0879-df2b-4811-8271-379bb7398473, generation=0)
--------- beginning of main
10-13 01:24:31.414 4476 4476 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 01:24:33.194 4476 4476 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-13 01:24:33.195 4476 4476 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.Class.newInstance(Native Method)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-13 01:24:33.195 4476 4476 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-13 01:24:33.195 4476 4476 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-13 01:24:33.195 4476 4476 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-13 01:24:33.195 4476 4476 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-13 01:24:33.195 4476 4476 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-13 01:24:33.195 4476 4476 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-13 01:24:33.195 4476 4476 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-13 01:24:33.195 4476 4476 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-13 01:24:33.369 4476 4476 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.
10-13 01:24:34.275 4476 4476 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-13 01:24:34.275 4476 4476 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-13 01:24:34.907 4476 4640 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-13 01:24:34.907 4476 4640 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-13 01:24:34.907 4476 4640 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-13 01:25:22.383 6952 6952 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 01:25:23.540 6952 6952 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-13 01:25:23.547 6952 6952 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.Class.newInstance(Native Method)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-13 01:25:23.547 6952 6952 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-13 01:25:23.547 6952 6952 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-13 01:25:23.547 6952 6952 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-13 01:25:23.547 6952 6952 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-13 01:25:23.547 6952 6952 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-13 01:25:23.547 6952 6952 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-13 01:25:23.547 6952 6952 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-13 01:25:23.548 6952 6952 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-13 01:25:23.929 6952 6952 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.
10-13 01:25:25.448 6952 6952 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-13 01:25:25.448 6952 6952 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-13 01:25:25.615 6952 6952 W com.mbwhatsapp: type=1400 audit(0.0:1960): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-13 01:25:25.635 6952 6952 W com.mbwhatsapp: type=1400 audit(0.0:1961): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-13 01:25:25.652 6952 6952 W com.mbwhatsapp: type=1400 audit(0.0:1962): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-13 01:25:25.769 6952 6952 W com.mbwhatsapp: type=1400 audit(0.0:1963): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-13 01:25:25.839 6952 6952 W com.mbwhatsapp: type=1400 audit(0.0:1964): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-13 01:25:26.124 6952 7133 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-13 01:25:26.124 6952 7133 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-13 01:25:26.124 6952 7133 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-13 01:32:56.492 13288 13288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 01:32:58.737 13288 13288 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.
10-13 01:33:05.720 13288 13560 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-13 01:33:05.720 13288 13560 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-13 02:19:07.432 18259 18259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 02:19:07.937 18259 18259 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
10-13 02:25:20.072 18717 18717 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 02:25:20.414 18717 18717 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
10-13 02:27:15.698 19373 19373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 02:27:16.184 19373 19373 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
10-13 02:30:27.041 19945 19945 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 02:30:27.426 19945 19945 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
10-13 02:34:19.672 20360 20360 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 02:34:19.981 20360 20360 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
10-13 02:41:02.525 20911 20911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 02:41:02.795 20911 20911 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
10-13 03:19:22.873 23483 23483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 03:19:23.523 23483 23483 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
10-13 04:19:27.309 27699 27699 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 04:19:28.058 27699 27699 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
10-13 05:18:53.929 30794 30794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 05:18:54.779 30794 30794 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
10-13 06:18:59.094 6105 6105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 06:19:00.089 6105 6105 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
10-13 06:32:55.691 8462 8462 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-13 06:32:56.176 8462 8462 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
10-14 01:10:58.335 17831 17831 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 01:10:58.987 17831 17831 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
10-14 01:20:13.122 20631 20631 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 01:20:13.804 20631 20631 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
10-14 10:51:52.040 12127 12127 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 10:51:54.313 12127 12127 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.
10-14 10:51:56.901 12127 12127 W com.mbwhatsapp: type=1400 audit(0.0:15325): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-14 12:54:49.696 17354 17354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 12:54:50.972 17354 17354 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
10-14 13:27:39.009 21547 21547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 13:27:39.415 21547 21547 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
10-14 14:27:43.875 23505 23505 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 14:27:44.310 23505 23505 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
10-14 14:48:46.268 26344 26344 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 14:48:46.838 26344 26344 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
10-14 15:03:39.175 29842 29842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 15:03:40.373 29842 29842 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
10-14 19:25:42.410 4181 4181 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 19:25:43.895 4181 4181 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
10-14 23:24:12.096 9626 9626 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 23:24:14.984 9626 9626 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.
10-14 23:24:50.712 10280 10280 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-14 23:25:04.797 10280 10280 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
10-15 02:39:58.630 21764 21764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 02:40:00.665 21764 21764 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
10-15 10:24:15.832 12017 12017 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 10:24:17.193 12017 12017 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
10-15 10:28:15.969 13589 13589 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 10:28:16.538 13589 13589 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
10-15 17:43:39.182 28285 28285 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 17:43:39.817 28285 28285 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
10-15 22:06:46.477 5004 5004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 22:06:51.167 5004 5004 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-15 22:06:51.167 5004 5004 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-15 22:06:51.167 5004 5004 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-15 22:06:51.167 5004 5004 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-15 22:06:51.168 5004 5004 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-15 22:06:51.168 5004 5004 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-15 22:06:51.168 5004 5004 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-15 22:06:51.168 5004 5004 W System.err: at
java.lang.Class.newInstance(Native Method)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-15 22:06:51.168 5004 5004 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-15 22:06:51.168 5004 5004 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-15 22:06:51.168 5004 5004 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-15 22:06:51.168 5004 5004 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-15 22:06:51.168 5004 5004 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-15 22:06:51.168 5004 5004 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-15 22:06:51.168 5004 5004 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-15 22:06:51.168 5004 5004 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-15 22:06:51.670 5004 5004 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
10-15 22:06:57.107 5004 5012 W com.mbwhatsapp: Suspending all threads took:
60.295ms
10-15 22:06:58.184 5004 5004 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-15 22:06:58.187 5004 5004 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-15 22:06:59.276 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1355): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 22:06:59.302 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1356): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 22:06:59.349 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1357): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 22:07:00.142 5004 5004 W com.mbwhatsapp: type=1400 audit(0.0:1358): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 22:07:03.279 5004 5540 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-15 22:07:03.279 5004 5540 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-15 22:07:03.279 5004 5540 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-15 22:07:03.625 5004 5624 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=ce811d5a-1570-47c7-920e-4b274ba256c3, generation=0)
10-15 22:07:39.148 7249 7249 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 22:07:42.916 7249 7249 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-15 22:07:42.917 7249 7249 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.Class.newInstance(Native Method)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-15 22:07:42.917 7249 7249 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-15 22:07:42.917 7249 7249 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-15 22:07:42.917 7249 7249 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-15 22:07:42.917 7249 7249 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-15 22:07:42.917 7249 7249 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-15 22:07:42.917 7249 7249 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-15 22:07:42.917 7249 7249 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-15 22:07:42.917 7249 7249 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-15 22:07:43.333 7249 7249 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.
10-15 22:07:47.156 7249 7249 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-15 22:07:47.162 7249 7249 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-15 22:07:49.085 7249 7706 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-15 22:07:49.085 7249 7706 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-15 22:07:49.085 7249 7706 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-15 23:16:04.466 21617 21617 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-15 23:16:05.920 21617 21617 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.
10-15 23:16:10.176 21617 21617 W com.mbwhatsapp: type=1400 audit(0.0:58786): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 23:16:10.176 21617 21617 W com.mbwhatsapp: type=1400 audit(0.0:58787): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 23:16:10.176 21617 21617 W com.mbwhatsapp: type=1400 audit(0.0:58788): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-15 23:16:10.176 21617 21617 W com.mbwhatsapp: type=1400 audit(0.0:58789): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
10-16 00:01:07.575 28137 28137 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 00:01:08.097 28137 28137 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
10-16 03:47:02.626 21774 21774 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 03:47:04.725 21774 21774 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.
10-16 03:47:08.414 21774 21774 W com.mbwhatsapp: type=1400 audit(0.0:92455): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-16 05:01:22.136 27624 27624 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 05:01:22.645 27624 27624 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
10-16 17:16:11.257 29986 29986 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 17:16:11.913 29986 29986 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.
10-16 17:16:13.546 29986 30079 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-16 17:16:13.546 29986 30079 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-16 17:16:13.546 29986 30079 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-16 20:02:44.874 8916 8916 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 20:02:47.464 8916 8916 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
10-16 20:46:04.605 20772 20772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 20:46:06.212 20772 20772 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.
10-16 20:46:08.905 20772 20829 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-16 20:46:08.905 20772 20829 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-16 20:46:08.905 20772 20829 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-16 22:15:41.327 7473 7473 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-16 22:15:44.932 7473 7473 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
10-17 08:50:22.922 19542 19542 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-17 08:50:24.821 19542 19542 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
10-17 09:16:03.809 25925 25925 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-17 09:16:04.682 25925 25925 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
10-17 10:01:20.505 4289 4289 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-17 10:01:20.955 4289 4289 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
10-17 10:15:39.323 6631 6631 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-17 10:15:42.308 6631 6631 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
10-17 15:59:06.412 15702 15702 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-17 15:59:08.820 15702 15702 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
10-17 22:12:44.972 31934 31934 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-17 22:12:49.529 31934 31934 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.
10-17 22:13:00.621 31934 31934 W com.mbwhatsapp: type=1400 audit(0.0:677568): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-17 22:13:00.621 31934 31934 W com.mbwhatsapp: type=1400 audit(0.0:677569): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-18 03:54:55.389 18624 18624 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 03:54:57.600 18624 18624 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
10-18 06:01:29.468 28880 28880 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 06:01:30.422 28880 28880 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
10-18 08:42:41.084 26393 26393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 08:42:43.384 26393 26393 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.
10-18 08:42:48.511 26393 26393 W com.mbwhatsapp: type=1400 audit(0.0:787369): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-18 09:16:06.574 32525 32525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 09:16:08.111 32525 32525 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
10-18 13:16:12.085 8759 8759 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 13:16:14.424 8759 8759 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
10-18 21:45:08.866 16436 16436 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 21:45:13.270 16436 16436 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
10-18 23:41:48.977 5138 5138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 23:41:53.245 5138 5138 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
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: ANR detected. Main
thread: "main" prio=5 tid=1 Native
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: | group="main" sCount=1
ucsCount=0 flags=1 obj=0x71134360 self=0xb9180e00
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: | sysTid=5138 nice=0
cgrp=foreground sched=0/0 handle=0xb9777470
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: | state=S
schedstat=( 1539152222 1771116910 6893 ) utm=70 stm=83 core=4 HZ=100
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: | stack=0xbe71f000-
0xbe721000 stackSize=8188KB
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: | held mutexes=
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: native: #00 pc 0005c070
/apex/com.android.runtime/lib/bionic/libc.so!libc.so (offset 5b000) (syscall+28)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: native: #01 pc 0014acef
/apex/com.android.art/lib/libart.so
(art::ConditionVariable::WaitHoldingLocks(art::Thread*)+82)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: native: #02 pc 004d8a01
/apex/com.android.art/lib/libart.so!libart.so (offset 424000)
(art::GoToRunnable(art::Thread*)+300)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: native: #03 pc 004d88b5
/apex/com.android.art/lib/libart.so!libart.so (offset 424000)
(art::JniMethodEnd(unsigned int, art::Thread*)+8)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.os.BinderProxy.transactNative(Native method)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.os.BinderProxy.transact(BinderProxy.java:595)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.content.pm.IPackageManager$Stub$Proxy.getCacheNum(IPackageManager.java:1140
1)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.PropertyInvalidatedCache.getCurrentNonce(PropertyInvalidatedCache.java:
461)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.PropertyInvalidatedCache.query(PropertyInvalidatedCache.java:526)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.permission.PermissionManager.checkPermission(PermissionManager.java:1333)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ContextImpl.checkPermission(ContextImpl.java:2171)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ContextImpl.isSystemOrSystemUI(ContextImpl.java:2155)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ContextImpl.createAppContext(ContextImpl.java:3069)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ContextImpl.createAppContext(ContextImpl.java:3060)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.Service.createServiceBaseContext(Service.java:904)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ActivityThread.handleCreateService(ActivityThread.java:4785)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ActivityThread.access$2000(ActivityThread.java:284)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2285)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.os.Looper.loopOnce(Looper.java:233)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.os.Looper.loop(Looper.java:334)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
java.lang.reflect.Method.invoke(Native method)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-18 23:42:22.505 5138 5145 W SigquitBasedANRDetector: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-18 23:42:24.384 5872 5872 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-18 23:42:28.538 5872 5872 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
10-19 02:05:52.840 32145 32145 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 02:05:55.003 32145 32145 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
10-19 04:01:42.108 13332 13332 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 04:01:42.728 13332 13332 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
10-19 04:03:55.056 13546 13546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 04:03:55.389 13546 13546 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
10-19 04:07:04.451 14008 14008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 04:07:04.790 14008 14008 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
10-19 05:01:17.928 18195 18195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 05:01:18.485 18195 18195 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
10-19 06:02:47.414 22460 22460 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 06:02:47.970 22460 22460 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
10-19 07:02:37.495 26369 26369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 07:02:38.166 26369 26369 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
10-19 09:03:02.846 3244 3244 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 09:03:03.129 3244 3244 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
10-19 09:06:03.501 3748 3748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 09:06:03.795 3748 3748 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
10-19 09:09:04.121 4237 4237 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 09:09:04.388 4237 4237 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
10-19 09:13:26.999 4671 4671 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 09:13:27.306 4671 4671 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
10-19 10:02:37.483 9133 9133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-19 10:02:38.059 9133 9133 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
10-20 00:49:42.522 11213 11213 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-20 00:49:47.061 11213 11213 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
10-20 00:57:51.338 14039 14039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-20 00:57:51.954 14039 14039 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
10-20 01:07:08.128 16259 16259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-20 01:07:08.661 16259 16259 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
10-20 10:45:14.661 22163 22163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-20 10:45:16.044 22163 22163 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
10-20 11:01:22.874 28080 28080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-20 11:01:23.232 28080 28080 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.
10-20 11:01:24.341 28080 28143 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-20 11:01:24.341 28080 28143 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-20 12:08:11.047 3919 3919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-20 12:08:11.669 3919 3919 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
10-21 00:40:19.067 6263 6263 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 00:40:19.941 6263 6263 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-21 00:40:19.941 6263 6263 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-21 00:40:19.941 6263 6263 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-21 00:40:19.941 6263 6263 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-21 00:40:19.941 6263 6263 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-21 00:40:19.941 6263 6263 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-21 00:40:19.941 6263 6263 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-21 00:40:19.941 6263 6263 W System.err: at
java.lang.Class.newInstance(Native Method)
10-21 00:40:19.941 6263 6263 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-21 00:40:19.941 6263 6263 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-21 00:40:19.941 6263 6263 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-21 00:40:19.941 6263 6263 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-21 00:40:19.941 6263 6263 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-21 00:40:19.941 6263 6263 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-21 00:40:19.941 6263 6263 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-21 00:40:19.942 6263 6263 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-21 00:40:19.942 6263 6263 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-21 00:40:19.942 6263 6263 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-21 00:40:19.942 6263 6263 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-21 00:40:19.942 6263 6263 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-21 00:40:19.942 6263 6263 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-21 00:40:19.942 6263 6263 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-21 00:40:20.006 6263 6263 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.
10-21 00:40:20.590 6263 6263 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-21 00:40:20.591 6263 6263 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-21 00:40:20.662 6263 6263 W com.mbwhatsapp: type=1400 audit(0.0:1768): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-21 00:40:20.679 6263 6263 W com.mbwhatsapp: type=1400 audit(0.0:1770): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-21 00:40:20.715 6263 6263 W com.mbwhatsapp: type=1400 audit(0.0:1771): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-21 00:40:21.220 6263 6401 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-21 00:40:21.220 6263 6401 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-21 00:40:21.220 6263 6401 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-21 00:40:21.816 6263 6437 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=90cd08c4-97dc-4f7e-8b90-635f024e8bbd, generation=0)
10-21 01:12:11.784 21270 21270 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 01:12:12.204 21270 21270 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
10-21 01:58:39.042 992 992 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 01:58:40.714 992 992 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.
10-21 01:58:43.887 992 992 W com.mbwhatsapp: type=1400 audit(0.0:26003): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-21 01:58:43.947 992 992 W com.mbwhatsapp: type=1400 audit(0.0:26004): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-21 02:00:05.819 3333 3333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 02:00:06.325 3333 3333 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
10-21 02:34:17.714 6557 6557 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 02:34:18.286 6557 6557 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
10-21 02:38:31.319 7126 7126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 02:38:31.634 7126 7126 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
10-21 02:39:55.892 7778 7778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 02:39:56.165 7778 7778 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
10-21 03:34:34.086 12088 12088 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 03:34:34.612 12088 12088 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
10-21 03:38:35.880 12624 12624 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 03:38:36.160 12624 12624 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
10-21 03:41:40.199 12939 12939 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 03:41:40.544 12939 12939 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
10-21 03:46:50.536 13333 13333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 03:46:50.858 13333 13333 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
10-21 03:57:50.419 13766 13766 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 03:57:50.732 13766 13766 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
10-21 04:16:35.014 14899 14899 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 04:16:35.295 14899 14899 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
10-21 04:39:18.333 15537 15537 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 04:39:18.588 15537 15537 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
10-21 05:34:02.323 17713 17713 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-21 05:34:02.828 17713 17713 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
10-22 06:16:31.467 9166 9166 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 06:16:32.863 9166 9166 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.
10-22 06:16:36.149 9166 9651 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-22 06:16:36.149 9166 9651 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-22 06:16:36.149 9166 9651 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-22 07:31:57.450 22826 22826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 07:31:58.727 22826 22826 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.
10-22 07:31:59.852 22826 22959 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-22 07:31:59.852 22826 22959 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-22 07:31:59.852 22826 22959 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-22 12:09:55.576 5958 5958 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 12:09:57.935 5958 5958 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
10-22 13:58:48.546 20195 20195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 13:58:49.745 20195 20195 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
10-22 17:45:29.686 17625 17625 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 17:45:32.212 17625 17625 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.
10-22 17:45:35.083 17625 18103 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-22 17:45:35.083 17625 18103 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-22 17:45:35.083 17625 18103 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-22 18:24:07.246 27393 27393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 18:24:07.903 27393 27393 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
10-22 19:16:58.817 6264 6264 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-22 19:16:59.442 6264 6264 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
10-23 00:38:37.449 4450 4450 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-23 00:38:41.081 4450 4450 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-23 00:38:41.082 4450 4450 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-23 00:38:41.082 4450 4450 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-23 00:38:41.086 4450 4450 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-23 00:38:41.087 4450 4450 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-23 00:38:41.087 4450 4450 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-23 00:38:41.087 4450 4450 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-23 00:38:41.087 4450 4450 W System.err: at
java.lang.Class.newInstance(Native Method)
10-23 00:38:41.087 4450 4450 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-23 00:38:41.087 4450 4450 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-23 00:38:41.088 4450 4450 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-23 00:38:41.088 4450 4450 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-23 00:38:41.088 4450 4450 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-23 00:38:41.088 4450 4450 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-23 00:38:41.088 4450 4450 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-23 00:38:41.088 4450 4450 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-23 00:38:41.088 4450 4450 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-23 00:38:41.089 4450 4450 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-23 00:38:41.089 4450 4450 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-23 00:38:41.089 4450 4450 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-23 00:38:41.089 4450 4450 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-23 00:38:41.089 4450 4450 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-23 00:38:41.348 4450 4450 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.
10-23 00:38:42.939 4450 4450 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-23 00:38:42.949 4450 4450 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-23 00:38:44.472 4450 4623 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-23 00:38:44.472 4450 4623 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-23 00:38:44.472 4450 4623 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-23 00:38:45.296 4450 4653 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=5d8138dd-936e-4848-9982-7a10f06dc2f9, generation=0)
10-23 00:39:45.450 6465 6465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-23 00:39:46.537 6465 6465 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-23 00:39:46.539 6465 6465 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-23 00:39:46.540 6465 6465 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-23 00:39:46.540 6465 6465 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-23 00:39:46.541 6465 6465 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-23 00:39:46.542 6465 6465 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-23 00:39:46.543 6465 6465 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-23 00:39:46.543 6465 6465 W System.err: at
java.lang.Class.newInstance(Native Method)
10-23 00:39:46.544 6465 6465 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-23 00:39:46.544 6465 6465 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-23 00:39:46.545 6465 6465 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-23 00:39:46.545 6465 6465 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-23 00:39:46.546 6465 6465 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-23 00:39:46.547 6465 6465 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-23 00:39:46.547 6465 6465 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-23 00:39:46.548 6465 6465 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-23 00:39:46.548 6465 6465 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-23 00:39:46.549 6465 6465 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-23 00:39:46.551 6465 6465 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-23 00:39:46.553 6465 6465 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-23 00:39:46.554 6465 6465 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-23 00:39:46.555 6465 6465 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-23 00:39:46.808 6465 6465 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.
10-23 00:39:48.469 6465 6465 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-23 00:39:48.470 6465 6465 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-23 00:39:48.605 6465 6465 W com.mbwhatsapp: type=1400 audit(0.0:1844): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-23 00:39:48.628 6465 6465 W com.mbwhatsapp: type=1400 audit(0.0:1845): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-23 00:39:48.722 6465 6465 W com.mbwhatsapp: type=1400 audit(0.0:1846): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-23 00:39:48.912 6465 6465 W com.mbwhatsapp: type=1400 audit(0.0:1847): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-23 00:39:48.945 6465 6465 W com.mbwhatsapp: type=1400 audit(0.0:1848): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-23 02:11:03.941 9229 9229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-23 02:11:04.703 9229 9229 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.
10-23 02:11:06.048 9229 9229 W com.mbwhatsapp: type=1400 audit(0.0:2496): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-23 02:11:06.048 9229 9229 W com.mbwhatsapp: type=1400 audit(0.0:2497): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-23 02:30:10.989 15673 15673 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-23 02:30:12.551 15673 15673 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
10-23 22:08:13.890 26658 26658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-23 22:08:17.175 26658 26658 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
10-24 02:20:39.456 6145 6145 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 02:20:40.616 6145 6145 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
10-24 02:24:30.999 8374 8374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 02:24:40.939 8570 8570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 02:24:41.235 8570 8570 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
10-24 02:34:32.398 13169 13169 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 04:03:16.368 32234 32234 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 04:03:17.357 32234 32234 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
10-24 04:12:05.130 32745 32745 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 04:12:05.535 32745 32745 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
10-24 05:57:32.109 6593 6593 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 05:57:34.293 6593 6593 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
10-24 05:58:20.296 8605 8605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 05:58:22.180 8605 8605 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
10-24 05:59:57.349 12512 12512 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 05:59:58.548 12512 12512 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
10-24 06:48:56.429 20393 20393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 06:48:57.305 20393 20393 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.
10-24 06:48:58.127 20393 20393 W com.mbwhatsapp: type=1400 audit(0.0:6122): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-24 07:00:18.321 21806 21806 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 07:00:19.012 21806 21806 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
10-24 07:48:29.767 3175 3175 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 07:48:30.722 3175 3175 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
10-24 07:53:01.474 4598 4598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 07:53:02.372 4598 4598 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.
10-24 07:53:03.634 4598 4732 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-24 07:53:03.634 4598 4732 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-24 07:53:03.634 4598 4732 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-24 07:57:03.962 5302 5302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 07:57:04.632 5302 5302 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
10-24 08:08:10.759 6656 6656 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 08:08:11.845 6656 6656 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
10-24 08:18:35.362 9740 9740 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 08:18:36.152 9740 9740 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
10-24 08:51:58.104 12590 12590 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 08:51:59.111 12590 12590 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.
10-24 08:52:01.097 12590 12648 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-24 08:52:01.097 12590 12648 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-24 08:52:01.097 12590 12648 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-24 09:48:56.809 18012 18012 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 09:48:57.423 18012 18012 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
10-24 10:48:36.126 25722 25722 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 10:48:37.234 25722 25722 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
10-24 11:48:36.989 6509 6509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 11:48:37.659 6509 6509 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.
10-24 11:48:39.338 6509 6563 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-24 11:48:39.338 6509 6563 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-24 11:48:39.338 6509 6563 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-24 13:02:42.446 29219 29219 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 13:02:43.894 29219 29219 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.
10-24 13:02:45.357 29219 29387 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-24 13:02:45.357 29219 29387 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-24 13:02:45.357 29219 29387 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-24 13:22:44.364 29937 29937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 13:22:44.686 29937 29937 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
10-24 14:30:16.546 30911 30911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 14:30:16.988 30911 30911 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
10-24 16:32:56.583 1148 1148 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 16:32:58.202 1148 1148 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
10-24 17:30:10.665 3935 3935 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 17:30:11.551 3935 3935 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
10-24 17:48:31.757 8807 8807 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 17:48:32.979 8807 8807 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
10-24 17:52:40.932 9613 9613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 17:52:41.364 9613 9613 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
10-24 17:57:06.231 10383 10383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 17:57:06.873 10383 10383 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
10-24 18:02:08.117 11334 11334 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 18:02:09.112 11334 11334 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
10-24 18:48:31.085 19135 19135 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 18:48:32.041 19135 19135 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
10-24 18:56:23.544 21918 21918 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 18:56:24.207 21918 21918 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
10-24 19:49:29.043 4227 4227 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 19:49:30.350 4227 4227 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
10-24 19:58:35.411 6257 6257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 19:58:35.983 6257 6257 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
10-24 20:18:38.939 15672 15672 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 20:18:39.676 15672 15672 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
10-24 20:53:37.469 20820 20820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 20:53:38.371 20820 20820 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
10-24 20:59:16.438 21504 21504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 20:59:16.786 21504 21504 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
10-24 21:04:13.990 22360 22360 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 21:04:14.259 22360 22360 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
10-24 22:19:48.553 9430 9430 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 22:19:49.127 9430 9430 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
10-24 22:48:56.979 17373 17373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-24 22:48:57.816 17373 17373 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
10-25 00:07:03.566 28375 28375 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 00:07:04.191 28375 28375 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
10-25 01:08:34.864 5652 5652 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 01:08:35.434 5652 5652 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
10-25 01:18:38.470 7080 7080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 01:18:39.167 7080 7080 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
10-25 01:48:48.038 9871 9871 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 01:48:48.633 9871 9871 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
10-25 02:49:15.652 14921 14921 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 02:49:16.774 14921 14921 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
10-25 04:08:00.479 29561 29561 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 04:08:01.431 29561 29561 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
10-25 05:06:25.053 31883 31883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 05:06:30.248 31883 31883 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
10-25 07:02:14.291 4682 4682 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 07:02:16.812 4682 4682 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-25 07:02:16.813 4682 4682 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.Class.newInstance(Native Method)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-25 07:02:16.813 4682 4682 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-25 07:02:16.813 4682 4682 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-25 07:02:16.813 4682 4682 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-25 07:02:16.813 4682 4682 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-25 07:02:16.813 4682 4682 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-25 07:02:16.813 4682 4682 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-25 07:02:16.813 4682 4682 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-25 07:02:16.813 4682 4682 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-25 07:02:16.975 4682 4682 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.
10-25 07:02:18.423 4682 4682 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-25 07:02:18.424 4682 4682 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-25 07:02:19.289 4682 4682 W com.mbwhatsapp: type=1400 audit(0.0:1361): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-25 07:02:19.362 4682 4682 W com.mbwhatsapp: type=1400 audit(0.0:1362): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-25 07:02:19.362 4682 4682 W com.mbwhatsapp: type=1400 audit(0.0:1363): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-25 07:02:19.362 4682 4682 W com.mbwhatsapp: type=1400 audit(0.0:1364): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-25 07:02:19.362 4682 4682 W com.mbwhatsapp: type=1400 audit(0.0:1365): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
10-25 07:02:20.218 4682 5257 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-25 07:02:20.218 4682 5257 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-25 07:02:20.218 4682 5257 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-25 07:56:30.701 28830 28830 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 07:56:31.869 28830 28830 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
10-25 08:56:30.739 10862 10862 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 08:56:32.127 10862 10862 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
10-25 17:54:18.290 4991 4991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 17:54:19.521 4991 4991 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-25 17:54:19.521 4991 4991 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-25 17:54:19.521 4991 4991 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-25 17:54:19.521 4991 4991 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-25 17:54:19.521 4991 4991 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-25 17:54:19.521 4991 4991 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-25 17:54:19.521 4991 4991 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-25 17:54:19.521 4991 4991 W System.err: at
java.lang.Class.newInstance(Native Method)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-25 17:54:19.522 4991 4991 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-25 17:54:19.522 4991 4991 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-25 17:54:19.522 4991 4991 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-25 17:54:19.522 4991 4991 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-25 17:54:19.522 4991 4991 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-25 17:54:19.522 4991 4991 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-25 17:54:19.522 4991 4991 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-25 17:54:19.522 4991 4991 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-25 17:54:19.748 4991 4991 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.
10-25 17:54:20.912 4991 4991 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-25 17:54:20.913 4991 4991 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-25 17:54:22.408 4991 5104 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-25 17:54:22.408 4991 5104 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-25 17:54:22.408 4991 5104 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-25 17:54:24.709 4991 5171 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-25 17:54:24.709 4991 5171 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-25 17:55:05.747 6990 6990 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 17:55:08.082 6990 6990 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-25 17:55:08.083 6990 6990 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-25 17:55:08.083 6990 6990 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-25 17:55:08.083 6990 6990 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-25 17:55:08.083 6990 6990 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-25 17:55:08.083 6990 6990 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-25 17:55:08.083 6990 6990 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-25 17:55:08.083 6990 6990 W System.err: at
java.lang.Class.newInstance(Native Method)
10-25 17:55:08.083 6990 6990 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-25 17:55:08.083 6990 6990 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-25 17:55:08.083 6990 6990 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-25 17:55:08.083 6990 6990 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-25 17:55:08.083 6990 6990 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-25 17:55:08.083 6990 6990 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-25 17:55:08.083 6990 6990 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-25 17:55:08.083 6990 6990 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-25 17:55:08.083 6990 6990 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-25 17:55:08.083 6990 6990 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-25 17:55:08.084 6990 6990 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-25 17:55:08.084 6990 6990 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-25 17:55:08.084 6990 6990 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-25 17:55:08.084 6990 6990 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-25 17:55:08.664 6990 6990 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
10-25 17:55:12.467 6990 6990 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-25 17:55:12.467 6990 6990 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-25 17:55:16.016 6990 6999 W com.mbwhatsapp: Suspending all threads took:
26.845ms
10-25 17:55:16.824 6990 7396 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-25 17:55:16.824 6990 7396 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-25 17:55:16.824 6990 7396 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-25 18:48:32.358 24694 24694 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 18:48:33.191 24694 24694 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
10-25 18:49:18.456 24798 24798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 18:49:18.795 24798 24798 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
10-25 19:48:32.331 5594 5594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 19:48:32.867 5594 5594 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
10-25 19:50:08.499 6363 6363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 19:50:08.809 6363 6363 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
10-25 20:49:17.664 18585 18585 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 20:49:18.609 18585 18585 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.
10-25 20:49:20.155 18585 18746 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-25 20:49:20.155 18585 18746 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-25 20:49:20.155 18585 18746 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-25 20:50:16.380 19195 19195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 20:50:17.030 19195 19195 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
10-25 21:49:08.742 32046 32046 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:49:09.300 32046 32046 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
10-25 21:50:55.905 987 987 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:50:56.490 987 987 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
10-25 21:54:20.154 3203 3203 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:54:20.410 3203 3203 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
10-25 21:54:33.855 3426 3426 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:54:34.142 3426 3426 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
10-25 21:59:05.293 4455 4455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:06.318 4455 4455 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
10-25 21:59:34.119 4977 4977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:34.547 4977 4977 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
10-25 22:02:04.435 6778 6778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:02:04.925 6778 6778 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
10-25 22:48:44.757 18433 18433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:48:45.496 18433 18433 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
10-25 22:49:37.163 18919 18919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:49:37.566 18919 18919 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
10-25 23:06:34.162 25486 25486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:06:34.747 25486 25486 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
10-25 23:07:13.093 25604 25604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:07:13.349 25604 25604 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
10-25 23:48:42.599 32645 32645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:48:43.428 32645 32645 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
10-25 23:52:03.508 1010 1010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:52:04.225 1010 1010 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
10-26 00:25:45.292 7781 7781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 00:25:46.021 7781 7781 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
10-25 21:59:05.293 4455 4455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:06.318 4455 4455 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.
10-25 21:59:34.119 4977 4977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:34.547 4977 4977 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.
10-25 22:02:04.435 6778 6778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:02:04.925 6778 6778 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.
10-25 22:48:44.757 18433 18433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:48:45.496 18433 18433 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.
10-25 22:49:37.163 18919 18919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:49:37.566 18919 18919 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.
10-25 23:06:34.162 25486 25486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:06:34.747 25486 25486 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.
10-25 23:07:13.093 25604 25604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:07:13.349 25604 25604 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.
10-25 23:48:42.599 32645 32645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:48:43.428 32645 32645 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.
10-25 23:52:03.508 1010 1010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:52:04.225 1010 1010 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.
10-26 00:25:45.292 7781 7781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 00:25:46.021 7781 7781 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.
09-27 01:32:05.797 25195 25195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 01:32:06.385 25195 25195 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.
09-27 01:32:07.296 25195 25195 W com.mbwhatsapp: type=1400 audit(0.0:90187): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-27 01:32:07.438 25195 25266 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-27 01:32:07.438 25195 25266 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-27 01:32:07.438 25195 25266 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-25 21:59:05.293 4455 4455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:06.318 4455 4455 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.
10-25 21:59:34.119 4977 4977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:34.547 4977 4977 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.
10-25 22:02:04.435 6778 6778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:02:04.925 6778 6778 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.
10-25 22:48:44.757 18433 18433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:48:45.496 18433 18433 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.
10-25 22:49:37.163 18919 18919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:49:37.566 18919 18919 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.
10-25 23:06:34.162 25486 25486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:06:34.747 25486 25486 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.
10-25 23:07:13.093 25604 25604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:07:13.349 25604 25604 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.
10-25 23:48:42.599 32645 32645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:48:43.428 32645 32645 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.
10-25 23:52:03.508 1010 1010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:52:04.225 1010 1010 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.
10-26 00:25:45.292 7781 7781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 00:25:46.021 7781 7781 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.
09-27 01:44:32.752 25718 25718 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 01:44:33.260 25718 25718 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.
09-27 01:44:34.053 25718 25768 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
09-27 01:44:34.053 25718 25768 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-25 21:59:05.293 4455 4455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:06.318 4455 4455 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.
10-25 21:59:34.119 4977 4977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:34.547 4977 4977 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.
10-25 22:02:04.435 6778 6778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:02:04.925 6778 6778 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.
10-25 22:48:44.757 18433 18433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:48:45.496 18433 18433 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.
10-25 22:49:37.163 18919 18919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:49:37.566 18919 18919 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.
10-25 23:06:34.162 25486 25486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:06:34.747 25486 25486 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.
10-25 23:07:13.093 25604 25604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:07:13.349 25604 25604 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.
10-25 23:48:42.599 32645 32645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:48:43.428 32645 32645 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.
10-25 23:52:03.508 1010 1010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:52:04.225 1010 1010 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.
10-26 00:25:45.292 7781 7781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 00:25:46.021 7781 7781 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.
09-27 02:00:48.829 26361 26361 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 02:00:49.137 26361 26361 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.
09-27 02:00:50.107 26361 26361 W com.mbwhatsapp: type=1400 audit(0.0:90856): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-27 02:00:50.137 26361 26361 W com.mbwhatsapp: type=1400 audit(0.0:90857): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-27 02:00:50.235 26361 26514 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-27 02:00:50.235 26361 26514 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-27 02:00:50.235 26361 26514 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-25 21:59:05.293 4455 4455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:06.318 4455 4455 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.
10-25 21:59:34.119 4977 4977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 21:59:34.547 4977 4977 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.
10-25 22:02:04.435 6778 6778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:02:04.925 6778 6778 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.
10-25 22:48:44.757 18433 18433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:48:45.496 18433 18433 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.
10-25 22:49:37.163 18919 18919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 22:49:37.566 18919 18919 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.
10-25 23:06:34.162 25486 25486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:06:34.747 25486 25486 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.
10-25 23:07:13.093 25604 25604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:07:13.349 25604 25604 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.
10-25 23:48:42.599 32645 32645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:48:43.428 32645 32645 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.
10-25 23:52:03.508 1010 1010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-25 23:52:04.225 1010 1010 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.
10-26 00:25:45.292 7781 7781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 00:25:46.021 7781 7781 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.
09-27 02:13:39.452 27031 27031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
09-27 02:13:40.267 27031 27031 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.
09-27 02:13:41.427 27031 27031 W com.mbwhatsapp: type=1400 audit(0.0:90990): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-27 02:13:41.443 27031 27031 W com.mbwhatsapp: type=1400 audit(0.0:90991): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-27 02:13:41.443 27031 27031 W com.mbwhatsapp: type=1400 audit(0.0:90992): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
09-27 02:13:41.578 27031 27101 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
09-27 02:13:41.578 27031 27101 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
09-27 02:13:41.578 27031 27101 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-26 02:48:37.235 12784 12784 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 02:48:38.108 12784 12784 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
10-26 04:06:13.651 19309 19309 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 04:06:14.422 19309 19309 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.
10-26 04:06:16.190 19309 19452 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-26 04:06:16.190 19309 19452 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-26 04:06:16.190 19309 19452 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-26 05:03:34.920 29126 29126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 05:03:35.881 29126 29126 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
10-26 05:04:37.808 30821 30821 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 05:04:38.729 30821 30821 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
10-26 05:52:03.979 20572 20572 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 05:52:04.814 20572 20572 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
10-26 06:04:42.152 21424 21424 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 06:04:42.747 21424 21424 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
10-26 06:07:56.914 21879 21879 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 06:07:57.148 21879 21879 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
10-26 06:49:01.406 30022 30022 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 06:49:01.879 30022 30022 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
10-26 07:49:24.336 13094 13094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 07:49:25.020 13094 13094 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
10-26 07:57:28.676 14581 14581 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 07:57:29.426 14581 14581 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
10-26 08:03:41.980 15494 15494 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 08:03:42.414 15494 15494 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
10-26 08:16:01.013 16347 16347 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 08:16:01.245 16347 16347 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
10-26 08:50:14.536 20401 20401 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 08:50:15.782 20401 20401 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
10-26 08:55:15.209 21680 21680 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 08:55:16.182 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.
--------- beginning of main
10-26 09:05:09.721 23346 23346 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 09:05:10.373 23346 23346 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
10-26 09:53:45.472 26742 26742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 09:53:46.247 26742 26742 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
10-26 10:55:20.087 31167 31167 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 10:55:20.802 31167 31167 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
10-26 11:16:11.144 31852 31852 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 11:16:11.886 31852 31852 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
10-26 12:37:46.994 3716 3716 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 12:37:47.754 3716 3716 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
10-26 13:53:26.946 5237 5237 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 13:53:28.372 5237 5237 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
10-26 14:53:46.894 13274 13274 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 14:53:47.552 13274 13274 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
10-26 15:05:09.011 14033 14033 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 15:05:09.836 14033 14033 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
10-26 15:19:50.748 14503 14503 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 15:19:50.998 14503 14503 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
10-26 15:24:32.667 15889 15889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 15:24:33.811 15889 15889 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
10-26 15:48:40.982 17974 17974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 15:48:41.548 17974 17974 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
10-26 15:59:43.611 19151 19151 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 15:59:44.135 19151 19151 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
10-26 16:18:50.573 20174 20174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 16:18:50.829 20174 20174 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
10-26 17:08:05.434 23522 23522 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 17:08:05.867 23522 23522 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
10-26 17:09:16.764 23827 23827 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 17:09:17.012 23827 23827 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
10-26 18:40:10.966 8783 8783 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 18:40:13.083 8783 8783 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
10-26 18:42:01.142 12613 12613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 18:42:01.891 12613 12613 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.
10-26 18:42:03.306 12613 12613 W com.mbwhatsapp: type=1400 audit(0.0:2623): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-26 18:44:51.744 16677 16677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 18:44:52.192 16677 16677 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
10-26 18:46:51.509 17381 17381 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 18:46:51.844 17381 17381 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
10-26 19:49:11.333 30171 30171 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 19:49:11.982 30171 30171 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
10-26 19:55:40.998 32626 32626 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 19:55:42.193 32626 32626 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.
10-26 19:55:43.325 32626 32686 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-26 19:55:43.325 32626 32686 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-26 19:55:43.325 32626 32686 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-26 20:02:19.903 3863 3863 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 20:02:20.511 3863 3863 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
10-26 20:38:53.549 18292 18292 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 20:38:55.463 18292 18292 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.
10-26 20:38:59.089 18292 18292 W com.mbwhatsapp: type=1400 audit(0.0:25145): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-26 20:38:59.089 18292 18292 W com.mbwhatsapp: type=1400 audit(0.0:25146): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-26 20:48:33.876 23881 23881 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 20:48:36.951 23881 23881 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
10-26 21:03:45.509 30423 30423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 21:03:52.838 30423 30423 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
10-26 21:26:50.321 10278 10278 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 21:26:51.120 10278 10278 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.
10-26 21:26:54.663 10278 10333 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-26 21:26:54.663 10278 10333 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-26 21:26:54.663 10278 10333 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-26 22:56:48.283 19227 19227 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 22:56:51.842 19227 19227 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
10-26 23:09:24.493 22567 22567 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:09:25.090 22567 22567 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
10-26 23:13:22.840 22820 22820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:13:59.569 23044 23044 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:13:59.971 23044 23044 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
10-26 23:24:45.812 26817 26817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:24:46.572 26817 26817 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
10-26 23:28:26.739 27297 27297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:33:50.819 27377 27377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:33:51.096 27377 27377 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
10-26 23:45:08.019 27598 27598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-26 23:45:08.305 27598 27598 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
10-27 00:02:26.886 28037 28037 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 00:02:27.216 28037 28037 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
10-27 01:11:28.671 18606 18606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 01:11:30.245 18606 18606 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
10-27 01:17:38.336 20347 20347 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 01:17:39.175 20347 20347 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
10-27 01:58:04.043 24274 24274 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 01:58:04.732 24274 24274 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
10-27 02:05:04.931 25572 25572 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 02:05:05.517 25572 25572 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
10-27 02:20:20.579 28710 28710 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 02:20:23.417 28710 28710 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
10-27 02:48:50.717 32003 32003 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 02:48:51.471 32003 32003 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
10-27 03:06:27.352 4639 4639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 03:06:27.985 4639 4639 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
10-27 03:20:35.851 5767 5767 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 03:20:36.626 5767 5767 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
10-27 03:32:27.168 6144 6144 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 03:32:28.782 6144 6144 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
10-27 03:58:34.025 16553 16553 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 03:58:35.385 16553 16553 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
10-27 04:42:25.807 20430 20430 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 04:42:26.510 20430 20430 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
10-27 05:45:01.974 26320 26320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 05:45:02.513 26320 26320 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
10-27 06:48:27.145 5352 5352 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 06:48:27.853 5352 5352 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
10-27 08:08:58.404 3699 3699 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 08:09:00.420 3699 3699 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-27 08:09:00.422 3699 3699 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-27 08:09:00.422 3699 3699 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-27 08:09:00.422 3699 3699 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-27 08:09:00.422 3699 3699 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-27 08:09:00.422 3699 3699 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-27 08:09:00.423 3699 3699 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-27 08:09:00.423 3699 3699 W System.err: at
java.lang.Class.newInstance(Native Method)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-27 08:09:00.423 3699 3699 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-27 08:09:00.423 3699 3699 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-27 08:09:00.423 3699 3699 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-27 08:09:00.423 3699 3699 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-27 08:09:00.423 3699 3699 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-27 08:09:00.423 3699 3699 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-27 08:09:00.423 3699 3699 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-27 08:09:00.423 3699 3699 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-27 08:09:00.782 3699 3699 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.
10-27 08:09:04.514 3699 3699 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-27 08:09:04.538 3699 3699 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-27 08:09:04.926 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1189): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 08:09:04.986 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1190): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 08:09:05.232 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1191): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-27 08:09:05.672 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1192): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 08:09:05.936 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1193): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 08:09:05.936 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1194): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 08:09:05.936 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1195): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 08:09:05.939 3699 3699 W com.mbwhatsapp: type=1400 audit(0.0:1196): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
10-27 08:09:07.981 3699 4519 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-27 08:09:07.981 3699 4519 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-27 08:09:07.981 3699 4519 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-27 08:10:35.369 8499 8499 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 08:10:36.646 8499 8499 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-27 08:10:36.647 8499 8499 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-27 08:10:36.647 8499 8499 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-27 08:10:36.647 8499 8499 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-27 08:10:36.647 8499 8499 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-27 08:10:36.647 8499 8499 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-27 08:10:36.647 8499 8499 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-27 08:10:36.647 8499 8499 W System.err: at
java.lang.Class.newInstance(Native Method)
10-27 08:10:36.647 8499 8499 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-27 08:10:36.647 8499 8499 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-27 08:10:36.647 8499 8499 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-27 08:10:36.648 8499 8499 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-27 08:10:36.648 8499 8499 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-27 08:10:36.648 8499 8499 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-27 08:10:36.648 8499 8499 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-27 08:10:36.648 8499 8499 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-27 08:10:36.648 8499 8499 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-27 08:10:36.648 8499 8499 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-27 08:10:36.648 8499 8499 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-27 08:10:36.648 8499 8499 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-27 08:10:36.648 8499 8499 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-27 08:10:36.648 8499 8499 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-27 08:10:36.752 8499 8499 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.
10-27 08:10:37.608 8499 8499 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-27 08:10:37.608 8499 8499 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-27 08:10:38.376 8499 8657 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-27 08:10:38.376 8499 8657 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-27 08:10:38.376 8499 8657 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-27 08:13:00.901 14957 14957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 08:13:04.329 14957 14957 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.
10-27 08:13:06.361 14957 14957 W com.mbwhatsapp: type=1400 audit(0.0:3577): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-27 08:15:00.598 19105 19105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 08:15:01.225 19105 19105 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
10-27 08:18:44.642 21628 21628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 08:18:45.069 21628 21628 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
10-27 08:43:16.672 17428 17428 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 08:43:17.993 17428 17428 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
10-27 09:03:32.926 5393 5393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 09:03:33.482 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
10-27 09:22:02.025 15000 15000 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 09:22:02.648 15000 15000 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
10-27 12:00:13.409 12491 12491 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 12:00:13.840 12491 12491 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
10-27 14:19:07.778 18107 18107 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:19:10.458 18107 18107 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
10-27 14:19:39.889 19843 19843 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:19:41.172 19843 19843 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
10-27 14:21:58.932 22269 22269 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:21:59.505 22269 22269 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
10-27 14:23:11.353 24191 24191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:23:12.439 24191 24191 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
10-27 14:26:31.962 25126 25126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:26:32.305 25126 25126 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
10-27 14:29:40.514 28047 28047 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:29:40.981 28047 28047 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
10-27 14:37:22.979 32547 32547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:37:23.771 32547 32547 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
10-27 14:48:18.556 6612 6612 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 14:48:19.189 6612 6612 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
10-27 16:04:45.638 31397 31397 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 16:04:46.165 31397 31397 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
10-27 16:27:44.411 3796 3796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 16:27:45.323 3796 3796 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
10-27 17:07:26.696 10718 10718 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 17:07:27.433 10718 10718 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
10-27 17:20:46.812 11375 11375 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 17:20:47.480 11375 11375 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
10-27 17:39:18.726 12366 12366 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 17:39:19.537 12366 12366 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
10-27 17:52:39.444 13693 13693 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 17:52:40.072 13693 13693 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
10-27 18:43:58.566 15982 15982 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 18:43:59.973 15982 15982 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
10-27 19:54:23.676 23608 23608 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 19:54:24.585 23608 23608 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
10-27 20:56:35.710 26706 26706 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 20:56:36.334 26706 26706 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
10-27 21:50:11.451 4633 4633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 21:50:13.087 4633 4633 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-27 21:50:13.087 4633 4633 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-27 21:50:13.088 4633 4633 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-27 21:50:13.088 4633 4633 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-27 21:50:13.088 4633 4633 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-27 21:50:13.088 4633 4633 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-27 21:50:13.088 4633 4633 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-27 21:50:13.088 4633 4633 W System.err: at
java.lang.Class.newInstance(Native Method)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-27 21:50:13.088 4633 4633 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-27 21:50:13.088 4633 4633 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-27 21:50:13.088 4633 4633 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-27 21:50:13.088 4633 4633 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-27 21:50:13.088 4633 4633 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-27 21:50:13.088 4633 4633 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-27 21:50:13.088 4633 4633 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-27 21:50:13.088 4633 4633 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-27 21:50:13.244 4633 4633 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.
10-27 21:50:15.477 4633 4633 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-27 21:50:15.478 4633 4633 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-27 21:50:15.752 4633 4633 W com.mbwhatsapp: type=1400 audit(0.0:1366): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:15.779 4633 4633 W com.mbwhatsapp: type=1400 audit(0.0:1367): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:15.859 4633 4633 W com.mbwhatsapp: type=1400 audit(0.0:1368): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:16.172 4633 4633 W com.mbwhatsapp: type=1400 audit(0.0:1369): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-27 21:50:16.874 4633 5153 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-27 21:50:16.874 4633 5153 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-27 21:50:16.874 4633 5153 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-27 21:50:18.870 4633 5159 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-27 21:50:18.870 4633 5159 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-27 21:50:44.283 6472 6472 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 21:50:45.702 6472 6472 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-27 21:50:45.703 6472 6472 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-27 21:50:45.703 6472 6472 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-27 21:50:45.703 6472 6472 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-27 21:50:45.703 6472 6472 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-27 21:50:45.703 6472 6472 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-27 21:50:45.703 6472 6472 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-27 21:50:45.703 6472 6472 W System.err: at
java.lang.Class.newInstance(Native Method)
10-27 21:50:45.703 6472 6472 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-27 21:50:45.703 6472 6472 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-27 21:50:45.703 6472 6472 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-27 21:50:45.703 6472 6472 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-27 21:50:45.703 6472 6472 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-27 21:50:45.703 6472 6472 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-27 21:50:45.703 6472 6472 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-27 21:50:45.704 6472 6472 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-27 21:50:45.704 6472 6472 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-27 21:50:45.704 6472 6472 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-27 21:50:45.704 6472 6472 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-27 21:50:45.704 6472 6472 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-27 21:50:45.704 6472 6472 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-27 21:50:45.704 6472 6472 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-27 21:50:45.803 6472 6472 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.
10-27 21:50:47.444 6472 6472 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-27 21:50:47.444 6472 6472 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
10-27 21:50:47.712 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1749): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:47.755 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1750): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:47.822 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1751): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-27 21:50:48.499 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1752): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:48.569 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1753): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:48.569 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1754): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:48.569 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1755): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
10-27 21:50:48.569 6472 6472 W com.mbwhatsapp: type=1400 audit(0.0:1756): avc:
denied { execmod } for path="/apex/com.android.runtime/lib/bionic/libc.so" dev="dm-
5" ino=433 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
10-27 21:50:49.287 6472 6696 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-27 21:50:49.287 6472 6696 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-27 21:50:49.287 6472 6696 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-27 21:50:50.169 6472 6709 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-27 21:50:50.170 6472 6709 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-27 21:52:46.833 10790 10790 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 21:52:47.786 10790 10790 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
10-27 21:55:48.810 13985 13985 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 21:55:49.371 13985 13985 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
10-27 22:02:07.449 17232 17232 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 22:02:08.152 17232 17232 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
10-27 22:12:38.683 20773 20773 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 22:12:39.395 20773 20773 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
10-27 22:17:24.319 21734 21734 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 22:17:25.240 21734 21734 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
10-27 22:29:53.642 26958 26958 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 22:29:54.760 26958 26958 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
10-27 23:55:34.242 13676 13676 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-27 23:55:35.037 13676 13676 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
10-28 00:44:25.482 16103 16103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 00:44:26.389 16103 16103 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.
10-28 00:44:27.770 16103 16178 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-28 00:44:27.770 16103 16178 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-28 00:44:27.770 16103 16178 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-28 01:47:46.715 3170 3170 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 01:47:48.704 3170 3170 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.
10-28 01:47:50.236 3170 3504 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-28 01:47:50.236 3170 3504 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-28 01:47:50.236 3170 3504 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-28 02:48:10.944 11963 11963 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 02:48:11.518 11963 11963 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
10-28 04:47:12.037 18842 18842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 04:47:12.623 18842 18842 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
10-28 05:44:31.878 20941 20941 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 05:44:32.223 20941 20941 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
10-28 06:53:54.038 24439 24439 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 06:53:54.601 24439 24439 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
10-28 07:13:53.151 25192 25192 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 07:13:53.706 25192 25192 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
10-28 07:13:59.396 25390 25390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 07:13:59.624 25390 25390 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
10-28 07:33:53.088 25968 25968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 07:33:53.335 25968 25968 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
10-28 08:41:54.207 27065 27065 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 08:41:54.768 27065 27065 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
10-28 08:44:21.500 27610 27610 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 08:44:21.763 27610 27610 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
10-28 09:53:54.013 29719 29719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 09:53:54.565 29719 29719 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
10-28 11:17:54.962 30762 30762 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 11:17:56.080 30762 30762 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
10-28 12:37:22.472 32205 32205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 12:37:23.079 32205 32205 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
10-28 12:40:50.647 1333 1333 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 12:40:51.071 1333 1333 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
10-28 12:48:55.514 2762 2762 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 12:48:55.829 2762 2762 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
10-28 12:53:23.456 4237 4237 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 12:53:24.601 4237 4237 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
10-28 12:58:42.358 5936 5936 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 12:58:43.143 5936 5936 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
10-28 13:18:56.013 7252 7252 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 13:18:56.746 7252 7252 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
10-28 13:33:23.751 7678 7678 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 13:33:23.956 7678 7678 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
10-28 14:38:18.692 19003 19003 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 14:38:19.556 19003 19003 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
10-28 14:41:32.186 20331 20331 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 14:41:33.234 20331 20331 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
10-28 14:50:04.072 21963 21963 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 14:50:05.838 21963 21963 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
10-28 14:51:02.620 22594 22594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 14:51:03.667 22594 22594 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
10-28 14:59:14.365 24364 24364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 14:59:17.406 24364 24364 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
10-28 15:19:56.205 27995 27995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 15:19:58.573 27995 27995 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
10-28 15:33:52.949 28773 28773 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 15:33:53.377 28773 28773 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
10-28 15:45:49.895 30397 30397 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 15:45:50.522 30397 30397 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
10-28 15:51:58.612 30961 30961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 15:51:59.179 30961 30961 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
10-28 16:45:39.110 9016 9016 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 16:45:41.478 9016 9016 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
10-28 17:05:43.003 9777 9777 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 17:05:43.429 9777 9777 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
10-28 17:11:44.647 10221 10221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 17:11:44.922 10221 10221 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
10-28 17:22:27.378 11826 11826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 17:22:27.788 11826 11826 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
10-28 17:32:49.076 12563 12563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 17:32:49.612 12563 12563 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
10-28 17:36:08.584 13334 13334 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 17:36:08.903 13334 13334 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
10-28 17:49:06.912 16250 16250 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 17:49:07.463 16250 16250 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
10-28 18:00:51.083 17008 17008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 18:00:51.763 17008 17008 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
10-28 18:54:44.165 27900 27900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 18:54:44.946 27900 27900 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
10-28 19:09:42.987 29286 29286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:09:43.561 29286 29286 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
10-28 19:16:01.068 29482 29482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:16:01.394 29482 29482 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
10-28 19:28:38.464 31776 31776 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:28:39.590 31776 31776 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
10-28 19:39:49.054 1352 1352 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:39:49.685 1352 1352 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
10-28 19:44:04.785 2886 2886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:44:05.489 2886 2886 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
10-28 19:52:01.960 3524 3524 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:52:02.628 3524 3524 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
10-28 19:58:53.482 4662 4662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 19:58:54.537 4662 4662 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
10-28 21:09:30.647 4977 4977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:09:32.485 4977 4977 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-28 21:09:32.485 4977 4977 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-28 21:09:32.485 4977 4977 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-28 21:09:32.485 4977 4977 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-28 21:09:32.485 4977 4977 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-28 21:09:32.485 4977 4977 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-28 21:09:32.485 4977 4977 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-28 21:09:32.485 4977 4977 W System.err: at
java.lang.Class.newInstance(Native Method)
10-28 21:09:32.485 4977 4977 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-28 21:09:32.485 4977 4977 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-28 21:09:32.485 4977 4977 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-28 21:09:32.485 4977 4977 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-28 21:09:32.485 4977 4977 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-28 21:09:32.485 4977 4977 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-28 21:09:32.485 4977 4977 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-28 21:09:32.485 4977 4977 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-28 21:09:32.485 4977 4977 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-28 21:09:32.486 4977 4977 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-28 21:09:32.486 4977 4977 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-28 21:09:32.486 4977 4977 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-28 21:09:32.486 4977 4977 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-28 21:09:32.486 4977 4977 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-28 21:09:32.657 4977 4977 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.
10-28 21:09:33.833 4977 4977 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-28 21:09:33.835 4977 4977 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-28 21:09:34.669 4977 5216 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-28 21:09:34.669 4977 5216 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-28 21:09:34.669 4977 5216 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-28 21:09:35.311 4977 5222 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-28 21:09:35.311 4977 5222 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-28 21:10:13.671 6851 6851 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:10:14.569 6851 6851 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-28 21:10:14.570 6851 6851 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-28 21:10:14.571 6851 6851 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-28 21:10:14.571 6851 6851 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-28 21:10:14.571 6851 6851 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-28 21:10:14.571 6851 6851 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-28 21:10:14.571 6851 6851 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-28 21:10:14.571 6851 6851 W System.err: at
java.lang.Class.newInstance(Native Method)
10-28 21:10:14.571 6851 6851 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-28 21:10:14.571 6851 6851 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-28 21:10:14.571 6851 6851 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-28 21:10:14.571 6851 6851 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-28 21:10:14.571 6851 6851 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-28 21:10:14.571 6851 6851 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-28 21:10:14.571 6851 6851 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-28 21:10:14.571 6851 6851 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-28 21:10:14.571 6851 6851 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-28 21:10:14.572 6851 6851 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-28 21:10:14.572 6851 6851 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-28 21:10:14.572 6851 6851 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-28 21:10:14.572 6851 6851 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-28 21:10:14.572 6851 6851 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-28 21:10:14.657 6851 6851 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.
10-28 21:10:15.543 6851 6851 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-28 21:10:15.543 6851 6851 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-28 21:10:16.570 6851 7010 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-28 21:10:16.570 6851 7010 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-28 21:10:16.570 6851 7010 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-28 21:10:17.339 6851 7022 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-28 21:10:17.340 6851 7022 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-28 21:12:01.380 10937 10937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:12:02.381 10937 10937 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
10-28 21:15:14.542 15085 15085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:15:16.119 15085 15085 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
10-28 21:18:53.011 18228 18228 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:18:53.596 18228 18228 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
10-28 21:27:48.241 19654 19654 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:27:48.931 19654 19654 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
10-28 21:33:03.696 20445 20445 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:33:05.068 20445 20445 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
10-28 21:56:53.347 24915 24915 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 21:56:53.994 24915 24915 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
10-28 22:11:34.633 25660 25660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 22:11:34.964 25660 25660 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
10-28 23:13:57.792 11329 11329 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 23:19:17.820 11567 11567 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-28 23:19:18.440 11567 11567 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
10-29 00:09:35.834 19642 19642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 00:09:36.461 19642 19642 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
10-29 01:04:03.579 27109 27109 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 01:04:06.208 27109 27109 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.
10-29 01:04:11.283 27109 27393 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-29 01:04:11.284 27109 27393 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-29 02:00:19.073 10270 10270 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 02:00:19.806 10270 10270 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
10-29 07:03:19.768 23114 23114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 07:03:20.631 23114 23114 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
10-29 07:08:22.159 23938 23938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 08:06:47.338 25148 25148 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 08:06:47.869 25148 25148 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.
10-29 08:06:49.405 25148 25340 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-29 08:06:49.405 25148 25340 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-29 08:06:49.405 25148 25340 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-29 08:52:53.407 26912 26912 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 08:52:54.398 26912 26912 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
10-29 09:15:22.995 28942 28942 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 09:15:24.274 28942 28942 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
10-29 09:33:16.494 30742 30742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 09:33:17.240 30742 30742 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
10-29 10:06:47.380 32469 32469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:06:47.880 32469 32469 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
10-29 10:07:20.775 32748 32748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:07:21.069 32748 32748 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
10-29 10:10:54.019 1021 1021 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:10:54.472 1021 1021 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
10-29 10:13:00.441 2992 2992 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:13:00.854 2992 2992 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
10-29 10:30:36.306 8034 8034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:30:36.843 8034 8034 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
10-29 10:41:52.383 8590 8590 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:41:52.720 8590 8590 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
10-29 10:53:51.343 11997 11997 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:53:52.372 11997 11997 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
10-29 10:54:52.664 12398 12398 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 10:54:52.950 12398 12398 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
10-29 11:19:58.766 13828 13828 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 11:19:59.529 13828 13828 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
10-29 12:17:31.516 18466 18466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 12:17:32.649 18466 18466 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
10-29 13:04:25.309 24802 24802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 14:20:53.392 27454 27454 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 14:20:54.365 27454 27454 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
10-29 14:40:28.409 28531 28531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 14:40:29.939 28531 28531 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
10-29 15:03:39.139 1649 1649 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 15:03:39.842 1649 1649 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
10-29 15:06:33.933 4177 4177 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 15:06:34.251 4177 4177 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
10-29 16:03:49.776 22995 22995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 16:03:50.508 22995 22995 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
10-29 18:05:09.278 11717 11717 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 18:05:11.263 11717 11717 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
10-29 18:09:00.792 14913 14913 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 18:09:01.613 14913 14913 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
10-29 18:12:13.589 15282 15282 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 18:12:14.094 15282 15282 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
10-29 18:12:35.929 15368 15368 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 18:12:36.187 15368 15368 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
10-29 19:03:39.168 24919 24919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 19:03:39.742 24919 24919 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
10-29 19:13:55.577 27185 27185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 19:13:56.339 27185 27185 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
10-29 19:32:16.016 30756 30756 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 19:32:16.950 30756 30756 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
10-29 23:11:32.625 4847 4847 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 23:11:33.814 4847 4847 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.
10-29 23:11:35.545 4847 4847 W com.mbwhatsapp: type=1400 audit(0.0:1326): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-29 23:48:58.119 21891 21891 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-29 23:48:58.895 21891 21891 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
10-30 09:18:08.794 6253 6253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 09:18:09.698 6253 6253 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-30 09:18:09.698 6253 6253 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-30 09:18:09.698 6253 6253 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-30 09:18:09.698 6253 6253 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-30 09:18:09.698 6253 6253 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-30 09:18:09.698 6253 6253 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-30 09:18:09.698 6253 6253 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-30 09:18:09.698 6253 6253 W System.err: at
java.lang.Class.newInstance(Native Method)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-30 09:18:09.699 6253 6253 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-30 09:18:09.699 6253 6253 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-30 09:18:09.699 6253 6253 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-30 09:18:09.699 6253 6253 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-30 09:18:09.699 6253 6253 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-30 09:18:09.699 6253 6253 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-30 09:18:09.699 6253 6253 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-30 09:18:09.699 6253 6253 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-30 09:18:09.798 6253 6253 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.
10-30 09:18:10.720 6253 6253 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-30 09:18:10.721 6253 6253 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-30 09:18:11.152 6253 6405 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-30 09:18:11.152 6253 6405 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-30 09:18:11.152 6253 6405 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-30 09:18:11.704 6253 6423 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=86ab00e3-f822-497c-986b-d8acfb478491, generation=0)
10-30 09:18:12.035 6253 6412 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-30 09:18:12.037 6253 6412 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-30 09:19:21.928 9423 9423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 09:19:23.390 9423 9423 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
10-30 09:20:01.420 11427 11427 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 09:20:01.942 11427 11427 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
10-30 10:11:18.965 21844 21844 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 10:11:19.767 21844 21844 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
10-30 11:19:39.843 30685 30685 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 11:19:41.277 30685 30685 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.
10-30 11:19:42.928 30685 30948 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-30 11:19:42.928 30685 30948 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-30 11:19:42.928 30685 30948 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-30 12:17:57.696 5005 5005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 12:17:58.512 5005 5005 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
10-30 12:38:05.008 5867 5867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 12:38:05.689 5867 5867 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
10-30 12:42:20.933 8103 8103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 12:42:23.465 8103 8103 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
10-30 12:44:29.654 9808 9808 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 12:44:30.318 9808 9808 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
10-30 12:48:41.093 10739 10739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 12:48:41.795 10739 10739 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
10-30 13:28:05.838 14321 14321 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 13:28:07.058 14321 14321 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
10-30 14:23:50.716 17211 17211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 14:23:51.687 17211 17211 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
10-30 14:43:01.388 18124 18124 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 14:43:02.072 18124 18124 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
10-30 15:32:46.573 19580 19580 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 15:32:47.313 19580 19580 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
10-30 16:01:26.381 26779 26779 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 16:01:27.034 26779 26779 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
10-30 16:11:48.153 28067 28067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 16:11:49.022 28067 28067 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
10-30 16:35:13.939 28777 28777 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 16:35:14.790 28777 28777 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
10-30 17:12:24.335 30214 30214 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 17:12:25.521 30214 30214 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
10-30 17:29:26.266 30734 30734 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 17:29:26.580 30734 30734 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
10-30 17:36:22.585 31591 31591 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 17:36:23.271 31591 31591 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
10-30 18:16:15.248 11269 11269 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 18:16:16.048 11269 11269 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
10-30 18:19:58.273 12910 12910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 18:20:00.115 12910 12910 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
10-30 19:11:16.947 25080 25080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 19:11:18.366 25080 25080 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
10-30 19:19:00.136 28496 28496 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 19:19:00.971 28496 28496 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
10-30 19:30:00.847 4099 4099 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 19:30:01.656 4099 4099 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
10-30 19:40:40.910 7000 7000 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 19:40:41.680 7000 7000 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
10-30 19:58:20.265 11506 11506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 19:58:20.919 11506 11506 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
10-30 20:33:17.062 28275 28275 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 20:33:17.846 28275 28275 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
10-30 21:36:05.207 18046 18046 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 21:36:05.878 18046 18046 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
10-30 21:38:04.736 18182 18182 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 21:38:05.037 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
10-30 22:38:10.532 23162 23162 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 22:38:11.634 23162 23162 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
10-30 22:39:21.135 23612 23612 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 22:39:21.710 23612 23612 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
10-30 23:46:14.562 8330 8330 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-30 23:46:15.177 8330 8330 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.
10-30 23:46:16.662 8330 8382 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-30 23:46:16.662 8330 8382 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
10-31 02:16:43.572 23141 23141 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 02:16:45.366 23141 23141 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
10-31 02:18:57.585 25041 25041 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 02:19:02.938 25041 25041 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
10-31 04:11:36.966 4397 4397 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 04:11:37.569 4397 4397 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
10-31 04:16:14.126 5211 5211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 04:16:14.445 5211 5211 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
10-31 05:11:09.930 9090 9090 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 05:11:10.754 9090 9090 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
10-31 05:53:23.596 13394 13394 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 05:53:24.731 13394 13394 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.
10-31 05:53:26.114 13394 13472 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-31 05:53:26.114 13394 13472 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-31 05:53:26.114 13394 13472 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
10-31 06:11:39.969 17708 17708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 06:11:40.805 17708 17708 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
10-31 06:16:25.259 18422 18422 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 06:16:26.306 18422 18422 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
10-31 07:11:41.545 25549 25549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 07:11:42.320 25549 25549 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
10-31 07:23:33.635 26131 26131 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 07:23:33.887 26131 26131 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
10-31 07:41:57.561 26786 26786 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 07:41:57.958 26786 26786 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
10-31 08:01:56.689 27885 27885 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 08:01:57.049 27885 27885 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
10-31 09:07:41.013 29353 29353 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 09:07:41.595 29353 29353 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
10-31 10:11:41.302 32218 32218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 10:11:42.299 32218 32218 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
10-31 10:14:28.552 3573 3573 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 10:14:29.219 3573 3573 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
10-31 10:17:00.422 4731 4731 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 10:17:01.450 4731 4731 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
10-31 10:20:34.444 5627 5627 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 10:20:35.490 5627 5627 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
10-31 10:29:24.602 6362 6362 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 10:29:25.275 6362 6362 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
10-31 10:41:12.918 7184 7184 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 10:41:13.401 7184 7184 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
10-31 11:14:59.083 11073 11073 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 11:15:00.775 11073 11073 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
10-31 11:24:28.930 12101 12101 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 11:24:29.498 12101 12101 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
10-31 11:55:41.646 17115 17115 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 11:55:42.227 17115 17115 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
10-31 12:21:24.751 19486 19486 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 12:21:25.616 19486 19486 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
10-31 12:32:42.584 20139 20139 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 12:32:43.426 20139 20139 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
10-31 13:08:40.550 24221 24221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 13:08:41.122 24221 24221 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
10-31 14:21:04.067 30663 30663 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 14:21:04.889 30663 30663 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
10-31 15:25:35.055 4141 4141 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 15:25:36.018 4141 4141 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
10-31 16:39:01.412 10259 10259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 16:39:02.366 10259 10259 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.
10-31 16:39:04.434 10259 10259 W com.mbwhatsapp: type=1400 audit(0.0:53591): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
10-31 17:40:00.520 21423 21423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 17:40:01.228 21423 21423 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
10-31 17:59:41.629 22431 22431 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 17:59:42.262 22431 22431 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
10-31 18:12:31.589 23126 23126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 18:12:32.951 23126 23126 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
10-31 18:29:13.854 28775 28775 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 18:29:15.418 28775 28775 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
10-31 18:31:28.835 30066 30066 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 18:31:29.784 30066 30066 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
10-31 19:19:13.860 6202 6202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 19:19:15.322 6202 6202 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
10-31 19:19:15.322 6202 6202 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
10-31 19:19:15.322 6202 6202 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
10-31 19:19:15.322 6202 6202 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
10-31 19:19:15.322 6202 6202 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
10-31 19:19:15.322 6202 6202 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
10-31 19:19:15.322 6202 6202 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
10-31 19:19:15.322 6202 6202 W System.err: at
java.lang.Class.newInstance(Native Method)
10-31 19:19:15.322 6202 6202 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
10-31 19:19:15.323 6202 6202 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
10-31 19:19:15.323 6202 6202 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
10-31 19:19:15.323 6202 6202 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
10-31 19:19:15.323 6202 6202 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
10-31 19:19:15.323 6202 6202 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
10-31 19:19:15.323 6202 6202 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
10-31 19:19:15.323 6202 6202 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
10-31 19:19:15.323 6202 6202 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
10-31 19:19:15.323 6202 6202 W System.err: at
android.os.Looper.loop(Looper.java:334)
10-31 19:19:15.323 6202 6202 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
10-31 19:19:15.323 6202 6202 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
10-31 19:19:15.323 6202 6202 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
10-31 19:19:15.324 6202 6202 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
10-31 19:19:15.433 6202 6202 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.
10-31 19:19:16.041 6202 6202 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
10-31 19:19:16.042 6202 6202 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
10-31 19:19:16.816 6202 6352 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
10-31 19:19:16.816 6202 6352 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
10-31 19:19:16.816 6202 6352 W com.mbwhatsapp: and incorrect proguard
optimizations.
10-31 19:19:17.296 6202 6431 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
10-31 19:19:17.296 6202 6431 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
10-31 19:20:22.501 8538 8538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 19:20:23.494 8538 8538 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
10-31 19:42:10.170 20477 20477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 19:42:10.927 20477 20477 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
10-31 20:12:49.513 30636 30636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 20:12:50.269 30636 30636 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
10-31 20:25:41.626 1553 1553 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 20:25:42.278 1553 1553 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
10-31 21:18:01.787 5852 5852 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 21:18:03.033 5852 5852 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
10-31 21:23:52.721 8395 8395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 21:23:53.544 8395 8395 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
10-31 22:12:48.662 16452 16452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 22:12:49.548 16452 16452 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
10-31 23:13:08.897 28888 28888 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 23:13:09.474 28888 28888 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
10-31 23:20:16.292 30897 30897 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 23:20:17.269 30897 30897 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
10-31 23:24:30.567 614 614 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
10-31 23:24:31.186 614 614 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
11-01 00:13:07.541 14030 14030 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 00:13:08.406 14030 14030 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
11-01 01:12:48.650 28856 28856 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 01:12:49.325 28856 28856 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
11-01 02:00:20.942 4889 4889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 02:00:25.082 4889 4889 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
11-01 02:12:48.642 6170 6170 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 02:12:49.208 6170 6170 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
11-01 02:38:01.761 8054 8054 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 02:38:02.589 8054 8054 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
11-01 03:01:01.101 9014 9014 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 03:01:02.659 9014 9014 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
11-01 03:08:28.801 4854 4854 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 03:08:29.978 4854 4854 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-01 03:08:29.979 4854 4854 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.Class.newInstance(Native Method)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-01 03:08:29.979 4854 4854 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-01 03:08:29.979 4854 4854 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-01 03:08:29.979 4854 4854 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-01 03:08:29.979 4854 4854 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-01 03:08:29.979 4854 4854 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-01 03:08:29.979 4854 4854 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-01 03:08:29.979 4854 4854 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-01 03:08:29.979 4854 4854 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-01 03:08:30.329 4854 4854 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.
11-01 03:08:31.687 4854 4854 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-01 03:08:31.687 4854 4854 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-01 03:08:33.304 4854 5075 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-01 03:08:33.304 4854 5075 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-01 03:08:33.304 4854 5075 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-01 03:08:38.666 4854 5245 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-01 03:08:38.667 4854 5245 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-01 03:08:39.225 4854 4863 W com.mbwhatsapp: Suspending all threads took:
22.790ms
11-01 03:13:06.236 12168 12168 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 03:13:06.722 12168 12168 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
11-01 03:14:25.849 13535 13535 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 03:14:26.386 13535 13535 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
11-01 05:55:02.337 18516 18516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 05:55:03.242 18516 18516 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
11-01 09:56:54.716 23039 23039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 09:56:56.226 23039 23039 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
11-01 12:59:39.906 13139 13139 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 12:59:40.751 13139 13139 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
11-01 17:20:53.480 3922 3922 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 17:20:55.753 3922 3922 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-01 17:20:55.754 3922 3922 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.Class.newInstance(Native Method)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-01 17:20:55.754 3922 3922 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-01 17:20:55.754 3922 3922 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-01 17:20:55.754 3922 3922 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-01 17:20:55.754 3922 3922 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-01 17:20:55.754 3922 3922 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-01 17:20:55.754 3922 3922 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-01 17:20:55.754 3922 3922 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-01 17:20:55.754 3922 3922 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-01 17:20:56.210 3922 3922 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.
11-01 17:21:01.007 3922 3922 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-01 17:21:01.008 3922 3922 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-01 17:21:06.309 3922 3939 W com.mbwhatsapp: Suspending all threads took:
15.591ms
11-01 17:21:06.728 3922 4471 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-01 17:21:06.728 3922 4471 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-01 17:21:06.728 3922 4471 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-01 17:21:09.927 3922 3939 W com.mbwhatsapp: Suspending all threads took:
25.058ms
11-01 18:15:18.449 27619 27619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 18:15:19.312 27619 27619 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.
11-01 18:15:20.560 27619 27619 W com.mbwhatsapp: type=1400 audit(0.0:5447): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-01 18:15:20.580 27619 27619 W com.mbwhatsapp: type=1400 audit(0.0:5448): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-01 18:26:17.975 28553 28553 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 18:26:18.288 28553 28553 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
11-01 19:16:25.907 9078 9078 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 19:16:27.008 9078 9078 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
11-01 19:20:46.039 10338 10338 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 19:20:46.940 10338 10338 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
11-01 20:15:12.709 31420 31420 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 20:15:13.990 31420 31420 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
11-01 21:15:34.109 15682 15682 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 21:15:35.026 15682 15682 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
11-01 21:18:35.614 16455 16455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 21:18:37.275 16455 16455 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.
11-01 21:18:39.512 16455 16455 W com.mbwhatsapp: type=1400 audit(0.0:43379): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-01 22:15:53.738 31782 31782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 22:15:55.098 31782 31782 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
11-01 23:16:27.698 16332 16332 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 23:16:28.656 16332 16332 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
11-01 23:36:16.285 17185 17185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 23:36:16.957 17185 17185 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
11-01 23:50:03.286 18916 18916 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 23:50:04.237 18916 18916 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
11-01 23:56:30.815 21263 21263 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-01 23:56:31.471 21263 21263 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
11-02 00:00:51.498 22142 22142 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 00:00:52.200 22142 22142 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
11-02 00:20:10.763 23485 23485 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 00:20:12.040 23485 23485 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
11-02 00:26:22.706 24964 24964 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 00:26:23.380 24964 24964 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
11-02 00:39:00.472 27141 27141 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 00:39:01.464 27141 27141 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
11-02 00:57:58.662 28203 28203 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 00:57:59.376 28203 28203 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
11-02 01:44:27.760 32308 32308 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 01:44:29.288 32308 32308 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
11-02 03:23:40.919 5245 5245 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 03:23:41.883 5245 5245 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.
11-02 04:45:42.838 7655 7655 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 04:45:44.233 7655 7655 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
11-02 05:24:00.663 11000 11000 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 05:24:01.388 11000 11000 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
11-02 06:30:22.662 15319 15319 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 06:30:23.321 15319 15319 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
11-02 06:37:51.971 15961 15961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 06:37:52.319 15961 15961 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
11-02 07:40:41.540 28468 28468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 07:40:42.674 28468 28468 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
11-02 08:40:47.750 4628 4628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 08:40:50.067 4628 4628 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-02 08:40:50.068 4628 4628 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.Class.newInstance(Native Method)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-02 08:40:50.068 4628 4628 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-02 08:40:50.068 4628 4628 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-02 08:40:50.068 4628 4628 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-02 08:40:50.068 4628 4628 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-02 08:40:50.068 4628 4628 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-02 08:40:50.068 4628 4628 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-02 08:40:50.068 4628 4628 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-02 08:40:50.068 4628 4628 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-02 08:40:50.672 4628 4628 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.
11-02 08:40:53.432 4628 4640 W com.mbwhatsapp: Suspending all threads took:
6.316ms
11-02 08:40:53.958 4628 4628 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-02 08:40:53.976 4628 4628 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-02 08:40:56.663 4628 4907 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-02 08:40:56.663 4628 4907 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-02 08:40:56.663 4628 4907 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-02 08:43:16.781 9504 9504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 08:43:18.447 9504 9504 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
11-02 08:45:03.250 12507 12507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 08:45:04.945 12507 12507 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.
11-02 08:45:07.137 12507 12507 W com.mbwhatsapp: type=1400 audit(0.0:3214): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-02 16:15:37.363 5820 5820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 16:15:39.245 5820 5820 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-02 16:15:39.246 5820 5820 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.Class.newInstance(Native Method)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-02 16:15:39.246 5820 5820 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-02 16:15:39.246 5820 5820 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-02 16:15:39.246 5820 5820 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-02 16:15:39.246 5820 5820 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-02 16:15:39.246 5820 5820 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-02 16:15:39.246 5820 5820 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-02 16:15:39.246 5820 5820 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-02 16:15:39.246 5820 5820 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-02 16:15:39.570 5820 5820 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.
11-02 16:15:41.328 5820 5820 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-02 16:15:41.329 5820 5820 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-02 16:15:41.702 5820 5820 W com.mbwhatsapp: type=1400 audit(0.0:1480): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-02 16:15:41.725 5820 5820 W com.mbwhatsapp: type=1400 audit(0.0:1481): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 16:15:41.799 5820 5820 W com.mbwhatsapp: type=1400 audit(0.0:1482): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 16:15:42.112 5820 5820 W com.mbwhatsapp: type=1400 audit(0.0:1483): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 16:15:42.222 5820 5820 W com.mbwhatsapp: type=1400 audit(0.0:1484): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 16:15:44.267 5820 5988 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-02 16:15:44.267 5820 5988 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-02 16:15:44.267 5820 5988 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-02 16:15:50.448 5820 6179 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-02 16:15:50.448 5820 6179 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-02 16:20:50.418 14436 14436 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 16:20:51.064 14436 14436 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.
11-02 16:20:53.740 14436 14436 W com.mbwhatsapp: type=1400 audit(0.0:3643): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 16:20:53.803 14436 14436 W com.mbwhatsapp: type=1400 audit(0.0:3644): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-02 17:09:24.074 20980 20980 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 17:09:24.911 20980 20980 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
11-02 18:09:21.068 27918 27918 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 18:09:21.942 27918 27918 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
11-02 18:10:31.398 28525 28525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 18:10:31.736 28525 28525 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
11-02 19:09:42.888 20785 20785 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 19:09:43.545 20785 20785 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.
11-02 19:09:44.961 20785 20785 W com.mbwhatsapp: type=1400 audit(0.0:9049): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-02 19:20:28.468 22909 22909 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 19:20:29.172 22909 22909 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
11-02 19:23:48.742 25211 25211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 19:23:51.693 25211 25211 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
11-02 19:39:21.230 28477 28477 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 19:39:22.305 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.
11-02 19:39:23.943 28477 28477 W com.mbwhatsapp: type=1400 audit(0.0:11902): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 19:39:23.943 28477 28477 W com.mbwhatsapp: type=1400 audit(0.0:11903): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-02 19:57:34.394 31453 31453 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 19:57:35.521 31453 31453 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
11-02 20:08:21.712 3576 3576 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 20:08:23.036 3576 3576 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.
11-02 20:08:25.322 3576 3576 W com.mbwhatsapp: type=1400 audit(0.0:16964): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-02 20:08:25.322 3576 3576 W com.mbwhatsapp: type=1400 audit(0.0:16965): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-02 20:15:33.659 7189 7189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 20:15:38.205 7189 7189 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
11-02 21:09:30.381 23606 23606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 21:09:31.508 23606 23606 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
11-02 21:35:05.649 30734 30734 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 21:35:07.150 30734 30734 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
11-02 22:09:23.725 4492 4492 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 22:09:24.682 4492 4492 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
11-02 23:10:33.079 20363 20363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 23:10:33.643 20363 20363 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
11-02 23:27:50.109 20665 20665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-02 23:27:50.489 20665 20665 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
11-03 00:09:30.777 30843 30843 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 00:09:31.672 30843 30843 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
11-03 00:11:31.461 31012 31012 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 00:11:31.779 31012 31012 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
11-03 01:21:05.643 10293 10293 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 01:21:06.433 10293 10293 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
11-03 02:24:30.531 23154 23154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 02:24:31.210 23154 23154 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
11-03 03:26:17.608 489 489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 03:26:18.623 489 489 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
11-03 04:31:54.486 6546 6546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 04:31:57.516 6546 6546 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
11-03 04:32:55.593 7594 7594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 04:32:56.553 7594 7594 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
11-03 05:24:31.149 28269 28269 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 05:24:31.850 28269 28269 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
11-03 05:27:32.578 28407 28407 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 05:27:32.889 28407 28407 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
11-03 05:35:09.984 28741 28741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 05:35:10.268 28741 28741 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
11-03 05:47:20.897 30465 30465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 05:47:21.805 30465 30465 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
11-03 05:49:38.334 520 520 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 05:49:38.764 520 520 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
11-03 06:24:32.562 5579 5579 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 06:24:33.279 5579 5579 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
11-03 07:24:26.981 16889 16889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 07:24:27.551 16889 16889 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.
11-03 07:24:28.911 16889 16889 W com.mbwhatsapp: type=1400 audit(0.0:8667): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-03 07:27:28.045 17645 17645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 07:27:28.367 17645 17645 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
11-03 07:30:39.332 19799 19799 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 07:30:41.420 19799 19799 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
11-03 08:29:21.114 26764 26764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 08:29:22.195 26764 26764 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.
11-03 08:29:23.697 26764 26764 W com.mbwhatsapp: type=1400 audit(0.0:11797): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-03 08:51:00.229 27984 27984 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 08:51:03.086 27984 27984 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
11-03 09:09:18.942 29290 29290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 09:09:19.538 29290 29290 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
11-03 09:22:19.136 32470 32470 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 09:22:20.083 32470 32470 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
11-03 10:24:07.249 6900 6900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 10:24:07.911 6900 6900 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.
11-03 10:24:09.112 6900 6900 W com.mbwhatsapp: type=1400 audit(0.0:182344): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-03 11:24:30.354 12362 12362 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 11:24:31.027 12362 12362 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
11-03 12:33:22.062 14952 14952 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 12:33:23.042 14952 14952 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
11-03 12:52:12.017 16383 16383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 12:52:12.789 16383 16383 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
11-03 14:04:28.092 17158 17158 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 14:04:28.666 17158 17158 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
11-03 16:09:22.281 19077 19077 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 16:09:23.228 19077 19077 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
11-03 17:14:12.134 20576 20576 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 17:14:13.893 20576 20576 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
11-03 18:00:09.940 31772 31772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 18:00:12.623 31772 31772 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
11-03 18:02:35.576 3638 3638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 18:02:36.206 3638 3638 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
11-03 18:05:49.713 5372 5372 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 18:05:50.752 5372 5372 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
11-03 18:09:19.427 6705 6705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 18:09:21.416 6705 6705 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
11-03 19:24:07.289 25098 25098 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 19:24:08.589 25098 25098 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
11-03 19:30:11.472 25773 25773 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 19:30:12.054 25773 25773 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
11-03 19:39:26.411 28671 28671 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 19:39:27.160 28671 28671 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
11-03 20:25:22.033 6514 6514 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 20:25:23.716 6514 6514 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
11-03 21:04:37.313 8965 8965 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 21:04:38.005 8965 8965 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
11-03 21:40:43.085 13731 13731 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 21:40:44.059 13731 13731 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
11-03 22:24:11.337 20745 20745 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 22:24:13.590 20745 20745 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
11-03 22:30:54.045 22860 22860 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 22:30:55.287 22860 22860 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
11-03 23:25:37.315 31985 31985 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 23:25:38.505 31985 31985 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.
11-03 23:25:40.182 31985 31985 W com.mbwhatsapp: type=1400 audit(0.0:218867): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-03 23:28:14.219 32513 32513 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 23:28:14.955 32513 32513 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
11-03 23:36:40.634 32714 32714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 23:36:42.422 32714 32714 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
11-03 23:47:41.965 4848 4848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-03 23:47:43.327 4848 4848 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
11-04 00:24:29.460 13792 13792 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 00:24:30.250 13792 13792 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
11-04 00:35:58.404 15848 15848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 00:35:59.596 15848 15848 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
11-04 01:24:41.240 28328 28328 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 01:24:41.973 28328 28328 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
11-04 01:45:20.546 32116 32116 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 01:45:21.587 32116 32116 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
11-04 02:24:07.455 7768 7768 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 02:24:08.753 7768 7768 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
11-04 03:00:04.422 18385 18385 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 03:00:06.322 18385 18385 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.
11-04 03:00:09.514 18385 18385 W com.mbwhatsapp: type=1400 audit(0.0:372981): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-04 03:00:09.514 18385 18385 W com.mbwhatsapp: type=1400 audit(0.0:372982): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-04 03:00:09.514 18385 18385 W com.mbwhatsapp: type=1400 audit(0.0:372983): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-04 04:09:43.936 4771 4771 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 04:09:44.745 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
11-04 04:24:14.914 6910 6910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 04:24:15.696 6910 6910 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
11-04 05:05:14.563 4413 4413 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:05:16.494 4413 4413 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-04 05:05:16.494 4413 4413 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.Class.newInstance(Native Method)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-04 05:05:16.494 4413 4413 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-04 05:05:16.494 4413 4413 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-04 05:05:16.494 4413 4413 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-04 05:05:16.494 4413 4413 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-04 05:05:16.494 4413 4413 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-04 05:05:16.494 4413 4413 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-04 05:05:16.494 4413 4413 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-04 05:05:16.495 4413 4413 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-04 05:05:17.105 4413 4413 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.
11-04 05:05:24.922 4413 4413 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-04 05:05:24.923 4413 4413 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-04 05:05:25.829 4413 4413 W com.mbwhatsapp: type=1400 audit(0.0:1410): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-04 05:05:25.230 4413 4422 W com.mbwhatsapp: Suspending all threads took:
14.891ms
11-04 05:05:25.855 4413 4413 W com.mbwhatsapp: type=1400 audit(0.0:1411): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-04 05:05:25.895 4413 4413 W com.mbwhatsapp: type=1400 audit(0.0:1412): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-04 05:05:26.229 4413 4413 W com.mbwhatsapp: type=1400 audit(0.0:1413): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-04 05:05:29.985 4413 5428 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-04 05:05:29.985 4413 5428 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-04 05:05:29.985 4413 5428 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-04 05:05:34.410 4413 4422 W com.mbwhatsapp: Suspending all threads took:
7.589ms
11-04 05:05:36.393 4413 5489 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-04 05:05:36.393 4413 5489 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-04 05:07:35.671 9538 9538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:07:36.286 9538 9538 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
11-04 05:24:33.016 19877 19877 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:24:33.540 19877 19877 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
11-04 05:27:27.410 20522 20522 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:27:28.937 20522 20522 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
11-04 05:31:39.008 21748 21748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:31:39.636 21748 21748 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
11-04 05:36:33.052 22581 22581 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:36:33.732 22581 22581 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
11-04 05:39:28.860 22947 22947 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:39:29.636 22947 22947 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
11-04 05:45:51.567 24494 24494 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:45:52.502 24494 24494 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
11-04 05:54:50.437 25368 25368 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 05:54:51.026 25368 25368 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
11-04 07:12:35.038 31050 31050 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 07:12:35.707 31050 31050 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
11-04 07:26:45.189 3069 3069 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 07:26:46.092 3069 3069 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.
11-04 07:26:47.223 3069 3069 W com.mbwhatsapp: type=1400 audit(0.0:9516): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-04 07:44:36.063 4484 4484 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 07:44:37.283 4484 4484 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
11-04 14:08:19.880 25494 25494 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 14:08:30.461 25494 25494 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
11-04 15:24:36.050 3898 3898 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 15:24:36.585 3898 3898 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.
11-04 15:24:37.868 3898 3898 W com.mbwhatsapp: type=1400 audit(0.0:24905): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-04 15:35:13.755 4462 4462 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 15:35:14.374 4462 4462 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
11-04 16:28:36.041 6179 6179 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 16:28:37.201 6179 6179 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
11-04 17:20:30.589 7172 7172 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 17:20:32.998 7172 7172 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
11-04 17:40:16.027 8289 8289 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 17:40:16.691 8289 8289 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
11-04 17:53:42.343 9063 9063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 17:53:42.826 9063 9063 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
11-04 18:31:29.244 12218 12218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 18:31:30.455 12218 12218 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
11-04 18:38:15.867 15553 15553 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 18:38:16.548 15553 15553 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
11-04 19:24:20.188 24713 24713 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 19:24:21.119 24713 24713 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
11-04 19:36:34.868 25761 25761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 19:36:35.659 25761 25761 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
11-04 19:47:33.998 26037 26037 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 19:47:34.467 26037 26037 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
11-04 20:06:33.485 27213 27213 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 20:06:34.168 27213 27213 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
11-04 20:19:16.844 27562 27562 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 20:19:17.805 27562 27562 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
11-04 20:37:42.159 28111 28111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 20:37:42.598 28111 28111 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
11-04 20:51:36.201 28576 28576 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 20:51:36.886 28576 28576 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
11-04 21:28:36.012 7931 7931 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 21:28:36.992 7931 7931 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.
11-04 21:28:38.869 7931 7931 W com.mbwhatsapp: type=1400 audit(0.0:36986): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-04 21:40:20.685 8879 8879 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 21:40:21.486 8879 8879 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
11-04 22:18:21.543 10642 10642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 22:18:22.490 10642 10642 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
11-04 23:24:55.882 22948 22948 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-04 23:24:56.542 22948 22948 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
11-05 00:34:36.907 3162 3162 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 00:34:38.115 3162 3162 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
11-05 01:38:48.453 14202 14202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 01:38:49.694 14202 14202 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
11-05 01:46:42.835 16496 16496 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 01:46:43.672 16496 16496 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
11-05 02:32:36.020 22259 22259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 02:32:38.233 22259 22259 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
11-05 04:17:12.813 23518 23518 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 04:17:13.377 23518 23518 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
11-05 06:19:35.108 25146 25146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 06:19:37.455 25146 25146 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
11-05 09:30:52.111 28714 28714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 09:30:55.753 28714 28714 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
11-05 09:32:56.132 31095 31095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 09:32:57.576 31095 31095 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
11-05 09:54:07.359 5710 5710 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 09:54:08.847 5710 5710 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
11-05 11:25:50.933 15181 15181 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 11:25:51.673 15181 15181 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
11-05 13:08:36.258 16813 16813 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 13:08:38.719 16813 16813 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
11-05 14:09:48.466 18012 18012 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 14:09:49.429 18012 18012 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
11-05 14:55:51.120 26423 26423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 14:55:53.052 26423 26423 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
11-05 15:00:33.301 29408 29408 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 15:00:34.115 29408 29408 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
11-05 17:05:23.109 5777 5777 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 17:05:25.106 5777 5777 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
11-05 17:55:03.892 8606 8606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 17:55:12.576 8606 8606 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
11-05 18:25:04.532 16755 16755 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 18:25:41.336 16755 16755 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.
11-05 18:25:51.554 16755 16755 W com.mbwhatsapp: type=1400 audit(0.0:118163): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-05 18:25:51.588 16755 16755 W com.mbwhatsapp: type=1400 audit(0.0:118164): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-05 18:39:12.692 18323 18323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 18:39:13.970 18323 18323 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
11-05 19:28:36.123 22918 22918 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 19:28:37.403 22918 22918 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
11-05 19:40:36.165 23402 23402 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 19:40:38.295 23402 23402 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
11-05 19:59:27.208 23765 23765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 19:59:27.987 23765 23765 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
11-05 20:15:52.899 24938 24938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 20:15:56.606 24938 24938 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
11-05 20:24:07.606 27946 27946 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 20:24:10.113 27946 27946 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
11-05 20:54:16.383 684 684 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 20:54:17.479 684 684 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
11-05 21:31:06.436 10764 10764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 21:31:07.596 10764 10764 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.
11-05 21:31:09.917 10764 10764 W com.mbwhatsapp: type=1400 audit(0.0:129611): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-05 21:44:35.039 12532 12532 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 21:44:35.703 12532 12532 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
11-05 21:51:17.038 12919 12919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 21:51:17.931 12919 12919 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
11-05 22:01:53.656 15308 15308 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 22:01:54.346 15308 15308 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
11-05 22:12:42.924 17495 17495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 22:12:43.688 17495 17495 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
11-05 22:16:44.702 17995 17995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 22:16:44.979 17995 17995 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
11-05 22:24:01.785 21915 21915 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 22:24:03.201 21915 21915 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
11-05 22:51:27.762 29433 29433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 22:51:29.076 29433 29433 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
11-05 23:24:15.461 9035 9035 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 23:24:16.245 9035 9035 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
11-05 23:47:32.217 13673 13673 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 23:47:32.848 13673 13673 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
11-05 23:54:13.211 15079 15079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-05 23:54:16.072 15079 15079 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
11-06 00:05:37.940 18130 18130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 00:05:42.571 18130 18130 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
11-06 00:08:31.535 19080 19080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 00:08:32.397 19080 19080 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
11-06 00:18:15.204 21346 21346 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 00:18:16.057 21346 21346 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
11-06 00:29:13.179 25689 25689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 00:29:14.298 25689 25689 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
11-06 00:54:15.057 29774 29774 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 00:54:15.781 29774 29774 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
11-06 02:00:13.167 17826 17826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 02:00:14.057 17826 17826 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
11-06 03:39:06.657 7753 7753 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 03:39:07.618 7753 7753 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
11-06 03:59:08.704 8119 8119 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 03:59:09.029 8119 8119 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
11-06 05:04:16.613 9344 9344 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 05:04:16.994 9344 9344 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
11-06 07:08:37.563 10323 10323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 07:08:38.288 10323 10323 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
11-06 10:04:43.609 13764 13764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 10:04:46.017 13764 13764 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
11-06 10:05:38.498 14979 14979 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 10:05:39.136 14979 14979 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
11-06 11:24:10.977 25175 25175 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 11:24:11.684 25175 25175 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
11-06 12:36:36.106 27098 27098 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 12:36:36.942 27098 27098 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
11-06 13:20:05.097 27714 27714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 13:20:05.437 27714 27714 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
11-06 13:22:56.367 29614 29614 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 13:22:57.067 29614 29614 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
11-06 13:48:14.261 30257 30257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 13:48:14.568 30257 30257 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
11-06 14:06:41.002 30805 30805 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 14:06:41.302 30805 30805 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
11-06 14:24:08.977 31789 31789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 14:24:09.344 31789 31789 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
11-06 14:38:20.237 32659 32659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 14:38:20.739 32659 32659 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
11-06 14:40:57.162 4907 4907 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 14:40:58.118 4907 4907 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
11-06 14:43:55.357 7190 7190 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 14:43:56.242 7190 7190 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
11-06 14:48:28.059 9214 9214 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 14:48:28.427 9214 9214 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
11-06 15:32:13.083 18991 18991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 15:32:13.870 18991 18991 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
11-06 15:53:30.391 19470 19470 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 15:53:32.185 19470 19470 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
11-06 16:44:52.659 20432 20432 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 16:44:55.282 20432 20432 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
11-06 16:50:25.743 22623 22623 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 16:50:27.064 22623 22623 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
11-06 16:53:35.602 25495 25495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 16:53:36.934 25495 25495 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
11-06 17:37:48.265 28997 28997 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 17:37:49.346 28997 28997 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
11-06 17:41:30.140 31371 31371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 17:41:30.998 31371 31371 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
11-06 17:56:18.195 32719 32719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 17:56:19.192 32719 32719 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
11-06 18:00:19.271 1628 1628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 18:00:19.626 1628 1628 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
11-06 18:45:49.600 8606 8606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 18:45:50.806 8606 8606 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
11-06 18:51:51.051 10527 10527 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 18:51:51.978 10527 10527 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
11-06 19:07:57.720 12494 12494 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 19:07:58.419 12494 12494 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
11-06 19:29:12.071 13324 13324 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 19:29:13.221 13324 13324 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
11-06 21:07:51.742 24544 24544 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 21:07:53.424 24544 24544 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
11-06 21:24:10.785 27562 27562 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 21:24:11.453 27562 27562 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
11-06 22:31:30.797 8272 8272 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 22:31:31.556 8272 8272 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
11-06 23:24:14.944 18201 18201 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-06 23:24:16.699 18201 18201 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
11-07 00:24:07.335 31156 31156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 00:24:08.406 31156 31156 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
11-07 01:25:55.286 3621 3621 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 01:25:57.578 3621 3621 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-07 01:25:57.579 3621 3621 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-07 01:25:57.580 3621 3621 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-07 01:25:57.580 3621 3621 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-07 01:25:57.580 3621 3621 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-07 01:25:57.580 3621 3621 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-07 01:25:57.580 3621 3621 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-07 01:25:57.580 3621 3621 W System.err: at
java.lang.Class.newInstance(Native Method)
11-07 01:25:57.583 3621 3621 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-07 01:25:57.583 3621 3621 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-07 01:25:57.583 3621 3621 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-07 01:25:57.583 3621 3621 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-07 01:25:57.584 3621 3621 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-07 01:25:57.584 3621 3621 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-07 01:25:57.584 3621 3621 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-07 01:25:57.584 3621 3621 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-07 01:25:57.584 3621 3621 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-07 01:25:57.584 3621 3621 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-07 01:25:57.584 3621 3621 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-07 01:25:57.584 3621 3621 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-07 01:25:57.584 3621 3621 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-07 01:25:57.584 3621 3621 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-07 01:25:58.577 3621 3621 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.
11-07 01:26:04.798 3621 3621 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-07 01:26:04.799 3621 3621 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-07 01:26:05.586 3621 3621 W com.mbwhatsapp: type=1400 audit(0.0:1183): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-07 01:26:05.602 3621 3621 W com.mbwhatsapp: type=1400 audit(0.0:1184): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-07 01:26:05.662 3621 3621 W com.mbwhatsapp: type=1400 audit(0.0:1185): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-07 01:26:06.026 3621 3621 W com.mbwhatsapp: type=1400 audit(0.0:1186): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-07 01:26:06.092 3621 3621 W com.mbwhatsapp: type=1400 audit(0.0:1187): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-07 01:26:08.196 3621 4328 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-07 01:26:08.196 3621 4328 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-07 01:26:08.196 3621 4328 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-07 01:26:12.484 3621 3630 W com.mbwhatsapp: Suspending all threads took:
18.333ms
11-07 02:28:28.780 18063 18063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 02:28:29.790 18063 18063 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.
11-07 02:28:31.099 18063 18063 W com.mbwhatsapp: type=1400 audit(0.0:8070): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-07 02:28:31.112 18063 18063 W com.mbwhatsapp: type=1400 audit(0.0:8071): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-07 02:49:40.059 18399 18399 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 02:49:40.418 18399 18399 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
11-07 03:57:40.090 19002 19002 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 03:57:40.572 19002 19002 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
11-07 06:01:40.396 20466 20466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 06:01:41.013 20466 20466 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
11-07 12:14:20.518 4382 4382 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 12:14:25.077 4382 4382 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-07 12:14:25.077 4382 4382 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-07 12:14:25.077 4382 4382 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-07 12:14:25.077 4382 4382 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-07 12:14:25.077 4382 4382 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-07 12:14:25.077 4382 4382 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-07 12:14:25.078 4382 4382 W System.err: at
java.lang.Class.newInstance(Native Method)
11-07 12:14:25.078 4382 4382 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-07 12:14:25.078 4382 4382 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-07 12:14:25.078 4382 4382 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-07 12:14:25.078 4382 4382 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-07 12:14:25.078 4382 4382 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-07 12:14:25.078 4382 4382 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-07 12:14:25.078 4382 4382 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-07 12:14:25.078 4382 4382 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-07 12:14:25.078 4382 4382 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-07 12:14:25.078 4382 4382 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-07 12:14:25.078 4382 4382 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-07 12:14:25.078 4382 4382 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-07 12:14:25.078 4382 4382 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-07 12:14:25.865 4382 4382 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.
11-07 12:14:29.999 4382 4382 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-07 12:14:30.000 4382 4382 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-07 12:14:30.057 4382 4399 W com.mbwhatsapp: Suspending all threads took:
14.695ms
--------- beginning of main
11-07 12:14:34.797 4382 5046 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-07 12:14:34.797 4382 5046 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-07 12:14:34.797 4382 5046 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-07 12:14:38.865 4382 4399 W com.mbwhatsapp: Suspending all threads took:
27.658ms
11-07 12:14:40.872 4382 5365 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-07 12:14:40.879 4382 5365 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-07 12:16:56.631 9370 9370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 12:16:58.946 9370 9370 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
11-07 13:11:37.763 6034 6034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-07 13:11:40.252 6034 6034 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-07 13:11:40.253 6034 6034 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.Class.newInstance(Native Method)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-07 13:11:40.253 6034 6034 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-07 13:11:40.253 6034 6034 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-07 13:11:40.253 6034 6034 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-07 13:11:40.253 6034 6034 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-07 13:11:40.253 6034 6034 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-07 13:11:40.253 6034 6034 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-07 13:11:40.253 6034 6034 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-07 13:11:40.254 6034 6034 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-07 13:11:40.831 6034 6034 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.
11-07 13:11:45.217 6034 6034 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-07 13:11:45.218 6034 6034 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-10 19:16:48.236 13855 13855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 19:16:48.721 13855 13855 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
11-10 19:29:13.942 14111 14111 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 19:29:14.226 14111 14111 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
11-10 19:47:06.286 14451 14451 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 19:47:06.621 14451 14451 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
11-10 21:23:20.836 26955 26955 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 21:23:23.028 26955 26955 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.
11-10 21:23:28.310 26955 26955 W com.mbwhatsapp: type=1400 audit(0.0:466177): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-10 21:33:54.908 29304 29304 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 21:33:55.666 29304 29304 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
11-10 21:37:26.230 31036 31036 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 21:37:26.972 31036 31036 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.
11-10 21:37:28.652 31036 31091 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-10 21:37:28.652 31036 31091 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-10 22:34:25.303 6114 6114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 22:34:28.713 6114 6114 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
11-10 23:12:18.957 13083 13083 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 23:12:22.282 13083 13083 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
11-10 23:14:59.192 14286 14286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 23:14:59.577 14286 14286 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
11-10 23:20:49.034 16751 16751 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 23:20:49.569 16751 16751 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
11-10 23:23:50.231 17188 17188 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 23:23:50.603 17188 17188 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
11-10 23:37:17.057 17684 17684 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-10 23:37:17.322 17684 17684 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
11-11 00:08:44.526 29254 29254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 00:08:45.299 29254 29254 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
11-11 00:10:18.933 29926 29926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 00:10:19.892 29926 29926 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
11-11 01:15:42.538 13327 13327 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 01:15:43.208 13327 13327 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.
11-11 01:15:44.939 13327 13451 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-11 01:15:44.939 13327 13451 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-11 01:20:08.056 14313 14313 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 01:20:08.854 14313 14313 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
11-11 01:24:16.593 14899 14899 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 01:24:17.531 14899 14899 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
11-11 02:18:22.060 19790 19790 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 02:18:24.333 19790 19790 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.
11-11 02:18:27.893 19790 19980 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-11 02:18:27.893 19790 19980 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-11 02:18:27.893 19790 19980 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-11 02:22:21.075 20529 20529 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 02:22:21.685 20529 20529 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
11-11 02:36:40.467 21939 21939 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 02:36:41.113 21939 21939 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
11-11 14:47:41.721 380 380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 14:47:45.410 380 380 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.
11-11 14:47:51.371 380 380 W com.mbwhatsapp: type=1400 audit(0.0:591346): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-11 14:48:01.232 1884 1884 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 14:48:02.143 1884 1884 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
11-11 15:00:28.343 6197 6197 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 15:00:29.869 6197 6197 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
11-11 23:02:33.800 6511 6511 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 23:02:35.394 6511 6511 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
11-11 23:04:36.130 11719 11719 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-11 23:04:37.994 11719 11719 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
11-12 00:48:21.950 18702 18702 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 00:48:22.974 18702 18702 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.
11-12 00:48:25.134 18702 18829 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-12 00:48:25.134 18702 18829 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-12 00:48:25.134 18702 18829 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-12 01:03:35.097 21968 21968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 01:03:35.966 21968 21968 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.
11-12 01:03:37.856 21968 22089 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-12 01:03:37.856 21968 22089 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-12 01:03:37.856 21968 22089 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-12 01:07:37.922 23017 23017 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 01:07:38.598 23017 23017 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
11-12 01:49:39.178 24145 24145 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 01:49:40.740 24145 24145 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
11-12 02:21:40.034 25097 25097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 02:21:40.925 25097 25097 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
11-12 02:33:31.974 28914 28914 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 02:33:32.889 28914 28914 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
11-12 14:11:42.108 32089 32089 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 14:11:43.139 32089 32089 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.
11-12 14:11:44.457 32089 32304 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-12 14:11:44.457 32089 32304 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-12 14:11:44.457 32089 32304 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-12 14:26:39.990 1884 1884 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 14:26:40.451 1884 1884 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
11-12 14:31:30.849 3280 3280 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 14:31:31.145 3280 3280 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
11-12 16:01:27.634 11163 11163 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 16:01:28.322 11163 11163 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.
11-12 16:01:29.677 11163 11294 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-12 16:01:29.677 11163 11294 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-12 16:01:29.677 11163 11294 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-12 16:26:31.686 12315 12315 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 16:26:32.461 12315 12315 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
11-12 17:43:27.070 13639 13639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 17:43:31.119 13639 13639 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
11-12 19:45:52.713 16314 16314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 19:45:53.623 16314 16314 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
11-12 22:49:46.741 19428 19428 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-12 22:49:48.167 19428 19428 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
11-13 01:41:42.717 3801 3801 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 01:41:44.917 3801 3801 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-13 01:41:44.919 3801 3801 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-13 01:41:44.919 3801 3801 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-13 01:41:44.920 3801 3801 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-13 01:41:44.922 3801 3801 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-13 01:41:44.922 3801 3801 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-13 01:41:44.922 3801 3801 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-13 01:41:44.922 3801 3801 W System.err: at
java.lang.Class.newInstance(Native Method)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-13 01:41:44.922 3801 3801 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-13 01:41:44.922 3801 3801 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-13 01:41:44.922 3801 3801 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-13 01:41:44.922 3801 3801 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-13 01:41:44.922 3801 3801 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-13 01:41:44.922 3801 3801 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-13 01:41:44.922 3801 3801 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-13 01:41:44.922 3801 3801 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-13 01:41:45.080 3801 3801 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.
11-13 01:41:48.438 3801 3801 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-13 01:41:48.439 3801 3801 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-13 01:41:49.302 3801 3801 W com.mbwhatsapp: type=1400 audit(0.0:1163): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-13 01:41:49.322 3801 3801 W com.mbwhatsapp: type=1400 audit(0.0:1164): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-13 01:41:49.362 3801 3801 W com.mbwhatsapp: type=1400 audit(0.0:1165): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-13 01:41:51.007 3801 4412 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-13 01:41:51.007 3801 4412 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-13 01:41:51.007 3801 4412 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-13 01:41:53.427 3801 4466 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-13 01:41:53.428 3801 4466 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-13 07:00:34.473 11488 11488 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 07:00:35.610 11488 11488 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.
11-13 07:00:37.123 11488 11488 W com.mbwhatsapp: type=1400 audit(0.0:9930): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-13 09:04:01.561 16151 16151 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 09:04:05.022 16151 16151 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
11-13 11:08:14.201 18883 18883 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 11:08:16.001 18883 18883 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.
11-13 11:08:18.608 18883 18883 W com.mbwhatsapp: type=1400 audit(0.0:10902): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-13 12:36:12.204 21198 21198 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 12:36:13.091 21198 21198 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
11-13 12:55:51.749 22360 22360 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 12:55:52.008 22360 22360 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
11-13 13:15:56.331 22863 22863 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 13:15:56.608 22863 22863 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
11-13 13:32:20.515 23084 23084 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 13:32:20.825 23084 23084 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
11-13 14:26:06.529 24483 24483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 14:26:07.165 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
11-13 15:37:01.833 30630 30630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 15:37:02.223 30630 30630 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
11-13 15:54:16.114 5236 5236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 15:54:16.842 5236 5236 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
11-13 17:12:10.484 15430 15430 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 17:12:12.168 15430 15430 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
11-13 19:06:43.591 26026 26026 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 19:06:45.004 26026 26026 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
11-13 19:09:47.776 28134 28134 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 19:09:50.238 28134 28134 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
11-13 19:12:54.498 30176 30176 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 19:12:55.597 30176 30176 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
11-13 19:16:46.687 31598 31598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 19:16:47.541 31598 31598 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
11-13 19:36:30.272 5074 5074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 19:36:31.002 5074 5074 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
11-13 19:47:34.859 7283 7283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 19:47:35.484 7283 7283 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
11-13 21:22:02.905 25267 25267 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 21:22:03.925 25267 25267 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
11-13 21:34:06.653 28334 28334 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 21:34:07.327 28334 28334 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
11-13 22:02:21.548 6183 6183 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 22:02:22.615 6183 6183 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
11-13 22:26:35.840 10722 10722 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 22:26:38.251 10722 10722 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
11-13 22:36:29.737 14223 14223 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 22:36:30.493 14223 14223 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
11-13 22:42:45.305 14525 14525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 22:42:45.559 14525 14525 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
11-13 22:56:34.453 14782 14782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 22:56:34.739 14782 14782 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
11-13 23:07:07.038 15728 15728 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 23:07:08.848 15728 15728 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
11-13 23:40:51.237 6788 6788 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 23:40:53.288 6788 6788 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
11-13 23:42:29.913 11070 11070 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 23:42:31.986 11070 11070 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
11-13 23:44:56.945 13223 13223 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-13 23:44:58.598 13223 13223 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
11-14 00:41:40.535 22395 22395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 00:41:41.206 22395 22395 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
11-14 00:51:42.043 23549 23549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 00:51:42.491 23549 23549 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
11-14 01:47:42.109 25316 25316 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 01:47:42.808 25316 25316 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
11-14 02:00:29.788 28470 28470 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 02:00:32.080 28470 28470 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
11-14 02:36:40.128 5677 5677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 02:36:40.613 5677 5677 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
11-14 03:36:36.777 12435 12435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 03:36:37.393 12435 12435 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
11-14 04:36:30.739 18522 18522 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 04:36:31.420 18522 18522 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
11-14 05:36:17.356 24265 24265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 05:36:18.268 24265 24265 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
11-14 06:36:33.276 31966 31966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 06:36:34.509 31966 31966 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
11-14 06:46:10.246 1374 1374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 06:46:10.812 1374 1374 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
11-14 07:14:51.007 3835 3835 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 07:14:51.849 3835 3835 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
11-14 07:38:22.012 5024 5024 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 07:38:22.702 5024 5024 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
11-14 07:57:00.072 5465 5465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 07:57:00.332 5465 5465 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
11-14 09:03:42.156 6186 6186 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 09:03:42.597 6186 6186 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
11-14 11:06:41.303 7750 7750 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 11:06:43.305 7750 7750 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
11-14 14:26:02.980 10737 10737 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 14:26:04.658 10737 10737 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.
11-14 14:26:09.057 11228 11228 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 14:26:10.144 11228 11228 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
11-14 15:36:22.070 15435 15435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 15:36:22.421 15435 15435 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
11-14 15:41:17.713 17298 17298 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 15:41:18.709 17298 17298 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
11-14 15:49:16.640 17651 17651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 15:49:16.913 17651 17651 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
11-14 16:02:30.055 17936 17936 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 16:02:30.322 17936 17936 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
11-14 16:18:58.101 19240 19240 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 16:18:58.663 19240 19240 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
11-14 16:36:44.515 23373 23373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 16:36:45.445 23373 23373 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
11-14 17:11:38.034 28449 28449 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 17:11:38.549 28449 28449 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
11-14 17:36:20.623 1021 1021 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 17:36:21.471 1021 1021 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
11-14 18:46:07.173 13342 13342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 18:46:07.777 13342 13342 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
11-14 20:00:28.500 20746 20746 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 20:00:29.297 20746 20746 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
11-14 20:36:57.159 26697 26697 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 20:36:58.211 26697 26697 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
11-14 21:36:26.042 4314 4314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 21:36:27.185 4314 4314 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
11-14 21:46:00.677 6317 6317 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 21:46:01.560 6317 6317 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.
11-14 21:46:02.973 6317 6422 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-14 21:46:02.973 6317 6422 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-14 21:46:02.973 6317 6422 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-14 22:36:54.652 21974 21974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 22:36:55.503 21974 21974 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
11-14 23:36:30.907 8819 8819 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-14 23:36:32.472 8819 8819 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
11-15 00:37:42.960 19103 19103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 00:37:43.960 19103 19103 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
11-15 00:41:05.149 21329 21329 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 00:41:05.727 21329 21329 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
11-15 00:45:47.513 22802 22802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 00:45:48.314 22802 22802 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
11-15 01:36:17.297 12496 12496 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 01:36:18.488 12496 12496 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
11-15 02:36:17.124 20023 20023 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 02:36:18.426 20023 20023 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.
11-15 02:36:21.982 20023 20023 W com.mbwhatsapp: type=1400 audit(0.0:6243): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-15 03:36:21.289 23568 23568 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 03:36:21.886 23568 23568 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
11-15 04:36:47.131 26791 26791 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 04:36:47.448 26791 26791 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
11-15 05:00:28.464 28408 28408 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 05:00:28.717 28408 28408 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
11-15 05:36:57.249 30937 30937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 05:36:58.251 30937 30937 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
11-15 06:01:30.564 902 902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 06:01:30.977 902 902 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
11-15 06:36:47.247 12787 12787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 06:36:48.099 12787 12787 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
11-15 06:41:33.607 14288 14288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 06:41:34.195 14288 14288 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
11-15 06:45:28.492 15207 15207 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 06:45:28.763 15207 15207 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
11-15 07:04:27.692 17184 17184 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 07:04:28.377 17184 17184 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
11-15 07:36:57.252 19231 19231 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 07:36:57.812 19231 19231 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
11-15 08:54:12.446 21547 21547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 08:54:13.557 21547 21547 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
11-15 10:55:33.284 23867 23867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 10:55:34.282 23867 23867 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
11-15 12:36:54.387 2370 2370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 12:37:25.919 3471 3471 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 12:37:27.010 3471 3471 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
11-15 13:04:56.634 7776 7776 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 13:04:57.691 7776 7776 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
11-15 14:22:42.173 10621 10621 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 14:22:43.080 10621 10621 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
11-15 15:03:57.296 12652 12652 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 15:03:58.493 12652 12652 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
11-15 16:19:07.651 18393 18393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 16:19:08.227 18393 18393 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
11-15 16:40:10.330 21960 21960 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 16:40:11.261 21960 21960 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
11-15 17:42:07.062 29446 29446 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 17:42:10.016 29446 29446 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
11-15 18:45:28.554 12141 12141 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 18:45:29.275 12141 12141 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
11-15 19:36:40.072 20977 20977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 19:36:40.786 20977 20977 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
11-15 20:12:53.257 30334 30334 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:12:53.826 30334 30334 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
11-15 20:16:54.143 30776 30776 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:16:54.485 30776 30776 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
11-15 20:24:57.208 30878 30878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:24:57.481 30878 30878 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
11-15 20:36:53.248 32180 32180 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:36:53.821 32180 32180 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
11-15 20:46:13.605 5986 5986 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:46:14.310 5986 5986 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
11-15 20:51:38.560 8928 8928 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:51:39.541 8928 8928 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
11-15 20:56:29.670 12243 12243 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 20:56:30.532 12243 12243 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
11-15 21:03:37.422 12712 12712 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 21:03:37.748 12712 12712 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
11-15 21:37:49.223 14636 14636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 21:37:51.209 14636 14636 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
11-15 21:48:56.352 15083 15083 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 21:49:01.879 15083 15083 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
11-15 22:37:57.736 18562 18562 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 22:37:58.616 18562 18562 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
11-15 22:42:06.823 19488 19488 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 22:42:08.804 19488 19488 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
11-15 22:45:58.837 20144 20144 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 22:45:59.465 20144 20144 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
11-15 23:41:43.833 30385 30385 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 23:41:44.680 30385 30385 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
11-15 23:48:12.307 31043 31043 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-15 23:48:12.711 31043 31043 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
11-16 00:36:17.214 13433 13433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 00:36:18.136 13433 13433 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
11-16 00:45:34.095 16476 16476 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 00:45:34.985 16476 16476 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
11-16 01:03:54.528 20539 20539 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:03:58.507 20539 20539 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
11-16 01:15:05.184 21070 21070 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:15:05.426 21070 21070 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
11-16 01:26:09.775 21738 21738 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:26:10.895 21738 21738 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
11-16 01:31:36.177 22822 22822 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:31:37.108 22822 22822 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
11-16 01:36:21.162 25848 25848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:36:21.708 25848 25848 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
11-16 01:56:27.174 26459 26459 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:56:27.466 26459 26459 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
11-16 01:57:58.288 27103 27103 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 01:57:58.509 27103 27103 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
11-16 02:03:38.682 28018 28018 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 02:03:38.900 28018 28018 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
11-16 02:56:05.604 3004 3004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 02:56:06.455 3004 3004 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
11-16 03:14:47.145 5122 5122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 03:14:47.787 5122 5122 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
11-16 03:42:00.359 6194 6194 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 03:42:00.840 6194 6194 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
11-16 04:01:56.813 7155 7155 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 04:01:57.184 7155 7155 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
11-16 05:31:05.277 8255 8255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 05:31:05.572 8255 8255 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
11-16 07:34:40.750 9347 9347 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 07:34:42.581 9347 9347 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
11-16 08:57:36.671 12368 12368 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 08:57:37.678 12368 12368 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
11-16 09:15:30.968 16967 16967 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 09:15:31.684 16967 16967 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
11-16 14:06:24.247 6969 6969 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 14:06:31.724 6969 6969 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-16 14:06:31.725 6969 6969 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.Class.newInstance(Native Method)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-16 14:06:31.725 6969 6969 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-16 14:06:31.725 6969 6969 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-16 14:06:31.725 6969 6969 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-16 14:06:31.725 6969 6969 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-16 14:06:31.725 6969 6969 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-16 14:06:31.725 6969 6969 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-16 14:06:31.725 6969 6969 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-16 14:06:31.725 6969 6969 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-16 14:06:32.055 6969 6969 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.
11-16 14:06:37.311 6969 6969 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-16 14:06:37.312 6969 6969 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-16 14:06:41.753 6969 6979 W com.mbwhatsapp: Suspending all threads took:
252.736ms
11-16 14:06:44.130 6969 7567 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=be23e718-329e-4dae-a8f9-8e9144f304a7, generation=0)
11-16 14:06:44.159 6969 7477 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-16 14:06:44.159 6969 7477 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-16 14:06:44.159 6969 7477 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-16 14:06:44.313 6969 7568 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-16 14:06:44.313 6969 7568 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-16 14:11:46.449 14010 14010 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 14:11:50.844 14010 14010 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
11-16 14:59:34.469 16150 16150 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 14:59:37.120 16150 16150 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.
11-16 14:59:42.405 16150 16316 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-16 14:59:42.405 16150 16316 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-16 14:59:42.405 16150 16316 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-16 15:59:38.890 24380 24380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 15:59:39.994 24380 24380 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
11-16 16:59:34.485 6852 6852 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 16:59:35.890 6852 6852 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
11-16 17:59:44.927 21419 21419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 17:59:45.649 21419 21419 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
11-16 18:02:03.683 22527 22527 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 18:02:03.988 22527 22527 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
11-16 18:04:41.194 23191 23191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 18:04:41.508 23191 23191 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
11-16 18:13:14.484 26082 26082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 18:13:15.329 26082 26082 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
11-16 18:29:49.642 29845 29845 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 18:29:53.792 29845 29845 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
11-16 18:40:54.625 32300 32300 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 18:40:54.865 32300 32300 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
11-16 18:59:41.791 9932 9932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 18:59:42.477 9932 9932 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
11-16 19:35:19.159 16336 16336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 19:35:19.965 16336 16336 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
11-16 20:41:04.528 32185 32185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 20:41:05.211 32185 32185 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
11-16 21:45:02.334 21835 21835 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 21:45:03.003 21835 21835 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.
11-16 21:45:04.878 21835 21900 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-16 21:45:04.879 21835 21900 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-16 22:52:39.281 10243 10243 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 22:52:40.082 10243 10243 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
11-16 23:02:19.789 11133 11133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-16 23:02:20.116 11133 11133 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
11-17 00:56:48.099 14463 14463 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 00:56:49.727 14463 14463 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
11-17 02:59:04.911 16169 16169 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 02:59:06.736 16169 16169 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
11-17 07:01:37.414 19067 19067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 07:01:39.245 19067 19067 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
11-17 08:04:23.218 28681 28681 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 08:04:24.195 28681 28681 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
11-17 08:27:42.707 4472 4472 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 08:27:44.249 4472 4472 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
11-17 08:45:09.965 7038 7038 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 08:45:10.550 7038 7038 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
11-17 08:59:34.448 10629 10629 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 08:59:35.299 10629 10629 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
11-17 09:59:37.903 16891 16891 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 09:59:38.848 16891 16891 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
11-17 16:35:40.995 5177 5177 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 16:35:45.249 5177 5177 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-17 16:35:45.262 5177 5177 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-17 16:35:45.262 5177 5177 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-17 16:35:45.262 5177 5177 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-17 16:35:45.262 5177 5177 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-17 16:35:45.262 5177 5177 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-17 16:35:45.262 5177 5177 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-17 16:35:45.262 5177 5177 W System.err: at
java.lang.Class.newInstance(Native Method)
11-17 16:35:45.262 5177 5177 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-17 16:35:45.262 5177 5177 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-17 16:35:45.262 5177 5177 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-17 16:35:45.262 5177 5177 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-17 16:35:45.262 5177 5177 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-17 16:35:45.262 5177 5177 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-17 16:35:45.262 5177 5177 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-17 16:35:45.263 5177 5177 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-17 16:35:45.263 5177 5177 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-17 16:35:45.263 5177 5177 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-17 16:35:45.263 5177 5177 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-17 16:35:45.263 5177 5177 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-17 16:35:45.263 5177 5177 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-17 16:35:45.263 5177 5177 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-17 16:35:45.565 5177 5177 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.
11-17 16:35:51.797 5177 5187 W com.mbwhatsapp: Suspending all threads took:
24.335ms
11-17 16:35:52.102 5177 5177 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-17 16:35:52.103 5177 5177 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-17 16:35:58.802 5177 5837 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-17 16:35:58.802 5177 5837 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-17 16:35:58.802 5177 5837 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-17 16:36:02.088 5177 6033 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=8109e457-c2a6-4165-ad51-50b7c4fb75f8, generation=0)
11-17 16:36:02.739 5177 6040 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-17 16:36:02.739 5177 6040 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-17 16:37:26.597 9033 9033 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 16:37:27.332 9033 9033 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
11-17 17:29:52.448 20813 20813 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 17:29:53.093 20813 20813 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
11-17 17:30:41.165 21202 21202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 17:30:41.483 21202 21202 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
11-17 18:41:04.646 4598 4598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 18:41:09.364 4598 4598 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-17 18:41:09.365 4598 4598 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.Class.newInstance(Native Method)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-17 18:41:09.365 4598 4598 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-17 18:41:09.365 4598 4598 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-17 18:41:09.365 4598 4598 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-17 18:41:09.365 4598 4598 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-17 18:41:09.365 4598 4598 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-17 18:41:09.365 4598 4598 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-17 18:41:09.365 4598 4598 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-17 18:41:09.366 4598 4598 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-17 18:41:09.594 4598 4598 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.
11-17 18:41:12.435 4598 4598 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-17 18:41:12.447 4598 4598 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-17 18:41:12.659 4598 4598 W com.mbwhatsapp: type=1400 audit(0.0:1243): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-17 18:41:12.685 4598 4598 W com.mbwhatsapp: type=1400 audit(0.0:1244): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-17 18:41:12.819 4598 4598 W com.mbwhatsapp: type=1400 audit(0.0:1245): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-17 18:41:13.185 4598 4598 W com.mbwhatsapp: type=1400 audit(0.0:1246): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-17 18:41:13.272 4598 4598 W com.mbwhatsapp: type=1400 audit(0.0:1247): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-17 18:58:56.380 10188 10188 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 18:58:59.303 10188 10188 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.
11-17 18:59:03.648 10188 10188 W com.mbwhatsapp: type=1400 audit(0.0:2871): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-17 18:59:03.764 10188 10188 W com.mbwhatsapp: type=1400 audit(0.0:2872): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-17 19:01:16.242 13414 13414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 19:01:17.770 13414 13414 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
11-17 20:00:00.082 28079 28079 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 20:00:00.943 28079 28079 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
11-17 20:02:51.496 29146 29146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 20:02:51.978 29146 29146 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
11-17 22:50:16.701 10406 10406 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 22:50:17.564 10406 10406 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.
11-17 22:50:19.179 10406 10552 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-17 22:50:19.179 10406 10552 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-17 22:54:18.959 11406 11406 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 22:54:19.373 11406 11406 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
11-17 22:56:36.514 11975 11975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 22:56:36.810 11975 11975 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
11-17 23:03:43.538 12156 12156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 23:03:43.785 12156 12156 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
11-17 23:19:01.581 12543 12543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 23:19:01.920 12543 12543 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
11-17 23:35:19.530 12923 12923 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-17 23:35:19.909 12923 12923 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
11-18 00:43:56.757 14193 14193 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 00:43:57.716 14193 14193 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
11-18 00:52:00.520 15394 15394 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 00:52:01.157 15394 15394 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
11-18 01:02:21.586 16441 16441 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 01:02:21.995 16441 16441 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
11-18 01:14:18.471 16716 16716 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 01:14:18.711 16716 16716 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
11-18 01:21:03.547 18457 18457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 01:21:04.147 18457 18457 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
11-18 01:39:22.717 20224 20224 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 01:39:23.263 20224 20224 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
11-18 01:50:41.212 22313 22313 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 01:50:41.814 22313 22313 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
11-18 02:14:30.524 22939 22939 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 02:14:30.772 22939 22939 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
11-18 02:54:37.572 23468 23468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 02:54:37.842 23468 23468 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
11-18 03:54:52.089 23947 23947 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 03:54:52.424 23947 23947 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
11-18 05:59:43.898 25262 25262 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 05:59:46.017 25262 25262 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
11-18 07:35:14.563 1752 1752 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 07:35:15.504 1752 1752 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
11-18 08:44:04.508 14051 14051 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 08:44:05.515 14051 14051 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
11-18 17:21:45.316 11692 11692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 17:21:46.253 11692 11692 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.
11-18 17:21:50.194 11692 11827 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-18 17:21:50.194 11692 11827 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-18 17:21:50.194 11692 11827 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-18 17:36:04.889 15546 15546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 17:36:05.886 15546 15546 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
11-18 17:39:06.266 16651 16651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 17:39:07.239 16651 16651 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
11-18 17:42:33.802 18088 18088 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 18:53:33.180 25796 25796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 18:53:38.136 25796 25796 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.
11-18 18:53:50.033 25796 25796 W com.mbwhatsapp: type=1400 audit(0.0:128999): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-18 18:56:54.459 30283 30283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 18:56:56.374 30283 30283 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
11-18 18:59:27.899 31797 31797 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 18:59:28.982 31797 31797 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
11-18 19:35:42.306 12995 12995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 19:35:43.588 12995 12995 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
11-18 19:42:41.818 15495 15495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 19:42:42.718 15495 15495 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
11-18 19:54:46.670 19469 19469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 19:54:47.295 19469 19469 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
11-18 20:58:21.861 9278 9278 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 20:58:22.601 9278 9278 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.
11-18 20:58:24.315 9278 9343 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-18 20:58:24.316 9278 9343 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-18 21:50:59.823 12969 12969 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 21:51:00.890 12969 12969 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
11-18 22:58:58.987 24882 24882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-18 22:59:01.665 24882 24882 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
11-19 07:08:51.432 6005 6005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-19 07:08:55.883 6005 6005 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-19 07:08:55.885 6005 6005 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.Class.newInstance(Native Method)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-19 07:08:55.885 6005 6005 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-19 07:08:55.885 6005 6005 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-19 07:08:55.885 6005 6005 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-19 07:08:55.885 6005 6005 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-19 07:08:55.885 6005 6005 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-19 07:08:55.885 6005 6005 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-19 07:08:55.885 6005 6005 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-19 07:08:55.885 6005 6005 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-19 07:08:56.648 6005 6005 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.
11-19 07:08:56.772 6005 6015 W com.mbwhatsapp: Suspending all threads took:
15.977ms
11-19 07:09:00.487 6005 6005 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-19 07:09:00.488 6005 6005 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-19 07:09:03.820 6005 6660 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-19 07:09:03.820 6005 6660 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-19 07:09:03.820 6005 6660 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-19 07:09:05.820 6005 6810 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-19 07:09:05.825 6005 6810 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-19 07:09:43.776 7963 7963 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-19 07:09:44.107 7963 7963 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-19 07:09:44.108 7963 7963 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-19 07:09:44.108 7963 7963 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-19 07:09:44.108 7963 7963 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-19 07:09:44.108 7963 7963 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-19 07:09:44.108 7963 7963 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-19 07:09:44.108 7963 7963 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-19 07:09:44.108 7963 7963 W System.err: at
java.lang.Class.newInstance(Native Method)
11-19 07:09:44.108 7963 7963 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-19 07:09:44.108 7963 7963 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-19 07:09:44.108 7963 7963 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-19 07:09:44.108 7963 7963 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-19 07:09:44.108 7963 7963 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-19 07:09:44.108 7963 7963 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-19 07:09:44.108 7963 7963 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-19 07:09:44.108 7963 7963 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-19 07:09:44.108 7963 7963 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-19 07:09:44.109 7963 7963 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-19 07:09:44.109 7963 7963 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-19 07:09:44.109 7963 7963 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-19 07:09:44.109 7963 7963 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-19 07:09:44.109 7963 7963 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-19 07:09:44.145 7963 7963 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.
11-19 07:09:44.446 7963 7963 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-19 07:09:44.446 7963 7963 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-19 07:09:44.839 7963 8068 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-19 07:09:44.839 7963 8068 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-19 07:09:44.839 7963 8068 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-19 07:09:45.269 7963 8068 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-19 07:09:45.270 7963 8068 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-19 07:10:43.879 10687 10687 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-19 07:10:44.227 10687 10687 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
11-20 10:58:13.808 16434 16434 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 10:58:14.635 16434 16434 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
11-20 12:04:56.600 22735 22735 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 12:04:57.604 22735 22735 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
11-20 12:19:46.406 23624 23624 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 12:19:46.860 23624 23624 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
11-20 13:46:32.892 5011 5011 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 13:46:33.513 5011 5011 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
11-20 13:53:22.133 6866 6866 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 13:53:23.257 6866 6866 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
11-20 13:58:27.995 8714 8714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 13:58:29.405 8714 8714 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
11-20 15:12:56.322 29299 29299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 15:12:57.523 29299 29299 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
11-20 15:30:21.484 30498 30498 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 15:30:22.502 30498 30498 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
11-20 16:35:34.689 31147 31147 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 16:35:36.094 31147 31147 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
11-20 18:42:42.160 1891 1891 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 18:42:43.858 1891 1891 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.
11-20 18:42:47.144 1891 2470 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-20 18:42:47.144 1891 2470 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-20 18:42:47.144 1891 2470 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-20 21:12:06.531 8975 8975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 21:12:10.745 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
11-20 21:15:09.764 9995 9995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 21:15:10.366 9995 9995 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
11-20 21:23:07.387 10383 10383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 21:23:07.955 10383 10383 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
11-20 21:34:21.572 10930 10930 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 21:34:21.885 10930 10930 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
11-20 21:54:25.435 11372 11372 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 21:54:25.798 11372 11372 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
11-20 22:18:15.505 12312 12312 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 22:18:16.503 12312 12312 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
11-20 22:36:13.787 13221 13221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 22:36:15.935 13221 13221 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
11-20 23:03:44.105 16885 16885 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 23:03:44.705 16885 16885 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
11-20 23:06:41.201 17369 17369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 23:06:41.804 17369 17369 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
11-20 23:13:52.232 17901 17901 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-20 23:13:52.611 17901 17901 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
11-21 00:05:18.317 26150 26150 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 00:05:20.314 26150 26150 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
11-21 00:10:42.969 28313 28313 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 00:10:43.847 28313 28313 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
11-21 01:02:48.395 32507 32507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 01:02:49.175 32507 32507 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
11-21 01:13:22.475 5783 5783 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 02:03:02.625 21242 21242 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 02:03:04.096 21242 21242 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
11-21 10:19:41.292 24917 24917 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 10:19:41.970 24917 24917 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.
11-21 10:19:47.517 24917 25088 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-21 10:19:47.517 24917 25088 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-21 10:19:47.517 24917 25088 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-21 11:20:44.626 25697 25697 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 11:20:45.099 25697 25697 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
11-21 13:27:45.282 27580 27580 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 13:27:45.631 27580 27580 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
11-21 15:07:45.311 9211 9211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 15:07:45.899 9211 9211 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
11-21 15:28:09.174 10081 10081 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 15:28:10.025 10081 10081 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
11-21 15:45:41.295 10767 10767 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 15:45:41.570 10767 10767 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
11-21 16:50:58.871 12078 12078 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 16:50:59.673 12078 12078 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
11-21 16:53:39.778 12409 12409 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 16:53:40.033 12409 12409 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
11-21 18:56:20.515 13874 13874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 18:56:20.853 13874 13874 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
11-21 22:37:08.117 19938 19938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-21 22:37:09.762 19938 19938 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.
11-21 22:37:11.383 19938 20124 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-21 22:37:11.383 19938 20124 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-21 22:37:11.383 19938 20124 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-22 00:19:44.402 4224 4224 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 00:19:44.833 4224 4224 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
11-22 00:28:51.878 5479 5479 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 00:28:52.882 5479 5479 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
11-22 00:50:05.354 6559 6559 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 00:50:06.216 6559 6559 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
11-22 01:02:39.053 8267 8267 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 01:02:39.574 8267 8267 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
11-22 01:21:58.240 9011 9011 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 01:21:58.735 9011 9011 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
11-22 01:41:52.250 12598 12598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 01:41:56.193 12598 12598 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
11-22 02:02:40.618 26772 26772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 02:02:41.439 26772 26772 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
11-22 02:47:45.331 28867 28867 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 02:47:45.889 28867 28867 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
11-22 03:05:04.452 31751 31751 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 03:05:06.217 31751 31751 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
11-22 03:23:45.430 32636 32636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 03:23:45.758 32636 32636 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
11-22 04:33:25.388 2204 2204 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 04:33:25.691 2204 2204 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
11-22 04:43:24.354 2824 2824 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 04:43:24.669 2824 2824 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
11-22 04:55:04.281 3622 3622 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 04:55:04.535 3622 3622 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
11-22 06:31:24.462 4168 4168 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 06:31:25.941 4168 4168 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-22 06:31:25.945 4168 4168 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-22 06:31:25.945 4168 4168 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-22 06:31:25.945 4168 4168 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-22 06:31:25.945 4168 4168 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-22 06:31:25.945 4168 4168 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-22 06:31:25.945 4168 4168 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-22 06:31:25.945 4168 4168 W System.err: at
java.lang.Class.newInstance(Native Method)
11-22 06:31:25.945 4168 4168 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-22 06:31:25.946 4168 4168 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-22 06:31:25.946 4168 4168 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-22 06:31:25.946 4168 4168 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-22 06:31:25.946 4168 4168 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-22 06:31:25.946 4168 4168 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-22 06:31:25.946 4168 4168 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-22 06:31:25.946 4168 4168 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-22 06:31:25.946 4168 4168 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-22 06:31:25.946 4168 4168 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-22 06:31:25.946 4168 4168 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-22 06:31:25.946 4168 4168 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-22 06:31:25.946 4168 4168 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-22 06:31:25.946 4168 4168 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-22 06:31:26.089 4168 4168 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.
11-22 06:31:28.391 4168 4168 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-22 06:31:28.391 4168 4168 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-22 06:31:28.626 4168 4168 W com.mbwhatsapp: type=1400 audit(0.0:1264): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:31:28.649 4168 4168 W com.mbwhatsapp: type=1400 audit(0.0:1265): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:31:28.692 4168 4168 W com.mbwhatsapp: type=1400 audit(0.0:1266): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:31:28.922 4168 4168 W com.mbwhatsapp: type=1400 audit(0.0:1267): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:31:28.976 4168 4168 W com.mbwhatsapp: type=1400 audit(0.0:1268): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-22 06:31:29.724 4168 4727 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-22 06:31:29.724 4168 4727 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-22 06:31:29.724 4168 4727 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-22 06:31:32.416 4168 4936 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-22 06:31:32.416 4168 4936 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-22 06:32:07.091 6642 6642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 06:32:08.589 6642 6642 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-22 06:32:08.589 6642 6642 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-22 06:32:08.589 6642 6642 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-22 06:32:08.589 6642 6642 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-22 06:32:08.589 6642 6642 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-22 06:32:08.589 6642 6642 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-22 06:32:08.589 6642 6642 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-22 06:32:08.589 6642 6642 W System.err: at
java.lang.Class.newInstance(Native Method)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-22 06:32:08.589 6642 6642 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-22 06:32:08.589 6642 6642 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-22 06:32:08.589 6642 6642 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-22 06:32:08.589 6642 6642 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-22 06:32:08.589 6642 6642 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-22 06:32:08.590 6642 6642 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-22 06:32:08.590 6642 6642 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-22 06:32:08.590 6642 6642 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-22 06:32:08.887 6642 6642 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.
11-22 06:32:10.099 6642 6642 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-22 06:32:10.099 6642 6642 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-22 06:32:10.222 6642 6642 W com.mbwhatsapp: type=1400 audit(0.0:1732): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:32:10.255 6642 6642 W com.mbwhatsapp: type=1400 audit(0.0:1733): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:32:10.339 6642 6642 W com.mbwhatsapp: type=1400 audit(0.0:1734): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-22 06:32:10.575 6642 6642 W com.mbwhatsapp: type=1400 audit(0.0:1735): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:32:10.785 6642 6642 W com.mbwhatsapp: type=1400 audit(0.0:1736): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-22 06:32:11.096 6642 6933 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-22 06:32:11.096 6642 6933 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-22 06:32:11.096 6642 6933 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-22 06:35:13.696 15602 15602 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 06:35:14.531 15602 15602 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
11-22 07:35:00.233 25845 25845 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 07:35:01.357 25845 25845 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
11-22 08:46:59.586 28395 28395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 08:47:00.981 28395 28395 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
11-22 10:50:58.447 31024 31024 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 10:50:59.690 31024 31024 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
11-22 10:51:19.080 31621 31621 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 10:51:19.402 31621 31621 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
11-22 11:56:53.636 971 971 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 11:56:54.692 971 971 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
11-22 12:02:01.191 5670 5670 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 12:05:51.167 6456 6456 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 12:05:51.783 6456 6456 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
11-22 12:18:46.947 8114 8114 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 12:18:47.595 8114 8114 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
11-22 12:31:38.215 9825 9825 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 12:31:38.535 9825 9825 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
11-22 12:36:36.939 11209 11209 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 12:36:37.977 11209 11209 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
11-22 14:23:23.316 14920 14920 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 14:23:24.351 14920 14920 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
11-22 14:42:12.274 15751 15751 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 14:42:12.767 15751 15751 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
11-22 15:25:51.571 19218 19218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 15:25:52.062 19218 19218 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
11-22 15:46:49.625 19725 19725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 15:46:50.079 19725 19725 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
11-22 16:25:49.206 26296 26296 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 16:25:50.041 26296 26296 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
11-22 16:31:55.959 27540 27540 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 16:31:56.928 27540 27540 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
11-22 16:37:00.331 28557 28557 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 16:37:01.200 28557 28557 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
11-22 17:27:01.659 4842 4842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 17:27:02.282 4842 4842 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
11-22 17:39:31.132 5742 5742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 17:39:33.623 5742 5742 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
11-22 19:40:24.865 23825 23825 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 19:40:26.526 23825 23825 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
11-22 20:04:32.972 25669 25669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 20:04:33.602 25669 25669 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
11-22 20:11:01.134 28365 28365 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 20:11:02.032 28365 28365 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
11-22 20:19:12.568 31537 31537 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 20:19:13.670 31537 31537 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
11-22 20:25:49.840 3293 3293 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 20:25:50.645 3293 3293 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
11-22 21:25:45.096 15301 15301 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 21:25:46.075 15301 15301 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
11-22 22:25:46.953 28086 28086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 22:25:49.739 28086 28086 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
11-22 22:53:31.133 7363 7363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 22:53:33.417 7363 7363 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.
11-22 22:53:38.591 7363 7594 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-22 22:53:38.592 7363 7594 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-22 23:38:19.924 20706 20706 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 23:38:20.767 20706 20706 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
11-22 23:56:10.991 23307 23307 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 23:56:12.352 23307 23307 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
11-22 23:57:18.435 23771 23771 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-22 23:57:19.961 23771 23771 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
11-23 00:26:54.420 26775 26775 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 00:26:55.379 26775 26775 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
11-23 00:38:10.185 27084 27084 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 00:38:10.997 27084 27084 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
11-23 01:30:51.314 30458 30458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 01:30:52.921 30458 30458 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
11-23 02:26:59.324 10393 10393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 02:26:59.943 10393 10393 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
11-23 02:40:41.836 10836 10836 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 02:40:42.830 10836 10836 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
11-23 03:02:59.438 11255 11255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 03:02:59.743 11255 11255 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
11-23 04:21:38.605 13490 13490 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 04:21:40.326 13490 13490 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
11-23 04:24:06.918 13842 13842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 04:24:07.233 13842 13842 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
11-23 04:46:59.414 14039 14039 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 04:46:59.714 14039 14039 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
11-23 05:30:08.050 15097 15097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 05:30:08.487 15097 15097 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
11-23 05:36:26.324 16504 16504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 05:36:27.218 16504 16504 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
11-23 05:48:02.189 16849 16849 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 05:48:02.443 16849 16849 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.
11-23 05:48:03.414 16849 16942 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-23 05:48:03.414 16849 16942 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
--------- beginning of main
11-23 06:09:43.212 18508 18508 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 06:09:43.580 18508 18508 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
11-23 06:27:51.082 19525 19525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 06:27:51.400 19525 19525 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
11-23 07:29:38.233 25691 25691 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 07:29:40.767 25691 25691 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
11-23 07:48:40.837 26435 26435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 07:48:41.225 26435 26435 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
11-23 08:51:36.240 27427 27427 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 08:51:37.121 27427 27427 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
11-23 10:52:31.235 29274 29274 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 10:52:35.041 29274 29274 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
11-23 14:18:59.624 31705 31705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 14:19:02.149 31705 31705 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
11-23 14:19:18.413 32620 32620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 14:19:19.610 32620 32620 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
11-23 15:47:04.248 5764 5764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 15:47:05.553 5764 5764 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-23 15:47:05.554 5764 5764 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.Class.newInstance(Native Method)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-23 15:47:05.554 5764 5764 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-23 15:47:05.554 5764 5764 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-23 15:47:05.554 5764 5764 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-23 15:47:05.554 5764 5764 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-23 15:47:05.554 5764 5764 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-23 15:47:05.554 5764 5764 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-23 15:47:05.555 5764 5764 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-23 15:47:05.555 5764 5764 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-23 15:47:05.722 5764 5764 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.
11-23 15:47:07.501 5764 5764 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-23 15:47:07.502 5764 5764 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-23 15:47:11.655 5764 6050 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-23 15:47:11.655 5764 6050 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-23 15:47:11.655 5764 6050 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-23 15:47:13.017 5764 6065 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-23 15:47:13.017 5764 6065 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-23 15:48:45.579 9558 9558 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 15:48:46.106 9558 9558 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
11-23 16:48:33.284 19863 19863 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 16:48:34.287 19863 19863 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
11-23 17:22:48.296 20982 20982 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 17:22:49.159 20982 20982 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
11-23 18:42:36.931 7651 7651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 18:42:39.095 7651 7651 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
11-23 18:56:01.140 12457 12457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 18:56:01.876 12457 12457 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
11-23 18:57:57.579 13697 13697 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 18:57:58.780 13697 13697 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
11-23 19:50:05.835 19001 19001 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 19:50:06.696 19001 19001 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
11-23 20:08:01.003 20151 20151 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 20:08:01.298 20151 20151 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
11-23 20:50:18.902 23964 23964 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 20:50:19.372 23964 23964 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
11-23 21:41:02.400 14973 14973 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 21:41:02.889 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
11-23 22:12:13.176 31918 31918 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 22:12:14.622 31918 31918 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.
11-23 22:12:16.065 31918 32113 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-23 22:12:16.065 31918 32113 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-23 22:12:16.065 31918 32113 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-23 22:41:35.416 9753 9753 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 22:41:36.282 9753 9753 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
11-23 22:46:36.865 11074 11074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 22:46:37.662 11074 11074 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
11-23 23:45:35.158 22342 22342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-23 23:45:35.923 22342 22342 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
11-24 00:51:39.175 27213 27213 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 00:51:39.746 27213 27213 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
11-24 00:57:55.185 27695 27695 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 00:58:40.456 27905 27905 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 00:58:41.123 27905 27905 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
11-24 01:03:36.093 28911 28911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 01:03:36.593 28911 28911 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
11-24 01:09:10.219 29491 29491 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 01:09:10.805 29491 29491 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
11-24 01:18:52.197 30393 30393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 01:18:52.525 30393 30393 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
11-24 01:29:54.561 31245 31245 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 01:41:21.898 5304 5304 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 01:41:22.676 5304 5304 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
11-24 02:12:31.644 8538 8538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 02:12:32.899 8538 8538 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
11-24 02:55:38.586 8912 8912 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 02:55:38.962 8912 8912 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
11-24 03:58:43.256 9878 9878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 03:58:45.830 9878 9878 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
11-24 04:59:39.290 10425 10425 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 04:59:39.970 10425 10425 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
11-24 05:07:09.867 10665 10665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 05:07:10.356 10665 10665 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
11-24 05:32:49.068 11630 11630 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 05:32:49.544 11630 11630 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
11-24 05:36:03.933 12094 12094 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 05:36:04.634 12094 12094 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
11-24 05:52:07.340 12986 12986 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 05:52:07.878 12986 12986 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
11-24 06:41:21.255 4808 4808 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 06:41:22.562 4808 4808 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-24 06:41:22.562 4808 4808 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-24 06:41:22.562 4808 4808 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-24 06:41:22.562 4808 4808 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-24 06:41:22.563 4808 4808 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-24 06:41:22.563 4808 4808 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-24 06:41:22.563 4808 4808 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-24 06:41:22.563 4808 4808 W System.err: at
java.lang.Class.newInstance(Native Method)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-24 06:41:22.563 4808 4808 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-24 06:41:22.563 4808 4808 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-24 06:41:22.563 4808 4808 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-24 06:41:22.563 4808 4808 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-24 06:41:22.563 4808 4808 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-24 06:41:22.563 4808 4808 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-24 06:41:22.563 4808 4808 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-24 06:41:22.563 4808 4808 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-24 06:41:22.874 4808 4808 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.
11-24 06:41:24.853 4808 4808 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-24 06:41:24.854 4808 4808 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
11-24 06:41:25.728 4808 4808 W com.mbwhatsapp: type=1400 audit(0.0:1346): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-24 06:41:25.818 4808 4808 W com.mbwhatsapp: type=1400 audit(0.0:1347): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-24 06:41:25.818 4808 4808 W com.mbwhatsapp: type=1400 audit(0.0:1348): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-24 06:41:25.818 4808 4808 W com.mbwhatsapp: type=1400 audit(0.0:1349): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-24 06:41:26.606 4808 5116 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-24 06:41:26.606 4808 5116 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-24 06:41:26.606 4808 5116 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-24 06:41:28.747 4808 5295 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-24 06:41:28.747 4808 5295 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-24 06:46:14.803 10997 10997 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 06:46:15.402 10997 10997 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
11-24 06:57:10.018 13504 13504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 06:57:10.618 13504 13504 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
11-24 06:57:24.239 14086 14086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 06:57:24.535 14086 14086 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
11-24 07:56:25.217 19009 19009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 07:56:28.504 19009 19009 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.
11-24 07:56:29.995 19009 19192 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-24 07:56:29.995 19009 19192 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-24 07:56:29.995 19009 19192 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-24 08:56:37.286 20012 20012 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 08:56:38.506 20012 20012 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
11-24 10:58:15.489 21438 21438 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 10:58:15.856 21438 21438 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
11-24 15:56:41.047 5822 5822 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 15:56:43.434 5822 5822 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
11-24 15:58:32.330 10143 10143 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 15:58:33.004 10143 10143 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
11-24 16:00:29.153 14197 14197 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 16:00:30.099 14197 14197 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
11-24 16:02:14.179 15025 15025 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 16:02:14.474 15025 15025 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
11-24 16:05:46.945 17659 17659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 16:05:47.556 17659 17659 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
11-24 16:08:53.679 18299 18299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 16:08:53.943 18299 18299 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
11-24 16:16:34.210 21506 21506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 16:16:35.279 21506 21506 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
11-24 16:52:24.270 28628 28628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 16:52:24.826 28628 28628 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
11-24 18:07:03.921 326 326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 18:07:04.546 326 326 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
11-24 18:56:56.843 6190 6190 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 18:56:57.701 6190 6190 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.
11-24 18:56:59.579 6190 6431 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-24 18:56:59.579 6190 6431 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-24 18:56:59.579 6190 6431 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-24 18:57:28.642 7915 7915 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 18:57:29.969 7915 7915 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
11-24 18:59:01.718 11418 11418 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 18:59:02.827 11418 11418 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
11-24 19:01:30.763 12842 12842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 19:01:31.986 12842 12842 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
11-24 19:04:59.543 13247 13247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 19:04:59.809 13247 13247 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
11-24 19:08:03.922 14507 14507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 19:08:04.725 14507 14507 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.
11-24 19:08:05.914 14507 14554 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-24 19:08:05.914 14507 14554 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-24 19:08:05.914 14507 14554 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-24 19:18:51.076 17824 17824 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 19:19:16.922 17824 17824 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.
11-24 19:19:27.038 17824 17871 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-24 19:19:27.038 17824 17871 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-24 19:19:27.038 17824 17871 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-24 19:24:29.957 18348 18348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 19:24:30.301 18348 18348 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
11-24 19:27:05.145 18747 18747 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 19:27:05.448 18747 18747 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
11-24 20:59:10.869 3132 3132 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 20:59:11.417 3132 3132 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
11-24 21:42:14.435 13965 13965 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 21:42:14.908 13965 13965 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
11-24 23:45:30.594 22058 22058 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-24 23:45:32.245 22058 22058 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
11-25 01:12:26.484 28904 28904 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 01:12:27.641 28904 28904 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
11-25 01:42:49.439 8859 8859 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 01:42:50.078 8859 8859 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
11-25 01:45:50.029 9926 9926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 01:45:51.142 9926 9926 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
11-25 02:07:23.028 10756 10756 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 02:07:23.659 10756 10756 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
11-25 02:29:39.660 11184 11184 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 02:29:40.496 11184 11184 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
11-25 02:45:38.332 11750 11750 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 02:45:39.244 11750 11750 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
11-25 02:56:00.194 12460 12460 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 02:56:00.739 12460 12460 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
11-25 03:25:03.388 17658 17658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 03:25:04.329 17658 17658 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
11-25 03:46:26.402 23123 23123 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 03:46:27.667 23123 23123 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
11-25 04:48:20.977 595 595 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 05:49:44.982 3991 3991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 05:49:45.938 3991 3991 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
11-25 07:00:22.104 5817 5817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 07:00:22.855 5817 5817 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
11-25 07:02:46.181 7395 7395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 07:02:46.772 7395 7395 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
11-25 09:08:23.303 9085 9085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 09:08:24.720 9085 9085 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
11-25 09:12:17.941 9564 9564 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 09:12:18.343 9564 9564 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
11-25 09:52:03.077 10365 10365 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 09:52:03.507 10365 10365 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
11-25 10:00:21.916 10948 10948 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 10:00:22.452 10948 10948 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
11-25 10:12:22.088 11229 11229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 10:12:22.447 11229 11229 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
11-25 10:28:21.928 11369 11369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 10:28:22.240 11369 11369 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
11-25 10:46:41.069 11531 11531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 10:46:41.365 11531 11531 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
11-25 11:59:02.701 13049 13049 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 11:59:04.140 13049 13049 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
11-25 12:04:18.902 13650 13650 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 12:04:19.260 13650 13650 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
11-25 13:49:47.516 15764 15764 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 13:49:49.062 15764 15764 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
11-25 13:51:32.120 16623 16623 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 13:51:32.499 16623 16623 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
11-25 14:02:43.617 17273 17273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 14:02:44.315 17273 17273 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
11-25 15:52:22.010 22671 22671 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 15:52:22.643 22671 22671 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
11-25 16:55:23.019 23468 23468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 16:55:23.469 23468 23468 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
11-25 17:03:53.174 27418 27418 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 17:03:54.233 27418 27418 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
11-25 17:51:19.781 5945 5945 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 17:51:21.812 5945 5945 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-25 17:51:21.813 5945 5945 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-25 17:51:21.814 5945 5945 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-25 17:51:21.814 5945 5945 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-25 17:51:21.814 5945 5945 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-25 17:51:21.814 5945 5945 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-25 17:51:21.814 5945 5945 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-25 17:51:21.814 5945 5945 W System.err: at
java.lang.Class.newInstance(Native Method)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-25 17:51:21.814 5945 5945 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-25 17:51:21.814 5945 5945 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-25 17:51:21.814 5945 5945 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-25 17:51:21.814 5945 5945 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-25 17:51:21.814 5945 5945 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-25 17:51:21.814 5945 5945 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-25 17:51:21.814 5945 5945 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-25 17:51:21.814 5945 5945 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-25 17:51:22.040 5945 5945 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.
11-25 17:51:25.050 5945 5945 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-25 17:51:25.050 5945 5945 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-25 17:51:27.053 5945 6392 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-25 17:51:27.053 5945 6392 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-25 17:51:27.053 5945 6392 W com.mbwhatsapp: and incorrect proguard
optimizations.
11-25 17:51:28.590 5945 6392 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
11-25 17:51:28.591 5945 6392 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
11-25 17:52:32.584 8317 8317 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 17:52:34.434 8317 8317 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
11-25 17:52:34.436 8317 8317 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
11-25 17:52:34.437 8317 8317 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
11-25 17:52:34.437 8317 8317 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
11-25 17:52:34.437 8317 8317 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
11-25 17:52:34.437 8317 8317 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
11-25 17:52:34.437 8317 8317 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
11-25 17:52:34.437 8317 8317 W System.err: at
java.lang.Class.newInstance(Native Method)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
11-25 17:52:34.437 8317 8317 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
11-25 17:52:34.437 8317 8317 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
11-25 17:52:34.437 8317 8317 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
11-25 17:52:34.437 8317 8317 W System.err: at
android.os.Looper.loop(Looper.java:334)
11-25 17:52:34.437 8317 8317 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
11-25 17:52:34.437 8317 8317 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
11-25 17:52:34.437 8317 8317 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
11-25 17:52:34.437 8317 8317 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
11-25 17:52:34.604 8317 8317 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.
11-25 17:52:39.708 8317 8317 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
11-25 17:52:39.709 8317 8317 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
11-25 17:56:07.319 13647 13647 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 17:56:07.931 13647 13647 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
11-25 18:45:19.706 30538 30538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 18:45:20.581 30538 30538 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
11-25 19:45:35.548 13739 13739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 19:45:36.336 13739 13739 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
11-25 19:56:23.785 18544 18544 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 19:56:24.236 18544 18544 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
11-25 20:05:10.720 18796 18796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 20:05:11.398 18796 18796 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
11-25 20:14:47.298 20237 20237 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 20:14:47.887 20237 20237 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
11-25 20:34:19.305 20727 20727 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 20:34:19.599 20727 20727 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
11-25 20:54:19.334 21331 21331 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 20:54:19.643 21331 21331 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
11-25 21:11:55.722 21727 21727 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 21:11:56.124 21727 21727 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
11-25 21:45:50.777 22549 22549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 21:45:51.097 22549 22549 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
11-25 21:51:41.316 23167 23167 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 21:51:42.042 23167 23167 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
11-25 21:54:40.624 23952 23952 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 21:54:41.147 23952 23952 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
11-25 21:58:16.156 24418 24418 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 21:58:16.503 24418 24418 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
11-25 22:57:15.606 1932 1932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 22:57:16.603 1932 1932 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
11-25 23:16:50.943 2933 2933 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 23:16:53.290 2933 2933 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.
11-25 23:16:55.053 2933 3106 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-25 23:16:55.053 2933 3106 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-25 23:16:55.053 2933 3106 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-25 23:30:10.076 4765 4765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 23:30:10.689 4765 4765 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
11-25 23:48:17.203 5037 5037 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-25 23:48:17.472 5037 5037 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
11-26 00:04:57.605 5644 5644 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 00:04:58.512 5644 5644 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
11-26 00:45:04.483 6758 6758 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 00:45:05.478 6758 6758 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
11-26 01:08:28.311 8090 8090 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 01:08:28.780 8090 8090 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
11-26 01:45:49.319 10025 10025 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 01:45:49.826 10025 10025 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
11-26 01:52:18.453 10586 10586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 01:52:18.859 10586 10586 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
11-26 02:04:51.557 10930 10930 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 02:04:51.918 10930 10930 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
11-26 02:23:36.299 11407 11407 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 02:23:36.818 11407 11407 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
11-26 02:42:20.268 11641 11641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 02:42:20.663 11641 11641 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
11-26 03:30:06.406 12295 12295 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 03:30:07.346 12295 12295 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
11-26 04:34:13.000 14811 14811 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 04:34:13.599 14811 14811 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
11-26 05:54:21.029 15636 15636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 05:54:22.004 15636 15636 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
11-26 06:50:18.548 18086 18086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 06:50:19.040 18086 18086 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
11-26 08:05:23.882 5324 5324 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:05:26.592 5324 5324 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.
11-26 08:05:27.821 5324 5324 W com.mbwhatsapp: type=1400 audit(0.0:1406): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-26 08:05:27.895 5324 5324 W com.mbwhatsapp: type=1400 audit(0.0:1407): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-26 08:08:43.007 11405 11405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:08:43.585 11405 11405 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
11-26 08:20:33.832 5684 5684 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:20:34.604 5684 5684 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
11-26 08:21:55.134 8699 8699 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:21:55.599 8699 8699 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
11-26 08:22:36.825 9921 9921 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:22:37.373 9921 9921 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
11-26 08:27:52.051 11547 11547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:27:52.455 11547 11547 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
11-26 08:32:09.997 12563 12563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 08:32:10.454 12563 12563 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
11-26 09:11:04.209 13232 13232 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 09:11:04.791 13232 13232 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
11-26 09:30:17.244 14381 14381 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 09:30:17.625 14381 14381 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
11-26 09:39:57.925 15826 15826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 09:39:58.511 15826 15826 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
11-26 09:45:48.600 16293 16293 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 09:45:49.564 16293 16293 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
11-26 10:06:49.758 18076 18076 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 10:06:50.444 18076 18076 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
11-26 10:57:48.866 21385 21385 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 10:57:49.479 21385 21385 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
11-26 11:57:48.889 25383 25383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 11:57:49.468 25383 25383 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
11-26 12:57:48.832 28556 28556 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 12:57:49.308 28556 28556 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
11-26 13:54:23.799 32765 32765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 13:54:24.395 32765 32765 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
11-26 14:57:58.658 5492 5492 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 14:57:59.462 5492 5492 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
11-26 15:57:48.880 8015 8015 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 15:57:49.480 8015 8015 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
11-26 16:55:24.417 13001 13001 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 16:55:25.069 13001 13001 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
11-26 17:58:20.703 24353 24353 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 17:58:21.791 24353 24353 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.
11-26 17:58:23.572 24353 24542 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-26 17:58:23.572 24353 24542 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-26 17:58:23.572 24353 24542 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-26 18:57:48.956 31533 31533 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 18:57:49.942 31533 31533 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.
11-26 18:57:51.609 31533 31581 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
11-26 18:57:51.609 31533 31581 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
11-26 18:57:51.609 31533 31581 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
11-26 19:03:24.416 31951 31951 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 19:03:24.951 31951 31951 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
11-26 19:12:48.898 32756 32756 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 19:12:49.424 32756 32756 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
11-26 19:58:21.690 10940 10940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 19:58:23.092 10940 10940 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
11-26 20:05:52.640 13059 13059 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 20:05:54.173 13059 13059 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
11-26 20:58:19.126 29035 29035 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 20:58:20.250 29035 29035 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
11-26 20:59:38.387 30183 30183 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 20:59:39.302 30183 30183 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
11-26 21:08:43.482 401 401 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 21:08:44.507 401 401 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
11-26 21:58:22.517 20141 20141 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 21:58:23.708 20141 20141 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
11-26 22:06:31.918 22937 22937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 22:06:32.977 22937 22937 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
11-26 23:14:14.928 29211 29211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 23:14:16.085 29211 29211 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
11-26 23:32:01.040 29687 29687 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 23:32:02.311 29687 29687 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
11-26 23:53:07.069 31112 31112 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-26 23:53:09.403 31112 31112 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
11-27 00:32:00.121 32299 32299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 00:32:02.063 32299 32299 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
11-27 01:14:35.956 2491 2491 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 01:14:36.581 2491 2491 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
11-27 02:18:58.012 5515 5515 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 02:18:59.154 5515 5515 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
11-27 03:38:48.089 8265 8265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 03:38:48.709 8265 8265 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
11-27 03:58:48.433 8660 8660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 03:58:48.738 8660 8660 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
11-27 05:03:50.915 10937 10937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 05:03:51.535 10937 10937 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
11-27 06:15:26.065 16009 16009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 06:15:29.664 16009 16009 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
11-27 07:26:52.624 21716 21716 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 07:26:53.185 21716 21716 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
11-27 08:32:01.094 26829 26829 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 08:32:02.325 26829 26829 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
11-27 09:38:21.632 29337 29337 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 09:38:24.437 29337 29337 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
11-27 11:34:58.124 32259 32259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 11:34:59.353 32259 32259 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
11-27 11:44:01.065 1972 1972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 11:44:01.352 1972 1972 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
11-27 11:56:01.032 3476 3476 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 11:56:01.318 3476 3476 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
11-27 12:07:30.211 4593 4593 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 12:07:30.615 4593 4593 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
11-27 12:15:04.281 5323 5323 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 12:15:04.661 5323 5323 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
11-27 12:28:05.128 6132 6132 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 12:28:05.489 6132 6132 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
11-27 12:55:32.184 13423 13423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 12:55:36.449 13423 13423 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
11-27 20:13:03.944 22351 22351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 20:13:10.064 22351 22351 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.
11-27 20:13:24.203 22351 22351 W com.mbwhatsapp: type=1400 audit(0.0:87098): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-27 20:13:24.356 22351 22351 W com.mbwhatsapp: type=1400 audit(0.0:87099): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-27 20:20:31.310 27827 27827 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-27 20:20:32.568 27827 27827 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
11-28 08:05:42.113 25510 25510 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-28 08:05:44.588 25510 25510 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.
11-28 08:05:52.212 25510 25510 W com.mbwhatsapp: type=1400 audit(0.0:108598): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
11-28 08:05:54.428 25510 25510 W com.mbwhatsapp: type=1400 audit(0.0:108599): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
11-30 02:21:52.817 1837 1837 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
11-30 02:21:53.318 1837 1837 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
12-01 00:01:18.173 31758 31758 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 00:01:25.632 31758 31758 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.
12-01 00:01:29.865 31758 31758 W com.mbwhatsapp: type=1400 audit(0.0:446358): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
12-01 00:03:50.632 4221 4221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 00:03:52.579 4221 4221 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
12-01 02:02:28.891 27476 27476 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 02:02:30.564 27476 27476 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.
12-01 02:02:33.728 27476 27796 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
12-01 02:02:33.728 27476 27796 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
12-01 02:02:33.728 27476 27796 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
12-01 03:12:10.097 4405 4405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 03:12:10.773 4405 4405 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
12-01 04:12:13.960 7493 7493 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 04:12:14.826 7493 7493 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
12-01 05:12:10.729 12549 12549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 05:12:11.433 12549 12549 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
12-01 06:12:11.265 15738 15738 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-01 06:12:11.968 15738 15738 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
12-02 00:40:36.030 3957 3957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-02 00:40:37.711 3957 3957 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.
12-02 00:40:41.206 3957 4262 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=76cfc1e4-7a81-4e99-a079-78cf5516538a, generation=0)
--------- beginning of main
12-02 02:27:22.218 22303 22303 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-02 02:27:23.891 22303 22303 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
12-02 03:12:56.989 27321 27321 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-02 03:12:57.843 27321 27321 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
12-02 05:12:17.016 10978 10978 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-02 05:12:17.963 10978 10978 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
12-02 20:06:55.893 1897 1897 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-02 20:07:06.028 1897 1897 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
12-03 01:57:07.395 25085 25085 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 01:57:08.959 25085 25085 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
12-03 03:12:20.245 7578 7578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 03:12:20.784 7578 7578 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
12-03 04:12:34.356 11101 11101 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 04:12:35.194 11101 11101 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
12-03 04:14:04.563 11535 11535 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 04:14:04.901 11535 11535 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
12-03 04:17:49.321 12000 12000 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 04:17:49.915 12000 12000 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
12-03 04:20:39.557 12736 12736 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 04:20:39.896 12736 12736 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
12-03 04:25:38.740 13231 13231 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 04:25:39.115 13231 13231 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
12-03 04:34:28.189 14422 14422 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 04:34:28.880 14422 14422 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
12-03 05:12:40.503 17625 17625 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 05:12:41.528 17625 17625 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
12-03 06:12:21.510 21468 21468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 06:12:22.143 21468 21468 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
12-03 18:59:13.720 22509 22509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 18:59:17.792 22509 22509 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.
12-03 18:59:28.656 22509 22509 W com.mbwhatsapp: type=1400 audit(0.0:712664): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=1237642 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
12-03 18:59:28.876 22509 22509 W com.mbwhatsapp: type=1400 audit(0.0:712665): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=1255874 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
12-03 19:22:48.870 31202 31202 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 19:22:49.648 31202 31202 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
12-03 20:12:39.222 12247 12247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-03 20:12:40.281 12247 12247 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
12-05 20:49:48.387 4781 4781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-05 20:49:55.233 4781 4781 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
12-05 20:49:55.251 4781 4781 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
12-05 20:49:55.251 4781 4781 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
12-05 20:49:55.251 4781 4781 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
12-05 20:49:55.251 4781 4781 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
12-05 20:49:55.251 4781 4781 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
12-05 20:49:55.251 4781 4781 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
12-05 20:49:55.251 4781 4781 W System.err: at
java.lang.Class.newInstance(Native Method)
12-05 20:49:55.251 4781 4781 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
12-05 20:49:55.251 4781 4781 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
12-05 20:49:55.251 4781 4781 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
12-05 20:49:55.251 4781 4781 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
12-05 20:49:55.251 4781 4781 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
12-05 20:49:55.251 4781 4781 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
12-05 20:49:55.251 4781 4781 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
12-05 20:49:55.251 4781 4781 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
12-05 20:49:55.251 4781 4781 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
12-05 20:49:55.255 4781 4781 W System.err: at
android.os.Looper.loop(Looper.java:334)
12-05 20:49:55.255 4781 4781 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
12-05 20:49:55.255 4781 4781 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
12-05 20:49:55.255 4781 4781 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
12-05 20:49:55.255 4781 4781 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
12-05 20:49:56.149 4781 4781 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.
12-05 20:50:00.111 4781 4805 W com.mbwhatsapp: Suspending all threads took:
81.503ms
12-05 20:50:02.226 4781 4781 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
12-05 20:50:02.226 4781 4781 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
12-05 20:50:04.572 4781 5458 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
12-05 20:50:04.572 4781 5458 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
12-05 20:50:04.572 4781 5458 W com.mbwhatsapp: and incorrect proguard
optimizations.
12-05 20:50:07.347 4781 5458 W System : ClassLoader referenced unknown path:
/system/framework/tcmclient.jar
12-05 20:50:07.348 4781 5458 W System : ClassLoader referenced unknown path:
/system/framework/tcmiface.jar
12-05 20:50:07.567 4781 5570 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=dfd4d4a3-bc86-493f-87aa-a1426c8ab4fe, generation=0)
12-05 20:51:17.747 7973 7973 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-05 20:51:18.876 7973 7973 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
12-05 20:51:18.876 7973 7973 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
12-05 20:51:18.876 7973 7973 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1121)
12-05 20:51:18.876 7973 7973 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1075)
12-05 20:51:18.876 7973 7973 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:998)
12-05 20:51:18.876 7973 7973 W System.err: at
java.lang.System.loadLibrary(System.java:1656)
12-05 20:51:18.876 7973 7973 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
12-05 20:51:18.876 7973 7973 W System.err: at
java.lang.Class.newInstance(Native Method)
12-05 20:51:18.876 7973 7973 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
12-05 20:51:18.876 7973 7973 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
12-05 20:51:18.876 7973 7973 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1177)
12-05 20:51:18.876 7973 7973 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1381)
12-05 20:51:18.876 7973 7973 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7120)
12-05 20:51:18.877 7973 7973 W System.err: at
android.app.ActivityThread.access$1800(ActivityThread.java:284)
12-05 20:51:18.877 7973 7973 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2266)
12-05 20:51:18.877 7973 7973 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
12-05 20:51:18.877 7973 7973 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
12-05 20:51:18.877 7973 7973 W System.err: at
android.os.Looper.loop(Looper.java:334)
12-05 20:51:18.877 7973 7973 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8333)
12-05 20:51:18.877 7973 7973 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
12-05 20:51:18.877 7973 7973 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
12-05 20:51:18.877 7973 7973 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1065)
12-05 20:51:19.040 7973 7973 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.
12-05 20:51:25.104 7973 7973 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
12-05 20:51:25.106 7973 7973 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
12-05 20:51:25.402 7973 7973 W com.mbwhatsapp: type=1400 audit(0.0:1925): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=1217844 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
12-05 20:51:25.432 7973 7973 W com.mbwhatsapp: type=1400 audit(0.0:1926): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=1256111 scontext=u:r:untrusted_app:s0:c2,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c2,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
12-06 07:18:56.169 22482 22482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
12-06 07:18:56.560 22482 22482 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.