bigBADbenny wrote:Indeed: that's why I'd send you both of mine for Android testing
The Mac one would be a contender, imho, no s-video plug, no driver CD, actually works (on a mac).
Easiest way to test is to get the hardware ID's to check. I believe Mac has the same command, if not, boot up a Linux Live CD, plug in your USB device and then open a terminal and issue the
lsusb command to bring up the hardware and vendor ID's of all detected USB devices (supported or not), eg:
- Code: Select all
$ lsusb
Bus 002 Device 004: ID 03eb:8406 Atmel Corp.
Bus 002 Device 003: ID 04ca:7027 Lite-On Technology Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04ca:7028 Lite-On Technology Corp.
Bus 001 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Bus 001 Device 003: ID 8087:0a04 Intel Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bdb:1936 Ericsson Business Mobile Networks BV
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$
So let's say I wanted to find out if the Bluetooth adapter above had support on a given OS but I didn't know who made it or what model it was, I could look up "0a5c:21e6" to find out. In this case the description of the device also conveniently gave us the exact brand and model number of the device, but if it really was unknown, we can now look up the
PCI database to find out that 0a5c is the Vendor ID for Broadcom and that 21e6 is the BCM20702 Bluetooth device - you can also throw "0a5c:21e6" into Google and usually get a match there too.
You can compare your Easycap's vendor and hardware ID's to those listed in the
Linux Easycap wiki. If it's listed as supported in the kernel with no additional tinkering there, there's a good chance it's supported in Android too. For Android, the STK1160 version of the Easycap is preferred and directly supported by projects like Timur's ROM.
I was going to procrastinate, but I put it off...