Sponsored Content
Full Discussion: Device Names on Android
Operating Systems Linux Android Device Names on Android Post 302866827 by fedora18 on Tuesday 22nd of October 2013 06:18:47 PM
Old 10-22-2013
haha sorry, that was in another forum.

but so far no success. it definitely is a driver issue and so that is why no /dev/ttyUSB* populates in /dev upon plug in.

I have seen that some companies to provide drivers for these adapters so kind of exploring options there.

Also, a lot of people mention that you must OTG usb port....dont know why this would matter as my tablet has a usb2.0 port already.

updates as they come...
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Device Files names and location

HI there. I am studying System administration right now and am stuck on a question that I have failed to find the answer for in my book. The question is: Do device files need to be in the /dev directory and to they need to follow a naming convention? My answer (so far) is that since the... (7 Replies)
Discussion started by: Carl1976
7 Replies

2. Android

Android Scripting Environment: Shell Scripting and Android

I just upgraded to Android 2.2 from 2.1. The GPS issue that was troublesome in 2.1 seems to have been fixed. Some of web browsing seems faster, but it could just be my connection is better today ;) Flash works in some browsers but not very good and it is too slow for Flash apps designed for... (0 Replies)
Discussion started by: Neo
0 Replies

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

4. Android

Running only the Linux kernel of an Android device

I am looking for a way to run on top of the Linux kernel of an Android device. I want to use the existing configured Linux beneath Android rather than put a new Linux distribution onto a device. The article "The Android boot process from power on" (sorry, forum won't let me paste the link)... (0 Replies)
Discussion started by: raoulney
0 Replies

5. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

6. UNIX for Beginners Questions & Answers

Android Device ID Changer shell script

this is worked "ANDROID NOUGAT" how can i use it for "ANDROID OREO" -plz help me... ------------------------------------------- echo " Ã-~-DEVICE ID CHANGINGÃ-~-" sleep 2 echo " " COUNT=1 while do ; echo "settings put secure android_id " | tr -d '\n' > X1... (4 Replies)
Discussion started by: f4is4l
4 Replies
UHSO(4) 						   BSD Kernel Interfaces Manual 						   UHSO(4)

NAME
uhso -- Option N.V. Wireless WAN modem driver SYNOPSIS
uhso* at uhub? port ? HARDWARE
The uhso driver supports at least the following adapters: GlobeSurfer HSUPA GlobeSurfer iCON 7.2 GlobeTrotter Express 40x GlobeTrotter Express HSUPA GlobeTrotter HSUPA GlobeTrotter Max HSDPA GlobeTrotter Module 382 GlobeTrotter iCON 225 GlobeTrotter iCON 321 GlobeTrotter iCON 322 GlobeTrotter iCON 401 GlobeTrotter iCON 505 GlobeTrotter iCON EDGE DESCRIPTION
The Option N.V. modems appear at first as a umass(4) device containing the Windows and MacOS drivers and, upon receipt of a SCSI "REZERO UNIT" command, will detach from the USB bus and reattach as a Wireless WAN modem. Unless disabled by clearing the sysctl(8) variable hw.uhso.autoswitch, the driver will handle that automatically. The modems provide a number of IO channels spread over several USB interfaces which are mapped by function to a standard port number in each driver instance. The defined channels are: Channel Name Port Control 0 Diagnostic 1 Diagnostic 2 2 Application 3 Application 2 4 GPS 5 GPS Control 6 PC Smartcard 7 Modem 8 MSD 9 Voice 10 Network 11 Apart from the Network port, which is attached as a network interface, the ports are attached as tty(4) devices using the port number as the minor device number. In order to connect using pppd(8), the Modem tty should be used (eg /dev/ttyHS0.08). The Network port provides a direct IPv4 interface, but before this can be used the modem needs to be placed in connected mode and network settings subsequently retrieved using the proprietary "_OWANCALL" and "_OWANDATA" AT commands on the Control port. Note that the Modem and Network ports should not be enabled at the same time for USB performance reasons. FILES
/dev/ttyHS?.?? /dev/dtyHS?.?? /dev/ctyHS?.?? SEE ALSO
intro(4), netintro(4), tty(4), uhub(4), usb(4), ifconfig(8) HISTORY
This driver originated as the hso module for FreeBSD written by Frederik Lindberg. It was rewritten for NetBSD, and to provide more complete device support with information extracted from the hso driver for Linux provided by Option N.V. The rewrite and this manual page by Iain Hibbert. BSD
August 26, 2011 BSD
All times are GMT -4. The time now is 05:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy