Closed GoogleCodeExporter closed 8 years ago
This happens daily on my Samsung Galaxy Nexus. When I went into the app the
icon was still green, as though the app still had a connection. When I stop and
start it again, it's fine again for a while.
Original comment by jbfran...@gmail.com
on 26 Feb 2012 at 4:02
Original comment by Florent....@gmail.com
on 28 Feb 2012 at 10:24
This happens a lot to me as well. The status circle gets stuck at Orange and
nothing happens. Sometimes Start/Stop works. Sometimes restarting the phone
works. Sometimes neither work to resolve the issue.
Original comment by jagriff...@gmail.com
on 31 Mar 2012 at 6:28
Same for me, Galaxy Nexus, build IMM76I
It didn't happen so much on my previous model (Nexus S with Gingerbread).
Original comment by did...@dfr.ch
on 15 May 2012 at 7:29
Could you please generate some log output:
http://code.google.com/p/gtalksms/wiki/GenerateAppLog
Original comment by fschm...@gmail.com
on 15 May 2012 at 8:34
Original comment by Florent....@gmail.com
on 19 Jun 2012 at 9:10
Same problem for me using gtalksms 3.5 on the HTC wildfire s. Application
starts fine but after a while the green status icon changes to Orange and the
app doesn't reconnect.I then have to manually stop start the app to reconnect.
Original comment by torsten....@gmail.com
on 3 Jul 2012 at 11:16
I would also like to add to this, on a Galaxy Nexus running 4.0.4. It connects
for a while, then disconnects until I manually reconnect it.
Original comment by Dris...@gmail.com
on 5 Jul 2012 at 2:18
Does it happen with WIFI connections too?
Original comment by Florent....@gmail.com
on 5 Jul 2012 at 3:34
It's happened to me on wifi numerous times.
Original comment by jbfran...@gmail.com
on 5 Jul 2012 at 3:55
Same for me when using WiFi. Sometimes it also seems to be connected on the
phone (green status) but contact appears disconnected in chat client.
Original comment by sebastie...@gmail.com
on 10 Jul 2012 at 8:26
It seems better with android 4.1.1 :)
Original comment by francois...@gmail.com
on 12 Jul 2012 at 2:23
GTalkSMS 4.3 was released yesterday. Please evaluate and provide feedback to
the gtalksms users group/mailing list @
http://groups.google.com/group/gtalksms-users
Original comment by fschm...@gmail.com
on 26 Jan 2013 at 6:02
Hi,
Just tested on 4.3, still happens. Haven't tried on wifi yet.
Original comment by antoine....@gmail.com
on 28 Jan 2013 at 5:08
same problem here. - shows that it is connected but it isn't. happens after
about 2 or 3 hours of use.
my phone is a lg e400 with android 2.3
i'm uyinv version 4.3 and it happens on wlan and 3g
Original comment by handgur...@gmail.com
on 8 Feb 2013 at 5:22
New ping setting added.
With my ISP I need to set the ping interval to 90s.
Default value is 600s.
Original comment by Florent....@gmail.com
on 15 Oct 2013 at 8:48
4.4.2 Beta 2 available in the Download section
Original comment by Florent....@gmail.com
on 18 Oct 2013 at 10:14
Bad news, I'm afraid:
4.4.2 Beta 2 tried on a Samsung Galaxy Ace Plus GT-S7500 (Gingerbread 2.3.6;
2.6.38.6-1208520).
Result: Very frequent disconnections.
Log attached.
Original comment by whaym...@gmail.com
on 19 Oct 2013 at 6:45
Attachments:
You seems to have another issue
10-19 07:40:41.909 D/gtalksms( 3056): xmpp disconnected due to error:
10-19 07:40:41.909 D/gtalksms( 3056): stream:error (undefined-condition) text:
InvalidInput: input string does not conform to zlib format or checksum failed
at lua_zlib.c line 155
Do you have the compression enabled in the connection settings?
Original comment by Florent....@gmail.com
on 19 Oct 2013 at 9:12
Re: the zlib error - It appears I *had* another issue. It no longer reproduces,
with or without compression enabled.
As for *this* bug, it appears to be fixed. No disconnections over a period of 4
hours or so. Previously it never lasted that long.
Thanks for sorting it out.
Original comment by whaym...@gmail.com
on 19 Oct 2013 at 6:03
Final version 4.4.2 available in the Download section
Original comment by Florent....@gmail.com
on 20 Oct 2013 at 7:37
Original comment by Florent....@gmail.com
on 26 Oct 2013 at 1:07
Original issue reported on code.google.com by
wapt...@gmail.com
on 1 Feb 2012 at 6:53Attachments: