ADB connectivity issues?

[Groxx]

Possibly this is a vagrant / virtualbox problem, but at the moment I'm completely unaware of how to fix :(

Basically, this happens on OSX normally (no vagrant box running):

• plug in Flame phone
• starts charging
• moments later, adb devices shows the device

From within Vagrant:

• plug in Flame phone
• starts charging, adb devices shows the device
• a couple minutes later, the adb connection drops, charging drops on the phone
• a handful of seconds later, it reconnects, but adb doesn't (usually) see the device any more. adb kill-server and adb devices sometimes works, usually doesn't

From OSX when Vagrant is running:

• similar behavior as within Vagrant, but sometimes shows ???????????? device instead of the ID

Unfortunately, this is preventing me from finishing the first ./build.sh run because I can't get a complete backup completed before the connection drops :( I can probably work around this in particular, but could it be a sign of something I've done wrong? Is anyone else seeing this?

I did add this (without testing before), which might not have helped:

diff --git a/Vagrantfile b/Vagrantfile
index 00894f6..862cee0 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -90,6 +90,7 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
     v.customize ['usbfilter', 'add', '0', '--target', :id, '--name', 'qualcomm', '--vendorid', '0x05c6']
     v.customize ['usbfilter', 'add', '0', '--target', :id, '--name', 'zte', '--vendorid', '0x19d2']
     v.customize ['usbfilter', 'add', '0', '--target', :id, '--name', 'spreadtrum', '--vendorid', '0x1782']
+    v.customize ['usbfilter', 'add', '0', '--target', :id, '--name', 'flame', '--vendorid', '0x05c6']
   end

 end

I can relatively easily drop everything and start from scratch if you have any suggestions - plenty of internets to be had, and I'm in no rush. And I'm absolutely thrilled to find this project, many many thanks for setting it up!