[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Resolved: mount MTP phone



Anthony Baldwin <baldwinlinguas@gmx.com> writes:

> Sorry for top-posting.
> Iḿ no t even sure what it was that DID solve this but the phone is now
> mounting at mtp://[usb:005,012]/
> Must have something to do with installing the jmtpfs pkg,
> because that's the only thing I can think of that I did yesterday that
> could be making a difference today.
> I did briefly put the phone on ptp/camera mode, and it let me download
> the photos on it, but now it's letting me completely access the
> storage for whatever (move photos, music, etc. phone<->computer)

Magic fixes like this *really* sound like a bad cable.

> On 09/05/2016 12:47 PM, Tony Baldwin wrote:
>> On 09/05/2016 11:09 AM, Nicolas George wrote:
>>> Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :
>>>> I've never been able to mount any MTP phone to Linux. Different
>>>> phones, different Android versions, different Linux installations,
>>>> nada.
>>>
>>> I have. With FUSE and gvfs, something like (the computer where I did
>>> it and
>>> kept notes is current shut down):
>>>
>>> gvfs-mount 'mtp://[usb:001,002]'
>>>
>>> You need to have gvfs-fuse already running, then it appears under
>>> /run/users/$UID/gvfs/.
>>>
>>> libmtp has a few tools to manipulate MTP devices without mounting
>>> them, but
>>> they have 0 documentation. Furthermore, MTP it awfully slow at startup
>>> for
>>> some tasks, so individual commands without a process to keep the library
>>> open will give awful results. I have started working on a tool with a
>>> script-friendly FTP-like interface, but not got very far yet due to other
>>> more pressing projects.
>>>
>>> Regards,
>>>
>>
>> Something has changed since yesterday (IN which I installeed jmtpfs).
>> Now when I do ls usb, I see this:
>> Bus 005 Device 012: ID 22b8:2ea4 Motorola PCS
>> I'm also seeing possibly relevant (I don't know) stuff in dmesg, such as
>> this:
>> [quote][75390.506984] hub 5-0:1.0: port 5 disabled by hub (EMI?),
>> re-enabling...
>> [75390.507000] usb 5-5: USB disconnect, device number 8
>> [75406.588441] usb 5-5: new high-speed USB device number 9 using ehci_hcd
>> [75406.722345] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
>> [75406.722360] usb 5-5: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [75406.722368] usb 5-5: Product: XT1254
>> [75406.722374] usb 5-5: Manufacturer: motorola
>> [75406.722379] usb 5-5: SerialNumber: ZY2234TGKZ
>> [81479.602219] usb 5-5: USB disconnect, device number 9
>> [81479.876441] usb 5-5: new high-speed USB device number 10 using ehci_hcd
>> [81480.010291] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
>> [81480.010305] usb 5-5: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [81480.010314] usb 5-5: Product: XT1254
>> [81480.010319] usb 5-5: Manufacturer: motorola
>> [81480.010325] usb 5-5: SerialNumber: ZY2234TGKZ
>> [81483.946880] usb 5-5: USB disconnect, device number 10
>> [81484.220444] usb 5-5: new high-speed USB device number 11 using ehci_hcd
>> [81484.354763] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
>> [81484.354778] usb 5-5: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [81484.354786] usb 5-5: Product: XT1254
>> [81484.354792] usb 5-5: Manufacturer: motorola
>> [81484.354797] usb 5-5: SerialNumber: ZY2234TGKZ
>> [81484.399977] usb 5-5: USB disconnect, device number 11
>> [81508.968204] usb 5-5: new high-speed USB device number 12 using ehci_hcd
>> [81509.102613] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea4
>> [81509.102627] usb 5-5: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [81509.102635] usb 5-5: Product: XT1254
>> [81509.102641] usb 5-5: Manufacturer: motorola
>> [81509.102647] usb 5-5: SerialNumber: ZY2234TGKZ
>> [/quote]
>>
>>
>> is your work in a github repo, sourceforge project, or similar, where
>> others could have a look, and, perhaps, contribute, Nicolas?
>>

-- 
"Erwin, have you seen the cat?" -- Mrs. Shrödinger


Reply to: