Device Detection

Device Detection

We can detect the type of player that a user has using the USB VID and PID that they identify to the system. To do this, we need to know the VID:PID of all the models Rockbox supports. Since there are conflicts with the usb ids, rbutil also uses other detection methods to detect a device.

Ideas for new Autodetection schemes

The current Autodetection is pretty dumb and needs improvements. So i will try to describe a new better scheme here. Feel free to edit and change.

Start with scanning the USB-IDs of the connected Devices. This can identify all targets where we know the USB-IDs, but as there are devices with duplicate ids, it might give us more then one possible Target for a given USB-ID. At moment it is also not possible to map a USB-ID to a mountpoint on all 3 major OS. But at least it gives us a hint at what targets we have to search for. There might be also Targets without (known) USB-ID, so we have to add those to the list of possible targets.

Next we scan all possible mountpoints and try the following detection methods. The results from this is merged with our list of possible targets.

• rbutil.log -> detects a target exactly
• rockbox-info.txt -> duplicate targets possible
• target-specific files -> duplicate targets possible
• target-specific folders -> duplicate targets possible

Now we analyse our list of possible targets, and check if all devices are fully detected, ie have only one target name, and exactly one mountpoint. If not, we try the target specific detection methods (ipodpatcher, etc) for the targets where we still need more info. The results are again merged into the list.

Finally we remove those entries from the list which dont have a USB-ID, and are still without other info and present the rest to the user.

Work in progress graph to visualize the possibilities: digraph G { graph [bgcolor="#b6c6e5"]; start -> usb [label="no mountpoint,\n 1..n devices" fontsize=8] usb -> mountpoints [label="1..n possible mountpoints,\n 1..n devices" fontsize=8]

mountpoints -> ipodpatcher [label="1 mountpoint,\n 1 device,\n ipod only" fontsize=8 color=yellow] mountpoints -> sansapatcher [label="1 mountpoint\n 1 device\n sansa only" fontsize=8 color=yellow] mountpoints -> "rockbox-info.txt" [label="1 mountpoint\n 1..n devices\n only if already installed", fontsize=8, color=yellow] mountpoints -> "rbutil.log" [label="1 mountpoint,\n 1 device,\n only if already installed" fontsize=8 color=yellow] mountpoints -> "player-specific files" [label="1 mountpoint,\n 1 device\n not always working" fontsize=8 color=yellow]

"rockbox-info.txt" -> end [color=yellow] "rbutil.log" -> end [label="unique match" color=yellowgreen, fontsize=8] ipodpatcher -> end [label="ipods only", color=yellowgreen, fontsize=8] sansapatcher -> end [label="sansas only\n (not e200r)", color=yellowgreen, fontsize=8] "player-specific files" -> end [label="only a few players,\nnot reliable", color=yellowgreen, fontsize=8]

start [shape=box, style=filled, color=red] sansapatcher [shape=box, color=orange, style=filled] ipodpatcher [shape=box, color=orange, style=filled] "rbutil.log" [shape=box,style=filled,color=yellowgreen] "player-specific files" [shape=box,style=filled,color=yellowgreen] end [shape=box,style=filled,color=green] }

Detection methods

Here is a list of all currently known detection methods. The best way to combine them has still to be found.

Device-specific detection

Here's a table of detection methods for the different devices. Items in Red are at the moment not possible to detect.

Modelname	Filename / Detectionmethod	Already used in rbutilqt
All Models	.rockbox/rockbox-info.txt (if it exists)	can't distinguish between X5 / X5V
All Models	rbutil log file (if it exists)
Apple
All Ipods	ipodpatcher / usb ids	video64mb will be detected as video - since Release 3.7 this is fine since we have a single unified build now
Archos
Ondio 128 FM	ondiost.bin
Ondio 128 SP	ondiosp.bin
Jukebox Player	archos.mod
Recorder V1	ajbrec.ajz
Recorder FM	ajbrec.ajz
Recorder V2	ajbrec.ajz
Cowon
iAudio X5, X5L	usb ids
iAudio X5V	usb ids	USB ID unknown, might be the same as X5 (and thus detected as X5)
iAudio M5, M5L	usb ids
iAudio M3, M3L	usb ids
Iriver
H100	usb ids
H120, H140	usb ids
H320, H340	usb ids
H10 20GB	usb ids
H10 5,6GB MTP	usb ids
H10 5,6GB UMS	usb ids
Sandisk
Sansa e200	sansapatcher / usbids
Sansa e200r	-
Sansa c200	sansapatcher
Toshiba
Gigabeat F Series, X Series	GBSYSTEM/
Olympus
m.robe 100	usb ids
Packard Bell
Vibe 500	usb ids

Please help me to fill in the blanks. If you have a idea to detect a device (all red device cant be detected at moment), write it here.

USB IDs

Here's a table of USB IDs. Items in Red are duplicates.

Finding USB IDs

In Windows

Please help me to fill in the blanks. Attach your device to your Windows computer and run usbids from a Windows command line to get a list of devices and their IDs attached to your system. Use the Device Manager to figure out which device is your USB disk, and edit the table above.

In Linux

Linux users can use 'lsusb' or in the /sys/devices tree as follows:

After you plug in the device, you should see a line in syslog similar to this:

scsi.agent[31802]: disk at /devices/pci0000:00/0000:00:10.3/usb1/1-4/1-4:2.0/host3/target3:0:0/3:0:0:0

Looking in /sys/devices/pci0000:00/0000:00:10.3/usb1/1-4/ you'll see a group of pseudofiles. Among them are 'idProduct' and 'idVendor', those are the ID numbers listed here.