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

04-06 20:39:09.151 3992 3992 E com.mbwhatsapp: Not starting debugger since

process cannot load the jdwp agent.
04-06 20:39:09.815 3992 3992 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-06 20:39:11.135 3992 3992 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-06 20:39:11.136 3992 3992 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
04-06 20:39:11.181 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537379): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.193 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537380): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.205 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537381): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.317 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537382): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.337 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537383): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.337 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537384): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.337 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537385): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-06 20:39:11.337 3992 3992 W com.mbwhatsapp: type=1400 audit(0.0:3537386): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
04-06 20:39:11.490 3992 4062 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-06 20:39:11.490 3992 4062 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-06 20:39:11.490 3992 4062 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-06 20:39:11.507 3992 3992 W com.mbwhatsapp: Method void X.0eU.A0h(X.0tK,
boolean) failed lock verification and will run slower.
--------- beginning of main
04-06 20:39:12.489 3992 4108 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-06 20:39:12.523 3992 4076 E OpenGLRenderer: fbcNotifyFrameComplete error:
undefined symbol: fbcNotifyFrameComplete
04-06 20:39:12.523 3992 4076 E OpenGLRenderer: fbcNotifyNoRender error: undefined
symbol: fbcNotifyNoRender
04-06 20:39:12.733 3992 4127 E PlayCore: UID: [10219] PID: [3992]
StandardIntegrity : Phonesky is not installed.
04-06 20:40:24.914 6020 6020 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 20:40:26.100 6020 6020 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-06 22:14:08.363 21249 21249 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:14:09.141 21249 21249 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-06 22:17:15.506 22950 22950 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:17:15.946 22950 22950 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-06 22:18:19.070 23270 23270 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:18:19.621 23270 23270 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-06 22:22:15.170 25390 25390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:22:15.811 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
04-06 22:29:11.470 30968 30968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:29:12.759 30968 30968 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-06 22:29:14.615 30968 31076 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-06 22:29:14.615 30968 31076 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-06 22:29:14.615 30968 31076 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-06 22:38:14.230 7458 7458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:38:17.505 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.
04-06 22:38:22.128 7458 7809 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-06 22:38:22.128 7458 7809 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-06 22:38:22.128 7458 7809 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-06 22:56:51.955 27988 27988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:56:52.599 27988 27988 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-06 22:56:54.294 27988 28037 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-06 22:56:54.294 27988 28037 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-06 22:56:54.294 27988 28037 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-06 23:31:09.648 11494 11494 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 23:31:10.761 11494 11494 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 00:33:36.355 14981 14981 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 00:33:36.826 14981 14981 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 01:15:30.105 21724 21724 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 01:15:30.748 21724 21724 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 01:15:31.865 21724 21785 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 01:15:31.865 21724 21785 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 01:15:31.865 21724 21785 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 02:13:01.922 32024 32024 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 02:13:02.809 32024 32024 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 02:22:04.906 3408 3408 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 02:22:05.332 3408 3408 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 08:02:55.822 19268 19268 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 08:02:56.180 19268 19268 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 08:02:57.409 19268 19323 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 08:02:57.409 19268 19323 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 08:02:57.409 19268 19323 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 08:17:56.799 20460 20460 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 08:18:07.155 20460 20460 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 08:21:21.356 20856 20856 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 08:21:21.732 20856 20856 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 09:13:18.102 28014 28014 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 09:13:18.844 28014 28014 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 10:21:13.027 14318 14318 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 10:21:13.684 14318 14318 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 11:26:17.896 16429 16429 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 11:26:18.795 16429 16429 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 11:26:21.474 16429 16573 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 11:26:21.474 16429 16573 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 11:26:21.474 16429 16573 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 11:34:15.463 19874 19874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 11:34:16.066 19874 19874 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 12:27:23.487 25861 25861 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 12:27:24.440 25861 25861 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 13:28:53.501 18628 18628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:28:54.644 18628 18628 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 13:51:27.129 28939 28939 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:51:28.609 28939 28939 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 13:51:31.211 28939 29302 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 13:51:31.211 28939 29302 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 13:51:31.211 28939 29302 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 13:54:24.201 3531 3531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:54:25.509 3531 3531 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 13:54:27.880 3531 3602 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 13:54:27.880 3531 3602 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 13:54:27.880 3531 3602 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 13:57:23.336 6122 6122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:57:24.125 6122 6122 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 14:32:55.642 10668 10668 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 14:32:56.835 10668 10668 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 15:29:59.378 13499 13499 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 15:29:59.929 13499 13499 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 15:38:03.448 16075 16075 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 15:38:04.744 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
04-07 16:00:41.445 23062 23062 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 16:00:42.264 23062 23062 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 16:15:09.006 31235 31235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 16:15:09.736 31235 31235 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 16:24:25.618 8382 8382 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 16:24:26.373 8382 8382 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 16:53:59.402 15881 15881 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 16:54:00.492 15881 15881 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 17:15:26.805 22885 22885 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 17:15:28.418 22885 22885 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 18:21:32.573 16455 16455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 18:21:33.162 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.
--------- beginning of main
04-07 18:21:59.379 16790 16790 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 18:22:00.141 16790 16790 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 18:30:00.155 21800 21800 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 18:30:01.468 21800 21800 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 20:26:04.363 29550 29550 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 20:26:05.889 29550 29550 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 20:27:58.349 4005 4005 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 20:28:01.096 4005 4005 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 20:28:05.710 4005 4005 W com.mbwhatsapp: type=1400 audit(0.0:3787341): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 20:28:05.710 4005 4005 W com.mbwhatsapp: type=1400 audit(0.0:3787342): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 20:28:05.710 4005 4005 W com.mbwhatsapp: type=1400 audit(0.0:3787343): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 20:28:05.710 4005 4005 W com.mbwhatsapp: type=1400 audit(0.0:3787344): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-07 20:30:35.445 9312 9312 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 20:30:36.932 9312 9312 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 20:34:10.028 16258 16258 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 20:34:11.025 16258 16258 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 20:34:12.458 16258 16258 W com.mbwhatsapp: type=1400 audit(0.0:3788337): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 20:34:12.840 16258 16429 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 20:34:12.840 16258 16429 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 20:34:12.840 16258 16429 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 22:13:08.148 18371 18371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:13:09.610 18371 18371 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 22:13:14.155 18371 18501 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 22:13:14.155 18371 18501 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 22:13:14.155 18371 18501 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 22:19:03.631 4932 4932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:19:04.863 4932 4932 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 22:19:06.987 4932 5011 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 22:19:06.987 4932 5011 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 22:19:06.987 4932 5011 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 22:28:17.279 21031 21031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:28:18.187 21031 21031 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 22:28:20.600 21031 21155 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 22:28:20.600 21031 21155 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 22:28:20.600 21031 21155 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 22:29:53.366 25213 25213 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:29:54.446 25213 25213 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 22:43:10.184 29122 29122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:43:12.441 29122 29122 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 22:43:15.092 29122 29288 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 22:43:15.092 29122 29288 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 22:43:15.092 29122 29288 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 22:45:25.050 31133 31133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:45:26.129 31133 31133 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 22:45:27.440 31133 31228 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 22:45:27.440 31133 31228 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 22:45:27.440 31133 31228 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 22:47:25.471 3677 3677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 22:47:27.452 3677 3677 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 22:47:31.394 3677 3972 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 22:47:31.394 3677 3972 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 22:47:31.394 3677 3972 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 23:13:08.943 21659 21659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 23:13:10.309 21659 21659 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-07 23:13:12.744 21659 21659 W com.mbwhatsapp: type=1400 audit(0.0:3875638): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 23:13:12.744 21659 21659 W com.mbwhatsapp: type=1400 audit(0.0:3875639): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 23:13:12.744 21659 21659 W com.mbwhatsapp: type=1400 audit(0.0:3875640): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 23:13:12.744 21659 21659 W com.mbwhatsapp: type=1400 audit(0.0:3875641): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
04-07 23:13:13.261 21659 21764 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 23:13:13.261 21659 21764 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 23:13:13.261 21659 21764 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-07 23:14:56.805 23221 23221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 23:14:57.480 23221 23221 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 23:15:56.754 23715 23715 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 23:15:57.633 23715 23715 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-07 23:47:48.969 12507 12507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 23:47:50.328 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.
04-07 23:47:52.694 12507 12738 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-07 23:47:52.694 12507 12738 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-07 23:47:52.694 12507 12738 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-08 00:16:12.514 21482 21482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 00:16:13.188 21482 21482 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 00:37:00.224 25894 25894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 00:37:01.174 25894 25894 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 00:42:16.047 27325 27325 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 00:42:16.709 27325 27325 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 01:17:17.454 762 762 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 01:17:18.352 762 762 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 01:34:22.841 5772 5772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 01:34:23.600 5772 5772 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 02:00:09.040 9795 9795 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 02:00:09.567 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
04-08 02:17:24.344 12428 12428 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 02:17:24.995 12428 12428 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 03:17:28.753 24641 24641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 03:17:29.707 24641 24641 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 04:13:57.013 4951 4951 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 04:25:59.967 5832 5832 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 04:26:00.515 5832 5832 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-08 04:26:01.561 5832 5909 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-08 04:26:01.561 5832 5909 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-08 04:26:01.561 5832 5909 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-08 04:46:00.190 9067 9067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 04:46:00.783 9067 9067 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 06:01:46.400 18791 18791 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 06:01:47.217 18791 18791 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 07:15:44.050 27838 27838 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 07:15:44.594 27838 27838 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 21:20:45.312 22433 22433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:20:46.237 22433 22433 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 21:26:13.151 27619 27619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:26:14.028 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.
--------- beginning of main
04-08 21:29:08.812 29566 29566 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:29:09.366 29566 29566 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 21:30:37.224 31674 31674 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:30:38.205 31674 31674 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 21:32:42.508 1567 1567 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:32:44.192 1567 1567 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-08 21:32:46.590 1567 1961 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-08 21:32:46.590 1567 1961 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-08 21:32:46.590 1567 1961 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-08 21:38:35.336 6451 6451 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:38:36.463 6451 6451 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 21:48:59.721 17902 17902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:49:01.818 17902 17902 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-08 21:49:05.581 17902 18093 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-08 21:49:05.581 17902 18093 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-08 21:49:05.581 17902 18093 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-08 22:08:09.592 10489 10489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 22:08:10.242 10489 10489 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-08 22:08:11.815 10489 10539 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-08 22:08:11.815 10489 10539 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-08 22:08:11.815 10489 10539 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-08 22:22:29.827 18174 18174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 22:22:30.637 18174 18174 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-08 22:22:32.470 18174 18219 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-08 22:22:32.470 18174 18219 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-08 22:22:32.470 18174 18219 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-08 22:41:43.716 18260 18260 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 22:41:44.586 18260 18260 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-08 23:43:30.333 20815 20815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 23:43:31.182 20815 20815 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 00:47:48.873 6384 6384 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 00:47:52.714 6384 6384 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-09 00:47:55.100 6384 6456 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-09 00:47:55.100 6384 6456 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-09 00:47:55.100 6384 6456 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-09 01:13:40.851 19725 19725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:13:41.152 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
04-09 01:27:15.707 21895 21895 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:27:16.083 21895 21895 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 02:00:05.129 29097 29097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 02:00:05.716 29097 29097 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 02:08:18.776 30183 30183 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 02:08:19.333 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
04-09 02:13:14.002 31060 31060 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 02:13:14.511 31060 31060 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 02:30:21.641 1209 1209 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 02:30:22.719 1209 1209 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 20:51:54.428 17177 17177 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 20:51:55.022 17177 17177 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 20:52:29.929 17557 17557 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 20:52:30.416 17557 17557 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 20:55:00.146 17902 17902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 20:55:00.581 17902 17902 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 20:59:44.314 20359 20359 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 20:59:44.986 20359 20359 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-09 20:59:46.345 20359 20404 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-09 20:59:46.345 20359 20404 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-09 20:59:46.345 20359 20404 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-09 21:00:52.218 21242 21242 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:00:52.837 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
04-09 21:01:56.172 22229 22229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:01:56.796 22229 22229 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-09 21:01:58.599 22229 22356 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-09 21:01:58.599 22229 22356 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-09 21:01:58.599 22229 22356 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-09 21:05:29.001 25755 25755 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:05:30.789 25755 25755 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-09 21:05:34.310 25755 26049 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-09 21:05:34.310 25755 26049 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-09 21:05:34.310 25755 26049 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-09 21:21:47.972 15062 15062 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:21:49.039 15062 15062 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-09 21:21:51.278 15062 15111 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-09 21:21:51.278 15062 15111 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-09 21:21:51.278 15062 15111 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-09 22:52:34.472 23409 23409 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:52:37.060 23409 23409 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-09 22:52:42.580 23409 23409 W com.mbwhatsapp: type=1400 audit(0.0:4330354): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-09 22:52:42.660 23409 23409 W com.mbwhatsapp: type=1400 audit(0.0:4330355): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-09 22:52:42.660 23409 23409 W com.mbwhatsapp: type=1400 audit(0.0:4330356): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-09 22:52:42.660 23409 23409 W com.mbwhatsapp: type=1400 audit(0.0:4330357): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-09 22:52:42.664 23409 23409 W com.mbwhatsapp: type=1400 audit(0.0:4330358): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-09 22:55:30.331 27777 27777 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:55:31.181 27777 27777 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-09 23:02:05.096 11754 11754 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 23:02:05.916 11754 11754 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 00:12:47.329 12084 12084 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 00:12:47.961 12084 12084 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 00:39:51.782 14915 14915 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 00:39:52.837 14915 14915 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 01:13:22.976 19260 19260 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 01:13:23.478 19260 19260 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 02:00:07.300 28816 28816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 02:00:07.832 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
04-10 02:16:27.269 30674 30674 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 02:16:28.122 30674 30674 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 13:54:03.420 21058 21058 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 13:54:04.418 21058 21058 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 15:13:45.821 32713 32713 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 15:13:46.440 32713 32713 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 15:15:43.101 2023 2023 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 15:15:43.705 2023 2023 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-10 15:16:15.189 3375 3375 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 15:16:16.337 3375 3375 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 15:19:30.241 6870 6870 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 15:19:30.770 6870 6870 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 15:23:09.805 7606 7606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 15:23:10.840 7606 7606 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 16:04:20.994 11691 11691 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:04:21.611 11691 11691 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-10 16:04:23.441 11691 11747 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-10 16:04:23.441 11691 11747 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-10 16:04:23.441 11691 11747 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-10 16:12:54.031 14007 14007 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:12:59.954 14181 14181 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:13:00.797 14181 14181 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-10 16:13:02.309 14181 14228 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-10 16:13:02.309 14181 14228 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-10 16:13:02.309 14181 14228 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-10 16:14:50.071 14621 14621 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:14:50.438 14621 14621 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 16:16:48.840 16449 16449 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:16:49.882 16449 16449 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 16:17:52.234 16729 16729 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:17:52.899 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
04-10 16:58:12.681 21480 21480 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 16:58:13.418 21480 21480 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 17:13:39.463 24680 24680 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 17:13:40.044 24680 24680 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 18:14:43.778 18195 18195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:14:44.536 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
04-10 18:17:55.951 19164 19164 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:17:56.375 19164 19164 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 18:19:41.701 19520 19520 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:19:42.263 19520 19520 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 18:23:13.121 21386 21386 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:23:14.018 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
04-10 18:31:03.675 22877 22877 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:31:04.274 22877 22877 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 18:31:05.481 22877 22927 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-10 18:31:05.481 22877 22927 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-10 18:31:05.481 22877 22927 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-10 18:32:35.483 23299 23299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:32:36.202 23299 23299 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 19:00:54.351 15851 15851 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 19:00:55.760 15851 15851 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 19:03:36.006 18091 18091 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 19:03:36.633 18091 18091 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 19:38:19.358 11009 11009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 19:38:19.980 11009 11009 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 20:41:11.302 15518 15518 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 20:41:12.078 15518 15518 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 20:43:46.751 21587 21587 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 20:43:47.263 21587 21587 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 22:45:07.254 1959 1959 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 22:45:07.960 1959 1959 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 23:47:31.240 30965 30965 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:47:33.219 30965 30965 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-10 23:47:36.162 30965 31178 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-10 23:47:36.162 30965 31178 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-10 23:47:36.162 30965 31178 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-10 23:50:00.704 3669 3669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:50:01.794 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
04-10 23:53:02.254 7762 7762 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:53:02.987 7762 7762 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-10 23:53:04.672 7762 7839 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-10 23:53:04.672 7762 7839 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-10 23:53:04.672 7762 7839 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-10 23:55:01.171 10339 10339 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:55:02.829 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.
04-10 23:55:06.547 10339 10339 W com.mbwhatsapp: type=1400 audit(0.0:4775280): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-10 23:55:06.591 10339 10339 W com.mbwhatsapp: type=1400 audit(0.0:4775282): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-10 23:55:06.659 10339 10339 W com.mbwhatsapp: type=1400 audit(0.0:4775283): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-10 23:55:06.979 10339 10339 W com.mbwhatsapp: type=1400 audit(0.0:4775284): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-10 23:55:07.107 10339 10339 W com.mbwhatsapp: type=1400 audit(0.0:4775285): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-10 23:56:20.492 12620 12620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:56:21.281 12620 12620 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-10 23:57:31.001 13462 13462 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:57:31.493 13462 13462 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 00:06:50.081 20027 20027 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 00:06:50.755 20027 20027 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-11 00:06:53.420 20027 20177 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-11 00:06:53.420 20027 20177 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-11 00:06:53.420 20027 20177 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-11 00:07:31.991 20842 20842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 00:07:32.541 20842 20842 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 00:16:20.600 29091 29091 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 00:16:21.550 29091 29091 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-11 00:16:23.517 29091 29259 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-11 00:16:23.517 29091 29259 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-11 00:16:23.517 29091 29259 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-11 00:34:31.721 20835 20835 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 00:34:32.336 20835 20835 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 01:27:30.794 32766 32766 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 01:27:31.402 32766 32766 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 01:41:32.670 2874 2874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 01:41:33.164 2874 2874 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 02:00:09.092 5731 5731 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 02:00:09.922 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
04-11 02:15:46.616 7687 7687 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 02:15:47.141 7687 7687 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 02:27:32.091 8403 8403 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 02:27:32.441 8403 8403 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 03:28:18.685 13796 13796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 03:28:19.307 13796 13796 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 03:57:34.741 15450 15450 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 03:57:35.248 15450 15450 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 04:14:11.049 16706 16706 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 04:14:11.563 16706 16706 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 04:47:51.928 21700 21700 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 04:47:52.859 21700 21700 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-11 04:47:54.162 21700 21762 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-11 04:47:54.162 21700 21762 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-11 04:47:54.162 21700 21762 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-11 05:32:38.131 25370 25370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 05:32:38.685 25370 25370 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-11 05:32:42.084 25370 25502 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-11 05:32:42.084 25370 25502 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-11 05:32:42.084 25370 25502 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-11 06:17:57.097 30036 30036 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:17:57.636 30036 30036 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 06:27:44.416 30488 30488 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:27:44.748 30488 30488 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-11 07:49:48.985 7535 7535 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 07:49:49.497 7535 7535 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-11 07:49:50.771 7535 7582 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-11 07:49:50.771 7535 7582 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-11 07:49:50.771 7535 7582 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-14 08:53:17.583 6848 6848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 08:53:18.448 6848 6848 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 08:53:22.898 22221 22221 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 08:53:23.623 22221 22221 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 08:53:38.227 23195 23195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 08:53:38.794 23195 23195 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 17:38:12.679 8426 8426 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:38:13.605 8426 8426 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 17:38:16.286 8426 8607 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
--------- beginning of main
04-15 17:38:17.691 8426 8672 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-15 17:38:17.731 8426 8633 E OpenGLRenderer: fbcNotifyFrameComplete error:
undefined symbol: fbcNotifyFrameComplete
04-15 17:38:17.731 8426 8633 E OpenGLRenderer: fbcNotifyNoRender error: undefined
symbol: fbcNotifyNoRender
04-15 17:38:34.831 9796 9796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:38:35.929 9796 9796 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 17:38:54.266 11654 11654 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:38:56.134 11654 11654 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 17:39:08.441 12282 12282 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:39:09.171 12282 12282 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 17:41:07.149 13966 13966 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:41:07.564 13966 13966 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 17:41:37.617 14927 14927 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:41:39.546 14927 14927 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 17:41:41.751 14927 14927 W com.mbwhatsapp: type=1400 audit(0.0:5767791): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-15 17:41:41.751 14927 14927 W com.mbwhatsapp: type=1400 audit(0.0:5767792): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-15 17:41:41.751 14927 14927 W com.mbwhatsapp: type=1400 audit(0.0:5767793): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-15 17:41:41.751 14927 14927 W com.mbwhatsapp: type=1400 audit(0.0:5767794): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-15 17:44:38.191 23954 23954 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:44:38.793 23954 23954 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 17:48:28.517 27679 27679 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:48:29.275 27679 27679 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 17:48:31.004 27679 27741 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-15 17:48:31.004 27679 27741 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-15 17:48:31.004 27679 27741 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-15 19:13:21.232 2601 2601 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 19:13:21.973 2601 2601 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 21:13:39.003 14971 14971 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 21:13:39.783 14971 14971 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 21:14:10.765 15571 15571 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 21:14:11.526 15571 15571 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 21:14:13.676 15571 15622 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-15 21:14:13.676 15571 15622 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-15 21:14:13.676 15571 15622 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-15 21:17:36.316 20995 20995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 21:17:37.037 20995 20995 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 22:12:58.989 29095 29095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:12:59.754 29095 29095 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 22:13:43.017 30916 30916 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:13:43.621 30916 30916 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 22:14:15.454 31639 31639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:14:16.085 31639 31639 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 22:17:51.851 4252 4252 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:17:53.213 4252 4252 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-15 22:17:55.730 4252 4332 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-15 22:17:55.730 4252 4332 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-15 22:17:55.730 4252 4332 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-15 22:20:53.528 7465 7465 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:20:54.189 7465 7465 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-15 23:23:56.190 17727 17727 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 23:23:56.862 17727 17727 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 00:46:01.279 11425 11425 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 00:46:02.278 11425 11425 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 00:46:04.252 11425 11510 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 00:46:04.252 11425 11510 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 00:46:04.252 11425 11510 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 02:51:30.704 5570 5570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 02:51:31.546 5570 5570 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 02:51:32.932 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883416): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:32.944 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883417): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:32.960 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883418): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:33.060 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883419): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:33.100 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883420): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:33.100 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883421): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:33.100 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883422): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 02:51:33.100 5570 5570 W com.mbwhatsapp: type=1400 audit(0.0:5883423): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
04-16 02:51:32.791 5570 5570 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-16 02:51:32.791 5570 5570 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
04-16 02:51:33.867 5570 5714 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 02:51:33.867 5570 5714 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 02:51:33.867 5570 5714 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 02:51:34.797 5570 5739 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=81285b66-b57f-4284-a5b0-b1b9f40f9114, generation=0)
04-16 02:58:07.486 9218 9218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 02:58:08.334 9218 9218 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 06:04:20.942 18349 18349 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 06:04:23.239 18349 18349 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 06:04:27.365 18349 18507 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 06:04:27.365 18349 18507 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 06:04:27.365 18349 18507 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 07:13:30.975 30133 30133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 07:13:31.870 30133 30133 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 08:13:30.251 15839 15839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 08:13:30.706 15839 15839 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 08:18:30.317 16902 16902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 08:18:30.785 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.
--------- beginning of main
04-16 09:13:33.701 20547 20547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 09:13:34.947 20547 20547 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 09:13:37.965 20547 20682 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 09:13:37.965 20547 20682 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 09:13:37.965 20547 20682 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 10:35:17.114 15821 15821 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
--------- beginning of main
04-16 11:16:21.716 31705 31705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 11:16:22.258 31705 31705 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1126)
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1080)
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1003)
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.System.loadLibrary(System.java:1661)
04-16 11:16:22.263 31705 31705 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.Class.newInstance(Native Method)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-16 11:16:22.263 31705 31705 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7268)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.ActivityThread.access$1900(ActivityThread.java:291)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2301)
04-16 11:16:22.263 31705 31705 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-16 11:16:22.263 31705 31705 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
04-16 11:16:22.263 31705 31705 W System.err: at
android.os.Looper.loop(Looper.java:334)
04-16 11:16:22.263 31705 31705 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8501)
04-16 11:16:22.263 31705 31705 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-16 11:16:22.263 31705 31705 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
04-16 11:16:22.263 31705 31705 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
04-16 11:16:22.327 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
04-16 17:18:33.114 26556 26556 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 17:18:33.979 26556 26556 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 17:18:36.217 26556 26800 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 17:18:36.217 26556 26800 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 17:18:36.217 26556 26800 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 17:21:06.054 29060 29060 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 17:21:06.675 29060 29060 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 17:23:01.303 30319 30319 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 17:23:01.708 30319 30319 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 18:27:20.057 3610 3610 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:27:21.946 3610 3610 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 18:27:49.409 5285 5285 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:27:50.212 5285 5285 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 18:27:52.453 5285 5389 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 18:27:52.453 5285 5389 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 18:27:52.453 5285 5389 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 18:28:21.109 5863 5863 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:28:21.458 5863 5863 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 18:31:42.755 6989 6989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:31:43.061 6989 6989 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 18:42:03.510 14582 14582 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:42:04.757 14582 14582 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 18:42:06.688 14582 14682 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 18:42:06.688 14582 14682 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 18:42:06.688 14582 14682 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 19:27:06.645 10397 10397 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 19:27:07.539 10397 10397 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 20:13:08.756 19669 19669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 20:13:09.585 19669 19669 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 21:12:55.891 31299 31299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 21:12:56.488 31299 31299 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 21:22:12.426 14685 14685 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 21:22:13.782 14685 14685 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-16 21:22:16.826 14685 14923 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-16 21:22:16.826 14685 14923 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-16 21:22:16.826 14685 14923 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-16 21:23:42.756 19724 19724 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 21:23:43.877 19724 19724 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 22:12:57.780 3881 3881 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 22:12:58.475 3881 3881 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-16 23:35:13.875 25978 25978 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 23:35:14.665 25978 25978 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-17 00:17:14.610 29837 29837 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 00:17:15.315 29837 29837 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-17 00:22:14.147 30414 30414 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 00:22:14.755 30414 30414 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-17 01:17:16.368 3109 3109 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 01:17:17.154 3109 3109 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-17 01:29:41.989 5302 5302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 01:29:42.558 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
04-17 02:00:10.094 6695 6695 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 02:00:10.593 6695 6695 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-17 02:24:33.880 8066 8066 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 02:24:34.130 8066 8066 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 10:23:39.471 18034 18034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 10:23:40.206 18034 18034 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 10:23:41.964 18034 18110 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=ccf86de2-3bf3-4a6a-9fd9-459b8bfdb6b6, generation=0)
--------- beginning of main
04-18 10:28:30.364 19275 19275 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 10:28:30.924 19275 19275 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 10:31:55.356 20574 20574 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 10:31:55.952 20574 20574 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 12:13:56.113 19426 19426 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 12:13:56.694 19426 19426 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 12:14:48.056 19763 19763 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 12:14:48.613 19763 19763 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 12:36:14.396 27692 27692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 12:36:16.012 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.
04-18 12:36:18.244 27692 27868 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 12:36:18.244 27692 27868 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 12:36:18.244 27692 27868 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 13:00:19.433 6716 6716 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 13:00:20.325 6716 6716 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 13:13:17.127 11099 11099 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 13:13:18.586 11099 11099 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 13:13:20.633 11099 11161 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 13:13:20.633 11099 11161 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 13:13:20.633 11099 11161 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 14:13:13.405 10137 10137 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:13:14.384 10137 10137 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 14:13:16.470 10137 10351 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 14:13:16.470 10137 10351 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 14:13:16.470 10137 10351 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-18 14:17:27.474 11934 11934 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:17:29.024 11934 11934 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 14:17:30.906 11934 11934 W com.mbwhatsapp: type=1400 audit(0.0:6491376): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 14:17:31.010 11934 11934 W com.mbwhatsapp: type=1400 audit(0.0:6491377): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 14:17:31.010 11934 11934 W com.mbwhatsapp: type=1400 audit(0.0:6491378): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 14:17:31.010 11934 11934 W com.mbwhatsapp: type=1400 audit(0.0:6491379): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-18 14:45:18.593 27995 27995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:45:20.222 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.
04-18 14:45:24.426 27995 27995 W com.mbwhatsapp: type=1400 audit(0.0:6493472): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 14:45:24.590 27995 27995 W com.mbwhatsapp: type=1400 audit(0.0:6493473): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 14:45:24.590 27995 27995 W com.mbwhatsapp: type=1400 audit(0.0:6493474): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 14:45:24.590 27995 27995 W com.mbwhatsapp: type=1400 audit(0.0:6493475): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-18 14:45:45.455 28861 28861 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:45:47.017 28861 28861 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 15:20:01.521 16930 16930 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 15:20:02.896 16930 16930 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 18:46:04.270 5115 5115 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:46:07.710 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.
04-18 18:46:13.076 5115 5115 W com.mbwhatsapp: type=1400 audit(0.0:6546667): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 18:46:13.232 5115 5115 W com.mbwhatsapp: type=1400 audit(0.0:6546668): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 18:46:13.236 5115 5115 W com.mbwhatsapp: type=1400 audit(0.0:6546669): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 18:46:13.236 5115 5115 W com.mbwhatsapp: type=1400 audit(0.0:6546670): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-18 18:46:13.236 5115 5115 W com.mbwhatsapp: type=1400 audit(0.0:6546671): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-18 18:46:20.322 6008 6008 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:46:23.009 6008 6008 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 18:47:25.612 8706 8706 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:47:26.762 8706 8706 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 18:48:05.675 9500 9500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:48:08.395 9500 9500 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 18:51:00.679 14842 14842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:51:03.032 14842 14842 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 20:13:56.023 9003 9003 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:13:56.599 9003 9003 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 20:19:26.156 11669 11669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:19:26.737 11669 11669 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 20:20:04.919 13013 13013 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:20:06.067 13013 13013 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 20:20:08.296 13013 13317 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 20:20:08.296 13013 13317 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 20:20:08.296 13013 13317 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 20:24:22.575 15326 15326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:24:23.746 15326 15326 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 20:24:25.741 15326 15378 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 20:24:25.741 15326 15378 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 20:24:25.741 15326 15378 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 20:52:36.560 27473 27473 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:52:37.261 27473 27473 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-18 21:12:47.308 31985 31985 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 21:12:48.257 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.
04-18 21:12:51.043 31985 32037 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 21:12:51.043 31985 32037 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 21:12:51.043 31985 32037 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 22:13:56.230 19182 19182 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 22:13:56.920 19182 19182 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 22:13:58.525 19182 19282 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 22:13:58.525 19182 19282 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 22:13:58.525 19182 19282 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 23:13:18.356 9438 9438 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 23:13:18.795 9438 9438 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-18 23:13:20.087 9438 9486 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-18 23:13:20.087 9438 9486 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-18 23:13:20.087 9438 9486 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-18 23:36:28.404 13156 13156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 23:36:29.199 13156 13156 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-19 00:14:47.040 18919 18919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 00:14:47.582 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
04-19 00:41:10.753 22286 22286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 00:41:11.496 22286 22286 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-19 01:15:08.397 27911 27911 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 01:15:08.942 27911 27911 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-19 01:31:15.781 29754 29754 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 01:31:16.225 29754 29754 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-19 02:12:47.322 5256 5256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 02:12:47.939 5256 5256 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-19 17:27:05.052 12161 12161 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 17:27:08.555 12161 12161 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-19 17:27:17.860 12161 12161 W com.mbwhatsapp: type=1400 audit(0.0:6830516): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 17:27:17.900 12161 12161 W com.mbwhatsapp: type=1400 audit(0.0:6830517): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 17:27:17.944 12161 12161 W com.mbwhatsapp: type=1400 audit(0.0:6830518): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 17:27:18.448 12161 12161 W com.mbwhatsapp: type=1400 audit(0.0:6830521): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 17:27:18.596 12161 12161 W com.mbwhatsapp: type=1400 audit(0.0:6830522): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 17:27:18.596 12161 12161 W com.mbwhatsapp: type=1400 audit(0.0:6830523): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-19 17:27:36.974 12942 12942 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 17:27:39.230 12942 12942 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 08:39:50.160 22689 22689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 08:39:50.708 22689 22689 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-20 08:39:52.695 22689 22774 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=07d1eeba-84ff-40e3-a1c0-4fe80a26330f, generation=0)
--------- beginning of main
04-20 08:51:24.004 24435 24435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 08:51:24.764 24435 24435 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 08:51:28.229 24562 24562 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 08:51:28.595 24562 24562 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 09:05:01.898 25563 25563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 09:05:04.005 25563 25563 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 10:23:33.926 9366 9366 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 10:23:34.716 9366 9366 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-20 10:23:36.261 9366 9366 W com.mbwhatsapp: type=1400 audit(0.0:7043903): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-20 10:23:36.518 9366 9420 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-20 10:23:36.518 9366 9420 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-20 10:23:36.518 9366 9420 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-20 10:27:44.889 11081 11081 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 10:27:45.747 11081 11081 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 12:13:54.312 17231 17231 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 12:13:55.070 17231 17231 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-20 12:13:56.552 17231 17281 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-20 12:13:56.552 17231 17281 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-20 12:13:56.552 17231 17281 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-20 12:20:13.805 23081 23081 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 12:20:14.446 23081 23081 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-20 12:20:16.404 23081 23333 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-20 12:20:16.404 23081 23333 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-20 12:20:16.404 23081 23333 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-20 12:28:26.169 31702 31702 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 12:28:27.114 31702 31702 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 12:47:46.409 21864 21864 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 12:47:46.973 21864 21864 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 13:12:54.649 27890 27890 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 13:12:55.404 27890 27890 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 14:12:56.620 24207 24207 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 14:12:57.658 24207 24207 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-20 14:12:59.756 24207 24283 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-20 14:12:59.756 24207 24283 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-20 14:12:59.756 24207 24283 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-20 16:26:54.913 8082 8082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 16:26:56.045 8082 8082 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 18:12:56.932 14179 14179 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 18:12:57.693 14179 14179 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 19:13:16.470 32560 32560 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 19:13:17.451 32560 32560 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-20 19:13:19.563 32560 32691 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-20 19:13:19.563 32560 32691 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-20 19:13:19.563 32560 32691 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-20 20:12:47.235 25714 25714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 20:12:47.898 25714 25714 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 21:12:52.495 30820 30820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 21:12:53.193 30820 30820 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 21:49:31.865 22377 22377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 21:49:33.271 22377 22377 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-20 22:12:47.311 11839 11839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 22:12:47.959 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.
04-20 22:12:49.690 11839 11885 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-20 22:12:49.690 11839 11885 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-20 22:12:49.690 11839 11885 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-21 12:38:57.285 18829 18829 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 12:38:58.188 18829 18829 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 12:39:00.794 18829 18909 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-21 12:39:00.794 18829 18909 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-21 12:39:00.794 18829 18909 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-21 12:41:26.152 19615 19615 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 12:41:27.129 19615 19615 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 14:15:28.438 13314 13314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 14:15:28.904 13314 13314 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 14:16:08.105 13478 13478 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 14:16:11.193 13478 13478 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:00:09.107 12104 12104 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:00:10.523 12104 12104 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:00:56.527 14508 14508 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:00:57.936 14508 14508 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:01:12.923 15464 15464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:01:13.460 15464 15464 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:02:54.093 20743 20743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:02:59.813 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
04-21 16:03:23.855 21878 21878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:03:24.701 21878 21878 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:03:35.760 22531 22531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:03:36.487 22531 22531 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:03:43.347 23009 23009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:03:44.344 23009 23009 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:04:35.440 23504 23504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:04:36.079 23504 23504 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:05:47.177 25122 25122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:05:47.631 25122 25122 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:06:06.087 25510 25510 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:06:06.655 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.
--------- beginning of main
04-21 16:07:49.488 26502 26502 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:07:50.633 26502 26502 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:08:19.059 27127 27127 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:08:19.757 27127 27127 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 16:09:06.020 27343 27343 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 16:09:06.789 27343 27343 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:01:55.270 11368 11368 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:01:55.876 11368 11368 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:03:10.257 11632 11632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:03:10.556 11632 11632 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:06:57.159 12753 12753 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:06:58.594 12753 12753 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:07:16.863 13164 13164 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:07:17.456 13164 13164 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:08:12.090 13285 13285 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:08:12.439 13285 13285 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:09:48.982 14059 14059 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:09:49.821 14059 14059 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:11:28.661 14458 14458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:11:29.003 14458 14458 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 17:14:41.285 14972 14972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:14:43.529 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
04-21 18:02:00.569 27490 27490 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:02:01.093 27490 27490 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:03:15.564 27616 27616 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:03:15.909 27616 27616 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:06:57.115 31302 31302 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:06:58.084 31302 31302 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:07:33.072 31705 31705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:07:34.380 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
04-21 18:08:15.102 31916 31916 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:08:16.156 31916 31916 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:09:48.990 32747 32747 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:09:49.792 32747 32747 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 18:09:51.073 32747 32747 W com.mbwhatsapp: type=1400 audit(0.0:120774): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-21 18:11:28.780 2191 2191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:11:29.645 2191 2191 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:12:22.686 3255 3255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:12:23.430 3255 3255 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:13:14.284 3732 3732 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:13:15.136 3732 3732 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 18:14:41.919 4729 4729 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:14:43.646 4729 4729 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:02:00.540 18101 18101 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:02:01.297 18101 18101 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:03:15.624 18404 18404 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:03:16.946 18404 18404 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:06:57.010 19259 19259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:06:57.954 19259 19259 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:07:46.655 19705 19705 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:07:47.533 19705 19705 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:08:15.119 20034 20034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:08:16.052 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
04-21 19:09:48.999 20379 20379 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:09:49.820 20379 20379 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:11:28.699 20906 20906 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:11:30.152 20906 20906 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:12:22.648 21157 21157 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:12:23.238 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
04-21 19:13:14.285 21583 21583 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:13:14.696 21583 21583 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 19:14:41.203 21866 21866 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:14:42.136 21866 21866 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:02:00.579 3988 3988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:02:01.517 3988 3988 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:03:15.578 4634 4634 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:03:16.698 4634 4634 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 20:03:18.341 4634 4634 W com.mbwhatsapp: type=1400 audit(0.0:122436): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-21 20:06:57.971 9209 9209 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:06:58.867 9209 9209 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:07:46.620 9850 9850 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:07:47.230 9850 9850 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:08:41.623 10971 10971 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:08:44.513 10971 10971 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:10:06.038 11602 11602 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:10:07.688 11602 11602 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:11:28.679 13380 13380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:11:29.414 13380 13380 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 20:11:31.221 13380 13380 W com.mbwhatsapp: type=1400 audit(0.0:123266): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-21 20:11:31.233 13380 13380 W com.mbwhatsapp: type=1400 audit(0.0:123267): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-21 20:11:31.265 13380 13380 W com.mbwhatsapp: type=1400 audit(0.0:123268): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-21 20:12:22.672 14464 14464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:12:24.215 14464 14464 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:13:27.669 16043 16043 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:13:28.939 16043 16043 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 20:14:41.196 17547 17547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:14:41.962 17547 17547 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 21:02:00.553 19868 19868 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:02:01.367 19868 19868 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 21:03:15.560 20381 20381 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:03:16.592 20381 20381 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 21:06:57.039 23180 23180 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:06:58.127 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.
04-21 21:07:00.029 23180 23180 W com.mbwhatsapp: type=1400 audit(0.0:194458): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-21 21:07:46.641 23701 23701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:07:47.571 23701 23701 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 21:08:41.616 25404 25404 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:08:42.728 25404 25404 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 21:10:05.643 27266 27266 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:10:06.359 27266 27266 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 21:11:28.685 27873 27873 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:11:29.355 27873 27873 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-21 21:12:22.656 28303 28303 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:12:23.385 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.
--------- beginning of main
04-21 21:13:29.330 31097 31097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:13:30.497 31097 31097 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 21:13:32.341 31097 31097 W com.mbwhatsapp: type=1400 audit(0.0:195539): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-21 21:14:41.189 1375 1375 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:14:43.348 1375 1375 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:02:00.526 30142 30142 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:02:01.291 30142 30142 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:03:15.547 30804 30804 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:03:16.331 30804 30804 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:06:57.045 4356 4356 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:06:57.579 4356 4356 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 22:06:59.133 4356 4356 W com.mbwhatsapp: type=1400 audit(0.0:198267): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-21 22:06:59.133 4356 4356 W com.mbwhatsapp: type=1400 audit(0.0:198268): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-21 22:06:59.133 4356 4356 W com.mbwhatsapp: type=1400 audit(0.0:198269): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-21 22:06:59.133 4356 4356 W com.mbwhatsapp: type=1400 audit(0.0:198270): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-21 22:07:46.630 6326 6326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:07:47.667 6326 6326 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:08:41.628 7071 7071 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:08:42.495 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.
--------- beginning of main
04-21 22:10:05.639 8507 8507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:10:06.654 8507 8507 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:11:28.711 9135 9135 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:11:29.781 9135 9135 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:12:28.443 9870 9870 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:12:29.245 9870 9870 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:13:27.401 11167 11167 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:13:28.404 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
04-21 22:14:41.214 12371 12371 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:14:42.160 12371 12371 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:48:12.513 27455 27455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:48:14.938 27455 27455 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:49:06.135 29481 29481 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:49:06.998 29481 29481 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:49:46.577 31087 31087 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:49:47.313 31087 31087 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:50:34.671 3519 3519 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:50:35.444 3519 3519 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 22:51:30.052 4628 4628 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:51:31.247 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.
--------- beginning of main
04-21 22:52:26.281 5144 5144 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:52:26.744 5144 5144 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:53:06.023 5423 5423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:53:06.428 5423 5423 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:54:06.073 6076 6076 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:54:06.431 6076 6076 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:55:48.588 6805 6805 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:55:49.246 6805 6805 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:56:06.062 7159 7159 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:56:06.569 7159 7159 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:57:06.054 7581 7581 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:57:06.501 7581 7581 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 22:58:27.445 7913 7913 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:58:27.875 7913 7913 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-21 22:59:07.990 8500 8500 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:59:08.709 8500 8500 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-21 23:00:36.462 8886 8886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:00:37.167 8886 8886 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:01:06.045 9309 9309 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:01:06.464 9309 9309 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:02:06.068 9984 9984 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:02:09.561 9984 9984 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:03:06.154 11320 11320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:03:07.026 11320 11320 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:04:06.034 11650 11650 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:04:06.989 11650 11650 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:05:17.925 12801 12801 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:05:18.607 12801 12801 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:06:10.550 14218 14218 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:06:12.875 14218 14218 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:07:06.481 14894 14894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:07:08.974 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
04-21 23:08:06.083 15665 15665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:08:06.859 15665 15665 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:09:06.059 16147 16147 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:09:06.797 16147 16147 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:10:40.867 16429 16429 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:10:41.287 16429 16429 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:14:14.546 17161 17161 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:14:14.967 17161 17161 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:15:06.071 18009 18009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:15:06.567 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.
--------- beginning of main
04-21 23:21:10.486 19127 19127 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:21:10.981 19127 19127 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:27:06.063 20305 20305 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:27:06.454 20305 20305 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-21 23:33:06.043 22101 22101 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 23:33:06.546 22101 22101 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 13:06:29.603 30707 30707 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:06:30.512 30707 30707 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-22 13:06:32.233 30707 30707 W com.mbwhatsapp: type=1400 audit(0.0:53188): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 13:06:32.277 30707 30707 W com.mbwhatsapp: type=1400 audit(0.0:53189): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 13:06:32.277 30707 30707 W com.mbwhatsapp: type=1400 audit(0.0:53190): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 13:06:32.277 30707 30707 W com.mbwhatsapp: type=1400 audit(0.0:53191): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 13:06:32.277 30707 30707 W com.mbwhatsapp: type=1400 audit(0.0:53192): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-22 13:15:56.477 3673 3673 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:15:57.244 3673 3673 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 14:03:33.092 15650 15650 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:03:34.013 15650 15650 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-22 14:03:35.801 15650 15650 W com.mbwhatsapp: type=1400 audit(0.0:54612): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 14:03:35.833 15650 15650 W com.mbwhatsapp: type=1400 audit(0.0:54613): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-22 15:19:34.979 32585 32585 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 15:19:35.620 32585 32585 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 16:18:01.199 9937 9937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 16:18:02.043 9937 9937 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 16:21:10.736 12471 12471 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 16:21:11.269 12471 12471 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 17:03:46.156 6570 6570 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 17:03:46.900 6570 6570 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-22 17:03:48.583 6570 6570 W com.mbwhatsapp: type=1400 audit(0.0:61044): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 17:03:48.583 6570 6570 W com.mbwhatsapp: type=1400 audit(0.0:61045): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 17:03:48.591 6570 6570 W com.mbwhatsapp: type=1400 audit(0.0:61046): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-22 17:03:48.595 6570 6570 W com.mbwhatsapp: type=1400 audit(0.0:61047): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-22 18:03:39.740 7316 7316 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 18:03:40.439 7316 7316 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 18:07:09.140 8074 8074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 18:07:09.750 8074 8074 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 19:04:07.402 15018 15018 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 19:04:08.047 15018 15018 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 19:14:56.986 17172 17172 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 19:14:57.802 17172 17172 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 20:03:48.606 23547 23547 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 20:03:49.345 23547 23547 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 20:06:00.846 26286 26286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 20:06:01.624 26286 26286 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 20:09:46.325 27886 27886 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 20:09:46.979 27886 27886 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 21:04:15.936 25664 25664 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 21:04:16.963 25664 25664 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 21:09:02.839 30336 30336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 21:09:03.448 30336 30336 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 21:18:39.444 4146 4146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 21:18:40.043 4146 4146 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 21:42:57.242 13121 13121 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 21:42:58.021 13121 13121 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-22 22:32:36.210 2017 2017 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 22:32:37.130 2017 2017 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-22 22:32:38.990 2017 2017 W com.mbwhatsapp: type=1400 audit(0.0:132194): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-22 23:08:54.225 10155 10155 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 23:08:55.249 10155 10155 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 00:11:35.990 28658 28658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 00:11:36.625 28658 28658 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 01:20:14.999 31871 31871 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 01:20:15.746 31871 31871 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 01:24:21.608 5714 5714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 01:24:22.119 5714 5714 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 01:30:14.494 8639 8639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 01:30:15.345 8639 8639 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-23 02:04:20.185 19927 19927 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 02:04:20.794 19927 19927 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 02:24:44.928 24361 24361 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 02:24:45.594 24361 24361 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 03:04:46.117 30046 30046 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 03:04:46.638 30046 30046 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 03:12:22.158 31645 31645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 03:12:22.467 31645 31645 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 04:04:47.486 10592 10592 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 04:04:47.908 10592 10592 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 05:04:50.937 19714 19714 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 05:04:51.994 19714 19714 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 05:26:59.222 22839 22839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 05:26:59.799 22839 22839 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 06:04:15.934 31058 31058 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 06:04:16.795 31058 31058 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 06:10:13.546 2401 2401 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 06:10:14.037 2401 2401 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 10:14:06.932 14778 14778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 10:14:07.614 14778 14778 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 11:59:52.476 27226 27226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 11:59:53.239 27226 27226 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 12:50:00.798 5909 5909 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 12:50:02.287 5909 5909 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 12:54:11.847 10798 10798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 12:54:12.938 10798 10798 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-23 12:54:14.638 10798 10798 W com.mbwhatsapp: type=1400 audit(0.0:148416): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-23 12:54:14.650 10798 10798 W com.mbwhatsapp: type=1400 audit(0.0:148419): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-23 12:54:14.662 10798 10798 W com.mbwhatsapp: type=1400 audit(0.0:148420): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-23 12:56:29.528 12216 12216 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 12:56:31.206 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
04-23 12:59:58.594 13745 13745 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 13:00:00.170 13745 13745 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 13:12:04.005 16421 16421 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 13:12:04.760 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
04-23 14:39:53.149 27897 27897 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 14:39:54.928 27897 27897 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-23 14:39:54.934 27897 27897 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-23 14:39:54.935 27897 27897 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1126)
04-23 14:39:54.935 27897 27897 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1080)
04-23 14:39:54.935 27897 27897 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1003)
04-23 14:39:54.935 27897 27897 W System.err: at
java.lang.System.loadLibrary(System.java:1661)
04-23 14:39:54.935 27897 27897 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-23 14:39:54.935 27897 27897 W System.err: at
java.lang.Class.newInstance(Native Method)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-23 14:39:54.935 27897 27897 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1227)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1384)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7268)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.ActivityThread.access$1900(ActivityThread.java:291)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2301)
04-23 14:39:54.935 27897 27897 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-23 14:39:54.935 27897 27897 W System.err: at
android.os.Looper.loopOnce(Looper.java:233)
04-23 14:39:54.935 27897 27897 W System.err: at
android.os.Looper.loop(Looper.java:334)
04-23 14:39:54.935 27897 27897 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8501)
04-23 14:39:54.935 27897 27897 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-23 14:39:54.935 27897 27897 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
04-23 14:39:54.935 27897 27897 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)
04-23 14:39:55.347 27897 27897 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-23 14:39:59.888 27897 27897 W com.mbwhatsapp: type=1400 audit(0.0:152434): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-23 14:42:53.040 32361 32361 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 14:42:54.063 32361 32361 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 14:54:51.224 10528 10528 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 14:54:52.392 10528 10528 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 16:03:36.428 19703 19703 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:03:37.164 19703 19703 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 16:05:46.819 21054 21054 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:05:47.844 21054 21054 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 16:09:00.610 23320 23320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:09:02.509 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
04-23 16:16:51.029 26961 26961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:16:52.056 26961 26961 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 17:06:36.168 10887 10887 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 17:06:36.768 10887 10887 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 18:03:27.194 32668 32668 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 18:03:27.780 32668 32668 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 19:04:10.464 17419 17419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 19:04:11.157 17419 17419 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 21:04:15.750 29501 29501 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 21:04:16.461 29501 29501 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 22:04:17.615 18019 18019 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 22:04:18.875 18019 18019 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-23 23:28:11.608 20559 20559 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 23:28:12.456 20559 20559 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 00:53:27.888 29171 29171 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 00:53:29.184 29171 29171 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 00:53:30.593 29171 29171 W com.mbwhatsapp: type=1400 audit(0.0:404248): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 00:53:30.649 29171 29171 W com.mbwhatsapp: type=1400 audit(0.0:404249): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 00:53:30.649 29171 29171 W com.mbwhatsapp: type=1400 audit(0.0:404250): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 00:53:30.649 29171 29171 W com.mbwhatsapp: type=1400 audit(0.0:404251): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 00:53:30.649 29171 29171 W com.mbwhatsapp: type=1400 audit(0.0:404252): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-24 02:54:56.943 7648 7648 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 02:54:58.100 7648 7648 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 02:55:03.212 7648 7966 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=b33e408e-3faf-4b45-894b-5907fe867393, generation=0)
04-24 02:55:03.229 7648 7966 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=b33e408e-3faf-4b45-894b-5907fe867393, generation=0)
--------- beginning of main
04-24 04:15:07.184 17417 17417 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 04:15:07.923 17417 17417 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 05:25:54.551 22369 22369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 05:25:55.452 22369 22369 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 05:52:44.337 27907 27907 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 05:52:46.459 27907 27907 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 06:05:55.879 30133 30133 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 06:05:56.688 30133 30133 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 06:28:46.364 8158 8158 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 06:28:46.827 8158 8158 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 06:28:49.977 8158 8158 W com.mbwhatsapp: type=1400 audit(0.0:408076): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 06:28:50.093 8158 8158 W com.mbwhatsapp: type=1400 audit(0.0:408077): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 06:28:50.093 8158 8158 W com.mbwhatsapp: type=1400 audit(0.0:408078): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 06:28:50.093 8158 8158 W com.mbwhatsapp: type=1400 audit(0.0:408079): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-24 06:39:04.670 19404 19404 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 06:39:05.439 19404 19404 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 07:04:34.381 24331 24331 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 07:04:35.069 24331 24331 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 07:25:25.459 27939 27939 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 07:25:27.296 27939 27939 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 07:31:59.237 30080 30080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 07:31:59.832 30080 30080 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 09:57:58.520 18531 18531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 09:57:59.090 18531 18531 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 09:58:00.450 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416419): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 09:58:00.378 18531 18531 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-24 09:58:00.458 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416420): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 09:58:00.378 18531 18531 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
04-24 09:58:00.474 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416421): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 09:58:00.594 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416422): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 09:58:00.662 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416423): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 09:58:00.662 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416424): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 09:58:00.662 18531 18531 W com.mbwhatsapp: type=1400 audit(0.0:416425): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-24 09:58:57.061 19776 19776 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 09:58:57.585 19776 19776 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 10:47:19.334 30266 30266 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 10:47:20.138 30266 30266 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 12:16:36.846 13773 13773 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:16:40.204 13773 13773 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 12:16:45.497 13773 13773 W com.mbwhatsapp: type=1400 audit(0.0:420868): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-24 12:42:08.928 19834 19834 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:42:10.521 19834 19834 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 12:44:24.216 21228 21228 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:44:24.690 21228 21228 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 12:45:04.146 21849 21849 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:45:04.624 21849 21849 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 12:48:49.615 23861 23861 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:48:50.691 23861 23861 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 12:52:06.261 25922 25922 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:52:06.877 25922 25922 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 12:59:46.769 31000 31000 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 12:59:47.674 31000 31000 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 16:43:18.682 20646 20646 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 16:43:20.512 20646 20646 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 16:43:25.217 20646 20646 W com.mbwhatsapp: type=1400 audit(0.0:455104): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 16:43:25.257 20646 20646 W com.mbwhatsapp: type=1400 audit(0.0:455105): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 16:43:25.257 20646 20646 W com.mbwhatsapp: type=1400 audit(0.0:455106): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 16:43:25.257 20646 20646 W com.mbwhatsapp: type=1400 audit(0.0:455107): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-24 17:01:55.804 25496 25496 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 17:01:57.222 25496 25496 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 18:04:19.669 14778 14778 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 18:04:20.714 14778 14778 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-24 18:04:22.621 14778 14778 W com.mbwhatsapp: type=1400 audit(0.0:458658): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-24 18:04:22.709 14778 14778 W com.mbwhatsapp: type=1400 audit(0.0:458659): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-24 18:07:11.509 17811 17811 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 18:07:13.614 17811 17811 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 19:05:39.155 20482 20482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 19:05:40.250 20482 20482 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 20:18:21.067 16080 16080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 20:18:21.769 16080 16080 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 20:36:41.265 18820 18820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 20:36:41.990 18820 18820 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 21:52:41.356 30709 30709 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 21:52:42.278 30709 30709 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-24 23:53:45.913 12750 12750 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 23:53:47.081 12750 12750 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 03:56:44.829 4721 4721 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 03:56:46.765 4721 4721 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-25 03:56:48.967 4721 4721 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-25 03:56:48.968 4721 4721 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
04-25 03:56:49.137 4721 4721 W com.mbwhatsapp: type=1400 audit(0.0:470662): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 03:56:49.161 4721 4721 W com.mbwhatsapp: type=1400 audit(0.0:470663): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023147 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 03:56:49.213 4721 4721 W com.mbwhatsapp: type=1400 audit(0.0:470664): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 03:56:49.449 4721 4721 W com.mbwhatsapp: type=1400 audit(0.0:470665): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-25 03:56:50.893 4721 5080 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=7cce56ce-86fe-47c1-a921-6ed382ae59d2, generation=0)
04-25 03:56:50.916 4721 5080 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=7cce56ce-86fe-47c1-a921-6ed382ae59d2, generation=0)
--------- beginning of main
04-25 05:39:03.205 12779 12779 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 05:39:05.100 12779 12779 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-25 05:40:58.521 15525 15525 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 05:40:59.210 15525 15525 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 05:52:58.711 17650 17650 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 05:52:59.400 17650 17650 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 06:04:41.169 23282 23282 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 06:04:41.874 23282 23282 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 07:03:28.354 13271 13271 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 07:15:00.864 16415 16415 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 07:15:01.735 16415 16415 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 09:23:26.174 32464 32464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 09:23:26.865 32464 32464 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 11:30:23.442 19803 19803 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 11:30:24.245 19803 19803 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 11:47:07.111 23706 23706 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 11:47:08.072 23706 23706 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 15:05:38.240 29994 29994 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 15:05:41.421 29994 29994 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-25 15:05:47.828 29994 29994 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
04-25 15:05:47.829 29994 29994 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
04-25 15:06:20.809 32178 32178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 15:06:22.539 32178 32178 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 15:07:33.304 5002 5002 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 15:07:34.619 5002 5002 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 15:14:01.220 11489 11489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 15:14:02.265 11489 11489 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 17:20:02.153 20335 20335 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 17:20:03.341 20335 20335 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 17:22:03.071 28069 28069 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 17:22:04.949 28069 28069 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 17:44:52.128 31992 31992 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 17:44:54.176 31992 31992 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 17:51:52.147 8817 8817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 17:51:53.677 8817 8817 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 19:22:11.912 15242 15242 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 19:22:13.897 15242 15242 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 19:24:07.549 19937 19937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 19:24:08.811 19937 19937 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 19:27:17.635 23659 23659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 19:27:18.761 23659 23659 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 19:34:06.916 26887 26887 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 19:34:08.019 26887 26887 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 19:45:25.358 30708 30708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 19:45:26.484 30708 30708 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 19:50:50.511 2746 2746 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 19:50:52.077 2746 2746 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 20:03:52.603 8222 8222 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 20:03:53.408 8222 8222 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 21:23:08.089 31752 31752 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 21:23:09.138 31752 31752 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 21:33:27.306 6051 6051 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 21:33:28.258 6051 6051 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 22:05:21.034 23273 23273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 22:05:22.054 23273 23273 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-25 22:05:23.669 23273 23273 W com.mbwhatsapp: type=1400 audit(0.0:592653): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:05:23.741 23273 23273 W com.mbwhatsapp: type=1400 audit(0.0:592654): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:05:23.741 23273 23273 W com.mbwhatsapp: type=1400 audit(0.0:592655): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:05:23.741 23273 23273 W com.mbwhatsapp: type=1400 audit(0.0:592656): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:05:23.741 23273 23273 W com.mbwhatsapp: type=1400 audit(0.0:592657): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
--------- beginning of main
04-25 22:25:40.826 29322 29322 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 22:25:41.533 29322 29322 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 22:45:57.218 9924 9924 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 22:45:59.920 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.
04-25 22:46:02.517 9924 9924 W com.mbwhatsapp: type=1400 audit(0.0:593111): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-10" ino=3023302 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:46:02.585 9924 9924 W com.mbwhatsapp: type=1400 audit(0.0:593113): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:46:02.717 9924 9924 W com.mbwhatsapp: type=1400 audit(0.0:593114): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023152 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:46:02.789 9924 9924 W com.mbwhatsapp: type=1400 audit(0.0:593115): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:46:02.789 9924 9924 W com.mbwhatsapp: type=1400 audit(0.0:593116): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:46:02.789 9924 9924 W com.mbwhatsapp: type=1400 audit(0.0:593117): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023149 scontext=u:r:untrusted_app:s0:c219,c256,c512,c768
tcontext=u:object_r:app_data_file:s0:c219,c256,c512,c768 tclass=file
app=com.mbwhatsapp
04-25 22:46:03.582 9924 10042 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-25 22:46:03.582 9924 10042 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-25 22:46:03.582 9924 10042 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-25 22:47:19.706 12022 12022 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 22:47:20.705 12022 12022 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 23:03:52.563 21226 21226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 23:03:53.427 21226 21226 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-25 23:08:32.923 22457 22457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-25 23:08:33.339 22457 22457 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 00:04:23.378 30822 30822 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 00:04:23.928 30822 30822 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 00:34:37.122 3874 3874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 00:34:37.769 3874 3874 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 00:58:42.844 8290 8290 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 00:58:43.678 8290 8290 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 01:03:37.929 9546 9546 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 01:03:38.276 9546 9546 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 01:13:03.694 10273 10273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 01:13:04.008 10273 10273 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 01:32:12.069 13463 13463 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 01:32:13.032 13463 13463 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 01:44:39.497 14946 14946 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 01:44:39.913 14946 14946 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 02:04:42.019 18064 18064 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 02:04:42.346 18064 18064 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 02:24:43.225 21056 21056 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 02:24:43.673 21056 21056 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 02:39:55.834 23701 23701 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 02:39:56.433 23701 23701 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 02:49:44.102 24954 24954 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 02:49:44.724 24954 24954 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 03:04:45.820 27394 27394 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 03:04:46.293 27394 27394 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 03:29:47.173 30080 30080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 03:29:47.584 30080 30080 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 03:59:50.685 3747 3747 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 03:59:51.940 3747 3747 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 04:04:51.047 4391 4391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 04:04:51.397 4391 4391 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 04:29:53.743 7232 7232 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 04:29:54.239 7232 7232 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 05:04:50.763 11390 11390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 05:04:51.274 11390 11390 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 05:09:58.228 12458 12458 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 05:09:58.630 12458 12458 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 06:03:43.171 20061 20061 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 06:03:44.280 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
04-26 06:40:08.864 12912 12912 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 06:40:09.787 12912 12912 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 07:41:15.047 29438 29438 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 07:41:15.737 29438 29438 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 07:52:30.861 31360 31360 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 07:52:31.583 31360 31360 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 13:45:35.973 3665 3665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 13:45:37.523 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.
04-26 13:45:38.681 3749 3749 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 13:45:38.945 3749 3749 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-26 13:45:45.132 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:46.225 3749 3749 E ArmVmp : Match on catch block at 0x0a in for
0x73529b904d
04-26 13:45:46.667 3749 4165 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-26 13:45:47.619 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.621 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.622 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.622 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.623 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.624 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.628 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:47.629 3749 3749 E com.mbwhatsapp: Invalid ID 0x00000000.
04-26 13:45:54.864 3749 4007 E OpenGLRenderer: fbcNotifyFrameComplete error:
undefined symbol: fbcNotifyFrameComplete
04-26 13:45:54.864 3749 4007 E OpenGLRenderer: fbcNotifyNoRender error: undefined
symbol: fbcNotifyNoRender
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: Failed to load saved
values from file
/data/user/0/com.mbwhatsapp/files/ShortcutInfoCompatSaver_share_targets/
targets.xml. Old state removed, new added
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver:
java.io.FileNotFoundException:
/data/user/0/com.mbwhatsapp/files/ShortcutInfoCompatSaver_share_targets/
targets.xml: open failed: ENOENT (No such file or directory)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
libcore.io.IoBridge.open(IoBridge.java:574)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
java.io.FileInputStream.<init>(FileInputStream.java:160)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at X.0nz.run(Unknown
Source:82)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
java.util.concurrent.FutureTask.run(FutureTask.java:264)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
java.lang.Thread.run(Thread.java:1012)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: Caused by:
android.system.ErrnoException: open failed: ENOENT (No such file or directory)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
libcore.io.Linux.open(Native Method)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
libcore.io.ForwardingOs.open(ForwardingOs.java:563)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
libcore.io.ForwardingOs.open(ForwardingOs.java:563)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8374)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: at
libcore.io.IoBridge.open(IoBridge.java:560)
04-26 13:45:58.745 3749 4776 E ShortcutInfoCompatSaver: ... 7 more
04-26 13:45:58.898 3749 4007 E FrameEvents: updateAcquireFence: Did not find
frame.
04-26 13:45:58.953 3749 4007 E FrameEvents: updateAcquireFence: Did not find
frame.
04-26 13:45:58.977 3749 4007 E FrameEvents: updateAcquireFence: Did not find
frame.
04-26 13:46:09.086 3749 3958 E PlayCore: UID: [10379] PID: [3749]
StandardIntegrity : Phonesky is not installed.
04-26 13:46:36.519 5335 5335 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 13:46:36.897 5335 5335 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-26 13:46:38.485 5335 5402 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-26 13:46:38.485 5335 5402 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-26 13:46:38.485 5335 5402 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-26 14:34:32.256 21598 21598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 14:34:34.333 21598 21598 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 17:41:00.570 21091 21091 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 17:41:01.121 21091 21091 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-26 17:47:20.586 23950 23950 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-26 17:47:20.926 23950 23950 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-27 02:00:38.657 29129 29129 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-27 02:00:39.562 29129 29129 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-27 02:00:42.830 29129 29556 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-27 02:00:42.830 29129 29556 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-27 02:00:42.830 29129 29556 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-27 05:41:12.337 9961 9961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-27 05:41:12.939 9961 9961 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-27 05:59:03.966 13611 13611 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-27 05:59:04.409 13611 13611 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-27 17:41:59.385 31093 31093 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-27 17:42:00.404 31093 31093 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-27 17:42:03.368 31093 31402 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-27 17:42:03.368 31093 31402 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-27 17:42:03.368 31093 31402 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-27 18:00:09.643 7013 7013 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-27 18:00:10.289 7013 7013 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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-27 18:06:29.866 7658 7658 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-27 18:06:30.394 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.
--------- beginning of main
04-28 02:00:01.658 16626 16626 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 02:00:02.148 16626 16626 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 02:00:07.802 16762 16762 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 02:00:12.618 16762 16762 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 05:59:10.124 9766 9766 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 05:59:10.645 9766 9766 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 05:59:12.126 9766 9766 W com.mbwhatsapp: type=1400 audit(0.0:1269161): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023030 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 05:59:12.166 9766 9766 W com.mbwhatsapp: type=1400 audit(0.0:1269162): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 05:59:12.166 9766 9766 W com.mbwhatsapp: type=1400 audit(0.0:1269163): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 05:59:12.166 9766 9766 W com.mbwhatsapp: type=1400 audit(0.0:1269164): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-28 05:59:12.166 9766 9766 W com.mbwhatsapp: type=1400 audit(0.0:1269165): avc:
denied { execmod } for path="/apex/com.android.runtime/lib64/bionic/libc.so"
dev="loop17" ino=38 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:system_lib_file:s0 tclass=file permissive=0 app=com.mbwhatsapp
04-28 05:59:12.435 9766 9941 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-28 05:59:12.435 9766 9941 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-28 05:59:12.435 9766 9941 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-28 06:02:24.663 9992 9992 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 06:02:25.160 9992 9992 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 06:47:39.496 14130 14130 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 06:47:40.210 14130 14130 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 06:47:41.573 14130 14223 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-28 06:47:41.573 14130 14223 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-28 06:47:41.573 14130 14223 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-28 22:43:36.495 13253 13253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-28 22:43:37.031 13253 13253 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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 00:00:08.996 32454 32454 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 00:00:10.118 32454 32454 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 00:00:12.345 32454 32654 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-29 00:00:12.345 32454 32654 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-29 00:00:12.345 32454 32654 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-29 02:00:00.136 10768 10768 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 02:00:00.618 10768 10768 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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:13:03.841 13226 13226 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-29 18:13:05.032 13226 13226 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 18:13:07.974 13226 13503 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
04-29 18:13:07.974 13226 13503 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-29 18:13:07.974 13226 13503 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
04-30 02:00:38.625 18353 18353 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-30 02:00:39.255 18353 18353 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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 15:39:39.114 23887 23887 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-30 15:39:39.634 23887 23887 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If 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 17:40:43.660 21930 21930 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-30 17:40:46.089 21930 21930 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-30 17:40:50.832 21930 21930 W com.mbwhatsapp: type=1400 audit(0.0:2092710): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
10" ino=3023008 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-30 17:40:50.900 21930 21930 W com.mbwhatsapp: type=1400 audit(0.0:2092711): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-30 17:40:51.216 21930 21930 W com.mbwhatsapp: type=1400 audit(0.0:2092712): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-10" ino=3023030 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
04-30 17:40:51.320 21930 21930 W com.mbwhatsapp: type=1400 audit(0.0:2092713): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-10" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-08 21:30:26.771 30091 30091 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-08 21:30:27.854 30091 30091 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:30:30.592 30091 30162 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
05-08 21:30:30.592 30091 30162 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-08 21:30:30.592 30091 30162 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-09 02:00:00.098 9558 9558 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 02:00:00.621 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
05-09 02:33:34.783 19917 19917 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 02:33:35.281 19917 19917 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31:37.738 12931 12931 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 09:31:38.429 12931 12931 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 09:31:41.208 12931 13155 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
05-09 09:31:41.208 12931 13155 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-09 09:31:41.208 12931 13155 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-09 09:36:33.983 14618 14618 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 09:36:34.820 14618 14618 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:30:31.535 20815 20815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 21:30:32.265 20815 20815 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 21:30:39.102 21245 21245 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 21:30:40.612 21245 21245 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:30:45.612 21495 21495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-09 21:30:45.996 21495 21495 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:00:38.653 12015 12015 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 02:00:39.077 12015 12015 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:35:13.323 17306 17306 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-10 02:35:14.809 17306 17306 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 02:00:26.285 14986 14986 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 02:00:26.893 14986 14986 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:51:03.626 19471 19471 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 05:51:04.129 19471 19471 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
05-11 09:12:41.028 10128 10128 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 09:12:41.612 10128 10128 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 09:12:43.171 10128 10299 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
05-11 09:12:43.171 10128 10299 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-11 09:12:43.171 10128 10299 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-11 09:33:48.006 24205 24205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 09:33:48.691 24205 24205 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:07:49.455 28341 28341 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 10:07:50.399 28341 28341 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:30:32.045 28543 28543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 15:30:33.164 28543 28543 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:56:45.452 28793 28793 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 16:56:45.931 28793 28793 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:31:53.686 7342 7342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-11 21:31:54.522 7342 7342 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:00:37.878 16845 16845 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 02:00:38.399 16845 16845 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31:00.967 11389 11389 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:31:02.691 11389 11389 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:32:05.596 14633 14633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:32:06.157 14633 14633 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 06:32:07.044 14633 14633 W com.mbwhatsapp: type=1400 audit(0.0:1358): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
11" ino=3023008 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-12 06:32:45.834 16530 16530 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:32:47.001 16530 16530 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:34:38.325 17648 17648 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:34:38.683 17648 17648 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:10.469 19626 19626 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:40:11.210 19626 19626 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:41:10.471 20409 20409 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:41:11.115 20409 20409 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:42:51.425 21510 21510 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:42:51.797 21510 21510 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:44:54.097 22659 22659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:44:55.371 22659 22659 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:45:21.772 23120 23120 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:45:22.438 23120 23120 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:46:10.986 23981 23981 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:46:12.081 23981 23981 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:47:10.467 24235 24235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:47:11.386 24235 24235 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:48:51.392 24748 24748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:48:52.379 24748 24748 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:49:10.441 24890 24890 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:49:11.053 24890 24890 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:50:10.440 25306 25306 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:50:10.955 25306 25306 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:52:10.456 26067 26067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:52:10.749 26067 26067 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:54:10.494 26504 26504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:54:10.886 26504 26504 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:55:10.442 26954 26954 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:55:11.072 26954 26954 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:56:10.420 27207 27207 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 06:56:11.526 27207 27207 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:00:16.662 28348 28348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:00:17.407 28348 28348 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:03:10.497 29474 29474 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:03:10.977 29474 29474 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:04:10.459 29633 29633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:04:11.034 29633 29633 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:05:10.465 30256 30256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:05:11.201 30256 30256 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:06:10.465 30443 30443 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:06:11.382 30443 30443 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:07:10.454 30685 30685 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:07:10.756 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.
--------- beginning of main
05-12 07:08:10.456 30815 30815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:08:10.724 30815 30815 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:09:31.771 31453 31453 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:09:32.511 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
05-12 07:10:18.997 31995 31995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:10:20.117 31995 31995 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:11:10.461 32374 32374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:11:10.982 32374 32374 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:13:38.523 807 807 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:13:39.240 807 807 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:15:10.464 2616 2616 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:15:11.026 2616 2616 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:18:10.450 3895 3895 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:18:10.839 3895 3895 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 07:18:11.915 3895 3942 W com.mbwhatsapp: Method void
X.2rL.A03(java.lang.Integer) failed lock verification and will run slower.
05-12 07:18:11.915 3895 3942 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
05-12 07:18:11.915 3895 3942 W com.mbwhatsapp: and incorrect proguard
optimizations.
--------- beginning of main
05-12 07:19:10.447 4083 4083 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:19:10.737 4083 4083 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:20:10.443 4678 4678 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:20:10.709 4678 4678 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:21:10.455 5604 5604 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:21:11.203 5604 5604 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:22:10.487 6215 6215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:22:11.274 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
05-12 07:23:10.446 6681 6681 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:23:10.916 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.
--------- beginning of main
05-12 07:24:11.418 7024 7024 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:24:12.061 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.
--------- beginning of main
05-12 07:25:10.440 7666 7666 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:25:11.102 7666 7666 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:26:10.462 7961 7961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:26:10.934 7961 7961 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:30:10.445 9170 9170 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:30:11.112 9170 9170 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:31:14.620 10180 10180 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:31:15.383 10180 10180 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:32:36.288 11127 11127 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:32:39.665 11127 11127 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:33:10.574 11429 11429 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:33:11.641 11429 11429 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:34:10.465 11789 11789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:34:11.439 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.
--------- beginning of main
05-12 07:35:10.447 12148 12148 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:35:10.784 12148 12148 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:37:07.484 13639 13639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:37:07.976 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
05-12 07:39:12.345 14878 14878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-12 07:39:15.649 14878 14878 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:33:55.563 19331 19331 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-22 19:33:56.076 19331 19331 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:56:27.470 32421 32421 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-26 07:56:28.291 32421 32421 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:27:00.319 7178 7178 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 01:27:09.902 7178 7178 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:29:51.242 13873 13873 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 01:29:52.925 13873 13873 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:30:46.129 16235 16235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 01:30:49.316 16235 16235 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:31:58.981 18877 18877 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 01:32:02.976 18877 18877 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:37:43.266 21002 21002 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 01:37:43.635 21002 21002 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:52:40.510 28645 28645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 01:52:41.335 28645 28645 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 02:31:11.567 7220 7220 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 02:31:12.873 7220 7220 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 02:33:09.374 7741 7741 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 02:33:09.935 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-28 02:37:43.251 8549 8549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 02:37:43.521 8549 8549 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 02:39:59.652 9150 9150 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 02:39:59.939 9150 9150 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 02:40:00.369 9150 9150 W com.mbwhatsapp: type=1400 audit(0.0:4287): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-11" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-28 03:31:12.188 14761 14761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 03:31:13.069 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
05-28 03:33:27.028 15374 15374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 03:33:27.327 15374 15374 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 03:33:27.818 15374 15374 W com.mbwhatsapp: type=1400 audit(0.0:4668): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-11" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-28 03:34:34.197 15833 15833 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 03:34:34.489 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
05-28 04:31:13.262 22488 22488 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 04:31:14.034 22488 22488 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:32:16.310 24598 24598 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 04:32:17.238 24598 24598 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 04:32:21.053 24598 24598 W com.mbwhatsapp: type=1400 audit(0.0:7130): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
11" ino=3023008 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
05-28 04:32:21.073 24598 24598 W com.mbwhatsapp: type=1400 audit(0.0:7131): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-11" ino=3023029 scontext=u:r:untrusted_app:s0:c124,c257,c512,c768
tcontext=u:object_r:app_data_file:s0:c124,c257,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
05-28 04:33:38.378 25497 25497 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 04:33:39.282 25497 25497 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 04:33:41.128 25497 25497 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (max-
target-q,core-platform-api, reflection, denied)
05-28 04:33:41.128 25497 25497 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V (max-
target-q, reflection, denied)
--------- beginning of main
05-28 04:35:34.220 26314 26314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 04:35:34.819 26314 26314 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:31:13.247 450 450 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 05:31:14.377 450 450 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:32:05.937 2798 2798 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 05:32:06.556 2798 2798 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:33:38.204 5533 5533 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 05:33:40.221 5533 5533 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:34:39.346 7031 7031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-28 05:34:39.797 7031 7031 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:45:05.434 29567 29567 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
05-31 07:45:06.254 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.
05-31 07:45:08.650 29567 29567 W libc : Access denied finding property
"ro.vendor.perf.scroll_opt.heavy_app"
--------- beginning of main
06-29 16:35:16.895 16040 16040 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 16:35:17.867 16040 16040 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:35:35.116 17012 17012 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 16:35:36.608 17012 17012 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:35:52.533 17012 17734 E ion : ioctl c0044901 failed with code -1:
Invalid argument
06-29 16:35:54.147 17012 17618 E OpenGLRenderer: fbcNotifyFrameComplete error:
undefined symbol: fbcNotifyFrameComplete
06-29 16:35:54.147 17012 17618 E OpenGLRenderer: fbcNotifyNoRender error: undefined
symbol: fbcNotifyNoRender
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: Failed to load saved
values from file
/data/user/0/com.mbwhatsapp/files/ShortcutInfoCompatSaver_share_targets/
targets.xml. Old state removed, new added
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver:
java.io.FileNotFoundException:
/data/user/0/com.mbwhatsapp/files/ShortcutInfoCompatSaver_share_targets/
targets.xml: open failed: ENOENT (No such file or directory)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
libcore.io.IoBridge.open(IoBridge.java:574)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
java.io.FileInputStream.<init>(FileInputStream.java:160)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at X.0nz.run(Unknown
Source:82)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
java.util.concurrent.FutureTask.run(FutureTask.java:264)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
java.lang.Thread.run(Thread.java:1012)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: Caused by:
android.system.ErrnoException: open failed: ENOENT (No such file or directory)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
libcore.io.Linux.open(Native Method)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
libcore.io.ForwardingOs.open(ForwardingOs.java:563)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
libcore.io.ForwardingOs.open(ForwardingOs.java:563)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8374)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: at
libcore.io.IoBridge.open(IoBridge.java:560)
06-29 16:35:57.273 17012 17898 E ShortcutInfoCompatSaver: ... 7 more
06-29 16:35:57.290 17012 17618 E FrameEvents: updateAcquireFence: Did not find
frame.
06-29 16:35:57.337 17012 17618 E FrameEvents: updateAcquireFence: Did not find
frame.
06-29 16:35:57.358 17012 17618 E FrameEvents: updateAcquireFence: Did not find
frame.
06-29 16:35:57.483 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.483 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.494 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.495 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.495 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.496 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.498 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:35:57.499 17012 17012 E com.mbwhatsapp: Invalid ID 0x00000000.
06-29 16:36:17.134 17012 17259 E PlayCore: UID: [10380] PID: [17012]
StandardIntegrity : Phonesky is not installed.
06-29 16:36:39.616 19645 19645 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
06-29 16:36:41.014 19645 19645 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.