Add support for Sandisk Sansa Fuze in hal

[Kenneth Mokkelbost]

Binary package hint: hal-info

Sandisk Sansa Fuze is currently not mentioned in 10-usb-music-player.fdi

I've included a patch which in essence is just a copy paste of the entry for Sansa Clip, but with an updated usb-id.

[Martin Pitt (pitti)]

Committed upstream.

[Launchpad Janitor (janitor)]

This bug was fixed in the package hal-info - 20081001+git20081007-0ubuntu1

---------------
hal-info (20081001+git20081007-0ubuntu1) intrepid; urgency=low

  * New git snapshot, with all the currently reported modem and music player
    FDIs from Launchpad committed. (LP: #246741, #261685, #267227, #267727,
    #278458, #278660, #279005, #279182)
  * Drop patches 03_dell_studio.patch and 10-samsung-Q1-keymap.patch,
    committed upstream.

 -- Martin Pitt <email address hidden> Tue, 07 Oct 2008 21:47:56 +0200

[Rob Martin (robmartin)]

Would it be possible to update this fdi, before Intrepid ships, to reflect the new firmware of both the Clip and Fuze as both now support Ogg and Flac (subject to a firmware upgrade)?

Firmware 1.01.15 for the Fuze http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&thread.id=4880
Firmware 01.01.30 for the Clip http://forums.sandisk.com/sansa/board/message?board.id=clip&thread.id=10533

[Martin Pitt (pitti)]

Hm, that's a bit tricky. If we add it, Rhythmbox & friends won't convert ogg/flac to mp3 on older players any more. Unless, of course, the firmware upgrade also changes the product string in a detectable way, so that they can be told apart? If you still have one with the old firmware, maybe you can plug it in, do "lshal > /tmp/old.txt", then upgrade the firmware, pull it out and plug it back in, and do "lshal > /tmp/new.txt" and attach both files?

[Rob Martin (robmartin)]

Martin

As requested.

old.txt (old firmware)
new.txt (new firmware, as mentioned above)

Hope this helps.

[Roger Binns (ubuntu-rogerbinns)]

I just bought an 8GB Fuze today. The current 10-usb-music-player.fdi on Intrepid is wrong. It needs to include 0x74c1 as the USB pid. You can also see 0x74c1 in Rob's listing. It also omits mp3 as a supported format! (The Clip also supports MP3). Actually the listing of supported formats across all Sansa devices in the .fdi file seems rather messy.

Sandisk do push their firmware updates heavily and their earlier releases were somewhat buggy so my preference would be to optimise for current firmware (ie Ogg, Flac support) vs the older stuff.

Doing a firmware upgrade is easy. Under Windows you run their updater software. Under Linux & Mac you place a single file in the root directory of the device and unplug from your computer. So if someone with old firmware ended up with Ogg/Flac files on their device and they didn't play, copying one more file and unplugging would be easy.

[Henry Gomersall (hgomersall)]

The ID on my clip is 0x7434, this needs adding too.

[Martin Pitt (pitti)]

Henry,

current hal-info already has this ID.

[Roger Binns (ubuntu-rogerbinns)]

Where exactly is this information? Just did an update on Intrepid and neither 7434 nor 74c1 show up.

$ grep 7434 /usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi
$ grep -r 7434 /usr/share/hal
$ grep -ri 74c1 /usr/share/hal
$

[Martin Pitt (pitti)]

Roger Binns [2009-01-21 11:54 -0000]:
> Where exactly is this information? Just did an update on Intrepid and
> neither 7434 nor 74c1 show up.

It's not yet on intrepid, but I'll upload the latest version into
intrepid/hardy-proposed soon.

[Rob Martin (robmartin)]

Latest hal-info from intrepid-proposed 20090128-0ubuntu1~intrepid2 has an error at line 497

<append key="portable_audio_player.output_formats" type="strlist">audio/aac</append>

Fuze doesn't support aac

Can I second Roger's suggestion re. rationalising the Sansa Fuze/Clip sections in the fdi. As both devices are based on the same audio chip can we assume a year zero as of Clip and Fuze support for flac November 26, 2008 and combine both devices under one section? Exceptions can be listed as and when new hardware revisions appear.

[Rob Martin (robmartin)]

@Martin

Just re-read the Oct 08 post re. Rhythmbox etc. can this info not be placed in the .is_audio_player file on the device? Am I correct in assuming that this file overrides the fdi info? If so, is the purpose of the hal-info is to identify the capabilities of the device, transcoding and prefered formats should be a userland choice and the responsibility of of those programs rhythmbox, banshee et al which are used to manage the device?

Just a thought.

[Rob Martin (robmartin)]

@Martin Sorry to harp on about this but banshee 1.4.2 has this ability in the Device Properties tab (see attached)

[Martin Pitt (pitti)]

.is_audio_player certainly works, and should override the hal-info tags. However, hal-info should still provide good defaults, so that users don't need to figure this out on their own all the time.

I committed the unification to upstream git:

http://cgit.freedesktop.org/hal-info/commit/?id=6d3dd857c7f7481d894dbad6e00da7b64eec2dcf