Database Users

Usb wireless modem app with linux

Help!!
I just insalled the latest xubuntu on one of my pcs (gutsy gibbon)
trying to get it to connect to the internet thru my uni's wmodem app by usb.
ran
sudo -i
modprobe usbserial vendor=0xbb4 product=0x0cf
already did mkdev for ttyUSB0
dmesg shows device connected to ttyUSB0
echo "ATDT*99#" > /dev/ttyUSB0
causes connection light to go on in wmodem app on uni
but...
when I run wvdialconf I get:
ttyUSB0<*1> ATQ0 V1 E1 .. failed with 2400 baud, next try;9600 baud
ttyUSB0<*1> ATQ0 V1 E1 .. failed with 9600 baud, next try;115200 baud
ttyUSB0<*1> ATQ0 V1 E1 .. failed with 2400 baud, giving up.
Sorry, no modem detected! Is it in use by another program?
Did you configure it properly with setserial?
what do I have 2 do?

oh yeah, tried making 'tmobile' in /etc/ppp/peers
contains:
----
hide-password
noauth
connect "usr/sbin/chat -v -f /etc/chatscripts/tmobile"
debug
ttyUSB0
115200
defaultroute
noipdefault
user "tmobile"
remotename tmobile
ipparam tmobile
usepeerdns
---
and in /etc/chatscripts/tmobile
---
# ispauth PAP
# abortstring
ABORT BUSY 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' "ATDT*99#"
# ispnumber
# OK-AT-OK "ATDT*99#"
# ispconnect
CONNECT \d\c
# prelogin
# ispname
# isppassword
# postlogin
-----
with
----
"tmobile" * "one2one"
----
in my chap-secrets
then tried using
pon tmobile
but light does not come on
running plog gives
last 2 lines as
chat[4923]: send (ATDT*99#^m)
chat[4923]: expect (CONNECT)
please can someone help as I'm not a linux xpert and the only way I have of using the internet is thru my uni.
ps uni works fine with my gf's laptop under XP

Similar problems for me
I have tried a very similar config with my Vario II (Hermes) with no avail. I have this working fine in XP & Vista x32 & x64.
I am also running Ubuntu 7.10 Gutsy. It would be great if someone could help on this issue as I suspect many people are trying to do this at the minute.
Dz

ok, was just being a luser
for some reason u have to use 'modprobe ipaq' instead of 'modprobe usbserial' then it works
Yipeeeeeeeeeeeeeeeeeeeeeeee!!!!

Connecting Android to a serial device using USB-Serial Converter

I am attempting to connect to a serial device from a Android tablet, via
USB-Serial Converter. In order to interface with this particular serial
device, a linux library must be used as an interface.
This library takes an integer as an argument, and tries to connect to the
device at the following location : /dev/ttySx, where x is the arguement. If
2 is provided to the library, it will look for the device at /dev/ttyS2.
Very simple.
When I connect the device to Ubuntu, there's is one simple extra step for
this device to work with the USB-Serial convert. The converter is exposed
at the location /dev/ttyUSB1. I just need to create a simple soft-link with
the serial port pattern (etc "ln -s /dev/ttyUSV1 /dev/ttyS99"). It works
perfectly.
Now the problem arises for Android. The converter is seen at
/dev/bus/usb/01/01. I never seen this convention in other project. The
question is how can I direct the I/O from /dev/ttySX to /dev/bus/usb/01/01

ehpaul said:
I am attempting to connect to a serial device from a Android tablet, via
USB-Serial Converter. In order to interface with this particular serial
device, a linux library must be used as an interface.
This library takes an integer as an argument, and tries to connect to the
device at the following location : /dev/ttySx, where x is the arguement. If
2 is provided to the library, it will look for the device at /dev/ttyS2.
Very simple.
When I connect the device to Ubuntu, there's is one simple extra step for
this device to work with the USB-Serial convert. The converter is exposed
at the location /dev/ttyUSB1. I just need to create a simple soft-link with
the serial port pattern (etc "ln -s /dev/ttyUSV1 /dev/ttyS99"). It works
perfectly.
Now the problem arises for Android. The converter is seen at
/dev/bus/usb/01/01. I never seen this convention in other project. The
question is how can I direct the I/O from /dev/ttySX to /dev/bus/usb/01/01
Click to expand...
Click to collapse
Which android device are you using and with which kernel and android build? In my case I am using kernel 3.0.+ with CM9 on a Kindle Fire and I do see the /dev/ttyUSBx getting created along with the /dev/bus/01/01. It has been a month since I tried it but I was able to see the problem you see and here is what I remember. When you plug the serial convertor both /dev get created but since the Android USB support only uses /dev/bus/usb/01/01, the kernel in order to save power "unmounts" the unused /dev/ttyUSBx after a certain time period. You can try using dmesg to see if that is happening in your case also. There is a kernel build flag that tells the kernel not to "unmount" it but I dont remember it off-hand. Best would be to use the Android USB support to talk to your device instead of the linux library if you can.
--------Update after testing it out again and checking dmesg etc---------------------------
When I plug the FTDI cable this is what shows up in dmesg:
<6>usb 1-1: new full speed USB device number 8 using musb-hdrc
<3>usb 1-1: device v0403 p6001 is not supported
<6>ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
<6>usb 1-1: Detected FT232RL
<6>usb 1-1: Number of endpoints 2
<6>usb 1-1: Endpoint 1 MaxPacketSize 64
<6>usb 1-1: Endpoint 2 MaxPacketSize 64
<6>usb 1-1: Setting MaxPacketSize 64
<6>usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
At this point if I check the filesystem I see both /dev/ttyUSB0 and /dev/bus/usb/001/0xx [ xx being the current device number ]
I can work with /dev/ttyUSB0 and all is well. Now as soon as I invoke any app that uses Android USB Host Mode API to connect
to USB (for enumeration, connection or whatever) the /dev/ttyUSB0 gets disconnected with following message from dmesg:
<6>ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
<6>ftdi_sio 1-1:1.0: device disconnected
At this point /dev/bus/usb/001/0xx is still alive and if I enumerate the USB devices using android API I see the same as the adaptor
name. So looks like till the Android USB API takes over the FTDI is available as /dev/ttyUSB0 but not afterwards.
------------------------Update ends--------------------------------

(a) If you see a /dev/ttyUSB1 device node created, then you can try the following in an Android terminal:
Code:
stty -F /dev/ttyUSB1 raw
cat /dev/ttyUSB1
If this shows data from your device, then you can use directly the device node to read()/write(), POSIX-style, without needing any library.
(b) If you cannot see a /dev/ttyUSB1 in your Android device, this means that you need to load the ftdi_sio kernel module (check android.serverbox.ch/?p=285 for instructions).

Let me link that for you:
"How to enable FTDI Support for your USB Host featuring Honeycomb Tablet (including sample native application)"
Also have a look at FTDI's Android Paper:
"White Paper: Connecting Peripherals to an Android Platform"
and this relevant blog, from this XDA thread.

pankaj013 said:
Which android device are you using and with which kernel and android build? In my case I am using kernel 3.0.+ with CM9 on a Kindle Fire and I do see the /dev/ttyUSBx getting created along with the /dev/bus/01/01. It has been a month since I tried it but I was able to see the problem you see and here is what I remember. When you plug the serial convertor both /dev get created but since the Android USB support only uses /dev/bus/usb/01/01, the kernel in order to save power "unmounts" the unused /dev/ttyUSBx after a certain time period. You can try using dmesg to see if that is happening in your case also. There is a kernel build flag that tells the kernel not to "unmount" it but I dont remember it off-hand. Best would be to use the Android USB support to talk to your device instead of the linux library if you can.
--------Update after testing it out again and checking dmesg etc---------------------------
When I plug the FTDI cable this is what shows up in dmesg:
<6>usb 1-1: new full speed USB device number 8 using musb-hdrc
<3>usb 1-1: device v0403 p6001 is not supported
<6>ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
<6>usb 1-1: Detected FT232RL
<6>usb 1-1: Number of endpoints 2
<6>usb 1-1: Endpoint 1 MaxPacketSize 64
<6>usb 1-1: Endpoint 2 MaxPacketSize 64
<6>usb 1-1: Setting MaxPacketSize 64
<6>usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
At this point if I check the filesystem I see both /dev/ttyUSB0 and /dev/bus/usb/001/0xx [ xx being the current device number ]
I can work with /dev/ttyUSB0 and all is well. Now as soon as I invoke any app that uses Android USB Host Mode API to connect
to USB (for enumeration, connection or whatever) the /dev/ttyUSB0 gets disconnected with following message from dmesg:
<6>ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
<6>ftdi_sio 1-1:1.0: device disconnected
At this point /dev/bus/usb/001/0xx is still alive and if I enumerate the USB devices using android API I see the same as the adaptor
name. So looks like till the Android USB API takes over the FTDI is available as /dev/ttyUSB0 but not afterwards.
------------------------Update ends--------------------------------
Click to expand...
Click to collapse
are you using ftdi's code to modify it?

change /system/etc/permissions
this is from a question on stackoverflow titled "Android USB host and hidden devices" (sorry, i can't add external URLs yet). it worked like a charm on a micromax A120 canvas 2 phone (kitkat 4.4.2). now i can control my Arduino! i used busybox tools to do all the command line work (otherwise chmod wouldn't work). my steps (perhaps some were not required):
(0) install PDAnet drivers on my Windows 8 computer.
(1) root the phone using Vroot (now called iRoot). Very simple, only catch is that the su grant/deny page is partly in chinese, no big deal.
(2) install busybox and jackpal's Android-Terminal-Emulator available on github and the google play store (free).
(3) open a terminal window and become the superuser:
# su
(4) the file system may be read-only, so you might have to remount it:
# mount -o rw,remount -t yaffs2 /
or
# mount -o rw,remount -t rootfs /
or
# mount -o rw,remount -t rootfs rootfs /system
(5) make default.prop read/write:
chmod 666 /default.prop
(6) edit /default.prop, make the following changes:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
... And this is the real meat of it:
(7) To enable USB host API support you should add a file named
android.hardware.usb.host.xml and containing the following lines:
<permissions>
<feature name="android.hardware.usb.host"/>
</permissions>
into folder
/system/etc/permissions
in that folder find file named
handheld_core_hardware.xml or tablet_core_hardware.xml
and add
<feature name="android.hardware.usb.host" />
into <permissions> section.
(8) Reboot your device. Usb host api should work.

"ping" command seems to reboot Nexus 10 with various ROMs

I'm an app developer, and have now received three reports of Nexus 10s, each with a different ROM, rebooting immediately after the Linux "ping" command is invoked.
ROMs include, but are not limited to:
mrRobinson's buttered AOKP (reported 26 April 2013)
ParanoidAndroid 3.90 (reported 3 August 2013)
CM10.2 (reported 17 August 2013)
I believe the early first case is a 4.2 ROM, while the second two are 4.3.
The exact ping command I'm invoking is:
Code:
ping -n -w 6 -c 5 somecomputername
The options on that command are:
-n (no hostname lookup, numeric output only)
-w 6 (6 second deadline)
-c 5 (stop after sending at most 5 ECHO_REQUEST packets)
I'm guessing just "ping somecomputername" will cause the problem though.
I'm posting this because I'm curious to see how widespread the issue might be. As it stands I have no idea where to report it. There may be a problem somewhere upstream of these ROM developers, but whether that's in AOSP or in common code used in a variety of ROMs is unknown to me.
If anyone could kindly check whether there device reboots as result of a ping command, I'd greatly appreciate it. I'm especially interested in whether or not a stock device will do it. And obviously, please do bear in mind that the device might spontaneously reboot if you try this.
Thanks!

Code:
/ # ping -n -w 6 -c 5 www.cnn.com
PING cnn-56m.gslb.vgtf.net (157.166.248.11) 56(84) bytes of data.
--- cnn-56m.gslb.vgtf.net ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5007ms
/ # ping -n -w 6 -c 5 www.spiegel.de
PING www.spiegel.de (62.138.116.3) 56(84) bytes of data.
64 bytes from 62.138.116.3: icmp_seq=1 ttl=246 time=38.5 ms
64 bytes from 62.138.116.3: icmp_seq=2 ttl=246 time=48.5 ms
64 bytes from 62.138.116.3: icmp_seq=3 ttl=246 time=45.5 ms
64 bytes from 62.138.116.3: icmp_seq=4 ttl=246 time=47.6 ms
64 bytes from 62.138.116.3: icmp_seq=5 ttl=246 time=47.0 ms
--- www.spiegel.de ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 38.520/45.452/48.500/3.603 ms
Works without reboot on flaming monkey, trinity_tn TX10.
BTW: -n only makes sense when pinging on addresses. -n suspresses reverse lookups but no lookups.

I'be forgotten to paste my third test: pinging an unresolveble hostname. Works without crash too.

I'll confirm I've got the same problem. Running Cyanogenmod (cm-10.2-20131102-SNAPSHOT-M1). All it takes is a ping <host> it reboots. Never noticed it until today. But never tried until today as far as I remember.

[Q] ppp widget not working

Dear friends,
I have rooted nexus 7 2012, and installed PPP widget. I have configured the APN. It says "connected", but the internet is not working. Here is the PPP widget log, please help me:
PPP Widget version 1.3.3
USB_ModeSwitch log from Mon Dec 23 15:00:41 IST 2013
Raw args from udev: 2-1/2-1:1.0
Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer USB Modem
product USB Modem
serial 1234567890ABCDEF
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/1c9e.f000
! matched. Reading config data
devList 1:
config: TargetVendor set to 1c9e
config: TargetProductList set to 9000,9603,9605,9607
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 2 -v 1c9e -p f000 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1c9e
DefaultProduct= 0xf000
TargetVendor= 0x1c9e
TargetProduct= not set
TargetClass= not set
TargetProductList="9000,9603,9605,9607"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 002/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 1c9e:f000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem
Serial No.: 1234567890ABCDEF
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Reading attributes ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 1c9e:9605 (USB Modem: USB Modem)
Device class of first interface is ff
Now checking for bound driver ...
Driver has bound, device is known
All done, exiting

Help with Sailfish Port

Hi I don't have enough posts to put this into the dev forum but here's what's going on.
I have the disappearing Mobile Network settings issue. I'm running Sailfish 1.1.6.27 from this thread http://forum.xda-developers.com/showpost.php?p=62438815&postcount=192 and am trying this solution to that problem. I run "devel-su systemctl restart [email protected]n" to get Mobile Network back to be visible. But I get
[[email protected] ~]$ devel-su systemctl restart [email protected]n
Password:
Job for [email protected]e failed. See 'systemctl status [email protected]e' and 'journalctl -xn' for details.
I run the status command and get
[[email protected] ~]$ systemctl status [email protected]e
[email protected]e - User Manager for UID 100000.session
Loaded: loaded (/lib/systemd/system/[email protected]; static)
Active: failed (Result: start-limit) since Thu 2015-09-03 22:08:06 CDT; 51s ago
Process: 3025 ExecStartPre=/usr/lib/startup/validate-user %i (code=exited, status=217/USER)
Any idea? Thanks.

Replace session with service and it works like it should.
Sent from my Nexus 4 using Tapatalk