Hi Mikkel, I can run pppd now but it failed with "unrecognized option '/dev/pts/1'" and "Couldn't attach to PPP unit 1: m".
Would you please tell me what is wrong with pppd? I have found there are device nodes /dev/pts/0 and /dev/pts1 created by gsm0710muxd. I have tried the following methods: 1. /system/bin/pppd $* 2. /system/xbin/pppd /dev/pts/1 115200 mru 1280 mtu 1280 nodetach debug dump defaultroute usepeerdns novj noauth novjccomp noipdefault ipcp-accept-local ipcp-accept-remote connect-delay 5000 Thanks in advance! Best Regards, Edward Attached pppd log: E/pppd ( 1034): unrecognized option '/dev/pts/1' D/pppd ( 1042): using channel 5 I/pppd ( 1042): Using interface ppp0 I/pppd ( 1042): Connect: ppp0 <--> /dev/pts/1 D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1042): rcvd P D/pppd ( 1042): sent P D/pppd ( 1050): using channel 5 E/pppd ( 1050): Couldn't attach to PPP unit 1: m I/pppd ( 1042): Modem hangup I/pppd ( 1042): Connection terminated. E/pppd ( 1059): unrecognized option '/dev/pts/1' # D/pppd ( 1068): using channel 6 I/pppd ( 1068): Using interface ppp0 I/pppd ( 1068): Connect: ppp0 <--> /dev/pts/1 D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1068): rcvd P D/pppd ( 1068): sent P D/pppd ( 1076): using channel 6 E/pppd ( 1076): Couldn't attach to PPP unit 1: m I/pppd ( 1068): Modem hangup I/pppd ( 1068): Connection terminated. E/pppd ( 1085): unrecognized option '/dev/pts/1' D/pppd ( 1093): using channel 7 I/pppd ( 1093): Using interface ppp0 I/pppd ( 1093): Connect: ppp0 <--> /dev/pts/1 D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1093): rcvd P D/pppd ( 1093): sent P D/pppd ( 1101): using channel 7 E/pppd ( 1101): Couldn't attach to PPP unit 1: m I/pppd ( 1093): Modem hangup I/pppd ( 1093): Connection terminated. D/pppd ( 1112): using channel 8 I/pppd ( 1112): Using interface ppp0 I/pppd ( 1112): Connect: ppp0 <--> /dev/pts/1 D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1112): rcvd P D/pppd ( 1112): sent P D/pppd ( 1120): using channel 8 E/pppd ( 1120): Couldn't attach to PPP unit 1: m I/pppd ( 1112): Modem hangup I/pppd ( 1112): Connection terminated. localhost login: localhost login: localhost login: ff Password: D/pppd ( 1131): using channel 9 I/pppd ( 1131): Using interface ppp0 I/pppd ( 1131): Connect: ppp0 <--> /dev/pts/1 D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P # D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P # D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P # D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P Login incorrect localhost login: D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P loD/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1131): rcvd P D/pppd ( 1131): sent P gD/pppd ( 1131): rcvd P D/pppd ( 1131): sent P D/pppd ( 1139): using channel 9 cE/pppd ( 1139): Couldn't attach to PPP unit 1: m I/pppd ( 1131): Modem hangup I/pppd ( 1131): Connection terminated. On Fri, Aug 7, 2009 at 9:50 PM, Christensen, Mikkel<m...@ti.com> wrote: > Try this: > > > > diff --git a/rootdir/etc/init.gprs-pppd b/rootdir/etc/init.gprs-pppd > > index 521eec9..c2367f0 100755 > > --- a/rootdir/etc/init.gprs-pppd > > +++ b/rootdir/etc/init.gprs-pppd > > @@ -13,7 +13,8 @@ PPPD_PID= > > > > /system/bin/log -t pppd "Starting pppd" > > > > -/system/bin/pppd $* > > +#/system/bin/pppd $* > > +/system/xbin/pppd /dev/pts/1 115200 mru 1280 mtu 1280 nodetach debug dump > defaultroute usepeerdns novj noauth novjccomp noipdefault ipcp-accept-local > ipcp-accept-remote connect-delay 5000 > > > > PPPD_EXIT=$? > > PPPD_PID=$! > > diff --git a/rootdir/etc/ppp/ip-up b/rootdir/etc/ppp/ip-up > > index cb2d577..7c684ac 100755 > > > > > > Remember to change the baudrate and the other ppp parameters accordingly to > your setup. > > > > Best regards, > > Mikkel > > ________________________________ > > From: samuel omlin [mailto:samuel.om...@gmail.com] > Sent: Friday, August 07, 2009 5:56 AM > To: Hald, Ulrik Bech > Cc: edwardlee lee; Christensen, Mikkel; omapandroid-discuss...@gforge.ti.com > > Subject: Re: RILD works abnormally after setting up APN via GPRS > > > > Hi Ulrik, > > (Updated) > > For the issue of pppd not working, the following changes have been patched > into the corresponding parts, as shown below. > 1> Enabling ppp support with kenel > > “Device Drivers” -> “Networking Support” -> “PPP” > > 2> Adding the control permissions for pppd in "/yourdroid/system/core/init/ > property_service.c" > > struct { > const char *service; > unsigned int uid; > > } control_perms[] = { > > {"pppd_gprs", AID_RADIO }, > {NULL, 0 } > }; > > 3> Adding the pppd setting in "youdroid/system/core/rootdir/Android.mk" > > copy_from := \ > > etc/init.gprs-pppd \ > etc/ppp/chap-secrets \ > etc/ppp/ip-down \ > etc/ppp/ip-up > > 4> Setting ppp property in init.rc > > setprop ro.radio.use-ppp yes > > 5> Defining ppp service entry to start up pppd in init.rc > > service pppd_gprs /etc/init.gprs-pppd /dev/pts/1 > user root > group radio cache inet misc > disabled > > 6> Contents of the init.gprs-pppd script > > > > #!/system/bin/sh > > # An unforunate wrapper script > > # so that the exit code of pppd may be retrieved > > > > > > # this is a workaround for issue #651747 > > > > > > > > #trap "/system/bin/sleep 1;exit 0" TERM > > > > > > PPPD_PID= > > > > /system/bin/setprop "net.gprs.ppp-exit" "" > > > > /system/bin/log -t pppd "Starting pppd" > > > > /system/bin/pppd $* > > > > > > > > > > PPPD_EXIT=$? > > PPPD_PID=$! > > > > /system/bin/log -t pppd "pppd exited with $PPPD_EXIT" > > > > /system/bin/setprop "net.gprs.ppp-exit" "$PPPD_EXIT" > > > > After going through the aforementioned six steps especially intended for > pppd, these messages below is still got, unable to enable pppd. > > Send<3>init: sys_prop: Unable to start service ctl [pppd_gprs] uid: 1001 > pid:977 > init: sys_prop: Unable to start service ctl [pppd_gprs] uid: 1001 pid:977 > > So, please double check that if the procedures above for starting up pppd > when establishing data connection via gprs/egprs(edge) is right. Meanwhile, > please also explain the reason of "Unable to start service ctl [pppd_gprd] > uid: 1001 pid:977" and correct me to boot up pppd to transfer data via > gprs/egprs(edge). > > Thanks a lot!! > > > B. R. > Samuel > > On Fri, Aug 7, 2009 at 6:48 PM, samuel omlin <samuel.om...@gmail.com> wrote: > > Hi Ulrik, > > For the issue of pppd not working, the following changes have been patched > into the corresponding parts, as shown below. > 1> Enabling ppp support with kenel > > “Device Drivers” -> “Networking Support” -> “PPP” > > 2> Adding the control permissions for pppd in "/yourdroid/system/core/init/ > property_service.c > > struct { > const char *service; > unsigned int uid; > > } control_perms[] = { > > {"pppd_gprs", AID_RADIO }, > {NULL, 0 } > }; > > 3> Setting ppp property in init.rc > > setprop ro.radio.use-ppp yes > > 4> Defining ppp service entry to start up pppd in init.rc > > service pppd_gprs /etc/init.gprs-pppd /dev/pts/1 > user root > group radio cache inet misc > disabled > > 5> Contents of the init.gprs-pppd script > > > > #!/system/bin/sh > > # An unforunate wrapper script > > # so that the exit code of pppd may be retrieved > > > > > > # this is a workaround for issue #651747 > > > > > > #trap "/system/bin/sleep 1;exit 0" TERM > > > > > > PPPD_PID= > > > > /system/bin/setprop "net.gprs.ppp-exit" "" > > > > /system/bin/log -t pppd "Starting pppd" > > > > /system/bin/pppd $* > > > > > > > > PPPD_EXIT=$? > > PPPD_PID=$! > > > > /system/bin/log -t pppd "pppd exited with $PPPD_EXIT" > > > > /system/bin/setprop "net.gprs.ppp-exit" "$PPPD_EXIT" > > > > After going through the aforementioned five steps especially intended for > pppd, these messages below is still got, unable to enable pppd. > > Send<3>init: sys_prop: Unable to start service ctl [pppd_gprs] uid: 1001 > pid:977 > init: sys_prop: Unable to start service ctl [pppd_gprs] uid: 1001 pid:977 > > So, please double check that if the procedures above for starting up pppd > when establishing data connection via gprs/egprs(edge) is right. Meanwhile, > please also explain the reason of "Unable to start service ctl [pppd_gprd] > uid: 1001 pid:977" and correct me to boot up pppd to transfer data via > gprs/egprs(edge). > > Thanks a lot!! > > > B. R. > Samuel > > On Fri, Aug 7, 2009 at 8:59 AM, edwardlee lee <edwardlee.2...@gmail.com> > wrote: > > pppd damemon still has not run. I have changed "dont_copy" to "copy_from". > > Also I have changed the file "property_service.c" because of "init: > sys_prop: Unable to start service ctl [pppd_gprs]" and I referred to > the post > "http://groups.google.com/group/android-platform/browse_thread/thread/6a30319fe85877ac";. > > Attached file is muxd log. > > I send "ATD*98*1#" at line 3093 and got "CONNECT" at line > 3128,3185,3257,3297,3330,3364,3398. > > But then I got "NO CARRIER" at line 3432 and pppd failed to run > because of "init: sys_prop: Unable to start service ctl [pppd_gprs]" > at line 3137. > > Many thanks for your help. > > > On Thu, Aug 6, 2009 at 7:28 PM, samuel omlin<samuel.om...@gmail.com> wrote: >> Hi Mikkel, >> >> Before this, we have discussed about these components/models necessary to >> implement the complete radio functionality including voice, data, sms, as >> shown below. >> >> RIL (Radio Interface Layer) >> PPP (Point-to-Point Protocol) >> MUX (TS 27.010 MUltipleXer protocol) >> >> From a phone's architecture perspective, it seems that the most underlying >> (i.e. UART) interfacing directly with modem (in this case, that is edg308) >> is not yet mentioned in the previous posts. >> >> So, for this part the following problems from me are highlighted. >> >> Q1: For UART(or serial), which parts of source codes within the kernel or >> others are involved to drive uart/serial well? >> >> Q2: How will UART/Serial be configured within the kernel or others? >> >> Q3: Besides these problems mentioned above, what other problems are taken >> care still? >> >> >> Thanks!! >> >> >> B. R. >> Samuel >> >> On Thu, Aug 6, 2009 at 12:42 PM, edwardlee lee <edwardlee.2...@gmail.com> >> wrote: >>> >>> Thank Mikkel and Samuel. I will try it. >>> >>> On Thu, Aug 6, 2009 at 11:27 AM, samuel omlin<samuel.om...@gmail.com> >>> wrote: >>> > Hi Edward, >>> > >>> > So sorry for my mistakes. Hopefully, the mistakes never cause >>> > something, >>> > bad >>> > or unfortunate happening!! >>> > >>> > So, particularly correct my own mistakes as shown below. >>> > >>> > copy_from := \ >>> > etc/init.gprs-pppd \ >>> > etc/ppp/chap-secrets \ >>> > etc/ppp/ip-down \ >>> > etc/ppp/ip-up >>> > >>> > In the meantime, note also that these contents shown above are >>> > positioned in >>> > the beginning of "Android.mk" which is located at the directory of >>> > "youdroid/system/core/rootdir/". >>> > For example, the contents are completely shown at the file of >>> > "Android.mk" >>> > as the following. >>> > >>> > LOCAL_PATH:= $(call my-dir) >>> > include $(CLEAR_VARS) >>> > >>> > # files that live under /system/etc/... >>> > copy_from := \ >>> > etc/init.gprs-pppd \ >>> > etc/ppp/chap-secrets \ >>> > etc/ppp/ip-down \ >>> > etc/ppp/ip-up >>> > >>> > Finally, just hope that it is available!! Good Luck!! >>> > >>> > >>> > B. R. >>> > Samuel >>> > >>> > On Wed, Aug 5, 2009 at 9:19 PM, Christensen, Mikkel <m...@ti.com> wrote: >>> >> >>> >> Hi, >>> >> >>> >> >>> >> >>> >> Actually you should add it to the “copy_from” section and not the >>> >> “dont_copy” section. >>> >> >>> >> >>> >> >>> >> Best regards, >>> >> >>> >> Mikkel >>> >> >>> >> ________________________________ >>> >> >>> >> From: samuel omlin [mailto:samuel.om...@gmail.com] >>> >> Sent: Wednesday, August 05, 2009 2:53 AM >>> >> To: edwardlee lee >>> >> Cc: Christensen, Mikkel; omapandroid-discuss...@gforge.ti.com >>> >> >>> >> Subject: Re: RILD works abnormally after setting up APN via GPRS >>> >> >>> >> >>> >> >>> >> Hi Edward, >>> >> >>> >> Please add the following line into the Android.mk located at the >>> >> directory, "system/core/rootdir/". >>> >> dont_copy := \ >>> >> etc/init.gprs-pppd \ >>> >> etc/ppp/chap-secrets \ >>> >> etc/ppp/ip-down \ >>> >> etc/ppp/ip-up >>> >> >>> >> And then, try it. Good Luck. >>> >> >>> >> >>> >> B. R. >>> >> Samuel >>> >> >>> >> On Wed, Aug 5, 2009 at 10:38 AM, edwardlee lee >>> >> <edwardlee.2...@gmail.com> >>> >> wrote: >>> >> >>> >> Sorry, would you please tell me how to modify >>> >> "system/core/rootdir/Android.mk"? >>> >> >>> >> Do you mean add "ppp \" in it? >>> >> >>> >> On Wed, Aug 5, 2009 at 3:51 AM, Christensen, Mikkel<m...@ti.com> wrote: >>> >> > Hi, >>> >> > >>> >> > >>> >> > >>> >> > This looks reasonable. You can get the init.gprs-pppd to be included >>> >> > in >>> >> > the >>> >> > system by modifying the following makefile: >>> >> > >>> >> > system/core/rootdir/Android.mk >>> >> > >>> >> > >>> >> > >>> >> > The code is self explaining. >>> >> > >>> >> > >>> >> > >>> >> > Best regards, >>> >> > >>> >> > Mikkel >>> >> > >>> >> > ________________________________ >>> >> > >>> >> > From: samuel omlin [mailto:samuel.om...@gmail.com] >>> >> > Sent: Tuesday, August 04, 2009 7:19 AM >>> >> > To: edwardlee lee; Christensen, Mikkel >>> >> > Cc: omapandroid-discuss...@gforge.ti.com >>> >> > Subject: Re: RILD works abnormally after setting up APN via GPRS >>> >> > >>> >> > >>> >> > >>> >> > Hi Mikkel/Edward, >>> >> > >>> >> > What a sharp pair of eyes, Mikkel!! The information for modem board >>> >> > is >>> >> > found >>> >> > out from the attachment about radio log. :) >>> >> > >>> >> > After reading through this article of "Modem on the Zoom platform" >>> >> > from >>> >> > omapzoom.org and based on the previous posts between us, some >>> >> > general >>> >> > rules >>> >> > of porting ril together with mux to modem that you select are >>> >> > highlighted, >>> >> > as follows. >>> >> > >>> >> > Statement: the way of Modem' communication with AP (Application >>> >> > Processor) >>> >> > is based on UART underneath Android platform. >>> >> > >>> >> > 1> Grabbing source codes of RIL and MUX (conforming to >>> >> > TS-27.007/TS-27.005 >>> >> > andTS-27.010 separately) from the following links. >>> >> > a. RIL from Edg308 Modem supporting GSM/GRPS/EGPRS(EDGE) >>> >> > >>> >> > git://git.omapzoom.org/platform/hardware/enfora/edg308-ril.git >>> >> > or broswing online >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > http://git.omapzoom.org/?p=platform/hardware/enfora/edg308-ril.git;a=tree >>> >> > >>> >> > b. MUX for multiplexing mutil virtual channels (e.g. at-command >>> >> > channel >>> >> > and >>> >> > ppp channel) via a single serial/uart >>> >> > git://git.omapzoom.org/platform/hardware/ti/omap3.git >>> >> > or browsing online >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git;a=tree;f=gsm0710muxd;h=49237ba9c7b5a535ac2821e566119d8934bac756;hb=HEAD >>> >> > >>> >> > c. PPP for establishing a connetion with point-to-point via modem >>> >> > for >>> >> > transferring data >>> >> > git://git.omapzoom.org/platform/external/ppp.git >>> >> > or browing online >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > http://git.omapzoom.org/?p=platform/external/ppp.git;a=tree;f=pppd;h=fc96368ad7991e0eec48d07ba52f5e33384c5388;hb=HEAD >>> >> > >>> >> > 2> Making RIL, MUX and PPP appropriate for the selected modem with a >>> >> > specific set of at commands from the source-code level >>> >> > >>> >> > 3> Putting together all source codes to build a complete system >>> >> > under >>> >> > android platform. Meanwhile, keeping in mind that enabling ppp >>> >> > support >>> >> > within the linux kernel by configuring the following lines. >>> >> > “Device Drivers” -> “Networking Support” -> “PPP” >>> >> > >>> >> > 4> Configuring the specific setting of modem within init.rc >>> >> > a. Changing permissions >>> >> > # change permissions for modem >>> >> > chmod 0660 /dev/ttyS0 >>> >> > chown radio radio /dev/ttyS0 >>> >> > >>> >> > b. Defining the modem-related settings >>> >> > # Define modem related settings >>> >> > setprop ro.radio.use-ppp yes >>> >> > >>> >> > c. Defining the muxd-related settings >>> >> > Note that checking which serial port is conneted to the selected >>> >> > modem, >>> >> > and >>> >> > the one supports what rangs of baud rates and which mux-mode, >>> >> > "basic" >>> >> > or >>> >> > "advanced". >>> >> > >>> >> > service mux /system/bin/gsm0710muxd -v -s /dev/ttyS0 -b 460800 -f 64 >>> >> > -m >>> >> > advanced >>> >> > user radio >>> >> > group radio cache inet misc >>> >> > oneshot >>> >> > >>> >> > d. Defining the rild-related settings >>> >> > service ril-daemon /system/bin/rild -l >>> >> > /system/lib/libenforaedg308-ril.so -- >>> >> > -d /dev/pts/0 >>> >> > socket rild stream 660 root radio >>> >> > socket rild-debug stream 660 radio system >>> >> > user root >>> >> > group radio cache inet misc >>> >> > >>> >> > e. Defining the ppp-related settings >>> >> > service pppd_gprs /etc/init.gprs-pppd /dev/pts/1 >>> >> > user root >>> >> > group radio cache inet misc >>> >> > disabled >>> >> > >>> >> > 5> Constructing the appropriate script of init.gprs-pppd to start up >>> >> > pppd >>> >> > The following lines is intended for the init.gprs-pppd script. >>> >> > >>> >> > #!/system/bin/sh >>> >> > >>> >> > # An unforunate wrapper script >>> >> > >>> >> > # so that the exit code of pppd may be retrieved >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > # this is a workaround for issue #651747 >>> >> > >>> >> > >>> >> > >>> >> > #trap "/system/bin/sleep 1;exit 0" TERM >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > PPPD_PID= >>> >> > >>> >> > >>> >> > >>> >> > /system/bin/setprop "net.gprs.ppp-exit" "" >>> >> > >>> >> > >>> >> > >>> >> > /system/bin/log -t pppd "Starting pppd" >>> >> > >>> >> > >>> >> > >>> >> > /system/bin/pppd $* >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > >>> >> > PPPD_EXIT=$? >>> >> > >>> >> > PPPD_PID=$! >>> >> > >>> >> > >>> >> > >>> >> > /system/bin/log -t pppd "pppd exited with $PPPD_EXIT" >>> >> > >>> >> > >>> >> > >>> >> > /system/bin/setprop "net.gprs.ppp-exit" "$PPPD_EXIT" >>> >> > >>> >> > Please also Mikkel double-check these contents above for the >>> >> > init.gprs-pppd. >>> >> > In the meantime, spell out how to make the init.gprs-pppd available >>> >> > and >>> >> > appropriate to the selected system. >>> >> > >>> >> > 6> Debugging >>> >> > a. Getting Radio Log to debug rild >>> >> > logcat -b radio >>> >> > >>> >> > b. Getting PPP Log to debug pppd >>> >> > logcat pppd:V*:S& >>> >> > >>> >> > c. Getting whole stack Log to debug android platform >>> >> > logcat >>> >> > >>> >> > >>> >> > Finally, please also Edward recheck the issuse pertaining to the >>> >> > exception >>> >> > of pppd when establishing data connection via gprs or egprs(edge), >>> >> > in >>> >> > accordance with the aforementioned procedures. Good Luck!! >>> >> > >>> >> > Reference: >>> >> > a. Modem on the Zoom platform >>> >> > https://omapzoom.org/gf/project/omapandroid/wiki/?pagename=modem >>> >> > b. Script of init.gprs-pppd >>> >> > http://paste.lisp.org/display/50709 >>> >> > c. Usages of the logcat and adb tools >>> >> > http://developer.android.com/guide/developing/tools/adb.html >>> >> > >>> >> > >>> >> > B. R. >>> >> > Samuel >>> >> > >>> >> > On Tue, Aug 4, 2009 at 8:59 AM, edwardlee lee >>> >> > <edwardlee.2...@gmail.com> >>> >> > wrote: >>> >> > >>> >> > Hi Mikkel, >>> >> > >>> >> > Thank for your reply! >>> >> > >>> >> > Yes, you are right. I ported gsm0710muxd of git.omapzoom.org to >>> >> > NXP5209. >>> >> > >>> >> > I have checked pppd and found pppd had not run. >>> >> > >>> >> > I make sure pppd exists in system/bin and system/xbin. >>> >> > >>> >> > Here are rild related setting in the init.rc: >>> >> > # Define modem related settings >>> >> > setprop ro.radio.use-ppp yes >>> >> > setprop keyguard.no_require_sim 1 >>> >> > setprop ro.config.nocheckin yes >>> >> > ... >>> >> > service mux /system/bin/gsm0710muxd -s /dev/ttyS0 -n 3 -m basic >>> >> > user radio >>> >> > group radio cache inet misc >>> >> > oneshot >>> >> > ... >>> >> > service ril-daemon /system/bin/rild -l >>> >> > /system/lib/libenforaedg308-ril.so -- -d /dev/pts/0 >>> >> > socket rild stream 660 root radio >>> >> > socket rild-debug stream 660 radio system >>> >> > user root >>> >> > group radio cache inet misc >>> >> > ... >>> >> > service pppd_gprs /etc/init.gprs-pppd /dev/pts/1 >>> >> > user root >>> >> > group radio cache inet misc >>> >> > disabled >>> >> > ... >>> >> > >>> >> > I have seen gprs connected for a while but then rild get "NO >>> >> > CARRIER" >>> >> > from the log. >>> >> > >>> >> > Does modem disconnect from carrier if gprs channel don't receive >>> >> > response from TE because pppd failed to run? >>> >> > >>> >> > Best Regards, >>> >> > >>> >> > Edward >>> >> > >>> >> > On Mon, Aug 3, 2009 at 9:39 PM, Christensen, Mikkel<m...@ti.com> >>> >> > wrote: >>> >> >> Hi, >>> >> >> >>> >> >> >>> >> >> >>> >> >> You are trying to use the Enfora RIL with a NXP Nexperia 5209 >>> >> >> modem. >>> >> >> It >>> >> >> might work but there could be places where you need to customize it >>> >> >> to >>> >> >> your >>> >> >> modem. You will have to look at the documentation that you got with >>> >> >> the >>> >> >> modem especially the AT command reference. >>> >> >> >>> >> >> >>> >> >> >>> >> >> Another area where I would look is in the pppd area. Get the log >>> >> >> from >>> >> >> pppd >>> >> >> and check if a PPP connection is getting established. Do like this >>> >> >> (logcat >>> >> >> pppd:V *:S&) >>> >> >> >>> >> >> If there are problems with the connection it might be some of the >>> >> >> PPP >>> >> >> parameters that China Mobile network does not support. Try to >>> >> >> modify >>> >> >> the >>> >> >> init.gprs-pppd file to find the right parameters to call pppd with. >>> >> >> >>> >> >> >>> >> >> >>> >> >> Good luck. >>> >> >> >>> >> >> >>> >> >> >>> >> >> Best regards, >>> >> >> >>> >> >> Mikkel >>> >> >> >>> >> >> ________________________________ >>> >> >> >>> >> >> From: samuel omlin [mailto:samuel.om...@gmail.com] >>> >> >> Sent: Monday, August 03, 2009 7:00 AM >>> >> >> To: Christensen, Mikkel >>> >> >> Cc: edwardlee.2...@gmail.com; omapandroid-discuss...@gforge.ti.com >>> >> >> Subject: RILD works abnormally after setting up APN via GPRS >>> >> >> >>> >> >> >>> >> >> >>> >> >> Hi Mikkel, >>> >> >> >>> >> >> First of all, thank you for your attention!! >>> >> >> >>> >> >> Here's a issue that is focused on the exceptions from rild or other >>> >> >> layers >>> >> >> after setting up apn via gprs under android!! >>> >> >> Meanwhile, just hope that you can give me a further analysis in >>> >> >> accordance >>> >> >> with your experiences. >>> >> >> >>> >> >> For this scenario of rild's exceptions, in addition, the originally >>> >> >> analyzed >>> >> >> result is as follows. >>> >> >> >>> >> >> 0> Attached to local mobile network for gprs or egprs (edge) >>> >> >> D/AT : AT> AT+CGREG=1 >>> >> >> D/AT : AT< OK >>> >> >> .... >>> >> >> .... >>> >> >> D/AT : AT> AT+CREG? >>> >> >> D/AT : AT< +CREG: 1,1 >>> >> >> D/AT : AT< OK >>> >> >> by judging from these at-commands and responses above, the mobile >>> >> >> terminal >>> >> >> is registered on "home network". >>> >> >> so, this procedure is normal. >>> >> >> (PS: this procedure is normally completed during the initiation of >>> >> >> radio >>> >> >> functionality, that is, rild is initialized.) >>> >> >> >>> >> >> >>> >> >> 1> Get Preferred APN, namely cmnet here. >>> >> >> D/GSM : Get PreferredAPN >>> >> >> D/GSM : [DataConnectionTracker] ***trySetupData due to >>> >> >> simLoaded >>> >> >> D/GSM : [DSAC DEB] trySetupData with mIsPsRestricted=false >>> >> >> D/GSM : [DataConnectionTracker] Create from allApns : [cmnet, >>> >> >> 3, >>> >> >> 46000, >>> >> >> cmnet, , , , , , *] >>> >> >> D/GSM : [DataConnectionTracker] Setup watingApns : [cmnet, 3, >>> >> >> 46000, >>> >> >> cmnet, , , , , , *] >>> >> >> D/GSM : [PdpConnection] Connecting to carrier: 'cmnet' APN: >>> >> >> 'cmnet' >>> >> >> proxy: '' port: ' >>> >> >> D/RILJ : [0054]> SETUP_DEFAULT_PDP cmnet >>> >> >> D/GSM : [DataConnectionTracker] setState: INITING >>> >> >> D/AT : AT< +CSQ: 9,99 >>> >> >> D/AT : AT< OK >>> >> >> D/RIL : onRequest: SETUP_DEFAULT_PDP >>> >> >> D/RIL : requesting data connection to APN 'cmnet' >>> >> >> >>> >> >> >>> >> >> 2> Defining an PDP context with APN before establishing a session >>> >> >> D/AT : AT> AT+CGDCONT=1,"IP","cmnet" >>> >> >> D/RILJ : [0053]< SIGNAL_STRENGTH {9, 99} >>> >> >> D/AT : AT< OK >>> >> >> >>> >> >> ====================================== >>> >> >> Below is the first exception or error from rild. >>> >> >> Q1: what reason causes the scenario? >>> >> >> >>> >> >> D/AT : AT> AT+CGEREP=1,0 >>> >> >> D/AT : AT< ERROR >>> >> >> ====================================== >>> >> >> >>> >> >> 3> Activating a seession directly by "ATD*99***1#" or "ATD*99#" >>> >> >> After a while, unfortunately, the gprs connection, seemingly >>> >> >> established, >>> >> >> is >>> >> >> broken by unknow reason!! >>> >> >> And, some information is shown out, for example, "no carrier". >>> >> >> After that, rild will be into the loop of rebooting!! >>> >> >> Q2: what reason causes the scenario? >>> >> >> >>> >> >> D/AT : AT> ATD*99***1# >>> >> >> D/AT : AT< *PSCALL: 11,1 >>> >> >> D/AT : AT< CONNECT >>> >> >> D/RILJ : [0054]< SETUP_DEFAULT_PDP {1, ppp0} >>> >> >> D/GSM : [PdpConnection] PDP setup on cid = 1 >>> >> >> D/AT : AT< CONNECT >>> >> >> D/AT : AT< CONNECT >>> >> >> D/AT : AT< CONNECT >>> >> >> D/AT : AT< CONNECT >>> >> >> D/AT : AT< CONNECT >>> >> >> D/AT : AT< CONNECT >>> >> >> D/AT : AT< NO CARRIER >>> >> >> D/AT : AT< *PSCALL: 11,0 >>> >> >> D/RILJ : [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED >>> >> >> D/AT : AT< *PSFS: 14 >>> >> >> W/RILC : EOS. Closing command socket. >>> >> >> I/RILJ ( 962): Connected to 'rild' socket >>> >> >> I/RILC : libril: new connection >>> >> >> I/RILC : RIL Daemon version: Enfora EDG308 RIL 1.0 >>> >> >> D/RILJ ( 962): Radio ON @ init; reset to OFF >>> >> >> D/RILJ ( 962): [0000]> RADIO_POWER >>> >> >> D/RIL : onRequest: RADIO_POWER >>> >> >> D/AT : AT> AT+CFUN=1 >>> >> >> D/RILJ ( 962): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED >>> >> >> RADIO_UNAVAILABLE >>> >> >> >>> >> >> >>> >> >> For more information, please kindly refer to the attachment!! >>> >> >> Thanks >>> >> >> a >>> >> >> lot!! >>> >> >> >>> >> >> >>> >> >> >>> >> >> B. R. >>> >> >> Samuel >>> >> >> >>> >> >> >>> >> > >>> >> > >>> >> >>> >> >>> > >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
