Cinterion PLS8-X disconnects after some hours without activity (Android RIL) | Thales IoT Developer Community
April 26, 2016 - 9:28am, 3360 views
I am working with the Cinterion PSL8-X through the PHS8_Adapter in a Android 4.4.3 embedded product, using the propetary Gemalto Android-LTE-RIL 01.04.
I am facing the following problem: when I boot the system I have a functional connection, but if I live the system idling for a long time (<24 hours) when I try to use the cellular connection, it does not work. When this happens, the modem is still detected, the network interface is present and has an IP and also the network is in the route table:
------------------------------------------------------------------------------------
/ # ping -c ***
ping: bad number of packets to transmit.
/ # ping -c 1 ***
ping: unknown host ***
/ # ping -c 1 ***
ping: unknown host ***
/ # busybox ash
/ # ping -c 1 ***
ping: unknown host ***
/ # busybox ifconfig -a
usb0 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:00
inet addr:100.117.195.118 Bcast:100.117.195.119 Mask:255.255.255.252
inet6 addr: 2600:1014:b023:c064:dcad:beff:feef:0/64 Scope:Global
inet6 addr: fe80::dcad:beff:feef:0/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:414 errors:0 dropped:0 overruns:0 frame:0
TX packets:286 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:370290 (361.6 KiB) TX bytes:31508 (30.7 KiB)
usb1 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:01
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
/ # busybox route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 100.117.195.117 0.0.0.0 UG 0 0 0 usb0
63.84.3.23 * 255.255.255.255 UH 0 0 0 usb0
100.117.195.116 * 255.255.255.252 U 0 0 0 usb0
------------------------------------------------------------------------------------
Leaving a ping running for 24 hours works with no problems, though.
Could you help with this issue?
Hello,
I think that this problem might be caused by the network operator - if the connection is idle for a long time it is disconnected.
Could you send also the RIL logs? Then we would be able to check what's going on.
Regards,
Bartłomiej
Hi Bartlomiej,
thanks for your quick answer! If the network operator drops the connection, should not the RIL attempt to reconnect again when the network is required by the system?
Thanks,
Jose
Find the RIL log here:
reconnectfailafter24hr.txt
Hello,
Thank you for the log. However it seems that it does not cover the moment when the connection was lost. It would be very helpful if you tried to setup the logging with timestamps and catch that moment.
Thanks,
Bartłomiej
Hi again,
here you have a logcat report with timestamps:
logcat.txt
Everything looks fine to me on that log, but the connection does not work. If I try to ping an IP directly, I loose most of the packages:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 100.82.203.31: icmp_seq=1 Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
However I do recieve some packages from 100.82.203.31 (on the cellular network). What can cause this?
Here is some aditional information:
ifconfig output:
usb0 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:00
inet addr:100.82.203.31 Bcast:100.82.203.63 Mask:255.255.255.192
inet6 addr: 2600:1014:b06c:15dd:dcad:beff:feef:0/64 Scope:Global
inet6 addr: fe80::dcad:beff:feef:0/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9867 (9.6 KiB) TX bytes:5269 (5.1 KiB)
usb1 Link encap:Ethernet HWaddr DE:AD:BE:EF:00:01
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
getprop | grep dns
[net.change]: [net.dns2]
[net.dns1]: [198.224.149.135]
[net.dns2]: []
[net.usb0.dns1]: [198.224.149.135]
[net.usb0.dns2]: [198.224.148.135]
route output:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 100.82.203.1 0.0.0.0 UG 0 0 0 usb0
100.82.203.0 * 255.255.255.192 U 0 0 0 usb0
216.58.192.174 * 255.255.255.255 UH 0 0 0 usb0
Hello,
We have analysed the log and again it looks like it starts too late and the moment of connection loss is missing in the log.
Regards,
Bartłomiej