Samsung quirks

The galaxy needs to have configuration 4 selected "onEnumeration"

onEnumeration.04e8.6877=echo '4' > $DEVPATH$/bConfigurationValue

The other galaxies might need similar settings...

One thing to make sure is that your actual server is not trying to grab the device via its udev rules which is interfering with virtualhere capturing the device. I don't know what your server is but if its a ubuntu desktop or something then it may already have udev rules that would capture and try to process the device (set configuration/interfaces) before its even given to the virtualhere server and this confuses the device. (If you are using a simple linux embedded board like a pi then they usually dont have complicated udev rules for ipads or phones built-in so there is no interference with virtualhere)

For example the ipad etc has rules in udev for ubuntu desktop, that perform capture and configuration of the device and these need to be disabled on a desktop server for virtualhere to work with these types of devices when performing complicated firmware updates or configuration changes on startup that the product requires.

The reason why quirks are needed occasionally is because the USB enumeration and configuration is split in two in virtualhere. Usually with direct cable connection the usb enumeration is done and then configuration is done immediately afterwards. Whereas in virtualhere the enumeration is done immediately and the configuration is done when the user begins "Use"ing the device remotely. Some devices are sensitive to this because they want the configuration set immediately so they know what type of device they need to be.

I find that devices which perform as different devices at different times have this requirement. e.g android can be a "Android debug device" or "USB disk" or "Android phone" etc. and ipad can be "Firmware update", or "usb disk" or "ipad"

I think from that vendor/id product id it is a samsung galaxy s2 or galaxy tab 10.1?

My advice would be this:

1. Download a usb tracing software e.g i use usblyzer (free demo is available which is all you need)
2. Run usblyzer or whatever one you use and capture all packets (check all boxes in the settings and check "Capture hot-plugged devices") and then click Start capture
2. Run that and plug the phone directly into your windows computer
3. Now what will happen is the first 20 or so USB messages are streamed on the the tracing screen, and you will see a message like "Set Configuration" and a value in the data section like 4 or something.
4. That setting has to be done as a quirk because the "Set Configuration 4" request as you see it only would happen after you use the device locally direclty connected.

That is the actual quirk that i told you to add, (Im guessing its configuration 4 like the old galaxy but could be something like 3)

If you need to remove a "quirk" you can Right click on the device in the client and use the work REMOVE instead for the quirk

e.g

onReset.$VENDOR_ID$.$PRODUCT_ID$=REMOVE and the server will tell you in the log its removed the quirk

I would recommend removing the reset quirk if it causes your device to jam, you probably only need the onEnumeration and onUse quirks.

Another thing to check if other people have had trouble mounting that device natively in linux. They usually have to add some udev rule to get it to work. You need to add that as a quirk to virtualhere instead of a udev rule.

Im out of ideas with this one, if you have a usb protocol analyzer you might be able to figure it out but its probably quite time consuming... I dont have that device to test with here locally at the office so i cant really help