iPod - Device Action - Manage with Amarok

Forum rules
Before you post please read this

iPod - Device Action - Manage with Amarok

Postby anandrkris on Wed Feb 06, 2013 12:21 am

Hi,

I was able to successfully use Amarok to manage my iPod Nano 4G(Transfer songs, album art work, sync ratings etc) after bit of tweaking. (By generating Hashinfo file and updating Sysinfo file).

Now, when i plug-in my iPod, the device notifier gives the following options -
    1. Open with Dolphin
    2. Download Photos with Gwenview
    3. Download Photos with DigiKam
The above options are more applicable to a Camera than to iPod. There is an iPod icon shown so system is detecting and identfying the device correctly. I believe it is a valid use case to show media related actions for iPod. It is actually possible to add custom 'Device Actions' in KDE System Settings.

Can someone help me in configuring the device action "Manage with Amarok" for iPod device. How exactly do i specify the device is iPod?

Update - Added Device Action screenshot.
Device_Action.jpeg
Screenshot
Device_Action.jpeg (154.68 KiB) Viewed 792 times
Cheers,
If there is a drive, there will be a path
User avatar
anandrkris
Level 5
Level 5
 
Posts: 835
Joined: Fri Nov 16, 2012 1:13 am
Location: Chennai

Linux Mint is funded by ads and donations.
 

Re: iPod - Device Action - Manage with Amarok

Postby anandrkris on Mon Feb 25, 2013 11:35 pm

All,

Update on the above query - I had posted the above question as a comment in the Amarok developer's (iPod specialist) blog and his response is given below.

Hi, your iPod is falsely identified as a camera. This is most usally caused by misconfigured udev rules. See https://bugs.kde.org/show_bug.cgi?id=313827 for background information and how to see if you're affected.

In short, your udev rules are probably setting ID_MEDIA_PLAYER=1 for your iPod while they should've set ID_MEDIA_PLAYER=ipod. This depends on whether gphoto2 and/or libmtp is installed and on the order of udev rules, which is distribution specific. Once you find the root cause, you should file a bug against your distribution so that other users won't get the same problem.


Will check on udevadm ouput once I reach home. Meanwhile am not very clear on udev rules. Any pointers / prior experiences of the issue?
Cheers,
If there is a drive, there will be a path
User avatar
anandrkris
Level 5
Level 5
 
Posts: 835
Joined: Fri Nov 16, 2012 1:13 am
Location: Chennai


Return to KDE

Who is online

Users browsing this forum: No registered users and 1 guest