search

kashif181 / gtalksms

Automatically exported from code.google.com/p/gtalksms
0 stars 0 forks source link

"Go SMS" and GtalkSMS lock up #162

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
IMPORTANT: An app log will help us greatly to analyze the problem.
http://code.google.com/p/gtalksms/wiki/GenerateAppLog

What steps will reproduce the problem?
1. User Go SMS as your primary texting app
2. Start GtalkSMS
3. Send/receive a few texts via Gtalksms, then try to open GoSMS

What is the expected output?
it should open as usual.

What do you see instead?
Both Go SMS and GtalkSMS lock up completely.

Additional informations:
GTalkSMS version = v2.2.3
Android OS version = 2.2
Phone model = Droid Incredible

Original issue reported on code.google.com by sbee...@gmail.com on 12 May 2011 at 2:31

GoogleCodeExporter commented 8 years ago 
App log pls

Original comment by fschm...@gmail.com on 12 May 2011 at 4:41

GoogleCodeExporter commented 8 years ago 
Sent.  Not sure it will help.  It looks like at the end it is registering the 
fact that I TRIED to toggle it/disable it, but it never does anything.  It also 
causes GoSMS to lock up.  The rest of the phone responds fine.  GtalkSMS and 
GoSMS never come back until I reboot.

Original comment by sbee...@gmail.com on 16 May 2011 at 6:53

GoogleCodeExporter commented 8 years ago 
Hmm we did not receive an AppLog linked to the Issue 162. Did you forget to set 
the subject in the AppLog Mail? We ask for an applog every time because it's 
the logical first step. If we see that we see nothing in the applog we can 
start thinking about how to change this (where to put log information in the 
source).

I did't had the time to take a deep look into this issue, but I am pretty sure 
that it has something to do with the way GtalkSMS and probably GoSMS access the 
built-in SMS Clients SMS Storage. If this is true then we may have to chance 
solving this issue.

Original comment by fschm...@gmail.com on 21 May 2011 at 4:39

GoogleCodeExporter commented 8 years ago 
Still no app log from issue 162

Original comment by fschm...@gmail.com on 27 Dec 2011 at 11:12

GoogleCodeExporter commented 8 years ago 
No further reports in 3 months

Original comment by fschm...@gmail.com on 12 Apr 2012 at 1:24