Well, this won't work unless you start a datacall in the first place. Can you try: adb root adb forward 2222 dev:/dev/ttyUSB0
And then talk to the modem with a suitble terminal (hyperterm?) and see if the modem replies? If it does then check that you've got network: at+cops? at+cgreg? Set a pdp context: at+cgdcont=1,"IP","..." dial: atd*99# then close your term and try starting the ppp deamon as you did... To use the reference ril, Replace the part of the init.rc with service ril-daemon /system/bin/rild -l /system/lib/libreference-ril.so -- -d /dev/ttyUSB0 and see if anything happens in logcat... I'm not sure that the reference ril handles switching the channel from command to data mode and back, so you may need to do some changes there... Ideally, your modem should have more than one com port, so you can dedicate one (or more) to control and one to data... Hope this helps. M. On Mar 22, 9:28 am, BiX <bixt...@gmail.com> wrote: > I've tried 'pppd ttyUSB0' on the console and logcat shows: > > D/pppd ( 1590): using channel 1 > I/pppd ( 1590): Using interface ppp0 > I/pppd ( 1590): Connect: ppp0 <--> /dev/ttyUSB0 > D/Tethering( 1062): ppp0 is not a tetherable iface, ignoring > W/pppd ( 1590): LCP: timeout sending Config-Requests > I/pppd ( 1590): Connection terminated. > E/Tethering( 1062): attempting to remove unknown iface (ppp0), > ignoring > D/pppd ( 1590): using channel 2 > I/pppd ( 1590): Using interface ppp0 > I/pppd ( 1590): Connect: ppp0 <--> /dev/ttyUSB0 > W/pppd ( 1590): tcflush failed: Bad file number > D/Tethering( 1062): ppp0 is not a tetherable iface, ignoring > E/Tethering( 1062): attempting to remove unknown iface (ppp0), > ignoring > > On Mar 17, 5:41 pm, Maffiou <maff...@gmail.com> wrote: > > > > > > > > > Can you send at command on ttyUSB0 ? > > > If yes then you need to try to put the reference ril on it and see > > what happens... (start it with "-d ttyUSB0") > > > Having just one com port may be a bit of a challenge if you want to do > > data... > > > M. > > > On Mar 16, 7:38 am, BiX <bixt...@gmail.com> wrote: > > > > Sorry I do not understand how to get it working with Ubuntu desktop. > > > I only know FTDI driver is needed because an 'lsusb' returns 'Future > > > Technology Devices International, Ltd FT232 USB-Serial (UART) IC'. > > > > Beagleboard booting: > > > > Initializing USB Mass Storage > > > driver... > > > usbcore: registered new interface driver usb- > > > storage > > > USB Mass Storage support > > > registered. > > > usbcore: registered new interface driver > > > usbserial > > > USB Serial support registered for > > > generic > > > usbcore: registered new interface driver > > > usbserial_generic > > > usbserial: USB Serial Driver > > > core > > > USB Serial support registered for > > > debug > > > usbcore: registered new interface driver > > > debug > > > USB Serial support registered for FTDI USB Serial > > > Device > > > usbcore: registered new interface driver > > > ftdi_sio > > > ftdi_sio: v1.5.0:USB FTDI Serial Converters > > > Driver > > > USB Serial support registered for > > > funsoft > > > usbcore: registered new interface driver > > > funsoft > > > USB Serial support registered forGSMmodem (1- > > > port) > > > usbcore: registered new interface driver > > > option > > > option: v0.7.2:USB Driver forGSMmodems > > > > When I plug in thegsmboard: > > > > usb 1-2.1: new full speed USB device using ehci-omap and address > > > 3 > > > ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter > > > detected > > > usb 1-2.1: Detected > > > FT232RL > > > usb 1-2.1: Number of endpoints > > > 2 > > > usb 1-2.1: Endpoint 1 MaxPacketSize > > > 64 > > > usb 1-2.1: Endpoint 2 MaxPacketSize > > > 64 > > > usb 1-2.1: Setting MaxPacketSize > > > 64 > > > usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 > > > > On Mar 16, 10:46 am, Hamilton Vera <hamilton.lis...@gmail.com> wrote: > > > > > Hi there, maybe the best approach is to make it work with your linux > > > > desktop, if you did that please let me know how. > > > > > Probably this device will be handled by a serial driver acm or usb, if > > > > you have one device created it is a good start. > > > > > If the low level driver part is ok we will deal with RIL. Please let > > > > me know about this. > > > > > On Fri, Mar 11, 2011 at 5:55 AM, BiX <bixt...@gmail.com> wrote: > > > > > I am using agsmmodules as shown > > > > > >http://www.google.com/url?sa=D&q=http://www.sparkfun.com/products/9427 > > > > > Currently, I've built FTDI serial driver and BeagleBoard recognize it > > > > > but Android does not receive any signal. > > > > > Can someone enlighten me on the modules or steps I am missing ? > > > > > Thanks. > > > > > > -- > > > > > unsubscribe: android-porting+unsubscr...@googlegroups.com > > > > > website:http://groups.google.com/group/android-porting > > > > > -- > > > > Hamilton Vera > > > > int Administrator (char Network[],char > > > > ComputationalSystems[])http://hvera.wordpress.com @hamiltonvera -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
