28 minutes ???
It's only 3 minutes for us in France, I am doubtful about this value.

2009/5/5 mathiastck <[email protected]>

>
> I found this:
>
> http://code.google.com/p/android-random/source/browse/trunk/TestKeepAlive/src/org/devtcg/demo/keepalive/KeepAliveService.java
>
> these guys set their keep alive interval to:
>
> private static final long KEEP_ALIVE_INTERVAL = 1000 * 60 * 28;
>
> I'm assuming their optmized for the T-Mobile G1.
>
> On May 5, 5:13 am, Guillaume Perrot <[email protected]> wrote:
> > Nobody can answer me ?
> > I am still forced to leave the setting to 30s and it drains users
> > battery.
> >
> > On 14 avr, 11:55, Guillaume Perrot <[email protected]> wrote:
> >
> > > Hi,
> > > I just wondered which frequency is OK to send whitespace keep alive
> > > packets onto a TCP connection to keep it alive on a T-Mobile 3G
> > > connectivity (the use case is to maintain an idle XMPP session alive).
> > > On SFR in France, we are disconnected if idle for 3 minutes, but I
> > > guess T-Mobile's timeout is lower.
> > > Any idea ?
> >
> > > By the way there is a bug in the Smack library, the "keep alive"
> > > setting is not enforced, e.g. if you set it to 30s, in the worst case
> > > the whitespace will not be sent until the double of this time (60s).
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to