On 4/23/25 6:21 PM, deloptes via tde-users wrote:
That said, mtp-detect reports the phone as a OneTouch 5042D rather than
A405DL and complains about being unable to initialize because GVFS or
KDE MTP is handling the device. On odd message because I am using TDE.
I'll have to try later with a fresh reboot.
now you are starting to narrow down :)
if something else is using whatever ...
When I plugin any phone here (Android or not) I always get a konqueror
popping up and opening the device with the tdeio-kamera, which is part of
kamera-trinity
Description: digital camera io_slave for Konqueror
This is a digital camera io_slave for TDE which uses gphoto2 and libgpio
to allow access to your camera's pictures with the URL camera:/
.
This package is part of Trinity, as a component of the TDE graphics module.
See the 'tde-trinity' and 'tdegraphics-trinity' packages for more
information.
I noticed something similar when I sent my previous reply. The
/lib/udev/hwdb.d/69-libmtp.hwdb and 20-libgphoto2.hwdb files list the
A405DL with a USB ID of 1bbb:901b (1BBBp901B).
On my computer lsusb shows 1bbb:900e.
Searching /lib/udev finds no IDs of 1bbb:900e (1BBBp900E). That might
explain why TDE fails to show the device. Might not. Since the device is
listed in both of those files, seems TDE should see the device using the
20-libgphoto2.hwdb file even if MTP is not supported.
Possibly all I need is to create a /etc/udev override files with the
correct ID and name plate. I need to dig further, but my brain is tapped
out for today.
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
