You are on page 1of 2

09-03 16:47:10.

927 1467 1596 E _V_VivoVibratorServiceImpl: VCode collect vibrator


Map={start_time=1693733909035, shock=[{intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=300,
module=com.whatsapp, pattern=-1}], end_time=1693734430927, uuid=2fc1f16d-6303-4548-
9076-b5883158530c}
09-03 18:09:55.565 1467 1596 E _V_VivoVibratorServiceImpl: VCode collect vibrator
Map={start_time=1693734431430, shock=[{intensity=145, times=300, module=null,
pattern=-1}, {intensity=145, times=350, module=com.instagram.android, pattern=-1},
{intensity=145, times=350, module=null, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}, {intensity=145, times=5,
module=com.simejikeyboard, pattern=-1}], end_time=1693739395565, uuid=2e11dafd-
c43f-4286-8edd-5361af356ec3}
09-03 20:19:31.566 3734 3831 E NPTH-TERM: do_attach:TMonitor exit flock by
traceePid=3400 die
09-03 20:19:31.566 3734 3831 E NPTH-TERM: TMonitor success waitLock
09-03 20:19:31.609 3734 3831 E NPTH-TERM: wait_inner:read alive_processes count=2
09-03 20:19:31.609 3734 3831 E NPTH-TERM: find attach tid unknown error
09-03 20:19:31.609 3734 3831 E NPTH-TERM: find none attach tid unknown error
09-03 20:19:31.636 3734 3831 E NPTH-TERM: 1693747171636: find killed=3400
09-03 20:19:31.691 3734 3831 E NPTH-TERM: found_process_died:pid=3400
09-03 20:19:32.405 3734 3831 E NPTH-TERM: wait_inner:my tracee 3400 was killed,
find next tracee:-1
09-03 20:19:32.406 3734 3831 E NPTH-TERM:
-----------------------------------------------------------
09-03 20:19:32.425 3734 3831 E NPTH-TERM: wait_inner:the worker is die, now i
will be worker
09-03 20:19:32.437 3734 3831 E NPTH-TERM: wait_inner:notify sig has been sent,
begin wait next tracee's attach request
09-03 20:19:42.638 4689 5085 E NPTH-TERM: do_attach_request:send attach sig to
tracerpid=3734 tracertid=3831
09-03 20:19:42.639 3734 3831 E NPTH-TERM: wait_inner:start handle pending attach
sig
09-03 20:19:42.639 3734 3831 E NPTH-TERM: do_attach:TMonitor start check lockFd
09-03 20:19:42.639 3734 3831 E NPTH-TERM: do_attach:TMonitor success check lockFd
09-03 20:19:42.639 4689 5085 E NPTH-TERM: do_attach_request:success handled, now
my tracerpid=3734 tracertid=3831
09-03 20:19:42.640 4689 5085 E NPTH-TERM: notify attach 3734
09-03 20:19:42.640 3734 3831 E NPTH-TERM: do_attach_request:do
check_pending_attach_request
09-03 20:19:42.643 3734 3831 E NPTH-TERM:
-----------------------------------------------------------
09-03 20:19:42.643 3734 3831 E NPTH-TERM: do_attach_request:startup new tracee
thread, old=3834
09-03 20:19:42.644 3734 3834 E NPTH-TERM: npth-tracee:thread_loop end wait
mutexlock...
09-03 20:19:42.651 3734 3834 E NPTH-TERM: npth-tracee:thread_loop end...
09-03 20:19:42.673 3734 5097 E NPTH-TERM: npth-tracee:thread_loop start...
09-03 20:19:42.687 3734 5097 E NPTH-TERM: npth-tracee:thread_loop got flock
success, lockfile
path=/data/user/0/com.ss.android.ugc.trill/files/npth/killHistory/proc/
3734/5097_lock...
09-03 20:19:42.687 3734 5097 E NPTH-TERM: npth-tracee:thread_loop start wait
mutexlock...
09-03 20:19:42.687 3734 3831 E NPTH-TERM: do_attach_request:send attach sig to
tracerpid=4689 tracertid=5085
09-03 20:19:42.687 3734 3831 E NPTH-TERM: do_attach_request:success handled, now
my tracerpid=4689 tracertid=5085
09-03 20:19:42.687 3734 3831 E NPTH-TERM: do_attach:TMonitor start flock,
traceepid=4689 traceetid=5096
09-03 20:19:42.745 4689 5085 E NPTH-TERM: do_attach:TMonitor start flock,
traceepid=3734 traceetid=5097
09-03 20:20:24.976 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.037347 0.441939 0.932959
09-03 20:21:06.109 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_Getgyro: accur 3, 0.164440 -0.313961 -0.373450
09-03 20:21:52.255 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: -0.037347 0.053469 1.121837
09-03 20:22:44.424 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.201429 0.358367 0.937347
09-03 20:29:11.696 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetMagData: accur 3, 30.631542 33.265343 19.463734
09-03 20:30:43.825 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetMagData: accur 3, 43.373417 -10.634404 5.700046
09-03 21:07:05.843 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.987449 0.037347 0.322857
09-03 21:07:47.938 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.984286 0.033163 0.337347
09-03 21:09:59.214 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.973061 0.052245 0.373469
09-03 21:11:32.385 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.970816 0.046122 0.373469
09-03 21:15:53.839 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetAccData: 0.637347 0.510306 -0.573673
09-03 21:19:10.609 954 1025 E android.hardware.sensors@2.0-service-mediatek:
MEMSIC_SetMagData: accur 3, -24.594545 36.257500 -7.737348

You might also like