So I'm following up to my above post. Because I couldn't go out and fly, last night I just connected using 4.3.0 and let it sit for two separate sessions of about .5-1 hour each, with no disconnects. I flew a full battery this morning, again, no errors. At this point, I don't know what caused yesterday's issue, but I did notice that the top of the Go screen said 'remote controller connection error' or something like that - even though the remote was still connected to my phone, and to the Mavic.....it's just the phone that wasn't connected to the Mavic.
LP