MJLennox:
The variable issue gets set to 1 if there's been no newData for a certain amount of time. This is because I want a way of dealing with connection loss from bluetooth. when issue gets set to 1,
That's fair enough - but don't make the calls to recv() dependent on it.
Good point, I've changed that. However, I still haven't figured out the main issue. I checked all connection to be correctly soldered and all of that. However I can get over the thought that it reminds me to much of the Servo+SoftwareSerial issue, even though I am no using SoftwareSerial right now. Any ideas on that?
Like this: YoutubeVideo
Just a bit more extreme.
You've had some good advice so far. It might also be worth writing something out to serial (or flashing a LED for a few seconds) in the begin() function, just to ensure that you notice any Nano restart when the motor is in use.