Comment 5 for bug 1160847

The problem here is that the USB Vendor and DeviceID are the same in Ubuntu Touch and in android (we use the same kernel so the device identifies itself the same way). Unlike android Ubuntu Touch doesn't ship and MTP userspace bits which makes the mount fail. I would expect gvfs to notice that and not try again as long as there was no reconnect but instead it fires a new mount attempt every minute (resulting in a new error popup).

gvfs should definitely not try mounting over and over once it knows there is no way to mount as long as there was no physical reconnect. We can't just rip out the device IDs from the rules file as this would break all devices of the same model using android here. Thenaks for the info that MTP does not interfere with adb, so in case we decide we will use it (this is not clear yet, we might decide to just connect as USB mass storage for more convenient device access) it would go away.

I still think teh behavior is a bug though. Can gvfs be told to not attempt constant mounting in a loop please ? An USB ID is not enough to identify if the MTP protocol is supported or not. A single mount attempt should be enough to notice if there is userspace support.