Ya I know what you mean by non-traditional for sure. With Busybox though I do have access to a lot of UNIX commands which is very helpfull. On the Android tablet this is what I am getting under /dev:
sorry for the long output!
THere are a ton of TTY device names but I am not sure what all of them are for. I also don't see any USB.
Ill keep looking into it. I don't see any reason why my simple serial port logger that works flawlessly on any Linux machine so far can't be setup to work on Android.
A last note: when i try random device names the application does seem to find the name and connect....however while listening (I used the C library's select() statement) it is not getting anything coming in.
Cheers
---------- Post updated at 09:32 AM ---------- Previous update was at 09:25 AM ----------
OH NO my mistake. that was for my desktop. /dev from the device yields:
Ugh... it looks like they just made every possible device without bothering to wonder which are actually present. Is tty.Bluetooth-Modem a symlink? Look for devices which are symlinks.
ya..not pretty.
I am using a serial to USB converter with hardware by Prolific. It is the pl2303 one.
when i call up lsmod on my Linux laptop that runs the application fine I see a module called: usbserial pl2303
when I call up lsmod on the android I don't see it which makes sense.
I am assuming this may be the reason why #lsusb returns seeing the device but /dev/ttyUSB0 doesnt get populated upon attaching the device.
I think my plan of attack is to find out how to get that module on there......thoughts?
---------- Post updated at 03:10 PM ---------- Previous update was at 03:07 PM ----------
Rudy, the system log outputs this when my device gets attached:
One thought: Just because lsusb shows it, does not mean your system has a driver for it. It recognizes by device serial numbers, of which lsusb has its own independent list. (much like lspci.)
If you can find it in /sys/ though, /sys/ can tell you the major and minor numbers of the device:
$ cat /sys/block/sdc/dev
8:32
$ ls -l /dev
...
brw-rw---- 1 root disk 8, 32 Oct 1 13:30 sdc
...
$
interesting....the device doesnt show up in /sys/block when plugged in.
HOWEVER, when i plug in a random usb key (dongle) type is see something being listed as sda
You would not see it in /sys/block, block devices are disks. I used my hard drive as an off-the-cuff example of how to get the major/minor numbers. It might be found under /sys/class/tty/. It is full of virtual terminals which you can ignore, but will have serial ports as well.
Lots of devices these days include a little hard drive thing along with the device. It might have device drivers on it or promotional software. Or it might be something else entirely, when you can see the hardware the way Linux does some things just act strange.
ya been hacking away here and that for sure is the problem.
I am going to look into devices allowing rs232-USB that have drivers for android readily availalble as this could be a long road.
/dev/bus/usb isn't for serial ports, it is for raw USB communication. His software would have to speak USB protocol, and know how to use it to talk to the device.
Sometimes this is necessary for strange cameras, but isn't often done.
They're just saying it must be a USB host port not a USB client port. If you had an android phone you could be stuck with a client port.
Your tablet obviously detects it, so must be acting as a host port. It doesn't have the right driver unfortunately.
The manufacturer is unlikely to have a linux driver, particularly one for Android. Many of these generic USB things work with common drivers though -- with a twiddled USB serial number so the linux driver no longer detects it.
ok then....
well another day here we go...ill see what I can uncover.
you are definitely right...such a PITA though.
trying some different paths here this morning and I notice that in /dev with a USB dongle plugged in I get a 4:0:0:0 number in there. it increments by 1 every time I plug it bag in.....anyone know what that number represents are how I can use it?
---------- Post updated at 09:32 AM ---------- Previous update was at 09:26 AM ----------
which they say they provide a driver for Android and this is the cable chip I am using....I just am not quite sure how to pull the driver out and install it on the tablet.....duh