Printer freezes mid print. Losing connection between printer and RPI

What is the problem?
My printer stops printing mid print. It freezes and will not move unless i cut the power and reboot it. (including octoprint) Never had these issues until this weekend it suddenly started.

What did you already try to solve it?
Checked ALL the connections of the printer. Tried multiple USB cables. Power supply on the RPI3b is 4 amps 5v via micro USB. Tried printing via SD card slot on printer works fine. It "feels" like the RPI loses connection with the printer, and the printer does not receive any commands thus stopping the print. But cant find the reason why.
I removed all "unnececary" plugins from the RPI.
I checked the RPI getting hot. This is not the case.

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)octoprint.log (575.9 KB)

Send: N1339 G1 F1200 X74.637 Y65.586 E387.46546*63
Recv: ok
Send: N1340 G0 F2100 X74.237 Y65.752*125
Recv:  T:204.97 /205.00 B:61.19 /60.00 @:42 B@:0
Recv: ok
Send: N1341 G1 F1200 X78.802 Y70.316 E387.78751*54
Recv: ok
Send: N1342 G0 F2100 X78.476 Y70.557*115
Recv: ok
Send: N1343 G1 F1200 X73.837 Y65.917 E388.11485*60
Recv: ok
Send: N1344 G0 F2100 X73.437 Y66.083*112
Recv: ok
Send: N1345 G1 F1200 X78.152 Y70.798 E388.44752*63
Recv: ok
Send: N1346 G0 F2100 X77.827 Y71.038*125
Recv: ok
Send: N1347 G1 F1200 X73.037 Y66.249 E388.78544*48
Recv: ok
Send: N1348 G0 F2100 X72.637 Y66.415*116
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1349 M105*24
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1350 M105*16
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1351 M105*17
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1352 M105*18
Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1353 M105*19
No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor
Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Error: Connection error, see Terminal tab"
Unexpected error while connecting to serial port: /dev/ttyUSB0 IOError: '[Errno 5] Input/output error' @ comm.py:_openSerial:2661 (hook default)

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)

I got a RPI 3b with the latest Octoprint firmware flashed to a SD card. OctoPrint : 1.3.12
RPI is connected via UTP cable (and wifi is configured) to a network router.
RPI is connected via USB cable (1,5mtr) to the printer.
Printer is a Chinese I3 cole with new motherboard. Flashed with latest marlin firmware.
Using Firefox as internet browser.
Serial port AUTO
Baudrate AUTO (250000)

Please, Help me. I have no knowledge of the errors or the octoprint.log. If you need info i did not supply please let me know!

Are you sure this isn't a charger? You might want to include the manufacturer and model for this since I've not heard of anything like this. Technically, the specs for microUSB indicate that the maximum power is supposed to be 5V @ 2.1A (even though the Pi 3B needs 2.5A minimally).

The printer cable @ 1.5 meters seems a bit long and is likely syncing/dropping power from the Pi, possibly. I don't think I'd suggest a serial cable longer than 12" or so, to be honest. And even then, it needs to be internally shielded or have a ferrite core.

Thank you for the fast reply.
It is a charger indeed. But the RPI is running on this for almost a year now without any problems. Never saw the lightning symbol with this one. Also forgot to mention the 5v+ has tape on the inside of the USB to prevent the RPI from powering the printer motherboard.

The USB cable is shielded and with a ferrite core at the end. Its the half transparant plastic type, so i can see the shielding.

A charger provides pulsating, positive 5V DC which is above/below this amount. An adapter provides a solid 5V DC which is a horizontal line seen on an oscilloscope.

Borrow a power adapter if you have to in order to verify that this isn't the cause.