Bug 339585 - Connected XiaoMi RedMi phone（紅米手機） not listed in Dolphin FM, despite that mtpfs is working
Summary: Connected XiaoMi RedMi phone（紅米手機） not listed in Dolphin FM, despite that mtp...
Status: RESOLVED WORKSFORME
Alias: None
Product: kio-extras
Classification: Frameworks and Libraries
Component: MTP (show other bugs)
Version: 18.04.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Philipp Schmidt
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-10-01 20:52 UTC by Ｖ字龍(Vdragon)
Modified: 2018-10-29 02:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ｖ字龍(Vdragon) 2014-10-01 20:52:09 UTC 
* kio-mtp version according to the software package is '0.75+git20140304-1' and is from Ubuntu 14.04 software sources
* Dolphin didn't list connected XiaoMi RedMi phone（紅米手機）
* mtpfs works
	* mtpfs mount output:
````
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=2717 and PID=1240) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
   Found 1 device(s):
   2717:1240 @ bus 2, dev 17
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: 2013023
````
* Google Nexus 7(2012/2013) works
* GNOME Nautilus(Files) has the same issue
* libmtp version '1.1.6-20-g1b9f164-1ubuntu2' from Ubuntu 14.04 software sources


Reproducible: Always

Steps to Reproduce:
1. Connect a XiaoMi RedMi phone

Actual Results:  
* Nothing happened

Expected Results:  
* XiaoMi RedMi phone listed in Dolphin FM's 'Places' widget
Comment 1 Elvis Angelaccio 2018-08-16 10:09:31 UTC 
As far as I know, if the device is not recognized it means libmtp doesn't know its  vendor ID. Does this problem still happen with recent versions of libmtp?
Comment 2 Ｖ字龍(Vdragon) 2018-08-16 10:29:38 UTC 
(In reply to Elvis Angelaccio from comment #1)
> As far as I know, if the device is not recognized it means libmtp doesn't
> know its  vendor ID. Does this problem still happen with recent versions of
> libmtp?

I no longer have the device now and thus unable to reproduce this bug.
Comment 3 Andrew Crouthamel 2018-09-28 03:31:29 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-29 02:03:02 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!