NukaNegan 8 Posted March 31, 2020 Share Posted March 31, 2020 Anyone else getting this over and over in their logcat? 2020-03-30 21:06:18.727 24458-24458/? W/qcom-system-dae: type=1400 audit(0.0:10567): avc: denied { read write } for name="diag" dev="tmpfs" ino=22599 scontext=u:r:vendor_qcomsysd:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0 2020-03-30 21:06:23.759 24461-24461/? E/QCOMSysDaemon: Can't find/open bootselect node: (No such file or directory) 2020-03-30 21:06:23.747 24461-24461/? W/qcom-system-dae: type=1400 audit(0.0:10568): avc: denied { read } for name="name" dev="sysfs" ino=33531 scontext=u:r:vendor_qcomsysd:s0 tcontext=u:object_r:sysfs_data:s0 tclass=file permissive=0 2020-03-30 21:06:23.747 24461-24461/? W/qcom-system-dae: type=1400 audit(0.0:10569): avc: denied { read write } for name="diag" dev="tmpfs" ino=22599 scontext=u:r:vendor_qcomsysd:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0 2020-03-30 21:06:23.759 24461-24461/? I/QCOMSysDaemon: Starting qcom system daemon 2020-03-30 21:06:23.759 24461-24461/? E/QCOMSysDaemon: Diag_LSM_Init failed : 0 Is there an issue with the Qualcomm software on the device? Quote Link to post Share on other sites
Slion 1,201 Posted March 31, 2020 Share Posted March 31, 2020 Not sure about that one specifically but I remember getting a lot of trash too over logcat thinking to myself they have room for improvements there. Quote Link to post Share on other sites
daniel.schaaaf 177 Posted March 31, 2020 Share Posted March 31, 2020 I see these errors as well. Looks like an SELinux issue. As with so many apps, libraries and other blobs, I would very much like to know what they all do ... Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.