Reading logs
Reading logs can be kind of hard, though, there are some things which can help!
First, lets look at what a log looks like, do note this log is using Logcat Colorizer, which is download-able below

You can see many things, let me break it down a little bit
- The Purple text on the left shows us exactly when something - for example an error - happened
- The colored squares to the right of that shows what kind of information it is, "E" for example is Error, "I" is Information, "D" is Debug, "W" is Warning and so on
- next to that - in teal/greenish blue - we see some random numbers that I have honestly no idea what they mean, maybe their PID?
- to the right of that we see the name of the program giving the Information, for example we can the first error in this screenshot is from "Perfsdkserver" and the warning at the bottom is from "Chimerautils"
- To the right of the Program Name, we can see whatever information the program wants us to see, for example "Non Chimera Object" next to that orange warning down there
You can use the tools above to see many different things a lot easier, like what is an error, a warning, and so on
You can filter logcats by different types (also without Logcatf or Logcat-colorizer) like this (In a Terminal or CMD/Powershell):
This can be useful to find a specific line, or a specific error, especially when many things are happening at once
To see a list of possible arguments and more information, check the official documentation
Tip : Filtering by word
You can also filter by specific words on Linux and macOS by adding |grep -i "your filtered word here"
at the end of the command! :)
on windows (Powershell), you can add | Select-String "your words here"
at the end of your Command