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

03-31 11:47:41.566 28890 28890 E com.mbwhatsapp: Not starting debugger since

process cannot load the jdwp agent.
03-31 11:47:44.306 28890 28890 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
03-31 12:04:07.151 18569 18569 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 12:04:07.885 18569 18569 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 12:12:29.821 24703 24703 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 12:12:30.952 24703 24703 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 12:20:33.723 31409 31409 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 12:20:34.532 31409 31409 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 12:25:33.094 13898 13898 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 12:25:33.851 13898 13898 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 12:25:34.790 13898 13898 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
03-31 12:25:34.790 13898 13898 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
03-31 12:43:01.124 21622 21622 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 12:43:02.772 21622 21622 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 13:42:45.689 8246 8246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 13:42:46.460 8246 8246 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 14:43:12.330 20862 20862 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 14:43:13.740 20862 20862 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
03-31 16:06:32.068 27636 27636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 16:06:32.792 27636 27636 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
03-31 16:06:34.149 27636 27636 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
03-31 16:06:34.150 27636 27636 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
03-31 16:23:18.603 15865 15865 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 16:23:19.302 15865 15865 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 16:42:43.049 31928 31928 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 16:42:44.370 31928 31928 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:05:29.192 21839 21839 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:05:30.124 21839 21839 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:06:02.611 22340 22340 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:06:03.734 22340 22340 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:06:41.943 24065 24065 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:06:43.685 24065 24065 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:33:43.986 11351 11351 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:33:45.212 11351 11351 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:34:21.125 11865 11865 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:34:21.862 11865 11865 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:42:04.843 18518 18518 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:42:06.743 18518 18518 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:42:11.862 18871 18871 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:42:12.170 18871 18871 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 17:45:15.974 22481 22481 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 17:45:16.573 22481 22481 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 18:42:49.122 11577 11577 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 18:42:50.110 11577 11577 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
03-31 18:42:51.633 11577 11577 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
03-31 18:42:51.636 11577 11577 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
03-31 19:12:38.043 1223 1223 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:12:38.702 1223 1223 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 19:43:53.524 14161 14161 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:43:55.592 14161 14161 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
03-31 19:43:58.363 14161 14161 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
03-31 19:43:58.364 14161 14161 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
03-31 19:44:19.064 14810 14810 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:44:19.631 14810 14810 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 19:48:05.348 20728 20728 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:48:12.510 20728 20728 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 19:48:24.178 21164 21164 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:48:25.264 21164 21164 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 19:49:31.928 22374 22374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:49:32.536 22374 22374 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 19:55:02.194 26364 26364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 19:55:02.627 26364 26364 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
03-31 19:55:03.571 26364 26364 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
03-31 19:55:03.571 26364 26364 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
03-31 20:17:27.802 7574 7574 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 20:17:29.202 7574 7574 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 21:42:42.846 25828 25828 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 21:42:44.445 25828 25828 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
03-31 21:47:15.549 30997 30997 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 21:47:16.987 30997 30997 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 21:51:34.851 7168 7168 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 21:51:35.453 7168 7168 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 22:11:47.753 20380 20380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 22:11:50.935 20380 20380 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 22:12:03.432 20810 20810 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 22:12:06.314 20810 20810 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 22:24:44.799 26756 26756 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 22:25:28.856 26756 26756 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
03-31 23:59:55.037 3075 3075 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
03-31 23:59:56.703 3075 3075 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 00:46:03.345 5308 5308 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 00:46:04.545 5308 5308 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 02:43:54.986 10098 10098 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 02:43:55.615 10098 10098 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 04:43:17.456 27776 27776 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 04:43:17.928 27776 27776 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 05:39:50.854 31341 31341 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 05:39:51.387 31341 31341 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 10:12:37.344 19034 19034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 10:12:39.480 19034 19034 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 10:58:42.632 25368 25368 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 10:58:46.917 25368 25368 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 11:25:21.516 5082 5082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 11:25:22.548 5082 5082 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 11:36:25.538 13318 13318 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 11:36:26.099 13318 13318 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 11:36:28.023 13318 13318 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-01 11:44:23.320 21552 21552 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 11:44:24.812 21552 21552 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 13:18:51.039 20601 20601 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 13:18:52.390 20601 20601 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 14:44:16.784 26212 26212 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 14:44:17.833 26212 26212 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-01 14:44:19.190 26212 26212 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-01 14:44:19.190 26212 26212 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-01 15:13:25.221 14866 14866 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 15:13:25.747 14866 14866 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 15:13:26.551 14866 14866 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-01 15:13:26.552 14866 14866 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-01 15:27:27.866 20996 20996 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 15:27:28.342 20996 20996 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 16:44:17.559 21766 21766 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 16:44:20.669 21766 21766 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 16:49:26.779 27593 27593 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 16:49:27.446 27593 27593 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 17:06:26.563 4740 4740 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 17:06:27.025 4740 4740 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 18:32:42.725 18638 18638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 18:32:45.853 18638 18638 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 19:30:08.308 15943 15943 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 19:30:08.908 15943 15943 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-01 19:30:09.955 15943 15943 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-01 22:49:38.638 4433 4433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 22:49:42.397 4433 4433 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-01 23:04:55.108 16545 16545 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-01 23:04:55.577 16545 16545 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 01:06:52.103 18807 18807 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 01:06:53.310 18807 18807 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 02:45:45.208 22036 22036 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 02:45:45.688 22036 22036 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-02 02:45:46.591 22036 22036 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-02 03:55:19.567 20314 20314 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 03:55:20.178 20314 20314 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 04:00:40.193 22116 22116 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 04:00:40.940 22116 22116 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 05:12:11.212 30558 30558 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 05:12:11.804 30558 30558 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-02 05:12:12.443 30558 30558 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-02 05:44:49.673 31631 31631 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 05:44:50.694 31631 31631 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 07:45:02.670 6646 6646 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 07:45:03.304 6646 6646 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 08:44:16.809 21336 21336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 08:44:17.418 21336 21336 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 09:44:16.644 9552 9552 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 09:44:17.311 9552 9552 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 10:44:17.022 28148 28148 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 10:44:17.618 28148 28148 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 11:03:42.017 5605 5605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 11:03:42.796 5605 5605 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 12:44:16.910 12232 12232 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 12:44:17.760 12232 12232 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 13:13:30.076 27972 27972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 13:13:30.948 27972 27972 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 13:38:35.532 26736 26736 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 13:38:36.380 26736 26736 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 14:03:30.697 3285 3285 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 14:03:31.286 3285 3285 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 14:45:21.414 19991 19991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 14:45:22.852 19991 19991 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 17:53:57.627 1442 1442 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 17:54:02.789 1442 1442 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 18:21:27.756 9512 9512 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 18:21:30.345 9512 9512 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 19:44:16.605 15002 15002 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 19:44:17.208 15002 15002 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-02 19:44:18.064 15002 15002 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-02 19:44:18.065 15002 15002 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-02 20:45:54.959 27784 27784 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 20:45:55.968 27784 27784 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 21:44:50.666 32080 32080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 21:44:51.347 32080 32080 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 21:44:52.539 32080 32080 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-02 21:47:54.110 6523 6523 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 21:47:55.040 6523 6523 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 22:02:47.550 14466 14466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 22:02:48.172 14466 14466 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 22:31:07.217 29393 29393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 22:31:08.290 29393 29393 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 22:54:11.911 3753 3753 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 22:54:12.569 3753 3753 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 23:24:00.663 17878 17878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 23:24:01.125 17878 17878 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 23:44:03.643 28049 28049 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 23:44:04.414 28049 28049 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-02 23:44:16.910 28744 28744 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-02 23:44:18.283 28744 28744 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 00:44:55.026 15038 15038 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 00:44:55.728 15038 15038 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 01:45:01.787 21463 21463 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 01:45:02.233 21463 21463 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 02:45:13.189 25924 25924 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 02:45:13.702 25924 25924 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 03:47:58.480 28708 28708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 03:47:59.024 28708 28708 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 04:52:30.738 5752 5752 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 04:52:31.345 5752 5752 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 05:45:38.185 7576 7576 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 05:45:38.712 7576 7576 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 06:07:40.361 10900 10900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 06:07:40.861 10900 10900 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 06:24:40.371 17463 17463 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 06:24:43.668 17463 17463 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-03 06:24:45.659 17463 17463 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-03 06:24:45.659 17463 17463 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-03 06:46:33.719 25343 25343 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 06:46:35.678 25343 25343 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 06:46:37.198 25343 25343 W com.mbwhatsapp: Verification of void X.3gG.run()
took 128.298ms (18612.84 bytecodes/s) (73648B approximate peak alloc)
04-03 07:05:45.802 25343 29766 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-03 07:44:17.938 9370 9370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 07:44:19.139 9370 9370 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 08:23:35.241 5182 5182 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 08:23:36.245 5182 5182 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 08:23:40.531 5319 5319 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 08:23:42.606 5319 5319 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 08:44:30.816 31505 31505 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 08:44:31.985 31505 31505 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-03 08:44:33.614 31505 31505 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-03 08:44:33.615 31505 31505 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-03 08:55:57.526 16229 16229 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 08:55:59.481 16229 16229 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 09:02:37.506 22355 22355 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 09:02:38.702 22355 22355 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 09:02:48.701 22715 22715 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 09:02:49.435 22715 22715 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 09:44:16.707 13086 13086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 09:44:17.362 13086 13086 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 10:44:16.547 1215 1215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 10:44:16.959 1215 1215 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 11:44:54.433 32635 32635 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 11:44:55.154 32635 32635 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-03 11:44:56.090 32635 32635 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-03 11:44:56.090 32635 32635 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-03 12:43:48.451 11341 11341 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 12:43:53.089 11341 11341 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:44:16.724 11374 11374 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:44:17.870 11374 11374 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-03 13:44:18.961 11374 11374 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-03 13:44:18.962 11374 11374 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-03 13:49:45.055 18504 18504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:49:45.921 18504 18504 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:50:20.133 19253 19253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:50:20.558 19253 19253 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:56:35.868 23910 23910 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:56:36.570 23910 23910 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:57:08.225 24989 24989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:57:08.973 24989 24989 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:58:26.926 28863 28863 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:58:27.669 28863 28863 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:59:08.992 29892 29892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:59:09.734 29892 29892 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 13:59:57.143 31781 31781 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 13:59:58.706 31781 31781 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:00:06.081 32174 32174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:00:08.113 32174 32174 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:00:17.031 32766 32766 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:00:17.759 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-03 14:00:20.506 838 838 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:00:21.267 838 838 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:22:10.083 24119 24119 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:22:11.251 24119 24119 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:22:14.816 24249 24249 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:22:15.524 24249 24249 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:22:18.611 24373 24373 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:22:18.868 24373 24373 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:22:49.883 24970 24970 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:22:50.614 24970 24970 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:22:53.570 25077 25077 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:22:53.797 25077 25077 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:28:58.892 31329 31329 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:28:59.946 31329 31329 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:29:37.885 32339 32339 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:29:38.615 32339 32339 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 14:48:56.657 17861 17861 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 14:48:58.259 17861 17861 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 15:13:13.120 30126 30126 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 15:13:13.773 30126 30126 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 15:31:34.045 10902 10902 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 15:31:34.758 10902 10902 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 15:37:41.178 20464 20464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 15:37:42.302 20464 20464 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 15:44:16.662 28110 28110 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 15:44:17.542 28110 28110 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 15:58:45.950 17162 17162 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 15:58:47.187 17162 17162 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 16:27:55.412 10157 10157 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 16:27:56.581 10157 10157 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 16:44:17.069 24116 24116 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 16:44:17.962 24116 24116 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 16:54:06.388 11405 11405 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 16:54:07.005 11405 11405 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 16:54:40.616 13027 13027 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 16:54:43.280 13027 13027 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 17:44:25.376 12267 12267 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 17:44:26.797 12267 12267 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 18:08:41.464 8581 8581 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 18:08:42.901 8581 8581 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 19:30:33.337 11112 11112 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 19:30:34.457 11112 11112 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 19:52:18.707 19073 19073 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 19:52:25.892 19073 19073 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 21:44:30.075 7811 7811 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 21:44:31.086 7811 7811 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-03 21:44:33.044 7811 7811 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-03 21:44:33.045 7811 7811 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-03 22:02:36.535 18483 18483 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 22:02:37.749 18483 18483 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-03 22:31:03.947 28482 28482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 22:31:04.508 28482 28482 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-03 22:31:05.048 28482 28482 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-03 22:31:05.049 28482 28482 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-03 23:51:59.397 31028 31028 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-03 23:51:59.866 31028 31028 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 00:46:02.188 2198 2198 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 00:46:04.608 2198 2198 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 05:38:21.017 16662 16662 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 05:38:22.046 16662 16662 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-04 05:38:22.794 16662 16662 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-04 05:38:22.795 16662 16662 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-04 05:38:24.490 16662 16838 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-04 05:38:24.770 16662 16881 E PlayCore: UID: [10884] PID: [16662]
StandardIntegrity : Phonesky is not installed.
04-04 05:42:45.505 17991 17991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 05:42:46.152 17991 17991 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 05:42:49.838 17991 18449 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-04 07:12:10.280 9878 9878 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 07:12:12.037 9878 9878 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 07:44:14.632 8735 8735 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 07:44:15.546 8735 8735 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 07:47:15.519 10894 10894 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 07:47:16.214 10894 10894 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 07:49:53.665 14692 14692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 07:49:57.362 14692 14692 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 07:52:26.419 19356 19356 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 07:52:27.600 19356 19356 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 08:44:14.508 3394 3394 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 08:44:15.216 3394 3394 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 08:50:18.204 8613 8613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 08:50:18.887 8613 8613 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 09:46:10.638 2344 2344 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 09:46:11.228 2344 2344 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 10:45:31.488 24293 24293 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 10:45:32.519 24293 24293 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 11:11:13.574 5544 5544 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 11:11:14.443 5544 5544 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 11:11:15.640 5544 5544 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-04 11:44:23.773 23601 23601 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 11:44:26.144 23601 23601 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 12:13:11.495 26097 26097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 12:13:12.002 26097 26097 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 12:46:33.396 31578 31578 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 12:46:34.270 31578 31578 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 13:44:54.235 4641 4641 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 13:44:54.709 4641 4641 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 15:12:37.542 20296 20296 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 15:12:40.829 20296 20296 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 15:44:14.531 27366 27366 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 15:44:15.143 27366 27366 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 16:31:19.999 13441 13441 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 16:31:20.587 13441 13441 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 16:44:14.673 20775 20775 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 16:44:15.806 20775 20775 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 18:45:06.204 8348 8348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 18:45:07.872 8348 8348 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-04 18:45:11.033 8348 8348 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-04 18:45:11.034 8348 8348 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-04 19:44:54.930 16761 16761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 19:44:55.421 16761 16761 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 20:19:02.660 22035 22035 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 20:19:22.729 22035 22035 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 21:45:39.058 12198 12198 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 21:45:39.775 12198 12198 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-04 21:45:41.138 12198 12198 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-04 21:54:43.532 15709 15709 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 21:54:44.202 15709 15709 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 22:15:55.449 24727 24727 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 22:15:56.533 24727 24727 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 22:42:00.905 5809 5809 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 22:42:01.937 5809 5809 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 22:44:14.556 8944 8944 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 22:44:15.282 8944 8944 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-04 23:41:56.441 20498 20498 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-04 23:41:58.639 20498 20498 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 00:13:10.109 24326 24326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 00:13:10.731 24326 24326 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 01:47:33.140 27244 27244 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 01:47:33.687 27244 27244 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 04:59:45.257 6563 6563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 04:59:46.570 6563 6563 W com.mbwhatsapp: Verification of void
X.0yS.attachBaseContext(android.content.Context) took 109.367ms (941.78
bytecodes/s) (3168B approximate peak alloc)
04-05 04:59:46.921 6563 6563 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-05 04:59:46.929 6563 6563 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-05 04:59:46.929 6563 6563 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1131)
04-05 04:59:46.929 6563 6563 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1085)
04-05 04:59:46.929 6563 6563 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1008)
04-05 04:59:46.929 6563 6563 W System.err: at
java.lang.System.loadLibrary(System.java:1664)
04-05 04:59:46.929 6563 6563 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-05 04:59:46.929 6563 6563 W System.err: at
java.lang.Class.newInstance(Native Method)
04-05 04:59:46.929 6563 6563 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-05 04:59:46.929 6563 6563 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-05 04:59:46.929 6563 6563 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1208)
04-05 04:59:46.929 6563 6563 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1256)
04-05 04:59:46.929 6563 6563 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7163)
04-05 04:59:46.930 6563 6563 W System.err: at
android.app.ActivityThread.access$1500(ActivityThread.java:265)
04-05 04:59:46.930 6563 6563 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2152)
04-05 04:59:46.930 6563 6563 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-05 04:59:46.930 6563 6563 W System.err: at
android.os.Looper.loop(Looper.java:257)
04-05 04:59:46.930 6563 6563 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8192)
04-05 04:59:46.930 6563 6563 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-05 04:59:46.930 6563 6563 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626)
04-05 04:59:46.930 6563 6563 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
04-05 04:59:47.070 6563 6563 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-05 04:59:50.083 6563 6563 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-05 04:59:50.084 6563 6563 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-05 04:59:50.330 6563 6563 W com.mbwhatsapp: Verification of void X.3gG.run()
took 178.999ms (13340.81 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-05 04:59:50.570 6563 6563 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-05 04:59:50.568 6563 6563 W com.mbwhatsapp: type=1400 audit(0.0:1075): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-05 04:59:51.516 6563 6563 W com.mbwhatsapp: type=1400 audit(0.0:1089): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-3" ino=17113 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-05 04:59:51.656 6563 6563 W com.mbwhatsapp: type=1400 audit(0.0:1090): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-3" ino=17069 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-05 04:59:51.656 6563 6563 W com.mbwhatsapp: type=1400 audit(0.0:1092): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-3" ino=17069 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-05 04:59:52.472 6563 6852 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
04-05 04:59:52.472 6563 6852 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-05 04:59:52.472 6563 6852 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-05 05:18:10.419 21803 21803 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 05:18:11.073 21803 21803 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 05:53:20.219 32392 32392 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 05:53:20.838 32392 32392 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 06:13:23.048 12618 12618 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 06:13:23.694 12618 12618 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 06:36:36.761 23165 23165 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 06:36:39.064 23165 23165 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 07:55:27.711 16288 16288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 07:55:29.916 16288 16288 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 08:34:48.089 23387 23387 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 08:34:50.990 23387 23387 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 08:53:19.941 6280 6280 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 08:53:20.576 6280 6280 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 09:53:20.147 22673 22673 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 09:53:20.974 22673 22673 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 10:00:25.333 26636 26636 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 10:00:26.072 26636 26636 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 10:23:40.787 5121 5121 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 10:23:41.984 5121 5121 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 10:53:20.290 13506 13506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 10:53:21.282 13506 13506 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 11:53:20.045 6728 6728 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 11:53:20.815 6728 6728 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 12:03:23.388 10439 10439 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 12:03:24.000 10439 10439 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 12:21:52.366 17953 17953 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 12:21:53.360 17953 17953 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 12:21:57.188 18258 18258 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 12:21:57.635 18258 18258 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 13:19:48.995 31797 31797 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 13:19:51.369 31797 31797 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 13:53:25.864 17930 17930 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 13:53:26.936 17930 17930 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 14:12:31.066 30748 30748 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 14:12:31.704 30748 30748 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 14:33:34.861 19511 19511 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 14:33:35.899 19511 19511 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 14:53:20.291 26424 26424 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 14:53:21.100 26424 26424 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 15:00:59.022 2356 2356 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 15:00:59.923 2356 2356 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 15:01:52.140 4424 4424 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 15:01:52.777 4424 4424 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 15:53:19.889 19225 19225 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 15:53:21.190 19225 19225 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 16:54:25.062 13382 13382 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 16:54:26.530 13382 13382 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 17:53:20.394 17146 17146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 17:53:21.456 17146 17146 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 18:08:53.857 28815 28815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 18:09:01.117 28815 28815 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 23:16:12.224 6776 6776 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 23:16:15.886 6776 6776 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 23:21:35.271 12809 12809 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 23:21:36.745 12809 12809 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-05 23:32:28.113 17739 17739 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-05 23:32:28.797 17739 17739 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 00:53:20.108 10605 10605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 00:53:20.726 10605 10605 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:14:32.342 18424 18424 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 01:15:23.298 18424 18424 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:51:26.805 8770 8770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 03:51:27.315 8770 8770 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:54:15.281 14044 14044 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 03:54:16.732 14044 14044 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:56:10.997 16765 16765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 03:56:11.554 16765 16765 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:56:54.626 17583 17583 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 03:57:02.084 17583 17583 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:57:57.002 18858 18858 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 03:57:57.495 18858 18858 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:58:34.647 20400 20400 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 03:58:35.566 20400 20400 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:01:40.530 25928 25928 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 04:01:41.812 25928 25928 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:53:35.088 29128 29128 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 07:53:35.881 29128 29128 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:04:52.185 5227 5227 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 08:04:53.326 5227 5227 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:33:58.734 4143 4143 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 08:33:59.544 4143 4143 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:53:19.832 9150 9150 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 08:53:20.386 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.
--------- beginning of main
04-06 08:55:48.991 13146 13146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 08:55:50.190 13146 13146 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:10:33.148 26255 26255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 09:10:34.053 26255 26255 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:23:58.695 5257 5257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 09:24:00.037 5257 5257 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:40:03.893 19191 19191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 09:40:05.881 19191 19191 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:43:11.288 30747 30747 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 09:43:12.685 30747 30747 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:53:19.849 28439 28439 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 09:53:20.510 28439 28439 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:53:19.958 18996 18996 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 10:53:21.594 18996 18996 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1131)
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1085)
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1008)
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.System.loadLibrary(System.java:1664)
04-06 10:53:21.595 18996 18996 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.Class.newInstance(Native Method)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-06 10:53:21.595 18996 18996 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1208)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1256)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7163)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.ActivityThread.access$1500(ActivityThread.java:265)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2152)
04-06 10:53:21.595 18996 18996 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-06 10:53:21.595 18996 18996 W System.err: at
android.os.Looper.loop(Looper.java:257)
04-06 10:53:21.595 18996 18996 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8192)
04-06 10:53:21.595 18996 18996 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-06 10:53:21.596 18996 18996 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626)
04-06 10:53:21.596 18996 18996 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
04-06 10:53:21.876 18996 18996 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-06 11:56:04.905 13030 13030 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 11:56:05.838 13030 13030 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:07:32.662 23830 23830 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 12:07:33.384 23830 23830 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:18:06.564 31529 31529 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 12:18:07.705 31529 31529 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:28:27.011 11164 11164 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 12:28:30.499 11164 11164 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-06 12:53:20.183 5633 5633 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 12:53:21.082 5633 5633 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:53:19.903 10759 10759 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 15:53:20.708 10759 10759 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:53:20.711 892 892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 16:53:22.495 892 892 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:08:04.927 9347 9347 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 17:08:05.446 9347 9347 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-06 17:20:28.734 15794 15794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 17:20:30.533 15794 15794 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:38:34.038 21882 21882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 17:38:35.019 21882 21882 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:54:33.280 21660 21660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 18:54:34.436 21660 21660 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:55:30.752 22603 22603 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 18:55:31.761 22603 22603 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:57:09.439 23400 23400 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 18:57:10.328 23400 23400 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:58:45.203 24419 24419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 18:58:45.891 24419 24419 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-06 18:59:52.140 25669 25669 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 18:59:52.762 25669 25669 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-06 19:13:52.176 30977 30977 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 19:13:52.969 30977 30977 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:33:55.570 8732 8732 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 19:33:56.083 8732 8732 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 19:33:57.210 8732 8732 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-06 19:46:02.075 16053 16053 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 19:46:03.074 16053 16053 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:53:19.841 20792 20792 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 19:53:20.382 20792 20792 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 20:53:20.341 10697 10697 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 20:53:21.281 10697 10697 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:53:22.801 10697 10697 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-06 21:53:25.895 21933 21933 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 21:53:26.273 21933 21933 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 21:53:27.125 21933 21933 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-06 22:08:52.126 24313 24313 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-06 22:08:52.612 24313 24313 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:54:51.216 22255 22255 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 03:54:52.223 22255 22255 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:56:05.473 5377 5377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 04:56:06.191 5377 5377 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:53:24.491 19542 19542 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 05:53:25.498 19542 19542 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-07 05:53:26.616 19542 19542 W com.mbwhatsapp: type=1400 audit(0.0:44361): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 05:53:26.621 19542 19542 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-07 06:07:28.014 26087 26087 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 06:07:28.696 26087 26087 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 06:17:33.458 31311 31311 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 06:17:34.428 31311 31311 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 06:17:42.583 31659 31659 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 06:17:43.432 31659 31659 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 06:53:28.149 19695 19695 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 06:53:29.490 19695 19695 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:55:03.199 32508 32508 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 07:55:04.051 32508 32508 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:07:10.368 2434 2434 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 08:07:11.288 2434 2434 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31:36.909 3915 3915 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 08:31:37.433 3915 3915 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:00:53.329 5125 5125 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 09:00:54.978 5125 5125 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:55:37.490 9509 9509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 09:55:38.086 9509 9509 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:55:37.323 11433 11433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 10:55:38.505 11433 11433 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:37.604 26021 26021 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 11:53:38.628 26021 26021 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:47.800 18620 18620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 12:53:48.527 18620 18620 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:49.794 18620 18620 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-07 13:13:16.477 24089 24089 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:13:17.095 24089 24089 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:38:49.169 1412 1412 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:38:50.117 1412 1412 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-07 13:54:31.926 9852 9852 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 13:54:32.788 9852 9852 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:17:38.148 21644 21644 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 14:17:39.376 21644 21644 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:22:17.643 24273 24273 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 14:22:18.407 24273 24273 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:20.272 18256 18256 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 15:53:21.440 18256 18256 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:22.801 18256 18256 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-07 16:20:24.185 28695 28695 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 16:20:24.938 28695 28695 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:05:41.095 9610 9610 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 17:05:41.561 9610 9610 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 17:05:42.235 9610 9610 W com.mbwhatsapp: type=1400 audit(0.0:121696): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-07 17:05:42.239 9610 9610 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-07 17:53:19.855 19905 19905 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 17:53:20.500 19905 19905 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:55:27.022 13267 13267 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 18:55:27.647 13267 13267 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:07:52.877 23845 23845 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 19:07:57.166 23845 23845 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:21:21.410 10622 10622 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 19:21:22.404 10622 10622 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:30:16.927 22347 22347 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 19:30:17.989 22347 22347 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:39:27.871 4398 4398 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 19:39:28.523 4398 4398 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:47:31.290 8959 8959 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 19:47:31.853 8959 8959 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-07 19:53:30.267 13424 13424 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 19:53:31.147 13424 13424 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:25:02.227 25136 25136 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 20:25:02.954 25136 25136 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:19.852 32105 32105 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 20:53:20.475 32105 32105 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-07 21:15:35.588 8441 8441 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 21:15:36.619 8441 8441 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:26:40.555 13207 13207 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 21:26:41.302 13207 13207 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:29:50.313 14419 14419 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 21:29:51.761 14419 14419 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:40:53.914 19652 19652 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 21:40:54.447 19652 19652 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:40:54.149 10435 10435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-07 23:40:56.726 10435 10435 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:55:20.196 20292 20292 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 00:55:20.864 20292 20292 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:13:16.490 25037 25037 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 03:13:18.081 25037 25037 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:26:03.258 27241 27241 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 03:26:03.663 27241 27241 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:57:33.070 31571 31571 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 03:57:33.524 31571 31571 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:24:59.913 2555 2555 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 04:25:00.663 2555 2555 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:53:20.157 11783 11783 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 05:53:21.182 11783 11783 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:05:00.310 16452 16452 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 06:05:00.983 16452 16452 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-08 06:26:40.334 28277 28277 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 06:26:41.648 28277 28277 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:40:11.900 3110 3110 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 06:40:12.788 3110 3110 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:51:24.680 7761 7761 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 06:51:25.480 7761 7761 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:44:11.916 3794 3794 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 09:44:13.492 3794 3794 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:54:29.479 11653 11653 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 09:54:30.372 11653 11653 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:53:34.224 23574 23574 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 10:53:34.996 23574 23574 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:53:20.199 9017 9017 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 11:53:21.420 9017 9017 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:20:27.458 24242 24242 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 12:20:28.149 24242 24242 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:54:00.540 4193 4193 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 12:54:02.030 4193 4193 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:44:45.811 18088 18088 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 14:44:46.645 18088 18088 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:44:47.947 18088 18088 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-08 14:44:47.948 18088 18088 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-08 14:56:41.891 25057 25057 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 14:56:43.155 25057 25057 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:59:46.079 28251 28251 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 14:59:48.169 28251 28251 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:53:35.086 29095 29095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 15:53:35.854 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-08 16:04:56.970 5457 5457 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 16:04:57.759 5457 5457 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:25:13.805 22342 22342 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 16:25:14.263 22342 22342 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-08 16:25:15.114 22342 22342 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-08 16:25:15.115 22342 22342 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-08 16:53:55.193 32563 32563 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 16:53:56.291 32563 32563 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 16:53:57.664 32563 32563 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-08 16:53:57.665 32563 32563 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-08 17:21:01.436 10720 10720 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 17:21:02.533 10720 10720 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:54:48.183 9106 9106 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 17:54:48.967 9106 9106 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:54:52.756 9106 9106 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-08 17:54:52.756 9106 9106 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-08 18:21:56.937 24787 24787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 18:21:57.583 24787 24787 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:42:05.389 7618 7618 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 18:42:06.398 7618 7618 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:34:03.779 10141 10141 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 19:34:04.545 10141 10141 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 20:55:17.359 21253 21253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 20:55:17.854 21253 21253 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:07:19.855 25912 25912 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:07:20.798 25912 25912 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:16:24.910 32040 32040 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:16:25.750 32040 32040 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:38:28.589 24866 24866 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:38:31.503 24866 24866 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:19.898 3253 3253 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 21:53:20.654 3253 3253 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:00:44.715 7272 7272 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 22:00:45.829 7272 7272 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:00:49.057 7272 7272 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-08 22:00:49.058 7272 7272 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-08 22:29:52.888 20177 20177 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 22:29:53.597 20177 20177 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:49:56.561 3325 3325 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 22:49:59.573 3325 3325 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:10:01.024 10718 10718 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 23:10:02.910 10718 10718 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-08 23:36:51.261 27170 27170 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 23:36:52.047 27170 27170 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:51:38.166 2550 2550 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-08 23:51:38.919 2550 2550 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:48:44.916 11074 11074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 00:48:45.727 11074 11074 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 01:03:17.123 14974 14974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:03:17.988 14974 14974 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 01:08:21.139 17996 17996 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:08:21.856 17996 17996 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:33:45.032 21843 21843 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:33:46.018 21843 21843 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:47:15.506 25120 25120 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:47:16.355 25120 25120 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 01:53:19.901 25917 25917 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 01:53:20.647 25917 25917 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:19.886 9725 9725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 02:53:20.558 9725 9725 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:53:20.011 23453 23453 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 03:53:20.949 23453 23453 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:21:50.185 31001 31001 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 04:21:52.694 31001 31001 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:49:57.233 6372 6372 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 04:49:57.962 6372 6372 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:49:18.666 25022 25022 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 05:49:19.336 25022 25022 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:51:33.383 26257 26257 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 05:51:34.737 26257 26257 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 06:59:41.405 4848 4848 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 06:59:44.979 4848 4848 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 08:53:19.865 24045 24045 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 08:53:20.485 24045 24045 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:15:56.544 21033 21033 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 09:15:57.705 21033 21033 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:06:58.223 17619 17619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 10:07:00.876 17619 17619 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 10:07:03.689 17619 17619 W com.mbwhatsapp: type=1400 audit(0.0:707456): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-09 10:07:03.695 17619 17619 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-09 10:51:37.004 28660 28660 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 10:51:37.586 28660 28660 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 11:10:54.772 30054 30054 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 11:11:00.808 30054 30054 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:53:19.930 4174 4174 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 11:53:20.861 4174 4174 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 12:53:20.198 2674 2674 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 12:53:21.164 2674 2674 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:29:21.154 25958 25958 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 13:29:21.987 25958 25958 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:48:28.408 328 328 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 13:48:29.004 328 328 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:53:20.256 4337 4337 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 13:53:21.064 4337 4337 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:12:31.187 14928 14928 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 14:12:32.273 14928 14928 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:54:23.497 5144 5144 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 14:54:24.196 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-09 14:54:25.171 5144 5144 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-09 15:03:13.710 12732 12732 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 15:03:14.320 12732 12732 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:20:17.340 26386 26386 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 15:20:18.168 26386 26386 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:21:00.024 27913 27913 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 15:21:02.606 27913 27913 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:26:41.561 19619 19619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 16:26:45.281 19619 19619 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:56:34.071 5679 5679 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 17:56:35.126 5679 5679 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:03:53.072 11112 11112 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 18:03:53.482 11112 11112 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:53:17.766 16007 16007 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 18:53:18.398 16007 16007 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:22:39.058 10284 10284 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 19:22:40.473 10284 10284 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:30:07.155 24186 24186 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 19:30:08.149 24186 24186 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:30:13.719 24386 24386 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 19:30:15.149 24386 24386 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:53:29.556 6997 6997 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 19:53:30.319 6997 6997 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:17.789 19892 19892 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 20:53:18.246 19892 19892 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:18:46.075 31523 31523 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:18:52.219 31523 31523 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:28:55.788 9675 9675 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:28:57.273 9675 9675 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:31.247 19912 19912 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 21:53:32.443 19912 19912 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:55:42.573 17826 17826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:55:44.503 17826 17826 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-09 22:56:45.123 20330 20330 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:56:46.014 20330 20330 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:57:40.680 21301 21301 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:57:41.667 21301 21301 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:58:16.437 22304 22304 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:58:17.365 22304 22304 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:58:51.424 23146 23146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:58:52.689 23146 23146 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:59:04.810 23749 23749 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 22:59:06.043 23749 23749 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:01:57.289 26961 26961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 23:01:57.968 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-09 23:06:03.992 31028 31028 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-09 23:06:05.194 31028 31028 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-10 00:59:51.782 5240 5240 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 00:59:52.603 5240 5240 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 00:59:53.631 5240 5240 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-10 00:59:53.631 5240 5240 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
--------- beginning of main
04-10 02:30:29.688 15692 15692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 02:30:30.320 15692 15692 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:55:34.100 26663 26663 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 03:55:34.662 26663 26663 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:55:35.404 26663 26663 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-10 04:53:57.671 20704 20704 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 04:53:58.661 20704 20704 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:55:34.255 28389 28389 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 05:55:35.663 28389 28389 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:09:40.984 32063 32063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 07:09:44.042 32063 32063 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:31:05.538 4427 4427 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 07:31:08.809 4427 4427 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:53:17.810 9938 9938 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 07:53:18.731 9938 9938 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:53:17.946 7395 7395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 08:53:18.747 7395 7395 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-10 09:53:52.264 14955 14955 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 09:53:56.685 14955 14955 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:53:39.006 23393 23393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 11:53:39.575 23393 23393 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-10 11:53:40.479 23393 23393 W com.mbwhatsapp: type=1400 audit(0.0:1082848): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-10 11:53:40.484 23393 23393 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-10 12:31:40.584 27366 27366 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 12:31:41.230 27366 27366 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:53:54.082 29484 29484 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 12:53:54.642 29484 29484 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:39.837 32129 32129 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 13:53:40.496 32129 32129 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:59:32.357 5884 5884 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 14:59:33.501 5884 5884 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:15.261 13516 13516 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 15:53:16.016 13516 13516 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:53:17.478 13516 13516 W com.mbwhatsapp: type=1400 audit(0.0:1089076): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-10 15:53:17.480 13516 13516 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-10 18:01:40.395 5818 5818 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 18:01:44.425 5818 5818 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31:32.762 30053 30053 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 19:31:35.956 30053 30053 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:36:58.319 3217 3217 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 20:37:06.372 3217 3217 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:53:15.368 17914 17914 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 21:53:16.127 17914 17914 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:08:20.395 29309 29309 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 22:08:21.153 29309 29309 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:24.275 30940 30940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 22:09:24.861 30940 30940 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:27:44.487 12028 12028 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 22:27:45.665 12028 12028 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:49:21.387 29161 29161 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 22:49:22.784 29161 29161 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:04:03.489 13416 13416 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:04:04.143 13416 13416 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:14:49.070 23796 23796 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-10 23:14:52.477 23796 23796 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:06:42.232 32490 32490 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 05:06:43.751 32490 32490 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:29:27.556 15976 15976 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 05:29:28.265 15976 15976 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:37:40.796 22030 22030 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 05:37:45.356 22030 22030 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:04:42.044 17574 17574 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:04:43.494 17574 17574 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:10:27.231 22506 22506 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:10:27.959 22506 22506 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31:39.713 11246 11246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:31:40.745 11246 11246 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:36:45.699 13903 13903 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:36:46.437 13903 13903 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:33.195 24211 24211 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 06:53:33.922 24211 24211 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:34.066 11416 11416 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 07:53:37.838 11416 11416 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:54:21.479 12400 12400 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 07:54:22.161 12400 12400 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:55:37.827 17283 17283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 07:55:39.694 17283 17283 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:58:15.173 25730 25730 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 07:58:15.959 25730 25730 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:58:17.173 25730 25730 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-11 08:06:45.901 5388 5388 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 08:06:47.068 5388 5388 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:35:39.631 31932 31932 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 08:35:40.384 31932 31932 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:35:42.230 31932 31932 W com.mbwhatsapp: Verification of void X.3gG.run()
took 115.853ms (20612.25 bytecodes/s) (73648B approximate peak alloc)
04-11 08:53:23.021 8626 8626 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 08:53:23.724 8626 8626 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:53:24.857 8626 8626 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-11 09:53:37.170 5106 5106 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 09:53:37.893 5106 5106 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-11 10:55:51.152 9531 9531 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 10:55:52.657 9531 9531 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:56:41.737 10521 10521 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 10:56:42.454 10521 10521 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:57:47.680 11145 11145 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 10:57:48.296 11145 11145 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:00:01.084 12408 12408 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 11:00:03.220 12408 12408 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:00:21.963 13089 13089 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 11:00:23.708 13089 13089 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:01:07.099 13801 13801 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 11:01:13.881 13801 13801 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:08:02.013 19973 19973 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 11:08:03.439 19973 19973 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-11 11:08:04.729 19973 19973 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-11 11:19:33.206 25367 25367 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 11:19:34.982 25367 25367 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:54:28.319 12429 12429 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 11:54:29.236 12429 12429 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:53:28.561 3530 3530 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 12:53:31.457 3530 3530 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:01:38.086 12095 12095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 13:01:39.473 12095 12095 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
--------- beginning of main
--------- beginning of main
04-11 13:23:36.766 17820 17820 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 13:23:37.291 17820 17820 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-11 14:06:03.383 8940 8940 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 14:06:04.661 8940 8940 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:06:07.354 8940 8940 W com.mbwhatsapp: Verification of void X.3gG.run()
took 130.989ms (18230.51 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-11 14:54:33.892 23759 23759 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 14:54:35.035 23759 23759 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:55:22.621 25526 25526 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 14:55:26.091 25526 25526 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:56:04.123 27125 27125 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 14:56:08.860 27125 27125 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:57:22.439 28643 28643 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 14:57:23.190 28643 28643 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:59:44.728 31422 31422 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 14:59:45.529 31422 31422 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:04:40.906 5206 5206 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 15:04:41.930 5206 5206 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 15:04:43.432 5206 5206 W com.mbwhatsapp: type=1400 audit(0.0:1394366): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-11 15:21:08.993 20782 20782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 15:21:10.163 20782 20782 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:30:13.319 26532 26532 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 15:30:13.954 26532 26532 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:35:27.183 29348 29348 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 15:35:27.984 29348 29348 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-11 15:53:16.172 13203 13203 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 15:53:17.583 13203 13203 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:14:20.351 19517 19517 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 16:14:21.271 19517 19517 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 16:14:22.942 19517 19517 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
--------- beginning of main
04-11 16:53:20.743 16097 16097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 16:53:21.776 16097 16097 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:08:47.409 28420 28420 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 17:08:48.775 28420 28420 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:33:10.342 9731 9731 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 17:33:10.880 9731 9731 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 17:33:11.944 9731 9731 W com.mbwhatsapp: type=1400 audit(0.0:1443625): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-11 17:33:11.949 9731 9731 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-11 17:33:11.956 9731 9731 W com.mbwhatsapp: type=1400 audit(0.0:1443626): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17118 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-11 17:37:10.419 11187 11187 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 17:37:11.061 11187 11187 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:48:14.685 17334 17334 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 17:48:15.393 17334 17334 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:53:57.783 23311 23311 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 17:54:01.226 23311 23311 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:15:20.795 32327 32327 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 18:15:25.064 32327 32327 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:16:26.093 4125 4125 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 18:16:27.748 4125 4125 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:47:29.019 30606 30606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 18:47:31.893 30606 30606 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:47:37.539 30847 30847 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 18:47:38.173 30847 30847 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:47:44.447 31121 31121 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 18:47:45.916 31121 31121 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:53:22.506 9462 9462 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 18:53:22.887 9462 9462 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:53:15.669 27806 27806 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 19:53:16.247 27806 27806 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 20:54:27.003 5822 5822 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 20:54:28.957 5822 5822 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-11 21:19:46.832 19821 19821 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 21:19:48.355 19821 19821 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:20:07.073 20308 20308 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 21:20:10.713 20308 20308 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1131)
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1085)
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1008)
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.System.loadLibrary(System.java:1664)
04-11 21:20:10.720 20308 20308 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.Class.newInstance(Native Method)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-11 21:20:10.720 20308 20308 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1208)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1256)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7163)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.ActivityThread.access$1500(ActivityThread.java:265)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2152)
04-11 21:20:10.720 20308 20308 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-11 21:20:10.720 20308 20308 W System.err: at
android.os.Looper.loop(Looper.java:257)
04-11 21:20:10.720 20308 20308 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8192)
04-11 21:20:10.720 20308 20308 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-11 21:20:10.720 20308 20308 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626)
04-11 21:20:10.721 20308 20308 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
04-11 21:20:10.994 20308 20308 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:44:20.658 5077 5077 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 21:44:21.245 5077 5077 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:44:22.539 5077 5077 W com.mbwhatsapp: type=1400 audit(0.0:1510318): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-11 21:44:22.543 5077 5077 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-11 21:51:24.628 10259 10259 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 21:51:25.727 10259 10259 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-11 21:53:15.418 13284 13284 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 21:53:18.230 13284 13284 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:22:48.555 13205 13205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-11 22:23:18.480 13205 13205 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:27:32.551 13205 13205 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-12 00:03:03.347 15976 15976 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 00:03:04.134 15976 15976 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 00:15:32.980 18279 18279 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 00:15:34.343 18279 18279 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 00:31:33.129 18819 18819 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 00:31:34.058 18819 18819 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 01:18:09.446 20057 20057 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 01:18:10.409 20057 20057 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 02:55:32.555 25651 25651 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 02:55:34.286 25651 25651 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 03:20:24.535 28207 28207 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 03:20:25.461 28207 28207 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 05:53:15.356 26677 26677 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 05:53:16.140 26677 26677 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 06:18:42.783 10461 10461 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 06:18:43.453 10461 10461 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 06:18:44.678 10461 10461 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-12 06:45:51.825 10961 10961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 06:45:53.213 10961 10961 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 06:45:55.546 10961 10961 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-12 06:45:55.550 10961 10961 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-12 06:46:08.171 11438 11438 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 06:46:10.415 11438 11438 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 06:52:43.976 13596 13596 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 06:52:44.837 13596 13596 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 06:52:46.726 13596 13596 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 06:54:29.229 15976 15976 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 06:54:29.761 15976 15976 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 07:53:15.404 5166 5166 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 07:53:16.430 5166 5166 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 08:17:20.044 6015 6015 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 08:17:20.894 6015 6015 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 08:42:25.617 26855 26855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 08:42:26.201 26855 26855 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 08:42:27.364 26855 26855 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 08:53:31.762 31268 31268 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 08:53:33.650 31268 31268 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-12 09:04:20.494 5466 5466 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 09:04:22.702 5466 5466 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 09:04:37.070 5844 5844 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 09:04:40.159 5844 5844 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 09:27:00.421 18772 18772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 09:27:01.262 18772 18772 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 09:53:15.405 3485 3485 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 09:53:16.933 3485 3485 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 10:53:15.250 22045 22045 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 10:53:15.956 22045 22045 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 11:10:08.097 27205 27205 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 11:10:08.740 27205 27205 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 11:19:15.791 30815 30815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 11:19:16.475 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.
04-12 11:19:17.499 30815 30815 W com.mbwhatsapp: type=1400 audit(0.0:1608266): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17118 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-12 11:40:04.084 9288 9288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 11:40:05.321 9288 9288 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-12 11:40:06.856 9288 9288 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 12:08:35.998 21783 21783 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 12:08:36.528 21783 21783 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 12:26:39.272 31808 31808 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 12:26:40.566 31808 31808 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
--------- beginning of main
04-12 12:41:24.165 22787 22787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 12:41:25.888 22787 22787 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 12:53:46.244 29833 29833 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 12:53:46.609 29833 29833 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 12:53:47.496 29833 29833 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 13:13:47.285 7690 7690 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 13:13:49.289 7690 7690 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 13:14:35.724 8842 8842 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 13:14:37.227 8842 8842 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 13:14:54.264 9526 9526 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 13:14:55.416 9526 9526 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 13:53:32.081 20459 20459 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 13:53:34.183 20459 20459 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 14:02:53.535 26802 26802 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 14:02:56.209 26802 26802 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 14:02:58.237 26802 26802 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 14:28:08.338 19627 19627 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 14:28:09.532 19627 19627 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 14:30:12.847 21971 21971 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 14:30:13.398 21971 21971 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 14:40:51.635 4004 4004 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 14:40:55.105 4004 4004 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 14:53:15.286 14244 14244 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 14:53:15.766 14244 14244 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 14:53:17.014 14244 14244 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-12 15:20:43.123 9703 9703 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 15:20:43.764 9703 9703 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 15:20:45.374 9703 9703 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 15:21:18.508 10390 10390 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 15:21:19.167 10390 10390 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 15:29:17.032 13464 13464 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 15:29:18.232 13464 13464 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 15:29:57.696 14235 14235 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 15:29:58.684 14235 14235 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 15:56:42.210 22528 22528 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 15:56:45.159 22528 22528 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 16:20:02.666 18772 18772 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 16:20:03.225 18772 18772 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-12 16:35:33.319 27985 27985 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 16:35:33.835 27985 27985 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 16:35:34.456 27985 27985 W com.mbwhatsapp: type=1400 audit(0.0:1737371): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-12 16:35:34.462 27985 27985 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 16:53:30.454 10632 10632 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 16:53:31.541 10632 10632 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 17:53:15.362 29236 29236 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 17:53:16.415 29236 29236 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 17:54:18.833 30135 30135 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 17:54:20.004 30135 30135 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 18:05:25.247 7954 7954 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 18:05:26.080 7954 7954 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 18:52:39.395 21276 21276 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 18:52:39.938 21276 21276 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-12 18:52:41.023 21276 21276 W com.mbwhatsapp: type=1400 audit(0.0:1788303): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-12 18:52:41.026 21276 21276 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-12 19:30:52.215 31086 31086 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 19:30:52.755 31086 31086 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 19:53:55.173 1968 1968 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 19:53:55.705 1968 1968 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 20:53:52.526 9052 9052 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 20:53:54.673 9052 9052 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 21:15:35.526 23608 23608 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 21:15:36.578 23608 23608 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 21:20:34.991 31158 31158 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 21:20:35.676 31158 31158 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 21:28:19.864 4468 4468 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 21:28:20.832 4468 4468 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 21:51:24.734 30299 30299 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 21:51:26.670 30299 30299 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 22:53:16.512 27619 27619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 22:53:21.769 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-12 22:53:43.795 27896 27896 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 22:53:55.116 27896 27896 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 23:03:11.666 7880 7880 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 23:03:12.242 7880 7880 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-12 23:15:32.668 22712 22712 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-12 23:15:33.337 22712 22712 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 09:55:55.395 6569 6569 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 09:55:56.253 6569 6569 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 09:55:57.315 6569 6569 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-13 10:28:46.557 20947 20947 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 10:28:47.638 20947 20947 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 10:55:07.037 13813 13813 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 10:55:07.863 13813 13813 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-13 10:55:09.454 13813 13813 W com.mbwhatsapp: type=1400 audit(0.0:1888598): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-13 10:55:09.458 13813 13813 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-13 10:55:09.470 13813 13813 W com.mbwhatsapp: type=1400 audit(0.0:1888599): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17118 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
--------- beginning of main
--------- beginning of main
04-13 10:55:57.198 15594 15594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 10:55:59.039 15594 15594 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 11:53:13.149 12982 12982 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 11:53:14.051 12982 12982 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-13 11:53:15.486 12982 12982 W com.mbwhatsapp: type=1400 audit(0.0:1903078): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17135 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-13 11:53:15.491 12982 12982 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-13 11:53:15.498 12982 12982 W com.mbwhatsapp: type=1400 audit(0.0:1903079): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17118 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-13 12:24:06.706 8922 8922 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 12:24:07.849 8922 8922 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 12:24:40.125 9975 9975 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 12:24:42.936 9975 9975 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 12:25:36.114 12059 12059 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 12:25:38.017 12059 12059 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 12:37:10.778 19795 19795 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 12:37:11.574 19795 19795 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 13:53:34.067 11115 11115 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 13:53:35.501 11115 11115 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 14:19:39.841 7770 7770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 14:19:46.464 7770 7770 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 14:44:56.292 18332 18332 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 14:44:59.999 18332 18332 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 14:46:08.951 20128 20128 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 14:46:10.992 20128 20128 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 14:46:45.138 20786 20786 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 14:53:40.257 23787 23787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 14:53:41.440 23787 23787 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 15:53:18.763 32638 32638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 15:53:19.519 32638 32638 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-13 15:53:20.963 32638 32638 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-13 16:06:41.626 15989 15989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 16:06:43.608 15989 15989 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 16:53:31.000 15551 15551 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 16:53:31.545 15551 15551 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 16:53:32.605 15551 15551 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-13 17:13:49.239 23815 23815 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:13:50.283 23815 23815 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-13 17:26:57.868 23735 23735 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:26:58.890 23735 23735 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 17:27:05.732 23967 23967 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:27:07.210 23967 23967 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 17:27:47.823 25827 25827 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:27:48.830 25827 25827 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 17:28:24.670 27545 27545 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:28:27.213 27545 27545 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 17:53:08.843 14369 14369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:53:09.256 14369 14369 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-13 17:53:09.966 14369 14369 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-13 17:53:10.923 14369 14441 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-13 17:53:11.423 14369 14430 E PlayCore: UID: [10884] PID: [14369]
StandardIntegrity : Phonesky is not installed.
04-13 17:53:31.178 15063 15063 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 17:53:31.584 15063 15063 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 17:53:33.048 15063 15138 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-13 17:53:33.262 15063 15166 E PlayCore: UID: [10884] PID: [15063]
StandardIntegrity : Phonesky is not installed.
04-13 18:01:53.092 17383 17383 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 18:01:53.740 17383 17383 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 18:05:41.019 20957 20957 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 18:05:44.695 20957 20957 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 18:05:59.643 21356 21356 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 18:06:05.065 21356 21356 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 18:24:33.863 2699 2699 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 18:24:35.252 2699 2699 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 19:36:22.921 21770 21770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 19:36:26.842 21770 21770 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 20:03:48.410 21770 26329 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-13 20:04:09.492 21770 26339 E PlayCore: UID: [10884] PID: [21770]
StandardIntegrity : Phonesky is not installed.
--------- beginning of main
04-13 20:20:15.233 10278 10278 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 20:20:16.061 10278 10278 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 20:53:16.190 22917 22917 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 20:53:17.387 22917 22917 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-13 20:53:18.234 22917 22917 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-13 20:53:18.235 22917 22917 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-13 21:01:48.864 3435 3435 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 21:01:50.038 3435 3435 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 21:20:39.265 26072 26072 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 21:20:40.132 26072 26072 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 21:20:41.620 26072 26072 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-13 21:53:42.359 21903 21903 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 21:53:43.057 21903 21903 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:12:34.653 29620 29620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:12:37.578 29620 29620 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:18:18.756 32380 32380 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:18:20.086 32380 32380 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:28:06.804 6276 6276 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:28:16.347 6276 6276 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:30:46.035 11149 11149 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:30:48.302 11149 11149 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:31:06.526 11683 11683 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:31:09.711 11683 11683 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:31:41.457 12834 12834 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:31:43.148 12834 12834 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:32:56.407 15708 15708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:32:57.243 15708 15708 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:37:18.155 21818 21818 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:37:19.211 21818 21818 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 22:53:32.623 1991 1991 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 22:53:33.526 1991 1991 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-13 23:53:13.118 11189 11189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-13 23:53:14.135 11189 11189 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-13 23:53:15.837 11189 11189 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-13 23:53:15.838 11189 11189 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-14 00:54:03.275 31782 31782 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 00:54:03.902 31782 31782 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-14 00:54:04.993 31782 31782 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-14 00:54:04.993 31782 31782 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-14 01:53:13.102 7643 7643 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 01:53:14.027 7643 7643 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 02:58:13.246 10283 10283 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 02:58:14.254 10283 10283 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 03:29:57.192 12629 12629 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 03:29:57.921 12629 12629 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 07:53:11.174 21356 21356 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 07:53:13.844 21356 21356 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 08:30:42.640 8378 8378 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 08:30:43.699 8378 8378 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 08:31:18.395 9377 9377 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 08:31:19.493 9377 9377 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 08:54:14.962 21755 21755 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 08:54:16.996 21755 21755 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 09:53:11.797 19976 19976 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 09:53:15.226 19976 19976 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 09:54:51.943 24166 24166 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 09:54:53.281 24166 24166 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 09:58:19.586 32673 32673 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 09:58:20.680 32673 32673 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 10:03:38.578 5326 5326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 10:03:40.273 5326 5326 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 10:12:31.198 9757 9757 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 10:12:32.633 9757 9757 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 10:29:17.114 19874 19874 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 10:29:20.230 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-14 10:53:14.347 4469 4469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 10:53:15.355 4469 4469 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 11:27:53.853 11495 11495 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 11:27:54.649 11495 11495 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 11:53:14.064 25564 25564 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 11:53:15.318 25564 25564 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-14 11:53:16.640 25564 25564 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-14 11:53:16.640 25564 25564 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-14 12:53:10.990 9744 9744 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 12:53:11.626 9744 9744 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-14 12:53:12.756 9744 9744 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-14 12:53:12.756 9744 9744 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-14 13:31:59.215 8622 8622 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 13:32:00.454 8622 8622 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 13:32:02.164 8622 8622 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-14 13:32:02.165 8622 8622 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-14 13:53:27.364 18306 18306 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 13:53:28.379 18306 18306 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 14:53:23.430 19585 19585 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 14:53:24.362 19585 19585 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-14 14:53:25.261 19585 19585 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-14 15:53:53.916 10423 10423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 15:53:55.363 10423 10423 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 16:53:55.258 5369 5369 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 16:53:56.518 5369 5369 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 17:53:56.246 1809 1809 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 17:53:58.631 1809 1809 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 18:32:33.605 10384 10384 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 18:32:34.547 10384 10384 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 19:48:52.526 20337 20337 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 19:48:53.196 20337 20337 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-14 19:48:54.326 20337 20337 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-14 20:18:23.063 23336 23336 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 20:18:24.027 23336 23336 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 20:53:23.720 31728 31728 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 20:53:26.248 31728 31728 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 21:02:35.542 9995 9995 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 21:02:37.270 9995 9995 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 21:17:50.571 31606 31606 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 21:17:51.554 31606 31606 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 23:11:05.872 27370 27370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 23:11:09.188 27370 27370 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 23:11:29.181 28370 28370 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 23:11:32.555 28370 28370 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 23:53:12.200 20834 20834 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-14 23:53:13.640 20834 20834 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-14 23:53:15.365 20834 20834 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-14 23:53:15.366 20834 20834 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-15 09:53:14.621 543 543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 09:53:16.249 543 543 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:21:33.065 5882 5882 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 11:21:33.844 5882 5882 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 11:21:35.061 5882 5882 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-15 11:53:18.642 19200 19200 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 11:53:21.020 19200 19200 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:16:29.855 16074 16074 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:16:31.165 16074 16074 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 12:16:32.396 16074 16074 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 12:16:32.398 16074 16074 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-15 12:17:34.612 17872 17872 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:17:36.066 17872 17872 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:20:34.608 24460 24460 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:20:35.758 24460 24460 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:24:35.630 30730 30730 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:24:37.479 30730 30730 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:24:45.286 31026 31026 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:24:45.890 31026 31026 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:25:24.040 31864 31864 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:25:26.291 31864 31864 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:32:34.574 4432 4432 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:32:35.827 4432 4432 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:48:34.791 11091 11091 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:48:36.063 11091 11091 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:53:28.707 13482 13482 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 12:53:30.724 13482 13482 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:20:34.577 5907 5907 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 13:20:35.658 5907 5907 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:20:36.992 5907 5907 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 13:20:36.992 5907 5907 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-15 13:54:31.140 22297 22297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 13:54:35.405 22297 22297 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-15 14:24:42.267 15154 15154 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 14:24:44.401 15154 15154 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:24:46.225 15154 15154 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 14:24:46.226 15154 15154 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-15 14:54:40.796 27326 27326 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 14:54:42.370 27326 27326 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-15 14:54:43.732 27326 27326 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 14:54:43.732 27326 27326 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-15 15:05:41.787 4455 4455 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 15:05:42.406 4455 4455 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-15 15:05:43.527 4455 4455 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 15:05:43.528 4455 4455 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-15 15:53:11.359 16900 16900 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 15:53:11.999 16900 16900 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 15:53:13.096 16900 16900 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-15 15:53:13.097 16900 16900 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-15 16:32:37.904 12611 12611 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 16:32:39.908 12611 12611 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:53:43.947 21970 21970 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 16:53:44.887 21970 21970 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:53:46.315 21970 21970 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 16:53:46.315 21970 21970 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-15 17:54:39.299 11639 11639 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 17:54:40.277 11639 11639 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:54:41.692 11639 11639 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 17:54:41.693 11639 11639 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-15 18:22:48.656 21507 21507 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 18:22:50.035 21507 21507 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:47:52.888 6683 6683 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 18:47:56.052 6683 6683 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:53:15.940 18889 18889 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 18:53:17.991 18889 18889 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:18:46.312 13708 13708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:18:54.481 13708 13708 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:24:23.837 21246 21246 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:24:29.117 21246 21246 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:39:22.351 10122 10122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:39:24.822 10122 10122 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:40:09.806 12708 12708 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 22:40:12.216 12708 12708 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:20:42.192 15766 15766 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 23:20:43.003 15766 15766 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:20:44.167 15766 15766 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-15 23:20:44.168 15766 15766 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-15 23:39:11.032 28733 28733 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 23:39:12.111 28733 28733 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:33.719 9805 9805 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-15 23:53:35.344 9805 9805 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:07:29.070 16492 16492 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 00:07:30.825 16492 16492 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:23:44.348 21038 21038 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 01:23:46.238 21038 21038 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:55:29.354 23789 23789 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 01:55:30.192 23789 23789 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:55:46.591 31980 31980 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 03:55:47.598 31980 31980 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:13:19.229 8989 8989 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 04:13:20.003 8989 8989 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 04:15:54.585 9881 9881 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 04:15:55.308 9881 9881 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:53:11.035 21919 21919 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 05:53:11.737 21919 21919 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 05:53:12.962 21919 21919 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-16 06:19:52.549 25354 25354 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 06:19:53.243 25354 25354 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:23:41.460 26034 26034 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 06:23:42.196 26034 26034 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:57:27.876 30568 30568 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 06:57:28.905 30568 30568 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:00:17.655 16545 16545 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 08:00:20.880 16545 16545 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-16 08:24:55.046 18151 18151 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 08:24:55.641 18151 18151 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:11.362 20717 20717 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 08:53:11.828 20717 20717 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-16 09:32:33.335 29751 29751 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 09:32:33.886 29751 29751 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:43:43.950 9742 9742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 09:43:44.364 9742 9742 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-16 09:43:45.254 9742 9742 W com.mbwhatsapp: type=1400 audit(0.0:2849075): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 09:43:45.255 9742 9742 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-16 10:53:11.527 30425 30425 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 10:53:12.243 30425 30425 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:53:06.818 17097 17097 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 11:53:07.876 17097 17097 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:53:11.469 16774 16774 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 12:53:11.983 16774 16774 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 12:53:12.911 16774 16774 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-16 12:59:14.606 23325 23325 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 12:59:15.858 23325 23325 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:12:51.533 3743 3743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:12:52.739 3743 3743 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:19:57.087 18033 18033 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:19:57.596 18033 18033 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 13:19:58.691 18033 18033 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-16 13:24:31.348 19872 19872 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:24:31.897 19872 19872 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:25:27.718 21858 21858 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:25:28.307 21858 21858 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:26:43.329 24949 24949 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:26:44.417 24949 24949 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:27:18.605 26877 26877 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:27:19.455 26877 26877 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:27:51.006 28586 28586 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:27:51.692 28586 28586 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:38:34.231 8195 8195 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:38:35.177 8195 8195 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:38:37.603 8195 8195 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-16 13:46:18.442 14399 14399 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:46:19.166 14399 14399 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-16 13:53:11.910 21168 21168 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 13:53:15.509 21168 21168 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:08:22.226 6617 6617 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 14:08:22.994 6617 6617 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:53:08.679 21346 21346 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 14:53:09.430 21346 21346 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-16 16:03:20.713 13605 13605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 16:03:21.548 13605 13605 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:22:27.513 22934 22934 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 16:22:28.074 22934 22934 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:22:29.243 22934 22934 W com.mbwhatsapp: type=1400 audit(0.0:36890): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-16 16:53:08.793 2728 2728 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 16:53:09.599 2728 2728 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:26.226 29600 29600 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 17:53:26.740 29600 29600 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:27.551 29600 29600 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-16 18:18:12.598 15620 15620 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:18:13.048 15620 15620 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-16 18:53:46.261 28562 28562 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 18:53:46.784 28562 28562 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:03:48.673 5045 5045 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 19:03:49.324 5045 5045 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:04:00.670 6325 6325 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 21:04:06.930 6325 6325 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:28:12.951 20703 20703 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 21:28:13.547 20703 20703 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:08.873 8101 8101 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 22:53:09.347 8101 8101 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 22:53:10.260 8101 8101 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-16 23:10:11.567 17191 17191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 23:10:12.257 17191 17191 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:28:53.951 28638 28638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 23:28:54.625 28638 28638 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:08.792 4924 4924 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-16 23:53:09.170 4924 4924 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:49.873 4057 4057 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 00:22:50.866 4057 4057 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 00:22:52.769 4057 4057 W com.mbwhatsapp: Verification of void X.3gG.run()
took 113.360ms (21065.60 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-17 00:29:27.951 8816 8816 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 00:29:29.417 8816 8816 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:53:57.763 18972 18972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 00:53:58.480 18972 18972 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:13:43.884 27247 27247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 01:13:44.678 27247 27247 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 01:13:45.731 27247 27247 W com.mbwhatsapp: type=1400 audit(0.0:184399): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 01:13:45.735 27247 27247 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-17 09:10:40.706 5742 5742 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 09:10:47.362 5742 5742 W com.mbwhatsapp: Verification of void
X.0yS.<clinit>() took 168.416ms (29.69 bytecodes/s) (1336B approximate peak alloc)
04-17 09:10:47.609 5742 5742 W com.mbwhatsapp: Verification of void
X.0yS.attachBaseContext(android.content.Context) took 128.366ms (802.39
bytecodes/s) (3168B approximate peak alloc)
04-17 09:10:48.396 5742 5742 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-17 09:10:48.418 5742 5742 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-17 09:10:48.419 5742 5742 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1131)
04-17 09:10:48.419 5742 5742 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1085)
04-17 09:10:48.427 5742 5742 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1008)
04-17 09:10:48.427 5742 5742 W System.err: at
java.lang.System.loadLibrary(System.java:1664)
04-17 09:10:48.427 5742 5742 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-17 09:10:48.427 5742 5742 W System.err: at
java.lang.Class.newInstance(Native Method)
04-17 09:10:48.427 5742 5742 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-17 09:10:48.427 5742 5742 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-17 09:10:48.427 5742 5742 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1208)
04-17 09:10:48.427 5742 5742 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1256)
04-17 09:10:48.427 5742 5742 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7163)
04-17 09:10:48.427 5742 5742 W System.err: at
android.app.ActivityThread.access$1500(ActivityThread.java:265)
04-17 09:10:48.427 5742 5742 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2152)
04-17 09:10:48.427 5742 5742 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-17 09:10:48.428 5742 5742 W System.err: at
android.os.Looper.loop(Looper.java:257)
04-17 09:10:48.428 5742 5742 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8192)
04-17 09:10:48.428 5742 5742 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-17 09:10:48.428 5742 5742 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626)
04-17 09:10:48.428 5742 5742 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
04-17 09:10:49.002 5742 5742 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-17 09:11:00.370 5742 5742 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-17 09:11:00.371 5742 5742 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
04-17 09:11:01.550 5742 5742 W com.mbwhatsapp: Verification of void X.3gG.run()
took 770.537ms (3099.14 bytecodes/s) (73648B approximate peak alloc)
04-17 09:11:02.386 5742 5742 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-17 09:11:02.380 5742 5742 W com.mbwhatsapp: type=1400 audit(0.0:1480): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:11:02.488 5742 5742 W com.mbwhatsapp: type=1400 audit(0.0:1481): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:11:02.600 5742 5742 W com.mbwhatsapp: type=1400 audit(0.0:1484): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-3" ino=17034 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:11:03.924 5742 5742 W com.mbwhatsapp: type=1400 audit(0.0:1489): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-3" ino=17034 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:11:03.924 5742 5742 W com.mbwhatsapp: type=1400 audit(0.0:1490): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-3" ino=17034 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:11:03.924 5742 5742 W com.mbwhatsapp: type=1400 audit(0.0:1491): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libwhatsapp.so"
dev="dm-3" ino=17034 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:11:07.444 5742 7422 W com.mbwhatsapp: Class X.2rL failed lock
verification and will run slower.
04-17 09:11:07.444 5742 7422 W com.mbwhatsapp: Common causes for lock
verification issues are non-optimized dex code
04-17 09:11:07.444 5742 7422 W com.mbwhatsapp: and incorrect proguard
optimizations.
04-17 09:11:10.401 5742 7515 W WM-Processor: Didn't find WorkSpec for id
WorkGenerationalId(workSpecId=68d850aa-a0b3-4341-abbb-557e95e3afa4, generation=0)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: Write failure
04-17 09:12:20.547 5742 8077 W FastPrintWriter: java.io.IOException: write
failed: EPIPE (Broken pipe)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.IoBridge.write(IoBridge.java:540)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
java.io.FileOutputStream.write(FileOutputStream.java:398)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.flushBytesLocked(FastPrintWriter.java:354
)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.flushLocked(FastPrintWriter.java:377)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.appendLocked(FastPrintWriter.java:322)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
com.android.internal.util.FastPrintWriter.print(FastPrintWriter.java:499)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
java.io.PrintWriter.println(PrintWriter.java:739)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.util.PrintWriterPrinter.println(PrintWriterPrinter.java:38)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.util.PrefixPrinter.println(PrefixPrinter.java:48)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteConnection$OperationLog.dump(SQLiteConnection.java:16
78)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteConnection.dumpUnsafe(SQLiteConnection.java:1293)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteConnection.dump(SQLiteConnection.java:1268)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteConnectionPool.dump(SQLiteConnectionPool.java:1149)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteDatabase.dump(SQLiteDatabase.java:2337)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteDatabase.dumpAll(SQLiteDatabase.java:2320)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.database.sqlite.SQLiteDebug.dump(SQLiteDebug.java:218)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.dumpDatabaseInfo(ActivityThread.java:1
755)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.dumpDbInfo(ActivityThread.java:1786)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.app.IApplicationThread$Stub.onTransact(IApplicationThread.java:1240)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.app.ActivityThread$ApplicationThread.onTransact(ActivityThread.java:1978)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.os.Binder.execTransactInternal(Binder.java:1159)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
android.os.Binder.execTransact(Binder.java:1123)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: Caused by:
android.system.ErrnoException: write failed: EPIPE (Broken pipe)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.Linux.writeBytes(Native Method)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.Linux.write(Linux.java:293)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.ForwardingOs.write(ForwardingOs.java:240)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.BlockGuardOs.write(BlockGuardOs.java:418)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.ForwardingOs.write(ForwardingOs.java:240)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: at
libcore.io.IoBridge.write(IoBridge.java:535)
04-17 09:12:20.547 5742 8077 W FastPrintWriter: ... 21 more
04-17 09:23:14.955 21888 21888 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 09:23:15.401 21888 21888 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 09:23:16.524 21888 21888 W com.mbwhatsapp: type=1400 audit(0.0:19784): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 09:23:16.528 21888 21888 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-17 09:23:16.540 21888 21888 W com.mbwhatsapp: type=1400 audit(0.0:19785): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-17 09:42:17.851 28411 28411 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 09:42:18.431 28411 28411 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 10:04:50.006 3926 3926 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 10:04:50.743 3926 3926 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 10:04:51.880 3926 3926 W com.mbwhatsapp: type=1400 audit(0.0:38642): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-17 10:11:21.582 7605 7605 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 10:11:22.420 7605 7605 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:04:50.744 16362 16362 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 12:04:51.673 16362 16362 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:04:52.780 16362 16362 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-17 12:25:36.182 28535 28535 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 12:25:37.066 28535 28535 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 12:25:40.280 28535 28535 W com.mbwhatsapp: type=1400 audit(0.0:79860): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-17 12:31:44.165 1972 1972 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 12:31:45.665 1972 1972 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-17 12:57:50.038 14697 14697 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 12:57:50.821 14697 14697 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:04:49.840 19817 19817 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 13:04:50.662 19817 19817 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 13:04:51.632 19817 19817 W com.mbwhatsapp: type=1400 audit(0.0:108095): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 13:04:51.637 19817 19817 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-17 14:04:50.138 7393 7393 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 14:04:50.641 7393 7393 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 14:04:53.047 7393 7393 W com.mbwhatsapp: type=1400 audit(0.0:111122): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 14:04:53.103 7393 7393 W com.mbwhatsapp: type=1400 audit(0.0:111123): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-17 15:06:42.314 26439 26439 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 15:06:43.825 26439 26439 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:06:45.003 26439 26439 W com.mbwhatsapp: Verification of void X.3gG.run()
took 175.572ms (13601.21 bytecodes/s) (73648B approximate peak alloc)
04-17 15:32:46.565 10920 10920 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 15:32:47.285 10920 10920 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-17 16:06:42.487 21538 21538 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 16:06:45.278 21538 21538 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:04:49.944 22543 22543 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 17:04:50.849 22543 22543 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:22:55.375 32489 32489 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 17:22:56.024 32489 32489 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:30:59.637 6735 6735 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 17:31:00.236 6735 6735 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 17:31:01.036 6735 6735 W com.mbwhatsapp: type=1400 audit(0.0:188583): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-17 17:59:03.054 23577 23577 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 17:59:03.680 23577 23577 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:34:51.532 2499 2499 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 18:34:53.846 2499 2499 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:51:59.561 9876 9876 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 18:52:01.103 9876 9876 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:06:01.218 15891 15891 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 19:06:03.609 15891 15891 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-17 19:12:27.949 21238 21238 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 19:12:28.880 21238 21238 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:16:13.837 25456 25456 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 19:16:14.392 25456 25456 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 20:05:30.215 31254 31254 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 20:05:30.758 31254 31254 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:04:49.822 21057 21057 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 21:04:50.439 21057 21057 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 21:04:51.387 21057 21057 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
--------- beginning of main
04-17 21:14:47.752 26268 26268 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 21:14:49.261 26268 26268 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:29:52.569 9228 9228 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 21:29:53.249 9228 9228 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-17 21:43:20.862 26423 26423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 21:43:21.368 26423 26423 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-17 21:43:21.770 26423 26423 W com.mbwhatsapp: type=1400 audit(0.0:275971): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-17 21:43:21.778 26423 26423 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-17 21:43:52.526 27594 27594 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 21:43:53.016 27594 27594 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:04:49.879 5723 5723 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 22:04:50.770 5723 5723 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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-17 22:04:51.692 5723 5723 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-17 22:33:53.352 15745 15745 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-17 22:33:53.745 15745 15745 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:03:10.738 8338 8338 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 12:03:11.232 8338 8338 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:03:12.070 8338 8338 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-18 12:03:14.076 8338 8413 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-18 12:03:14.393 8338 8403 E PlayCore: UID: [10884] PID: [8338]
StandardIntegrity : Phonesky is not installed.
04-18 13:05:00.933 29216 29216 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 13:05:02.260 29216 29216 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:05:03.584 29216 29216 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-18 14:04:57.199 29107 29107 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:04:58.023 29107 29107 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:04:59.823 29107 29107 W com.mbwhatsapp: Verification of void X.3gG.run()
took 103.302ms (23116.48 bytecodes/s) (73648B approximate peak alloc)
04-18 14:04:59.910 29107 29107 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-18 14:12:39.268 2829 2829 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:12:39.868 2829 2829 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:18:42.955 8134 8134 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:18:43.575 8134 8134 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 14:47:39.375 18404 18404 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 14:47:40.052 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.
04-18 14:47:41.185 18404 18404 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-18 15:24:05.584 9382 9382 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 15:24:06.635 9382 9382 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:40:32.528 13765 13765 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 15:40:32.983 13765 13765 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-18 16:03:51.574 21433 21433 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 16:03:54.426 21433 21433 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:26:18.346 28213 28213 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 16:26:19.223 28213 28213 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:36:21.905 2265 2265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 16:36:22.455 2265 2265 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:07:15.011 28890 28890 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 17:07:15.822 28890 28890 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 17:27:22.514 29769 29769 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 17:27:23.125 29769 29769 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 17:27:24.301 29769 29769 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-18 17:49:47.291 10899 10899 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 17:49:47.897 10899 10899 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-18 17:49:49.205 10899 10899 W com.mbwhatsapp: type=1400 audit(0.0:492934): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-18 18:04:50.640 20693 20693 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:04:51.648 20693 20693 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:04:53.025 20693 20693 W com.mbwhatsapp: type=1400 audit(0.0:495788): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-18 18:17:50.793 29770 29770 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:17:51.376 29770 29770 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:33:20.769 6365 6365 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 18:33:21.450 6365 6365 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:04:49.796 30743 30743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:04:50.468 30743 30743 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:04:51.733 30743 30743 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-18 20:05:06.904 31510 31510 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 20:05:09.355 31510 31510 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:07:03.705 7185 7185 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 21:07:07.441 7185 7185 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:07:51.739 8142 8142 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 21:07:55.047 8142 8142 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:26:51.461 22555 22555 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 21:26:52.032 22555 22555 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:32:02.745 26692 26692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 21:32:03.960 26692 26692 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 22:04:59.419 23974 23974 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 22:05:00.220 23974 23974 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 23:06:01.885 3294 3294 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-18 23:06:02.344 3294 3294 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:06:03.049 3294 3294 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-19 00:06:03.436 5219 5219 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 00:06:04.028 5219 5219 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:05:59.116 10264 10264 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 02:05:59.672 10264 10264 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-19 02:06:00.455 10264 10264 W com.mbwhatsapp: type=1400 audit(0.0:567797): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
--------- beginning of main
04-19 02:06:00.471 10264 10264 W com.mbwhatsapp: type=1400 audit(0.0:567798): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libvlc.so" dev="dm-
3" ino=17040 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 06:04:50.041 22488 22488 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 06:04:50.399 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
04-19 10:15:00.265 4011 4011 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 10:15:02.309 4011 4011 W com.mbwhatsapp: Verification of void
X.0yS.attachBaseContext(android.content.Context) took 197.149ms (522.45
bytecodes/s) (3168B approximate peak alloc)
04-19 10:15:03.083 4011 4011 W System.err: java.lang.ClassNotFoundException:
mbmodsd.mbmodsw.ui.views.btn.BtnBK
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.Runtime.nativeLoad(Native Method)
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.Runtime.nativeLoad(Runtime.java:1131)
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1085)
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.Runtime.loadLibrary0(Runtime.java:1008)
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.System.loadLibrary(System.java:1664)
04-19 10:15:03.084 4011 4011 W System.err: at arm.EpicVm.<clinit>(Unknown
Source:2)
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.Class.newInstance(Native Method)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
04-19 10:15:03.084 4011 4011 W System.err: at
androidx.core.app.CoreComponentFactory.instantiateApplication(Unknown Source:0)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.Instrumentation.newApplication(Instrumentation.java:1208)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.LoadedApk.makeApplication(LoadedApk.java:1256)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.ActivityThread.handleBindApplication(ActivityThread.java:7163)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.ActivityThread.access$1500(ActivityThread.java:265)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2152)
04-19 10:15:03.084 4011 4011 W System.err: at
android.os.Handler.dispatchMessage(Handler.java:106)
04-19 10:15:03.084 4011 4011 W System.err: at
android.os.Looper.loop(Looper.java:257)
04-19 10:15:03.084 4011 4011 W System.err: at
android.app.ActivityThread.main(ActivityThread.java:8192)
04-19 10:15:03.084 4011 4011 W System.err: at
java.lang.reflect.Method.invoke(Native Method)
04-19 10:15:03.084 4011 4011 W System.err: at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626)
04-19 10:15:03.084 4011 4011 W System.err: at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
04-19 10:15:03.556 4011 4011 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 10:15:04.082 4011 4011 W ContextImpl: Failed to ensure
/dev/null/Android/media/com.mbwhatsapp: java.lang.SecurityException: Invalid mkdirs
path: /dev/null/Android/media/com.mbwhatsapp is not a known app path.
04-19 10:15:09.600 4011 4011 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-19 10:15:09.601 4011 4011 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-19 14:59:47.104 8454 8454 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 14:59:51.320 8454 8454 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:51:35.892 5665 5665 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 16:51:37.122 5665 5665 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 16:51:39.703 5665 5665 W com.mbwhatsapp: Verification of void X.3gG.run()
took 124.429ms (19191.67 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-19 18:19:57.738 32678 32678 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 18:19:58.998 32678 32678 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:20:00.322 32678 32678 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-19 18:23:15.052 4686 4686 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 18:23:16.744 4686 4686 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 18:36:24.582 12059 12059 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 18:36:25.624 12059 12059 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 18:36:29.392 12059 12059 W com.mbwhatsapp: Verification of void X.3gG.run()
took 172.066ms (13878.34 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-19 18:41:31.011 15395 15395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 18:41:31.649 15395 15395 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 18:41:32.665 15395 15395 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-19 18:59:34.073 26068 26068 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 18:59:34.658 26068 26068 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 19:09:34.742 2540 2540 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 19:09:35.790 2540 2540 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 20:10:54.776 23743 23743 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 20:10:56.198 23743 23743 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 20:10:58.506 23743 23743 W com.mbwhatsapp: type=1400 audit(0.0:79016): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so"
dev="dm-3" ino=17049 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-19 20:10:58.511 23743 23743 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-19 21:09:33.788 9206 9206 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 21:09:34.989 9206 9206 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 21:09:36.503 9206 9206 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
04-19 22:09:53.470 21080 21080 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-19 22:09:55.610 21080 21080 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:10:03.015 19138 19138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 05:10:05.151 19138 19138 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:18:45.843 21191 21191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 05:18:51.047 21191 21191 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 05:18:51.732 21191 21191 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-20 10:45:38.630 19676 19676 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 10:45:45.318 19676 19676 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:52.208 28787 28787 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 13:09:52.860 28787 28787 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 13:09:53.996 28787 28787 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-20 14:09:52.224 19760 19760 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 14:09:53.191 19760 19760 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:09:55.432 19760 19760 W com.mbwhatsapp: Verification of void X.3gG.run()
took 256.209ms (9320.49 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
--------- beginning of main
04-20 15:23:32.919 15635 15635 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 15:23:33.635 15635 15635 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:47:05.760 19395 19395 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 15:47:06.186 19395 19395 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-20 17:37:30.150 24671 24671 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 17:37:30.553 24671 24671 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:28:31.783 3413 3413 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 18:28:33.844 3413 3413 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:34.082 25692 25692 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 19:09:35.302 25692 25692 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:24:41.445 32391 32391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 19:24:42.618 32391 32391 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 20:11:34.066 15066 15066 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 20:11:36.251 15066 15066 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:36:48.411 30958 30958 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 21:36:53.546 30958 30958 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:33.951 16480 16480 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 22:09:34.543 16480 16480 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 23:11:10.443 25937 25937 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-20 23:11:11.108 25937 25937 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 23:11:12.249 25937 25937 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-21 06:12:13.571 27009 27009 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 06:12:15.089 27009 27009 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:09:48.170 7509 7509 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 07:09:48.700 7509 7509 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:30:07.608 12286 12286 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 07:30:07.971 12286 12286 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:39:51.687 15247 15247 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 07:39:52.186 15247 15247 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 07:58:20.871 18619 18619 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 07:58:22.099 18619 18619 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 08:06:51.844 21391 21391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 08:06:53.366 21391 21391 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 09:09:31.603 8189 8189 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 09:09:32.228 8189 8189 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-21 10:09:31.578 23201 23201 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 10:09:32.166 23201 23201 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:09:32.037 12827 12827 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 11:09:32.810 12827 12827 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:30:35.770 28474 28474 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 11:30:36.998 28474 28474 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:42:18.830 4947 4947 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 11:42:19.500 4947 4947 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 11:42:20.380 4947 4947 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-21 11:42:21.817 4947 5034 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-21 11:42:22.196 4947 5045 E PlayCore: UID: [10884] PID: [4947]
StandardIntegrity : Phonesky is not installed.
04-21 12:09:31.776 22288 22288 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 12:09:32.784 22288 22288 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 12:40:29.662 15638 15638 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 12:40:30.626 15638 15638 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:01:30.867 27239 27239 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 13:01:31.447 27239 27239 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:09:32.527 320 320 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 13:09:33.255 320 320 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:25:38.565 15265 15265 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 13:25:39.258 15265 15265 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 13:25:40.724 15265 15265 W com.mbwhatsapp: Verification of void X.3gG.run()
took 101.770ms (23464.46 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-21 14:09:31.632 9305 9305 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 14:09:32.307 9305 9305 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:14:12.209 11702 11702 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 14:14:12.876 11702 11702 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-21 14:24:19.502 22490 22490 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 14:24:20.462 22490 22490 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:40:25.193 7965 7965 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 14:40:27.005 7965 7965 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:09:32.094 20013 20013 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 15:09:33.024 20013 20013 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:32:08.406 28391 28391 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 15:32:11.331 28391 28391 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:37:28.831 4469 4469 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 15:37:30.049 4469 4469 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:37.659 16011 16011 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:09:38.191 16011 16011 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:39:08.002 30179 30179 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 17:39:08.498 30179 30179 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:10:14.117 24350 24350 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:10:21.066 24350 24350 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:15:58.982 29826 29826 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:16:03.419 29826 29826 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:16:25.238 30402 30402 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 18:16:32.933 30402 30402 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:10:16.233 19031 19031 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 19:10:17.580 19031 19031 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:32.047 9439 9439 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:09:33.149 9439 9439 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:15:37.014 11423 11423 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 20:15:37.680 11423 11423 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:15:38.992 11423 11423 W com.mbwhatsapp: Verification of void X.3gG.run()
took 105.377ms (22661.33 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-21 21:09:31.773 2191 2191 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:09:32.883 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.
04-21 21:09:34.325 2191 2191 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-21 21:34:36.356 13505 13505 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 21:34:36.948 13505 13505 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:41:36.764 11087 11087 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-21 22:41:37.318 11087 11087 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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:41:38.095 11087 11087 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-22 00:09:44.357 16613 16613 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 00:09:44.890 16613 16613 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 01:09:44.200 18579 18579 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 01:09:44.592 18579 18579 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 02:10:56.378 24164 24164 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 02:10:57.148 24164 24164 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 02:53:03.876 26504 26504 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 02:53:04.211 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
04-22 02:59:06.220 28305 28305 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 02:59:06.637 28305 28305 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 03:44:24.886 31624 31624 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 03:44:25.311 31624 31624 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 05:09:37.052 13082 13082 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 05:09:37.770 13082 13082 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 06:09:31.829 25243 25243 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 06:09:32.540 25243 25243 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 11:03:52.667 6441 6441 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 11:03:55.320 6441 6441 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 11:03:59.124 6441 6441 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-22 11:03:59.125 6441 6441 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-22 11:27:14.453 22689 22689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 11:27:16.434 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.
--------- beginning of main
04-22 11:56:23.202 4122 4122 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 11:56:23.604 4122 4122 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-22 13:31:39.171 3443 3443 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:31:40.275 3443 3443 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:33:07.171 6736 6736 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:33:07.850 6736 6736 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:38:33.175 9156 9156 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:38:34.489 9156 9156 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:39:23.810 9978 9978 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:39:24.698 9978 9978 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:42:27.819 12367 12367 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 13:42:31.617 12367 12367 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:08:35.985 22724 22724 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:08:36.812 22724 22724 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:31.754 24297 24297 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:09:32.800 24297 24297 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:13:02.859 25192 25192 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:13:03.620 25192 25192 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-22 14:14:05.866 26061 26061 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:14:07.040 26061 26061 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:14:13.861 26670 26670 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:14:14.814 26670 26670 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:14:40.251 27363 27363 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:14:40.855 27363 27363 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:15:54.739 28681 28681 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 14:15:55.206 28681 28681 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-22 15:16:57.326 27961 27961 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 15:16:59.281 27961 27961 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 15:17:03.500 27961 27961 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
--------- beginning of main
04-22 16:04:36.867 11146 11146 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 16:04:37.529 11146 11146 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:27:41.069 29689 29689 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 16:27:42.085 29689 29689 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:39:47.284 11499 11499 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 16:39:47.947 11499 11499 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:31.822 21014 21014 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 18:09:32.683 21014 21014 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:17:38.850 1353 1353 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 18:17:39.764 1353 1353 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:20:03.942 5067 5067 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 18:20:08.973 5067 5067 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:31.578 14813 14813 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 19:09:32.307 14813 14813 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:12:16.062 17754 17754 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 19:12:16.692 17754 17754 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:13:25.016 19266 19266 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 19:13:25.546 19266 19266 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31:20.373 28364 28364 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 19:31:20.996 28364 28364 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:20:38.339 17596 17596 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 20:20:44.257 17596 17596 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-22 20:41:09.031 31095 31095 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 20:41:09.985 31095 31095 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
04-22 20:41:11.576 31095 31095 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-22 21:05:23.482 9549 9549 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 21:05:23.934 9549 9549 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 21:05:24.941 9549 9549 W linker : Warning:
"/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libc++_shared.so" unused
DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)
--------- beginning of main
04-22 22:15:19.312 14120 14120 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 22:15:19.885 14120 14120 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:41:17.385 16280 16280 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 22:41:17.825 16280 16280 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-22 23:05:41.665 17885 17885 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-22 23:05:42.061 17885 17885 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:10:24.515 22587 22587 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 00:10:24.984 22587 22587 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:57.110 30584 30584 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 01:09:57.756 30584 30584 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:07:37.938 2579 2579 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 02:07:38.710 2579 2579 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:14.544 6715 6715 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 03:12:15.420 6715 6715 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-23 04:10:07.150 13642 13642 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 04:10:08.500 13642 13642 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:37:28.616 23240 23240 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 05:37:29.465 23240 23240 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:57:02.541 28113 28113 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 05:57:03.657 28113 28113 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:24:04.517 32497 32497 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 06:24:24.780 32497 32497 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:03:02.296 5515 5515 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 11:03:06.973 5515 5515 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
04-23 11:03:18.587 5515 5515 W com.mbwhatsapp: type=1400 audit(0.0:729303): avc:
granted { execute } for
path="/data/data/com.mbwhatsapp/files/decompressed/libs.spk.zst/libcurve25519.so"
dev="dm-3" ino=17039 scontext=u:r:untrusted_app:s0:c116,c259,c512,c768
tcontext=u:object_r:app_data_file:s0:c116,c259,c512,c768 tclass=file
app=com.mbwhatsapp
04-23 11:30:52.877 17985 17985 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 11:31:05.506 17985 17985 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:09:32.889 23855 23855 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 12:09:33.397 23855 23855 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.
--------- beginning of main
--------- beginning of main
04-23 13:19:20.918 16593 16593 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 13:19:22.273 16593 16593 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:18:14.669 6000 6000 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 14:18:18.081 6000 6000 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:50.686 17340 17340 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:03:51.334 17340 17340 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 16:03:53.049 17340 17340 W com.mbwhatsapp: Verification of void X.3gG.run()
took 135.875ms (17574.95 bytecodes/s) (73648B approximate peak alloc)
--------- beginning of main
04-23 16:09:29.590 21215 21215 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:09:30.495 21215 21215 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:31.570 21215 21215 W com.mbwhatsapp: Verification of void X.3gG.run()
took 188.026ms (12700.36 bytecodes/s) (73648B approximate peak alloc)
04-23 16:46:44.983 27988 27988 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 16:46:47.681 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.
--------- beginning of main
04-23 17:04:11.863 8138 8138 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 17:04:12.394 8138 8138 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:17:19.814 13725 13725 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 17:17:20.398 13725 13725 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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:44:24.198 28655 28655 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-23 17:44:27.150 28655 28655 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 17:44:33.308 28655 28655 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/OpenSSLSocketImpl;->setUseSessionTickets(Z)V (greylist-
max-q,core-platform-api, reflection, denied)
04-23 17:44:33.308 28655 28655 W com.mbwhatsapp: Accessing hidden method
Lcom/android/org/conscrypt/AbstractConscryptSocket;->setUseSessionTickets(Z)V
(greylist-max-q, reflection, denied)
--------- beginning of main
04-24 15:22:14.985 29321 29321 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 15:22:17.135 29321 29321 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 15:22:22.028 29593 29593 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 15:22:24.830 29593 29593 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this 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 15:22:33.766 29593 29593 E libc : Access denied finding property
"ro.vendor.scroll.preobtain.enable"
04-24 15:22:34.463 29593 29593 E com.mbwhatsapp: Invalid ID 0x00000000.
04-24 15:22:43.589 29593 29593 E ArmVmp : Match on catch block at 0x0a in for
0x139
04-24 15:22:46.748 29593 29593 E com.mbwhatsapp: Invalid ID 0x00000000.
04-24 15:22:46.750 29593 29593 E com.mbwhatsapp: Invalid ID 0x00000000.
04-24 15:22:46.753 29593 29593 E com.mbwhatsapp: Invalid ID 0x00000000.
04-24 15:22:46.759 29593 29593 E com.mbwhatsapp: Invalid ID 0x00000000.
04-24 15:23:05.855 29593 30593 E ion : ioctl c0044901 failed with code -1:
Invalid argument
04-24 15:23:12.555 29593 31261 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-24 15:23:12.555 29593 31261 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-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
libcore.io.IoBridge.open(IoBridge.java:492)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
java.io.FileInputStream.<init>(FileInputStream.java:160)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at X.0nz.run(Unknown
Source:82)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
java.util.concurrent.FutureTask.run(FutureTask.java:266)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
java.lang.Thread.run(Thread.java:923)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: Caused by:
android.system.ErrnoException: open failed: ENOENT (No such file or directory)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
libcore.io.Linux.open(Native Method)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
libcore.io.ForwardingOs.open(ForwardingOs.java:166)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
libcore.io.BlockGuardOs.open(BlockGuardOs.java:254)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
libcore.io.ForwardingOs.open(ForwardingOs.java:166)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8075)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: at
libcore.io.IoBridge.open(IoBridge.java:478)
04-24 15:23:12.555 29593 31261 E ShortcutInfoCompatSaver: ... 7 more
04-24 15:23:12.670 29593 30593 E FrameEvents: updateAcquireFence: Did not find
frame.
04-24 15:23:12.713 29593 30593 E FrameEvents: updateAcquireFence: Did not find
frame.
04-24 15:23:18.034 29593 29593 E libc : Access denied finding property
"ro.vendor.scroll.preobtain.enable"
04-24 15:23:34.978 29593 29936 E PlayCore: UID: [10946] PID: [29593]
StandardIntegrity : Phonesky is not installed.
04-24 15:24:42.897 1537 1537 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 15:24:43.725 1537 1537 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you 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 15:25:20.383 3098 3098 E com.mbwhatsapp: Not starting debugger since
process cannot load the jdwp agent.
04-24 15:25:21.910 3098 3098 E CustomActivityOnCrash: IMPORTANT WARNING! You
already have an UncaughtExceptionHandler, are you sure this is correct? If you use
a custom UncaughtExceptionHandler, you must initialize it AFTER
CustomActivityOnCrash! Installing anyway, but your original handler will not be
called.