An update from my experience,
Switching to Windows 10 (and a faster windows platform) seems to have solved/hidden the problem.
Steve
Further update, i spoke too soon!
System: Windows 10, B4A 6.00, Nexus 7 Android 6.0.1, Bridge 2.14
Using rapid debug over bridge often (probably every time) causes the Nexus to loose its WiFi connection when the target program starts BLE2 scanning and connecting. Up to the point where i start that process on the Tablet the debugger is working as it should. Sometimes the tablet will re-connect to the WiFi other times it needs a re-boot then i can reconnect B4A to the bridge. After that the log window usually does not display all program generated log lines (for a new debug run) despite clicking on connect in the log window. I seem to have to restart B4A or switch to legacy - start a run then stop and switch back to rapid to get the log display showing log lines again.
Using Legacy debug over bridge works ok and Nexus stays connected to WiFi.
While breakpoints etc. work as they always did on the Legacy debugger it seems that the stop function (on the legacy debugger) no longer stops the target program which carries on running until i start a new debug run or manually stop it on the tablet. Is this a new feature?