Scribd
Upload
38 views7 pages

System Log Analysis for Vivo Device

The document contains a log of system events and operations related to various services such as AnalysisService and FingerprintService, detailing their initialization and connection statuses. It also includes updates on application operations and settings changes, as well as warnings and errors related to system performance and device management. Additionally, there are entries related to network statistics and audio device management, indicating ongoing system activity and potential issues.

Uploaded by

baihaqial224
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
38 views7 pages

System Log Analysis for Vivo Device

The document contains a log of system events and operations related to various services such as AnalysisService and FingerprintService, detailing their initialization and connection statuses. It also includes updates on application operations and settings changes, as well as warnings and errors related to system performance and device management. Additionally, there are entries related to network statistics and audio device management, indicating ongoing system activity and potential issues.

Uploaded by

baihaqial224
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

06-22 [Link].

053 1308 1454 I SystemServerTimingAsync:


InitThreadPoolExec:[Link]
06-22 [Link].053 1308 1454 I _V_AnalysisService: reconnect to hwbinder...
06-22 [Link].058 1308 1454 I _V_AnalysisService: hwbinder connected
06-22 [Link].585 1308 1454 I SystemServerTimingAsync:
InitThreadPoolExec:[Link]
06-22 [Link].585 1308 1454 V FingerprintService: mDaemon was null, reconnect to
fingerprint
06-22 [Link].590 1308 1454 V FingerprintService: Fingerprint HAL id: -
5476376635208806016
06-22 [Link].796 1308 1454 V FingerprintService: Enumerating user(0)
06-22 [Link].729 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link].metatrader5 changed
06-22 [Link].733 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].733 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].734 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].734 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].735 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].736 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].737 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].740 1308 1454 I SystemServerTimingAsync: InitThreadPoolExec:Update
app-ops uidState in case package [Link] changed
06-22 [Link].454 1308 2036 W _V_PackageManager: setEnabledSetting
packageName:[Link] className:null newState:1 userId:0
callingPackage:[Link] callingUid:1000 callingPid:2250
06-22 [Link].454 1308 1349 W _V_VivoAmsImpl: mCallingPidFilter=-
1,mCallingUidFilter=-1
06-22 [Link].300 1763 2170 D _V_ANRMonitor: at
[Link]([Link])
06-22 [Link].454 1308 3380 E VgcUtil : getFile name :theme_dir_pathnot exit in
vgc_path_config.xml
06-22 [Link].454 1308 2159 D CompatibilityChangeReporter: Compat change id
reported: 135754954; UID 1000; state: DISABLED
06-22 [Link].759 3464 3464 W ContextImpl: Calling a method in the system
process without a qualified user: [Link]
[Link]
[Link].c:454 [Link].k:395
[Link]
06-22 [Link].454 1681 3855 W ContextImpl: Calling a method in the system
process without a qualified user: [Link]
[Link] i2.a$[Link]
[Link] [Link]
06-22 [Link].454 1308 1350 W ActivityManager: Slow operation: 103ms so far, now
at startProcess: done updating battery stats
06-22 [Link].454 1308 1350 W ActivityManager: Slow operation: 103ms so far, now
at startProcess: building log message
06-22 [Link].454 1308 1350 I ActivityManager: Start proc
4277:[Link]:UnityKillsMe/u0a229 for broadcast
{[Link]/[Link]}
06-22 [Link].409 1308 1659 I _V_SettingsProvider: insert settings success:true,
table:SETTINGS_SYSTEM name:alarm_boot_time value:1750606145408
pkg:[Link] userId:0
06-22 [Link].060 1308 1478 D _V_ActivityManager: StartMode packageName =
[Link] ,pid = -1 ,alwaysRestrict = true ,startMode =
2 ,UidRec:UidRecord{4f34541 u0a72 RCVR bg:+9s831ms procs:1 seq(0,0,0)}
06-22 [Link].972 1308 1833 D _V_ActivityManager: StartMode packageName =
[Link] ,pid = -1 ,alwaysRestrict = true ,startMode =
2 ,UidRec:UidRecord{4f34541 u0a72 RCVR bg:+10s743ms procs:1 seq(0,0,0)}
06-22 [Link].454 1308 4444 D _V_DisplayPowerControllerImpl: mSettingBrightness
= -1.0 as request 0.039215688
06-22 [Link].089 1308 2443 D _V_ActivityManager: StartMode packageName =
[Link] ,pid = -1 ,alwaysRestrict = true ,startMode =
2 ,UidRec:UidRecord{4f34541 u0a72 RCVR bg:+1m13s860ms idle change:idle procs:1
seq(0,0,0)}
06-22 [Link].392 1308 3982 D _V_ActivityManager: StartMode packageName =
[Link] ,pid = -1 ,alwaysRestrict = true ,startMode =
2 ,UidRec:UidRecord{4f34541 u0a72 RCVR bg:+1m14s162ms idle change:idle procs:1
seq(0,0,0)}
06-22 [Link].581 917 917 E wificond: vivo add tx_good 7454 tx_bad 60 rx_good
9492 tx_retry 657
06-22 [Link].102 917 917 E wificond: vivo add tx_good 7787 tx_bad 60 rx_good
10454 tx_retry 963
06-22 [Link].713 917 917 E wificond: vivo add tx_good 10454 tx_bad 60 rx_good
15495 tx_retry 1211
06-22 [Link].736 917 917 E wificond: vivo add tx_good 10454 tx_bad 60 rx_good
15524 tx_retry 1211
06-22 [Link].454 917 917 E wificond: vivo add tx_good 10765 tx_bad 60 rx_good
17709 tx_retry 1396
06-22 [Link].454 917 917 E wificond: vivo add tx_good 11293 tx_bad 60 rx_good
20931 tx_retry 1784
06-22 [Link].676 917 917 E wificond: vivo add tx_good 45455 tx_bad 103
rx_good 65292 tx_retry 3305
06-22 [Link].454 917 917 E wificond: vivo add tx_good 48470 tx_bad 129
rx_good 69268 tx_retry 3398
06-22 [Link].579 917 917 E wificond: vivo add tx_good 82543 tx_bad 209
rx_good 121225 tx_retry 4544
06-22 [Link].001 917 917 E wificond: vivo add tx_good 106509 tx_bad 213
rx_good 145406 tx_retry 4876
06-22 [Link].893 917 917 E wificond: vivo add tx_good 145488 tx_bad 255
rx_good 196854 tx_retry 6177
06-22 [Link].961 917 917 E wificond: vivo add tx_good 173454 tx_bad 259
rx_good 212505 tx_retry 6548
06-22 [Link].943 923 986 E [Link]@2.0-service-mediatek:
akm_log setv_acc(720/g) -646, 182, 270 ts 4819454966
06-22 [Link].312 925 18936 E Hal3ARaw: [setParams] ReqMagic(#31454),
i4MagicOfLceGainFrame(31453), History(#31452,#31453,#31454) (setParams)
{#1577:vendor/mediatek/proprietary/hardware/mtkcam/aaa/source/mt6765/../isp_40/
wrapper/[Link]}
06-22 [Link].353 925 18936 E Hal3ARaw: [setParams] ReqMagic(#31455),
i4MagicOfLceGainFrame(31454), History(#31453,#31454,#31455) (setParams)
{#1577:vendor/mediatek/proprietary/hardware/mtkcam/aaa/source/mt6765/../isp_40/
wrapper/[Link]}
06-22 [Link].395 925 18936 E Hal3ARaw: [setParams] ReqMagic(#31456),
i4MagicOfLceGainFrame(31455), History(#31454,#31455,#31456) (setParams)
{#1577:vendor/mediatek/proprietary/hardware/mtkcam/aaa/source/mt6765/../isp_40/
wrapper/[Link]}
06-22 [Link].885 923 986 E [Link]@2.0-service-mediatek:
akm_log setv_mag(uT) 48.450001, -10.950001, -25.800001 ts 4845408517
06-22 [Link].334 9151 12093 E rtcplatform: [connectionId: a4914e1f-72c7-46a9-
b689-67c38e68d836] [signalingId: 3830611573] [[Link]:operator():159]
NTP estimator failed for ts=, badTimestamp: 3774493556, while accepting ts=,
[Link]: 3774545396
06-22 [Link].334 9151 12093 E rtcplatform: [connectionId: a4914e1f-72c7-46a9-
b689-67c38e68d836] [signalingId: 3830611573] [[Link]:operator():159]
NTP estimator failed for ts=, badTimestamp: 3774493556, while accepting ts=,
[Link]: 3774545396
06-22 [Link].107 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-22 [Link].176 454 17476 E AudioALSAStreamManager: createCaptureHandler(),
ptr is NULL!!
06-22 [Link].218 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].224 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].288 454 5055 E AudioMTKGainController: getGainDevice(), error,
devices (65536) not support, return GAIN_DEVICE_SPEAKER
06-22 [Link].454 510 12927 I APM_AudioPolicyManager:
[MTK_APM_Route]setOutputDevices mIoHandle 13 : changing device 0x1 to 0x1, delayMs
= 0, force = 1
06-22 [Link].025 923 986 E [Link]@2.0-service-mediatek:
akm_log setv_acc(720/g) -679, 164, 252 ts 4854548017
06-22 [Link].099 454 17476 E AudioALSAStreamManager: createCaptureHandler(),
ptr is NULL!!
06-22 [Link].101 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].107 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].250 454 515 E AudioMTKGainController: getGainDevice(), error,
devices (65536) not support, return GAIN_DEVICE_SPEAKER
06-22 [Link].454 510 1515 V APM_AudioPolicyManager: getOutput() stream 0
selected devices {type:0x2,@:}, output 13
06-22 [Link].714 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-22 [Link].782 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].787 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].829 454 515 E AudioMTKGainController: getGainDevice(), error,
devices (65536) not support, return GAIN_DEVICE_SPEAKER
06-22 [Link].148 9151 9151 E Parcel : at
[Link]([Link])
06-22 [Link].149 9151 9151 E Parcel : at
[Link]([Link])
06-22 [Link].973 454 515 E AudioMTKGainController: getGainDevice(), error,
devices (65536) not support, return GAIN_DEVICE_SPEAKER
06-22 [Link].130 454 8322 E AudioALSADeviceConfigManager:
ApplyDeviceTurnonSequenceByName DeviceName = voice_speaker_output descriptor ==
NULL
06-22 [Link].750 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-22 [Link].800 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].805 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].880 454 515 E AudioMTKGainController: getGainDevice(), error,
devices (65536) not support, return GAIN_DEVICE_SPEAKER
06-22 [Link].560 454 515 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-22 [Link].583 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].588 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].021 454 515 E FMQ : grantorIdx must be less than 3
06-22 [Link].022 454 515 E FMQ : grantorIdx must be less than 3
06-22 [Link].025 454 20629 E AudioALSAStreamManager: createCaptureHandler(),
ptr is NULL!!
06-22 [Link].265 454 8322 E AudioALSADeviceConfigManager:
ApplyDeviceTurnonSequenceByName DeviceName = voice_speaker_output descriptor ==
NULL
06-22 [Link].267 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].272 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-22 [Link].293 454 20629 E AudioALSAStreamManager: createCaptureHandler(),
ptr is NULL!!
06-22 [Link].446 454 515 E AudioMTKGainController: getGainDevice(), error,
devices (65536) not support, return GAIN_DEVICE_SPEAKER
06-22 [Link].454 2250 2733 E VivoSensorTest: vivo_sensor_factory_test system
start
06-23 [Link].454 2250 2733 E VivoSensorTest: vivo_sensor_factory_test system
start
06-23 [Link].454 2250 2733 E VivoSensorTest: vivo_sensor_factory_test system
start
06-23 [Link].454 2222 18447 E [Link]:
(2222)onHeartBeatSuccess system not support
06-23 [Link].454 2250 2733 E VivoSensorTest: vivo_sensor_factory_test system
start
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup26: Permission denied
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup27: Permission denied
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup28: Permission denied
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup30: Permission denied
06-23 [Link].066 454 515 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].096 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-23 [Link].102 454 8322 E AudioALSAPlaybackHandlerBase: -
getHardwareBufferInfo(), pcm_get_htimestamp fail, ret = -1, pcm_get_error = flag =
0x6
06-23 [Link].832 24454 24454 E [Link]: Not starting debugger since
process cannot load the jdwp agent.
06-23 [Link].108 24545 24545 E [Link]: Not starting debugger since
process cannot load the jdwp agent.
06-23 [Link].004 1308 3982 E IntervalStats: Unable to parse usage stats package
454
06-23 [Link].692 25048 25454 E ActivityThread: Failed to find provider info for
[Link]
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup26: Permission denied
06-23 [Link].971 1308 1332 E _V_VivoVibratorServiceImpl: onProcessDied pid:
24454,uid: 10217
06-23 [Link].454 2384 3065 E BitmapFactory: Unable to decode stream:
[Link]:
/oem/etc/theme/icons/neutral/dynamic_icon/[Link]/nullclock_minute.png
: open failed: ENOENT (No such file or directory)
06-23 [Link].454 1308 1308 E VgcUtil : getFile name :theme_dir_pathnot exit in
vgc_path_config.xml
06-23 [Link].104 1308 1332 E _V_VivoVibratorServiceImpl: onProcessDied pid:
24545,uid: 10185
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup29: Permission denied
06-23 [Link].108 3500 3518 I .[Link]: Background young concurrent
copying GC freed 45490(2500KB) AllocSpace objects, 2(104KB) LOS objects, 6% free,
21MB/22MB, paused 832us total 141.992ms
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup28: Permission denied
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
362
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
365
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
374
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
376
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
379
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
380
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
381
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
383
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
394
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
397
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
398
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
399
06-23 [Link].454 1308 1348 E IntervalStats: Unable to parse usage stats package
402
06-23 [Link].498 1308 1348 E IntervalStats: Unable to parse usage stats package
454
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup28: Permission denied
06-23 [Link].760 454 515 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].825 2222 28734 E [Link]: (2222)token is
null, key is PUBACK, msg id:1386599257234477454 msgId 1386599257234477454
06-23 [Link].736 28739 28764 E _V_AccountSDK-DeviceProxy: at
[Link]([Link])
06-23 [Link].308 454 515 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].980 454 515 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].454 1308 1349 E ActivityManager: Already have existing proc
ProcessRecord{15598be 25743:[Link]/u0a240} when adding
ProcessRecord{a5b8d9a 0:[Link]/u0a240}
06-23 [Link].660 31350 31390 E _V_AccountSDK-DeviceProxy: at
[Link]([Link])
06-23 [Link].366 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].454 524 524 E ccci_fsd(1): Failed to read from FS device (-1) !!
errno = 4
06-23 [Link].454 659 675 E VoLTE REG: is video call check returns 0
(module/volte//volte_stack/src/reg/reg.c:1845)
06-23 [Link].454 421 428 E [Link]@1.0-service: Error opening
kernel wakelock stats for: wakeup27: Permission denied
06-23 [Link].454 1308 1702 E ActivityManager: Sending non-protected broadcast
[Link].action_authorized from system 1953:[Link]/1000
pkg [Link]
06-23 [Link].002 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].478 507 4546 I mtkpower_client: perf_lock_rel, hdl:2261, tid:4546
06-23 [Link].750 507 4545 I mtkpower_client: perf_lock_rel, hdl:2260, tid:4545
06-23 [Link].881 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].354 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].467 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].256 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].267 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].522 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].534 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].451 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].461 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].760 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].771 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].955 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].963 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].527 8541 4548 E _V_ContentCatcher-PackageUtil: [getPackageInfo]
Exception in
06-23 [Link].876 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].282 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].879 454 11183 E AudioALSADeviceConfigManager:
ApplyDeviceTurnoffSequenceByName(), DeviceName = voice_speaker_output descriptor ==
NULL
06-23 [Link].279 483 1599 I libPowerHal: [perfLockAcq] idx:3 hdl:2454 hint:11
pid:483 duration:30000 => ret_hdl:2454
06-23 [Link].279 483 1599 I libPowerHal: [PE] scn:3 hdl:2454 hint:11
comm:mtkpower@1.0-se pid:483
06-23 [Link].388 483 1599 I libPowerHal: [perfLockRel] hdl:2454, idx:3
06-23 [Link].388 483 1599 I libPowerHal: [PD] scn:3 hdl:2454 hint:11
comm:mtkpower@1.0-se pid:483
06-23 [Link].308 917 917 E wificond: vivo add tx_good 241199 tx_bad 2387
rx_good 297454 tx_retry 7327
06-23 [Link].454 917 917 E wificond: vivo add tx_good 241395 tx_bad 2387
rx_good 297978 tx_retry 7346
06-23 [Link].454 483 1599 I libPowerHal: [perfLockAcq] idx:2 hdl:2758
hint:1173 pid:507 duration:0 => ret_hdl:2758
06-23 [Link].454 483 1599 I libPowerHal: [PE] scn:2 hdl:2758 hint:1173
comm:vperf@1.0-servi pid:507
06-23 [Link].454 5769 5769 E libc : Access denied finding property
"[Link]"

Common questions

Powered by AI

The 'Permission denied' error from 'android.system.suspend@1.0-service' suggests a failure to access necessary kernel wakelock stats, which could impact system power management. Without access to these stats, the system might not efficiently manage CPU usage during idle periods, potentially leading to increased battery consumption and system instability. Addressing this error would require ensuring correct permissions are set for accessing kernel resources .

Frequent 'ApplyDeviceTurnoffSequenceByName' errors could indicate a persistent issue with handling audio device configurations. These errors can lead to the malfunctioning of the audio output, affecting user experience as the voice_speaker_output descriptor is not found, resulting in the inability to control audio routing effectively. Persistent errors may also suggest potential hardware or software compatibility problems, necessitating further investigation and likely software updates to resolve underlying issues .

'PCM get_h timestamp' failures indicate issues in retrieving precise audio playback timestamps, which are critical for ensuring smooth and synchronized audio output. These failures can lead to audio playback issues such as delays, jitter, or disruptions in the audio experience as the system might struggle to maintain playback continuity. Addressing these failures requires rectifying potential hardware or driver issues to ensure reliable audio performance .

Slow operations logged by 'ActivityManager' may lead to noticeable delays in application responses. Such slowdowns could result from inefficient resource allocation or blocking operations within the system, creating bottlenecks. These delays can hinder user experience by causing lag in application startup, slowing down task processing, or affecting battery efficiency due to prolonged CPU usage. Identifying and optimizing these operations might be necessary to enhance system performance .

Reconnecting to 'hwbinder' indicates establishing or re-establishing connections necessary for hardware interfaces, which is crucial for the stable operation of services such as 'AnalysisService.' Similarly, 'Fingerprint HAL id' is essential for identifying and managing the secure fingerprint hardware interface. Successful initialization of services relying on these indicators ensures functionalities like biometric authentication and data analysis are operational, emphasizing the importance of robust and reliable connections for system stability .

Failed access to 'usage stats package' logs suggests difficulties in tracking app usage statistics reliably. This failure could lead to inaccurate app usage reports, affecting monitoring and analysis processes, such as identifying resource-hogging apps or gauging app popularity. Without reliable stats, optimization of resource allocation and user experience personalization may be adversely affected, posing challenges for app developers and system administrators to maintain efficient operations .

'Tx_good' and 'tx_bad' metrics are crucial for evaluating network performance. 'Tx_good' indicates successfully transmitted packets, whereas 'tx_bad' counts failed transmissions. A high 'tx_good' relative to 'tx_bad' suggests healthy network performance with efficient data flow. However, a high 'tx_bad' could indicate network congestion, interference, or hardware issues, prompting further investigation to maintain network quality. Analyzing these metrics helps in identifying transmission issues, guiding optimization and troubleshooting efforts .

The 'insert settings success:true' log indicates successful updates to system configurations, reflecting the accuracy of changes made in the device settings database. This success suggests that changes, such as setting alarms or modifying certain system parameters, have been effectively implemented, affirming the system's ability to process configuration requests without errors, thereby maintaining optimal operational settings .

NTP (Network Time Protocol) estimator failures in real-time communication systems can critically affect the syncing of time-sensitive data exchanges, such as audio or video transmissions. Accurate timestamps are essential for maintaining synchronous data playback and ensuring the integrity of communication sessions. Failures in NTP estimations can result in desynchronized audio or video streams, potentially degrading communication quality and reliability, necessitating robust timestamp handling mechanisms .

The logs for 'setOutputDevices' changing devices indicate frequent adjustments in audio routing settings. Such behavior might be seen in devices trying to optimize audio output based on current usage conditions. However, if these changes occur too frequently or erratically, they could lead to inconsistent audio performance, with potential delays or interruptions experienced by users. This behavior suggests an adaptive system that dynamically adjusts audio output, but frequent unnecessary changes might indicate a configuration issue in device logic requiring further tuning .

You might also like