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.
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.