GTalkSMS failed to achieve a permanent connection

[GoogleCodeExporter]

It seems that on my phone (Nexus S running 2.3.4) GTalkSMS logs out after a 
while (half a day or so).  It would be nice to have an option where it retries 
connecting unless "start/stop" was physically toggled.

Original issue reported on code.google.com by leo.alek...@gmail.com on 20 May 2011 at 2:10

[GoogleCodeExporter]

This is already the default behavior.

The AppLog should tell you why the connection is not persistent.

Original comment by fschm...@gmail.com on 20 May 2011 at 4:16

[GoogleCodeExporter]

Original comment by fschm...@gmail.com on 20 May 2011 at 4:17

• Changed title: GTalkSMS failed to achieve a permanent connection

[GoogleCodeExporter]

What information can I get from the log?  I see lines like the following:

W/ActivityManager: Scheduling restart of crashed service 
com.googlecode.gtalksms/.MainService in 24974ms

or 
D/Smack   : [XMPPConn] close connection, notifyClosed=false
D/GTalkService: [GTalkConnection.20] connectionClosed: connId=523319, 
error=CONNECTION FAILED

(this last one seems to be when the phone switched from 3g to wifi, also, it's 
not clear to me whether it pertains to gtalksms or to the google talk app).

Even though I enabled the detailed logging in options, I don't see any gtalksms 
specific tags...

Original comment by leo.alek...@gmail.com on 21 May 2011 at 5:49

[GoogleCodeExporter]

Just follow the steps from here: 
http://code.google.com/p/gtalksms/wiki/GenerateAppLog
And make sure to change the subject line to the issue number!

Original comment by fschm...@gmail.com on 21 May 2011 at 5:57

[GoogleCodeExporter]

I find that AppLog only collects information starting from the time that I 
start the application in order to collect log data, which is useless.  

I just observed my phone spontaneously signing out of IM, and tried to collect 
log data.  AppLog was empty.  System log had the following info:

05-22 14:38:46.365 I/ActivityManager(  110): No longer want 
com.googlecode.gtalksms (pid 26505): hidden #16
05-22 14:38:46.416 I/EventLogService(  232): Aggregate from 1306087858045 
(log), 1306087726202 (data)
05-22 14:38:46.416 W/ActivityManager(  110): Scheduling restart of crashed 
service com.googlecode.gtalksms/.MainService in 5000ms
05-22 14:38:46.420 I/WindowManager(  110): WIN DEATH: Window{4053d280 
com.googlecode.gtalksms/com.googlecode.gtalksms.panels.MainScreen paused=false}
05-22 14:38:48.892 D/dalvikvm(  194): GC_EXTERNAL_ALLOC freed 60K, 45% free 
5777K/10375K, external 15886K/16078K, paused 41ms
05-22 14:38:51.420 I/ActivityManager(  110): Start proc com.googlecode.gtalksms 
for service com.googlecode.gtalksms/.MainService: pid=31978 uid=10090 
gids={1006, 3003, 1015, 1007}
05-22 14:38:51.646 I/gtalksms(31978): onCreate(): service thread created

Original comment by leo.alek...@gmail.com on 22 May 2011 at 6:48

[GoogleCodeExporter]

AppLog works for me. Not sure whats the issue in your case. But it seems that 
you have some skills with adb logcat. If so, you could try
adb shell logcat -v time
for a complete log. And/Or
adb shell logcat -v time |grep gtalksms
for a log with messages from gtalksms only (If you are on a system witch allows 
piping and grep)

The log part you have attached here is a pretty standard situation on Android. 
The ActivityManager tries to free some memory by killing processes and 
restarting them after a certain amount of time. GTalkSMS is able to detect such 
a situation and restores the connection after the service thread is recreated @ 
05-22 14:38:51.646.
But the log ends here. If debug log was enabled, we should see the reconnection 
occur. Not sure whats wrong here, could be a different behavior of Gingerbread 
or just some missing lines in the log.

Hopefully my SGS will have Gingerbread soon, so I can support the new Android 
release better. 

Original comment by fschm...@gmail.com on 22 May 2011 at 7:26

[GoogleCodeExporter]

The complete log | grep gtalksms (see attached) doesn't show much more info 
than what I posted.  The next log entry from gtalksms is when I initiated 
AppLog collection, which had only one line:
--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
05-22 14:38:51.646 I/gtalksms(31978): onCreate(): service thread created

Original comment by leo.alek...@gmail.com on 22 May 2011 at 8:18

Attachments:

• gtalksmslog.txt

[GoogleCodeExporter]

I suspect android's ActivityManager behind this. But we need the log part from 
the last messages from GTalkSMS together with the system log. I am not sure yet 
why in your case the AppLog feature of GTalkSMS only shows the last few 
messages, but with "adb" as mentioned in 
http://code.google.com/p/gtalksms/issues/detail?id=173#c6 we should be able to 
gather all information.

Original comment by fschm...@gmail.com on 23 Jun 2011 at 9:34

• Changed state: UserFeedBack

[GoogleCodeExporter]

Closing old UserFeedback Issues. Feel free to reopen when needed.

Original comment by fschm...@gmail.com on 19 Jul 2011 at 7:03

• Changed state: Invalid