Ok, we know this thing is written in Mono with a Linux OS, so what about support for Linux? I am running Ubuntu Feisty Fawn and am unable to get this to work even with libmtp.
There is no plan for LINUX support for the Sansa Connect. Currently only Windows XP (32-bit) and VISTA (32-bit) are supported.
On the box it says, Requirements are: windows xp or vista
I get that, surely nearly every MP3 player ever created says “Windows” or “Mac” are a requirement however this has not stopped people from getting them to work with Linux. One would guess that an MP3 player using Linux as the OS would be more easily ported or incorporated into libmtp. I’m not saying SanDisk should do this (although it would be cool) but was wondering if anyone else in the “community” has achived linux-only nirvana.
Not that I am aware of, but I personally don’t use Linux.
Through my experiments with Fedora 7 and the Gnome desktop environment, I’ve been able to download some libraries from http://libmtp.sourceforge.net/ and using Gnomad http://gnomad2.sourceforge.net/ . I discovered that it works for basic transfer in MTP mode, but there has been no luck with DRM Subscription files. If you are using KDE, then you would need to try Amarok instead. Note that I have not had much luck getting Amarok to work with libmtp libraries in a Gnome environment. Hope this helps =^_^=
Message Edited by Psychomaze on 07-25-2007 02:56 PM
I don’t know much about it, but maybe WINE can help…
nvm, my friend uses Ubuntu too and I remember he has a similar problem with his printer.
Message Edited by Zovistograt on 08-01-2007 09:01 PM
Thanks for all the info everyone. I decided to just switch back to Windows XP. Not only does the Connect not work with Linux, but I had problems with wifi and bluetooth. I like Linux but if it’s not going to work for my needs, I have no choice but to use XP.
crazy train
FYI, for you *nix users out there, I downloaded the most recent libmtp source tarball and saw that the Connect is now “supported” by libmtp on Linux. I have yet to try it out myself since I reverted back to WinXP since I could never get the Connect to work with Ubuntu but I may install a virtual Puppy Linux to see if I can test out libmtp.
Libmtp sould work with most MTP mode MP3 Players.
It’s funny, I’ve had this thing for a few days now, and I haven’t even attempted to connect it to my computer. I’ve been filling it up wirelessly
@sansa_e280r wrote:
Libmtp sould work with most MTP mode MP3 Players.
Correct, however libmtp did not support the Connect until this latest release. MTP devices still need to be defined in the libmtp “glue” file which ties the device id together with the correct libmtp settings.
I haven’t had a chance to test the connect with libmtp as of yet but I do know that you are able to get the e200/e200r (in playsforsure mode) working with libmtp 0.2.2. I’ve also gotten the c100, c200, and sansa express working with libmtp. I started hacking around with libmtp and was able to get it working with the sansa view even but I was only able to use it as a root user due to incorrect permissions. This is after setting up the udev rules to include the view. The connect like mentioned earlier is a linux device running mono. For some reason I haven’t been able to get it detected by the os at all. I’ll connect the player and in the cli I run dmesg grep | tail and it doesn’t mention any device being plugged in. I’ll have to test it today when I get a chance.
This is exactly what I was seeing too until I added the Connect’s device ID to the glue file. After that it was detected but didn’t work with libmtp… I have not tried with the new version of libmtp though.
@mistawright wrote:
I haven’t had a chance to test the connect with libmtp as of yet but I do know that you are able to get the e200/e200r (in playsforsure mode) working with libmtp 0.2.2. I’ve also gotten the c100, c200, and sansa express working with libmtp. I started hacking around with libmtp and was able to get it working with the sansa view even but I was only able to use it as a root user due to incorrect permissions. This is after setting up the udev rules to include the view. The connect like mentioned earlier is a linux device running mono. For some reason I haven’t been able to get it detected by the os at all. I’ll connect the player and in the cli I run dmesg grep | tail and it doesn’t mention any device being plugged in. I’ll have to test it today when I get a chance.
Just a quickie:
install libmtp 0.2.6 from sourceforge
http://sourceforge.net/project/showfiles.php?group_id=158745
Use:
./configure --prefix=/usr
NOTE: the --prefix is dependent on yer OS… I use openSuse and it likes that =)
make all
sudo make install
download and install taglib via yum or yast2 or whatever. (every distribution worth a hill of beans provides it. If not, source is here:
http://developer.kde.org/~wheeler/taglib.html
then see if your distribution offers ‘qlix’ ie- yum install or yast2 and search for qlix install it… run qlix and transfer to your Connect to your hearts content.
you can obtain qlix from source at:
Enjoy.
