I understand … I suggest … divide and rule 
There is this which you might dip into to get you started Reading and Writing Logs | Android Developers.
In your big log much of what you need to fix is expressed in those first 61 lines. I would place them alone in a text file … you might open it in a word processor and use bold or colour to help you break down what you can understand.
Checking the time + date stamps. We see
line 1 06-25 13:28:57.191
line 61 06-25 13:28:57.191
line 1120 06-25 14:27:49.221
So all the recorded events are in quite a tight timeline. Then you notice that the remainder of the log has timestamps during today.
Notice all Errors contain (in the priority character column) “space” E “space”.
E
^F (Find) can be used to mark thus highlight these entries.
The second level of starting to understand the crash logs might be to use ^F to see how similar or dissimilar are the “19 events” each occupying roughly 60 lines in the first “crash” section before you reach
--------- beginning of system
06-28 01:05:34.300
Again ^F is your friend; each of the nineteen events starts
E AndroidRuntime: Process: ch.bcv.mobile.android, PID:
PID is “process ID” – each event has a new PID.
When we use /e/OS we put our faith in microG to do this activity in a way that aims to connect with Google “services” but anonymously.
Some micoG bookmarks: