Friday, December 21, 2012

Re: [android-developers] Mobile network idle sockets disconnected

Robert,

Thanks again for clarifying. Basically if I open up GCM I'm allowing user to work with gtalk, so I will want to avoid that.
Looks like sending the heartbeat every 5 minutes is the only option I have left.

Thanks for the help. Much appreciated.
Cheers

On 21 December 2012 15:44, Robert Greenwalt <rgreenwalt@google.com> wrote:
I believe most of the google apps rely on GCM (calendar, gmail, contacts, talk, etc), also 3rd party apps that need pushed notifications are encouraged to use GCM.  Unless you are making a custom build and denying app installs you probably have apps that will be broken without GCM.

Of course, if you have very limited data plans on special purpose phones, you may wish for all those apps to be broken - they can use quite a bit of data.

I don't know what GCM's steady-state data rate is for a device.  I believe it does a carrier keep-alive ping every 20-30 minutes.  It also checks for updates whenever the screen comes on.  Other than that I think it is dependent on user or network-originating app traffic.

R


On Fri, Dec 21, 2012 at 2:23 AM, Goncalo Oliveira <goncalo@minkan.net> wrote:
Robert,

Thank you for the explanation. There's just one more thing that I'd like you to help me understand. If we choose to allow the GCM connection, what kind of traffic can we expect to have? Like I said previously, we have a very tight data plan, so if the GCM connection adds more than just a few bytes, that might be a bad idea to enable it. Also, by enabling GCM connection, what am I allowing the users to do? Can they use gtalk or something else?

Cheers


On 21 December 2012 00:17, Robert Greenwalt <rgreenwalt@google.com> wrote:

The GCM is part of the platform - 3rd party apps depend on it and so there's no mechanism for deactivating it.

If you can allow the GCM connection to succeed, you should avoid the current problems, but if you're going for a secure platform you may not want the GCM connection to succeed.

You could potentially hijack the dns resolution: have your dns server report an address you control for mtalk.google.com, then allow connections to your own server, but no real functionallity.  With some reverse engineering you may be able to get to a quiet connection that doesn't trigger these data-stall triggers.

The easiest solution is to adjust your keep-alive ping to < 6 minutes.  That will effect the battery, but less than allowing the resets to happen.

I have created internal issues to examine this issue, but even if we fixed it today internally you wouldn't see it for a long while.  The first issue is to find what traffic is causing this connection reset.  The second is to re-eval counting udp packets (I am assuming that's causing part of this problem).

I'm sorry you have hit this issue.

Robert 


On Thu, Dec 20, 2012 at 4:30 AM, Goncalo Oliveira <goncalo@minkan.net> wrote:
Robert,

Any updates on this?

Cheers


On 18 December 2012 10:06, Goncalo Oliveira <goncalo@minkan.net> wrote:
consider opening up the addre



--
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment