Bug 8510

Summary: Patch to add support for Motorola V360 phone as audio player
Product: hal Reporter: Adam Williamson <adamw>
Component: miscAssignee: David Zeuthen (not reading bugmail) <zeuthen>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: high CC: ernstp
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: patch to support motorola v360 phone as audio player
patch to add support for v360 and appropriate audio paths for PSP and w800
patch to add support for v360 and appropriate audio paths for PSP and w800

Description Adam Williamson 2006-10-05 00:26:23 UTC
Here's a patch (based on the guide at http://blog.pcode.nl/?p=176 ) which
modifies 10-usb-music-players.fdi to see the Motorola V360 phone (when connected
in mass storage mode via its mini-USB port) as an audio player. (It should
actually probably be seen as a video player too, but I'm not sure how to do
that, and this better than nothing :>). I don't know if this can be specified
via HAL, but if it can, the song files should be stored in the /mobile/audio/
directory on the device. I've tested this patch and it works.
Comment 1 Adam Williamson 2006-10-05 00:28:24 UTC
Created attachment 7268 [details] [review]
patch to support motorola v360 phone as audio player
Comment 2 Adam Williamson 2006-10-05 13:41:48 UTC
I did some tooling about and it seems that you can use the key
portable_audio_player.audio_folders to tell the system where audio files should
be stored. I've thus updated the patch to add this key to the V360 entry,
pointing to the appropriate directory - /mobile/audio . I also took the
opportunity to add a couple of other such lines, one for the PSP pointing to
/PSP/MUSIC (that's the correct path for music files on the PSP), and one for the
w800, pointing to /mp3 : there is a comment at the top of the entry for the w800
saying this is where audio files should go, but no actual key. I assume the
entry was written before this key was introduced, or whoever wrote the entry
didn't know about it. Hope this patch is useful.
Comment 3 Adam Williamson 2006-10-05 13:42:40 UTC
Created attachment 7270 [details] [review]
patch to add support for v360 and appropriate audio paths for PSP and w800
Comment 4 Adam Williamson 2006-10-11 15:06:35 UTC
Well, since no-one looked at this yet, here's one more updated version of the
patch - it just adds storage.model and storage.vendor keys for the V360, which
seems to result in apps displaying a more sane name for it.
Comment 5 Adam Williamson 2006-10-11 15:07:49 UTC
Created attachment 7367 [details] [review]
patch to add support for v360 and appropriate audio paths for PSP and w800
Comment 6 Adam Williamson 2006-10-26 09:44:54 UTC
anyone? please? this should be a no-brainer to merge...
Comment 7 Adam Williamson 2006-12-19 14:37:12 UTC
*forlorn poke*
Comment 8 Ernst Sjöstrand 2007-02-11 13:33:42 UTC
Oh, I was just about to report this oneliner for the W800. Why hasn't this been merged?

I actually put in this for the W800:
<append key="portable_audio_player.audio_folders" type="strlist">MP3/</append>
<append key="portable_audio_player.audio_folders" type="strlist">MSSEMC/Media files/audio/</append>

Uppercase MP3 and the other directory is ok also I think. 
A company like Sony Ericsson should hire someone to help with this.. :-)
Comment 9 Adam Williamson 2007-02-12 12:32:21 UTC
I've no idea why it hasn't been merged yet, I keep bumping it :/
Comment 10 Danny Kukawka 2007-02-21 08:56:18 UTC
commit defc0819bb691d3adad05b1b61df080e4db0f726
Author: Danny Kukawka <danny.kukawka@web.de>
Date:   Wed Feb 21 17:54:27 2007 +0100

    amend entries for SE W800i and Motorola V360

    Applied slightly adopted parts of a patch from Adam Williamson
    <awilliamson@mandriva.com> to amend the entries for the SE W800i and
    Motorola V360 with folder and name information (fd.o bug #8510).
Comment 11 Adam Williamson 2007-02-21 11:29:29 UTC
Thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.