[HD2 Android Q&A, Help & Troubleshooting and Genera] letama:
Hi aussiebum,

Interesting logs here. Here is how I interpret it:

First, logs disconnect but data timeout:

- Here, we have this:

11-15 18:53:58.565 D/GSM ( 285): [GsmDataConnectionTracker](0)no DATAIN in a while; polling PDP

11-15 18:53:58.565 D/RILJ ( 285): [0800]> DATA_CALL_LIST

11-15 18:53:58.565 D/RIL_WRAP( 178): PL:hackOnRequestDataCallList token=(a9f8)

11-15 18:53:58.565 D/HTC_RIL ( 178): ril_func_get_pdp_context_list():called

11-15 18:53:58.565 D/HTC_RIL ( 178): @(t=1289807638)>> 14:poll

11-15 18:53:58.565 D/HTC_RIL ( 178): RX::> STATE=down\nCID=0\n

11-15 18:53:58.565 D/HTC_RIL ( 178): qmi0_read_thread():qmi read thread got [[STATE=down

11-15 18:53:58.565 D/HTC_RIL ( 178): CID=0

11-15 18:53:58.565 D/HTC_RIL ( 178): (17)]] data from qmi fd 14.

11-15 18:53:58.565 D/HTC_RIL ( 178): @(t=1289807638)< 14:STATE=down

11-15 18:53:58.565 D/HTC_RIL ( 178): CID=0

11-15 18:53:58.565 D/HTC_RIL ( 178): 0

11-15 18:53:58.565 D/HTC_RIL ( 178):

11-15 18:53:58.565 I/HTC_RIL ( 178): qmi_notify_pdp_change():receive qmi notify for unknow reason

11-15 18:53:58.565 D/HTC_RIL ( 178): @(t=1289807638)%% STATE=down

11-15 18:53:58.565 D/HTC_RIL ( 178): CID=0

11-15 18:53:58.565 D/HTC_RIL ( 178):

11-15 18:53:58.565 D/HTC_RIL ( 178): qmi0_read_thread():qmi read thread is waiting in poll(fd:14) now!

11-15 18:53:58.565 D/HTC_RIL ( 178): @(t=1289807638)<< [ch:0]0

11-15 18:53:58.565 D/HTC_RIL ( 178):

11-15 18:53:58.569 W/RIL_WRAP( 178): DataCallList

11-15 18:53:58.569 D/RIL_WRAP( 178): call[0]:cid=-1, active=0, type=, apn=, add=

11-15 18:53:58.569 D/RIL_WRAP( 178): call[1]:cid=-1, active=0, type=, apn=, add=

11-15 18:53:58.569 D/RIL_WRAP( 178): call[2]:cid=-1, active=0, type=, apn=, add=

This is something I just figured now, android doesn't see data for a while and polls pdp (data modem configuration). But unfortunately, it does it on rmnet! And of course, doesn't see any active connection. I will try to intercept this call and handle it properly to return ppp pdp, but it's not going to be easy as I can't read modem answers in wrapper.

After that, I see one ppp launch that fails at 18:54:04->18:54:35 then I see wrapper kick in, relaunch pppd at 18:54:42 (normal delay), and ppp negociation starting normally but taking forever doing ping-pong with server to negociate ms-dns. You should try options novj and novjccomp to see if it improve things. I think Hastarin launched a thread about options, you should take a look there (http://xdaforums.com/showthread.php?t=838583).

On your second log serie "pppd connected but data timeout", again, interesting stuff there, the problem is here:

(14084): Couldn't attach to PPP unit 1: Invalid argument.

I see this also:

11-15 19:08:04.563 I/pppd (14087): local IP address 175.32.0.145

11-15 19:08:04.563 I/pppd (14087): remote IP address 10.64.64.64

11-15 19:08:04.563 D/pppd (14087): Script /etc/ppp/ip-up started (pid 14091)

11-15 19:08:04.583 D/pppd (14087): Script /etc/ppp/ip-up finished (pid 14091), status = 0x0

11-15 19:08:10.743 D/pppd (14096): using channel 84

11-15 19:08:10.754 E/pppd (14096): Couldn't attach to PPP unit 1: Invalid argument

11-15 19:08:10.754 I/pppd (14087): Modem hangup

11-15 19:08:10.754 I/pppd (14087): Connect time 0.1 minutes.

11-15 19:08:10.754 I/pppd (14087): Sent 122 bytes, received 0 bytes.

11-15 19:08:10.754 D/pppd (14087): Script /etc/ppp/ip-down started (pid 14105)

11-15 19:08:10.754 I/pppd (14087): Connection terminated.

11-15 19:08:10.754 D/pppd (14097): using channel 85

11-15 19:08:12.053 D/pppd (14087): Script /etc/ppp/ip-down finished (pid 14105), status = 0x0

We have multiple pppd processes launching almost at the same time, 14087 seems to do fine and get the ip, then gets hangup at 19:08:10.754. and in the middle of it, you have 14096 that kicks in, can't attach PPP unit and dies.

If I look at corresponding period in radio, I see this:

11-15 19:08:00.142 D/RIL_WRAP(14084): AT> ATD*99***1#

11-15 19:08:00.143 D/HTC_RIL ( 178): RX::> 1\r

11-15 19:08:00.143 D/HTC_RIL ( 178): RX::> +PCD: 1,1\r\n

11-15 19:08:00.143 D/HTC_RIL ( 178): (t=1289808480)%% +PCD: 1,1\r\n

11-15 19:08:01.037 W/RIL_WRAP( 5491): Mon: start pppd (net=1)

11-15 19:08:01.037 D/RIL_WRAP( 5491): pppd pid is 14087

11-15 19:08:01.037 D/RIL_WRAP(14087): atd+ppd

11-15 19:08:01.037 D/RIL_WRAP(14087): AT> AT+CGACT=0,1

So, it looks like with have two monitor processes running at the same time there. I have no clue yet on how we ended up in this situation, I'll take look.

Thanks again, good material for me there.

LeTama