It seems we switched our traffic stats strategy recently (JB) and now UDP packets are getting included when they arguably shouldn't be. If your DNS server is disconnected from the internet and can't resolve the mtalk.google.com queries you'll end up with outgoing queries and no responses. This will cause the resets you see every 6 minutes. If the DNS is resolving, then we probably have some other packet slipping out with no return.
A couple questions: Is your production environment going to be this isloated? Gtalk is what's providing the GCM channel that many 3rd party apps need. Why aren't you using GCM? It provides a push notification system for apps, and by sharing it you get better battery life and have less development headache. I'm trying to contact the gcm/gtalk team to find out if there's a non-root way to turn off the service, but I'm not hopeful. R On Mon, Dec 17, 2012 at 10:13 AM, Goncalo Oliveira <[email protected]>wrote: > Can't get QTAGUID STATS INFO on samsung. On the other device also fails > retrieving that info. I'm going to try to get another device. > Meanwhile, I published the whole bugreport output, maybe you can see > something that I can't... > > https://www.dropbox.com/sh/18o32mndge2rrpd/vAeETMVnh6 > > Cheers > > > On 17 December 2012 17:46, Goncalo Oliveira <[email protected]> wrote: > >> Robert, >> >> Kind of a wild guess but... GTalkService? >> >> logcat >> 12-17 17:14:47.212 473 1312 E *GTalkService: connectionClosed: no >> XMPPConnection - That's strange*! >> 12-17 17:14:47.220 213 223 E AlarmManagerService: >> android_server_AlarmManagerService_set to type=2, 4627.149000000 >> 12-17 17:14:47.665 292 292 D STATUSBAR-NetworkController: >> onServiceStateChanged state=0 >> 12-17 17:14:47.673 292 292 W SignalStrength: getGsmLevel=3 >> 12-17 17:14:47.673 292 292 W SignalStrength: getLevel=3 >> (SignalStrength: 99 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 gsm|lte 3) >> 12-17 17:14:47.673 292 292 D StatusBar.NetworkController: >> getDataServiceState : NoSuchMethodException >> 12-17 17:14:47.673 213 988 D STATUSBAR-NotificationService: >> cancelNotification - pkg:com.android.systemui, id:273, tag:null >> 12-17 17:14:47.689 3183 3183 D StatusChecker: onReceive : >> android.intent.action.SERVICE_STATE >> 12-17 17:14:47.689 3183 3183 D StatusChecker: Service state changed : 0 >> 12-17 17:14:47.689 292 292 D STATUSBAR-NetworkController: >> onDataConnectionStateChanged: state=2 type=3 >> >> radio >> 12-17 17:15:49.618 371 371 D GSM : [GsmDCT] updateDataStallInfo: >> OUT sent=12 mSentSinceLastRecv=29 >> 12-17 17:15:49.626 371 371 D GSM : [GsmDCT] onDataStallAlarm: >> tag=24748 do recovery action=1 >> 12-17 17:15:49.626 371 371 D GSM : [GsmDCT] handleMessage msg={ >> what=270354 when=-3ms } >> 12-17 17:15:49.626 371 371 D GSM : [GsmDCT] overall state is >> CONNECTED >> 12-17 17:15:49.626 371 371 D GSM : [GsmDCT] doRecovery() cleanup >> all connections >> >> SERVICE com.google.android.gsf/.gtalkservice.service.GTalkService >> 12-17 17:15:08.158 473 473 D GTalkService: [ReconnectMgr] >> setInternalNetworkState: type=0, state=CONNECTED >> 12-17 17:15:08.158 473 473 I GTalkService/c: >> [AndroidEndpoint@1093684528] connect: acct=1000000, state=CONNECTING >> 12-17 17:15:08.168 473 1312 D GTalkService/c: >> [AndroidEndpoint@1093684528] doConnectDelegate: making main connection >> 12-17 17:15:08.168 473 1312 D Smack: [SSLXMPPConnection@1094231880] >> create socket connection(mtalk.google.com, 5228) >> 12-17 17:15:52.215 473 1312 D GTalkService: >> [AndroidEndpoint@1093684528] doConnect: caught XMPPError connecting to >> mtalk.google.com:5228.: (502) >> -- caused by: java.net.ConnectException: failed to connect to >> mtalk.google.com/173.194.78.188 (port 5228): connect failed: ETIMEDOUT >> (Connection timed out) >> 12-17 17:15:52.215 473 1312 D GTalkService/c: >> [AndroidEndpoint@1093684528] handleDoConnectError for 1000000, error=2, >> xmppError=null >> 12-17 17:15:52.215 473 1312 D GTalkService/c: >> [AndroidEndpoint@1093684528] closeConnection for 1000000, notify=true, >> xmppConn=null >> 12-17 17:15:52.216 473 1312 E GTalkService: connectionClosed: no >> XMPPConnection - That's strange! >> 12-17 17:15:52.216 473 1312 D GTalkService: [ReconnectMgr] ### >> report Inet status: online=false, networkType=0 >> >> like I said, kind of a wild guess. I'll try to replicate here with >> another device also (rooted), as in this one I can't get the QTAGUID STATS. >> >> Cheers >> >> >> On 17 December 2012 17:24, Robert Greenwalt <[email protected]>wrote: >> >>> I'll try this here as well and see if I can repro the problem on a >>> rooted device. >>> >>> >>> On Mon, Dec 17, 2012 at 9:20 AM, Goncalo Oliveira <[email protected]>wrote: >>> >>>> Fred, >>>> >>>> Just to clarify, I haven't declined the heartbeat option. I just would >>>> like to avoid low timestamps such as every 5 minute. >>>> I'm trying to identify what's happening behind the scenes like Robert >>>> suggested, as it seems that it's not just my app that throws this stall. >>>> I'll post my results as soon as possible. >>>> >>>> >>>> On 17 December 2012 17:03, Fred Niggle <[email protected]>wrote: >>>> >>>>> Well, just to recap: >>>>> >>>>> You know that android is not supposed to keep an idle connection open >>>>> for an extended period. >>>>> Also you have declined the option to use of a heartbeat to keep the >>>>> connection open. >>>>> >>>>> You also know that GCM (C2DM) have a way of keeping in touch. >>>>> >>>>> At this point the main(only?) route to pursue is to look over the GCM >>>>> libs from google and see how they do it. >>>>> >>>>> Best regards, >>>>> Fred >>>>> >>>>> >>>>> On 17 December 2012 16:49, Goncalo Oliveira <[email protected]>wrote: >>>>> >>>>>> Fred, >>>>>> >>>>>> I do understand that this is not a "standard" for most android apps. >>>>>> Therefore, there are a number of scenarios, like Mark pointed out. In >>>>>> this >>>>>> case, the connection is also used for data pushing. Polling would be much >>>>>> simpler, but it does not fit the required scenario. >>>>>> >>>>>> >>>>>> On 17 December 2012 16:43, Mark Murphy <[email protected]>wrote: >>>>>> >>>>>>> On Mon, Dec 17, 2012 at 11:37 AM, Fred Niggle >>>>>>> <[email protected]> wrote: >>>>>>> > I am wondering why you are trying to maintain an idle connection? >>>>>>> >>>>>>> You would do this for any sort of push delivery from the server: >>>>>>> standard push notifications, VOIP for incoming calls, etc. >>>>>>> >>>>>>> So, for example, C2DM used to have this sort of heartbeat logic, and >>>>>>> I >>>>>>> presume GCM does too. >>>>>>> >>>>>>> -- >>>>>>> Mark Murphy (a Commons Guy) >>>>>>> http://commonsware.com | http://github.com/commonsguy >>>>>>> http://commonsware.com/blog | http://twitter.com/commonsguy >>>>>>> >>>>>>> Aqui estão alguns sites onde você pode perguntar ou responder dúvidas >>>>>>> sobre desenvolvimento de aplicações para Android: >>>>>>> http://www.andglobe.com >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Android Developers" group. >>>>>>> To post to this group, send email to >>>>>>> [email protected] >>>>>>> To unsubscribe from this group, send email to >>>>>>> [email protected] >>>>>>> For more options, visit this group at >>>>>>> http://groups.google.com/group/android-developers?hl=en >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Gonçalo Oliveira >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Android Developers" group. >>>>>> To post to this group, send email to >>>>>> [email protected] >>>>>> To unsubscribe from this group, send email to >>>>>> [email protected] >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/android-developers?hl=en >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Sent from an Ubuntu Desktop. >>>>> >>>>> Ubuntu Speech >>>>> input<https://play.google.com/store/apps/details?id=com.nds.ubuntuspeechinput>is >>>>> now available on Google Play, along with Magnetic >>>>> Door Alarm >>>>> app<https://play.google.com/store/apps/details?id=com.nds.magneticdooralarm> >>>>> . >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Android Developers" group. >>>>> To post to this group, send email to >>>>> [email protected] >>>>> To unsubscribe from this group, send email to >>>>> [email protected] >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/android-developers?hl=en >>>>> >>>> >>>> >>>> >>>> -- >>>> Gonçalo Oliveira >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Android Developers" group. >>>> To post to this group, send email to >>>> [email protected] >>>> To unsubscribe from this group, send email to >>>> [email protected] >>>> For more options, visit this group at >>>> http://groups.google.com/group/android-developers?hl=en >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Android Developers" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/android-developers?hl=en >>> >> >> >> >> -- >> Gonçalo Oliveira >> > > > > -- > Gonçalo Oliveira > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
