so analyzing this a bit deeper, it actually does not have anything to do with adb but with the fact that gvfs assumes that if an USB device registers with:
Product: Android Manufacturer: Android (seen in dmesg) gvfs blindly assumes there is mtp support on the other side ... Ubuntu Touch currently does not ship any mtp support which causes the gvfs mount to fail and to retry over and over (once every 60 seconds). we should: a) not make gvfs try to mount at all if we detect an adb connection since then it is clear that we are in developer or flashing mode. b) probably make gvfs not try to remount at all if it already knows there is no mtp on the responding side c) at some point ship mtp support on the ubuntu touch images though it has to be researched if this interferes with adb which we require for flashing, debugging and development currently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1160847 Title: please add an option to inhibit gvfs mtp mounts Status in “gvfs” package in Ubuntu: Confirmed Bug description: trying to use phablet-flash in raring to flash a phone or tablet (or when just running adb shell or adb root from commandline) causes a constant reconnect loop of an attached mtp device. it seems adb and gvfs try concurrently to establish a connection which results in permanent reconnects and a huge amount of mtp popup windows on the desktop PC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1160847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
