Samsung YP-U3 MP3 Player Not Recognized

byker · 03-14-2009, 12:08 PM

I'm only days old to Linux and using LINUXMINT Distro, I have Samsung YP-U3 MP3 Player and it doesn't connect

I know for Microsoft I needed MTP support Drivers so i have downloaded the drivers for linux but it still isn't recognized does anyone please have a simple (FOR DUMMIES) solution

Cheers

rich_c · 03-14-2009, 03:20 PM

I've got a YP-U3 and it works perfectly with Amarok. I'm sure similar apps will play nice with it too, but I've stuck with what works best. I've never even tried to see it as a mass storage device.

jschiwal · 03-14-2009, 03:35 PM

You may also need a libmtp-hal package to get the fdi definitions.

Code:

rpm -qf /usr/share/hal/fdi/information/20thirdparty/10-usb-music-players-libmtp.fdi
libmtp-hal-0.3.3-0.pm.1
libmtp8-0.3.4-2.1
jschiwal@qosmio:/usr/share/hal/fdi> grep U3 /usr/share/hal/fdi/information/20thirdparty/10-usb-music-players-libmtp.fdi
      <!-- Samsung YP-U3 -->
          <merge key="info.product" type="string">YP-U3</merge>
      <!-- Cowon iAudio U3 (MTP mode) -->
          <merge key="info.product" type="string">iAudio U3 (MTP mode)</merge>

Here is the entire xml entry, which you could insert into your 10-usb-music-players-libmtp.fdi file:

Code:

      <!-- Samsung YP-U3 -->
      <match key="usb.vendor_id" int="0x04e8">
        <match key="usb.product_id" int="0x507d">
          <match key="info.capabilities" contains_not="portable_audio_player">
            <append key="info.capabilities" type="strlist">portable_audio_player</append>
          </match>
          <merge key="info.vendor" type="string">Samsung</merge>
          <merge key="info.product" type="string">YP-U3</merge>
          <merge key="info.category" type="string">portable_audio_player</merge>
          <merge key="portable_audio_player.access_method" type="string">user</merge>
          <match key="portable_audio_player.access_method.protocols" contains_not="mtp">
            <append key="portable_audio_player.access_method.protocols" type="strlist">mtp</append>
          </match>
          <append key="portable_audio_player.access_method.drivers" type="strlist">libmtp</append>
          <match key="portable_audio_player.output_formats" contains_not="audio/mpeg">
            <append key="portable_audio_player.output_formats" type="strlist">audio/mpeg</append>
          </match>
          <match key="portable_audio_player.output_formats" contains_not="audio/x-ms-wma">
            <append key="portable_audio_player.output_formats" type="strlist">audio/x-ms-wma</append>
          </match>
          <merge key="portable_audio_player.libmtp.protocol" type="string">mtp</merge>
        </match>
      </match>

byker · 03-15-2009, 05:34 AM

I've tried the above comments with still no joy

Didier Spaier · 03-15-2009, 05:47 AM

I do not have Linx Mint but make sure all libmtp* package (i.e. all packages whose name begin with libmtp) for your distribution are properly installed. Do not install any package for another distribution or version, you would mess up your system.

jschiwal · 03-15-2009, 12:54 PM

The name of the libmtp-hal package is probably standard. If your distro uses HAL & udev, it probably has it.

The name of the fdi file may be different than 10-usb-music-players-libmtp.fdi. You also need to insert the segment in the correct place so you don't end up with an invalid xml file. (If that is your course of action) Of course, make a backup of your old file, and examine it first to make sure it makes sense. My system has a usb-music-players fdi file in /usr/share/hal/fdi/information/10freedesktop/ as well. The YP-U3 isn't listed but other sansa devices are. The one in 20thirdparty is probably an update with newer devices, which haven't been added to the freedesktop.org standard fdi files yet.

Yes, if your system has it's own version containing the fdi files, use that instead of inserting the segment I posted. Also make sure that the dbusd and hald daemons are running. If you boot with the noacpi option, they won't start.
Also try the sansa site and see if they have posted fdi entries to add or a .fdi file.

You might try monitoring /var/log/messages while plugging in the device. Sometimes there is valuable information logged.