fatmac,
Don't give up! ;)
http://support.creative.com/kb/ShowArticle.aspx?sid=19287
For a ZEN Micro, ZEN Sleek, ZEN Touch and ZEN Xtra, the firmware version will show 2.XX.XX if the player has been upgraded into its MTP/PlaysForSure firmware. To check your player's firmware version number:
- Turn on your player.
- From the main menu, select System and Information.
So, what is your ZEN Touch version?
http://en.wikipedia.org/wiki/Creative_Zen
Current Players — ZEN Touch 2
The first ZEN with Android 2.1 on board. (Upgradeable to 2.2) Has a microSD card slot, Bluetooth, wifi, and is available in 8 GB with GPS, or 8 GB or 16 GB without GPS.[4] The player comes bundled with the popular EP-630 in-ear earphones from Creative. A GPS version is also available in the 8 GB capacity.
A firmware to update the player to Android 2.2 was released by Creative on the 26 of April. With the update, the ZEN Touch 2 now support Flash and also Audible content for certain region.
Discontinued players — Zen Touch
The redesigned 40 GB Zen Touch was released on June 7, 2004.[13] The model incorporated major changes in design, functionality and technology.
The Zen Touch has a smaller form factor and larger backlit blue display in a curved industrial design. In addition, the device uses a touch-sensitive vertical strip on the front of the unit for easier file navigation. These changes were enabled by the use of Hitachi's smaller 1.8-inch hard drives. The Touch is available in capacities of 20 and 40 GB. Unlike the previous two generations, the Zen Touch does not have a removable battery, and plays audio for approximately 24 hours. Even though the battery is not removable, it can be replaced rather easily since the case is closed with screws only and the battery attaches with a connector.
The Zen Touch has a brief uncredited appearance in Pepsi's new commercial which aired during Super Bowl XL.[14]
So, seems like Zen Touch not supports MTP, while Zen Touch 2 supports it.
http://askubuntu.com/questions/25571/how-can-i-get-the-creative-zen-touch-to-work
$ lsusb
Bus 002 Device 004: ID 041e:4131 Creative Technology, Ltd Zen Touch (mtp)
What is your output of lsusb
command?
It is interesting for me, and I tried my Lenovo A760 in all existing modes, and here my outputs:
Mass Storage (UMS)
Bus 001 Device 012: ID 17ef:7604 Lenovo
Mass Storage (UMS) + USB debug mode
Bus 001 Device 013: ID 17ef:7605 Lenovo
Media device (MTP)
Bus 001 Device 014: ID 17ef:760a Lenovo
Media device (MTP) + USB debug mode
Bus 001 Device 015: ID 17ef:760b Lenovo
Camera (PTP)
Bus 001 Device 016: ID 17ef:760c Lenovo
Camera (PTP) + USB debug mode
Bus 001 Device 017: ID 17ef:760d Lenovo
I unzipped /usr/share/misc/usb.ids.gz from usbids package. Seems like it knows about Vendor ID 17ef (Lenovo) but knows nothing about Device IDs 7604 and other. I added next lines to the end of Lenovo subsection:
7604 A760 (Mass Storage mode)
7605 A760 (Mass Storage mode, with debug)
760a A760 (MTP mode)
760b A760 (MTP mode, with debug)
760c A760 (PTP mode)
760d A760 (PTP mode, with debug)
After that I gzipped this file and tried again lsusb command. Now I get human readable names like this one:
Bus 001 Device 028: ID 17ef:760a Lenovo A760 (MTP mode)
And I submitted all that numbers in the usb.ids authors web site here. Waiting for checking by administration (I know it may take a long long time).
Also I added my device in the /etc/udev/rules.d/69-libmtp.rules (shipped with libmtp package) to the end of Lenovo section:
# Lenovo A760 (MTP mode)
ATTR{idVendor}=="17ef", ATTR{idProduct}=="760a", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
# Lenovo A760 (MTP mode + USB Debug Mode)
ATTR{idVendor}=="17ef", ATTR{idProduct}=="760b", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
It works as before. And gMTP shows that my device is unknown as before too (but it works anyway). Seems like I should re-build libmtp with these changes.
PS. I think this article is partially useful too: https://bbs.archlinux.org/viewtopic.php?id=68587
It describes how to modify /etc/udev/rules.d/65-libmtp.rules (in our case it is 69-libmtp.rules).
But next part (with Amarok) is not so useful because we use gMTP instead.