MTP mode in Ubuntu Gutsy Gibbon

[sdyson]

I've successfully got MTP mode to work in Ubuntu Gutsy Gibbon so thought I'd share the details here.

First of all this uses a library called libmtp. The version in the Gutsy Gibbon repositories is 0.2.1 and does not work with the Sansa View. Unless you can find an alternative repository you're going to need to build this yourself. But don't worry, it's straightforward. Download the latest version from http://libmtp.sourceforge.net (I got 0.2.4) and unpack the archive. Then in a console cd to the directory you just unpacked and run the following 3 commands:

./configure
sudo make
sudo make install

Next you need to edit /etc/udev/rules.d/libmtp.rules in your favourite editor and add the Sansa View to the list of devices as follows. Notice the MODE is 666 to ensure your own user has access to the device. You will need to restart for these changes to take effect.

# SanDisk Sansa View
ATTRS{idVendor}=="0781", ATTRS{idProduct}=="74b0", SYMLINK+="libmtp-%k", MODE="666", GROUP="audio"

Now we want to make sure everything is working so you want to install mtp-tools using the package manager or as follows:

sudo apt-get install mtp-tools

Connect the Sansa View to the PC using the supplied cable and then run the following command:

mtp-detect

This will detect any available MTP devices and print out lots of information about the View if successful.

At this stage you should be able to use the View as an MTP device using your preferred media application. I use Amarok which is packaged with MTP support in Gutsy Gibbon. All you need to do is go to Media Devices in the configuration dialog and add an 'MTP Media Device', then press the connect button on the 'Devices' view.

[CrowdAds]

[Symbolis]

I seem to have hit a snag.

symbolis@symbolis-desktop:~$ mtp-detect
libmtp version: 0.2.1

Attempting to connect device(s)
Potential MTP Device with VendorID:0781 and ProductID:74b0 responded to control message 2 with a response that was too short. Problems may arrise but continuing
Device 1 (VID=0781 and PID=74b0) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
usb_claim_interface(): Device or resource busy
LIBMTP PANIC: Unable to initialize device 1
LIBMTP PANIC: configure_usb_devices() error code: 7 on line 1806
Detect: There has been an error connecting. Exiting
symbolis@symbolis-desktop:~$

Any ideas?

[sdyson]

Looks like you are still running against libmtp 0.2.1. Run through the installation of 0.2.4 again and double check the output for errors - particularly the configure stage. In particular watch out for libusb missing. If it is missing install it through synaptic.

[sdyson]

If that doesn't work then try configure without the prefix. You may need to reboot afterwards.

./configure

[bike]

Ah, I was about to publish my experiences as well. One advantage of libmtb over the UMS/MSC hack is you get album art. Using the new libmtp I'm able to get it working at a libmtp device with amarok. I'm able to transfer music on and off, although it doesn't come off with album art for some reason.

Have you been able to get playlists working?

[advcomp2019]

Bike, have you tried embedding the album art. Then transferring the songs.

[sdyson]

You can use album art in MSC mode. You just need to drop a file named folder.jpg in the album directory.

If you use Amarok there is a cool script called CopyCover that will copy the album covers from the Amarok profile directory to the album's directory:
http://kde-apps.org/content/show.php...17&forumpage=7

[Sciamano]

I'm having the same problem as Symbolis: I've libusb (and -dev) installed, followed the installation procedure, but still when I launch mtp-tools it says it's using libmtp version 0.2.1

Any help? My View is on its way...

[Sciamano]

I managed to make it work, but Amarok does not connect to the View...

[Sciamano]

Ok, now it works. For anyone interested, I followed the instructions written by sdyson here but they did not work for me. After compiling libmtp-0.2.5 I kept receiving errors when trying 'mtp-detect'.

This is what I did, it solved the problem for me but YMMV:

1) Open a terminal and write:

sudo aptitude reinstall libmtp6

2) Restart your PC.
3) It should now work

I have no idea how or why it worked, but it did...

[sdyson]

If you're using Ubuntu Gutsy then all that does is install 0.2.1.

[Sciamano]

Originally Posted by sdyson

If you're using Ubuntu Gutsy then all that does is install 0.2.1.

That's what it should do. But not what it does.
Unless you can explain why mtp-tools now reports using libmtp-0.2.5

[Sciamano]

Ok, I had the same problem on another computer: when trying mtp-detect it would output:

mtp-detect: error while loading shared libraries: libmtp.so.7: cannot open shared object file: No such file or directory

A suggestion that makes more sense to me (and which worked) is this.
Follow the tutorial written by sdyson, but just after editing the file /etc/udev/rules.d/libmtp.rules do the following:

open a terminal and write:

sudo ldconfig

Now it will work.
Hope this helps someone else in my same situation.

[foxx]

Hello,

I packaged libmtp 0.2.6 and Rhythmbox 0.11.5, mtpfs 0.8svn, Gnomad2 2.9.1 linked against it in my Ubuntu Gutsy repository. You can get it by adding my repository http://ubuntu.jbbr.net/

sudo wget http://ubuntu.jbbr.net/gutsy.list -O /etc/apt/sources.list.d/jbbr.list
wget -q http://ubuntu.jbbr.net/jbbr_ubuntu.asc -O- | sudo apt-key add - && sudo apt-get update

Afterwards do a upgrade. Rhythmbox should be upgraded and libmtp should be installed with this upgrade. If you like to use gnomad2 or mtpfs you can install them

sudo apt-get upgrade
sudo apt-get install mtpfs gnomad2

With mtpfs you can "mount" your player like a mass storage device. Do:

mkdir ~/MTP
mtpfs ~/MTP

to have your player accessible in /home/username/MTP

Regards,
foxx

[ellocco]

Originally Posted by foxx

Hello,
[...]

mkdir ~/MTP
mtfs ~/MTP

to have your player accessible in /home/username/MTP

Regards,
foxx

You probably mean "mtpfs", but I can not understand,
why this mounts my device, as I understand it you just
establish a mtp filesystem at the new location "~/MTP"

Regards,

Stefan

[foxx]

Hello,

Originally Posted by ellocco

You probably mean "mtpfs"

Thank you, I changed this line.

Originally Posted by ellocco

but I can not understand,
why this mounts my device, as I understand it you just
establish a mtp filesystem at the new location "~/MTP"

It looks like it automatically looks for MTP device attached via USB. If you have only one MTP device attached its getting mounted - I don't know whats happening if you attach more than one device.

Regards,
foxx

[ellocco]

Here are my investigation results to this problem (the problem is not yet resolved, state Apr-2008):
http://www.jpberlin.de/st.pofahl/htm...-protocol.html

Regards,

ellocco

[ellocco]

Originally Posted by foxx

Hello,
[...]

It looks like it automatically looks for MTP device attached via USB. If you have only one MTP device attached its getting mounted - I don't know whats happening if you attach more than one device.

Regards,
foxx

Here on my machine it does not work, ls gives the feedback:

ls -la /media/mtp
ls: /media/mtp: Der Socket ist nicht verbunden

("Der Socket ist nicht verbunden" means: "socket is not connected")

And then from time to time a warning window pops up, that says:
"Eingehängter Datenträger /media/mtp reagiert nicht ..."
(Mounted device /media/mtp is not responding ...)

So, for me it is not yet the solution to the problem :-(

Regards,

ellocco

[foxx]

I don't understand you problem: If you player is detected by the installed libmtp version (try it by using "mtp-detect") mtpfs should mount it like expected - doesnt it mount on you machine?
Are you using my repository? Gutsy ships only libmtp 0.2.1 by default but players like the YP-T10 by Samsung are only supported from 0.2.4.

Regards,
foxx

EDIT: I started writing my answer before you post appeared... Which libmtp version are you using and which player are you using? Does "mtp-detect" detect you player?

[ellocco]

Originally Posted by foxx

I don't understand you problem: If you player is detected by the installed libmtp version (try it by using "mtp-detect") mtpfs should mount it like expected - doesnt it mount on you machine?
Are you using my repository?

No, - not yet.

Originally Posted by foxx

Gutsy ships only libmtp 0.2.1 by default but players like the YP-T10 by Samsung are only supported from 0.2.4.

Regards,
foxx

EDIT: I started writing my answer before you post appeared... Which libmtp version are you using and which player are you using? Does "mtp-detect" detect you player?

a.) I use libmtp vers.0.2.6.1. - b.) No, "mtp-detect" breaks down with an error-message, here is another post from me to this topic:
http://www.anythingbutipod.com/forum...237#post237237