Dear Maintainer,

I get screenshots saying "Unable to mount Samsung Samsung Android/"
and constantly asks permissions for phone access. This usen't used to
before. I am unablto diagnose whether its a udev issue or something
else.

lsusb gives me this, maybe it can help in isolating at least where to look -
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M
    |__ Port 1: Dev 53, If 1, Class=Vendor Specific Class, Driver=, 480M
    |__ Port 1: Dev 53, If 0, Class=Imaging, Driver=usbfs, 480M
    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 6: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 7: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 7: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 8: Dev 6, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 8: Dev 6, If 0, Class=Video, Driver=uvcvideo, 480M

As can be seen it doesn't even describe/announce where it is attached.
Maybe I'm expecting too much.

Having that error come up again and again is irritating, please fix it.

What is making the screenshots?  libadb can't do that.  Also, where do
you see the message "Unable to mount Samsung Samsung Android/"?  Where
are you seeing a prompt that asks permission for phone access?

at bottom :-

I meant the dialog box, not screenshots, sorry. Attaching one to make
it more understandable.

It just appears every few minutes making using the phone for charging
or data delivery that much inconvenient. It didn't use to happen
before. I don't know if the issue is in libadb or udev or some other
sub-system which migt have got upgraded recently. Would be glad to
diagnose if you are able to share the commands to figure out more or
give me more clues/commands so that I can run and give output to you.

It asks for phone access on my phone every few minutes or so.

Having the dialog box appear again and again on my lappy every few
minutes takes the fun out of things :(

I did check to see if the usb cable had developed some snags but on my
external hdd it runs smooth.

The prompt is on my phone every few minutes. I have turned on
Developer Options ages ago. I did see a thread about it as well which
talks of having own .ini file

https://stackoverflow.com/questions/15396423/adb-doesnt-see-device

Mind you the thread is from 2013 and I don't see anything in
/etc/udev/rules.d/ a file named android.rules or anything like that.

/etc/udev/rules.d> ls

 [100%]
.  ..  70-persistent-cd.rules  70-persistent-net.rules

Maybe the above info. gives a bit more clues.

That dialog clearly says MTP.  adb nor any of the Android Tools packages
have anything to do with MTP.  So this is not an adb nor Android Tools bug.

reassign 874216 gvfs-backends
thanks

Hi there,

Thank you for maintaining libmtp all these years and at times it has
been a lifesaver.

Although now, It seems aggresive polling is being used by libmtp as I get
notifications of denial as shared in screenshots and there are a
multiple ones at that.

The only change I did (and this is months ago) was add developer
options and changed from MTP to charging options. I am on Android 6.0
marshmallow latest updated version. The phone is a Galaxy J5.

These are the options it shows me -

    Transferring media files through MTP - This seems to be only one
way from phone to PC and not the other way around :(

    Transferring images or files through a PTP connection (guess it's
a lower bandwidth connection)

    Connecting MIDI devices

    Charging.

and am using the last option charging. Is there a way to minimize
libmtp polling for usb devices or just have to live with that.

In 5 minutes I got about 40-50 notifications or copies of the
notifications as seen above,  Sharing another screenie as before. m

I am on Android Marshmallow 6.0 (latest update) and the phone is a
Samsung Galaxy J5 . Please let me know if any more info. is needed.

The 'grave' severity is reserved for major security bugs or bugs where
users lose data, etc.

https://www.debian.org/Bugs/Developer#severities

Thanks,
Jeremy Bicha

Adding a title.