No SMS notification

[GoogleCodeExporter]

===  IMPORTANT - READ THIS!  ===
An app log will help us greatly to analyze the problem. So ALWAYS generate
an AppLog, even if it does not show anything (which will tell use that we
have to improve the log part ;-) ).
http://code.google.com/p/gtalksms/wiki/GenerateAppLog
================================
applog on the way.

What steps will reproduce the problem?
1. GTalkSMS is connected and configured to send from one account to another
2. SMS message is received
3. No notification in chat window

What is the expected output?
SMS notification in chat window

What do you see instead?
Noting

Additional informations:
Phone model: Motorola Droid

Original issue reported on code.google.com by la...@kvetsch.com on 25 Jul 2011 at 2:10

[GoogleCodeExporter]

Same problem, applog sent. Samsung Galaxy S2

Original comment by mreg...@gmail.com on 27 Jul 2011 at 5:32

[GoogleCodeExporter]

To clarify, I can send messages just fine. I can read messages (if I know who 
sent them) with the line

sms:#Contact#

and then I send replies with

sms:#Contact#:Message

But I'm only getting notifications of successful sending of messages. I'm using 
Pidgin, sending messages to epiccyndaquil@jabber.org, from 
epiccyndaquilphone@jabber.org. I'm not sure if it's doing that exactly right, 
as I seem to be communicating with epiccyndaquil@jabber.org.

I also sent my applog.

Original comment by epiccynd...@gmail.com on 28 Jul 2011 at 6:34

[GoogleCodeExporter]

Ok, we got 2 applogs with nothing in the log and another one with an problem 
which seems to be related to the sent/delivered SMS notifications. So I'd like 
to ask all affected by this issue to disable the sent AND delivered SMS 
notifications, kill all remaining gtalksms processes/services and restart the 
app.
I am not sure yet what's the exact problem here. If you want to help finding 
the cause you could install adblogcat or catlog and search for logs tagged with 
"gtalksms". Make sure you have enabled debug log in the GTalkSMS preferences!

And am I right that all of you see the GTalkSMS account online and that you are 
able to send command to gtalksms. Only the new sms notifications are not 
working, right?

Original comment by fschm...@gmail.com on 28 Jul 2011 at 10:22

• Changed state: Accepted

[GoogleCodeExporter]

You are correct that the GTalkSMS account appears in the chat client, and SMS 
notifications do not appear in the client.  I will check out those apps and get 
logs to you ASAP.

Original comment by la...@kvetsch.com on 28 Jul 2011 at 11:43

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

attaching an applog, but nothing showed up when I received a text this morning.

Original comment by la...@kvetsch.com on 28 Jul 2011 at 2:45

Attachments:

• 2011-07-28-09-04-47.txt

[GoogleCodeExporter]

I'm experiencing the same issues.

Using a Galaxy S2 android 2.3.3

Original comment by Ravers...@gmail.com on 10 Aug 2011 at 9:56

[GoogleCodeExporter]

I should also add my version is the 3.0 Full paid

Original comment by Ravers...@gmail.com on 10 Aug 2011 at 9:57

[GoogleCodeExporter]

I suggest that everyone with this issue generates an AppLog shortly after an 
incoming SMS message and sends us the log with the issue number in the subject 
of the mail. Instructions are here: 
http://code.google.com/p/gtalksms/wiki/GenerateAppLog

Original comment by fschm...@gmail.com on 11 Aug 2011 at 8:24

[GoogleCodeExporter]

I just had 2 txts fail to forward to my jabber account.  Attached log and sent 
:)

Original comment by Ravers...@gmail.com on 16 Aug 2011 at 4:01

[GoogleCodeExporter]

There is a new version in the download tab: 
http://code.google.com/p/gtalksms/downloads/list
It does not include a bug fix, but improved log messages for this issue. Please 
update and send us the logs.

Original comment by fschm...@gmail.com on 17 Aug 2011 at 8:04

[GoogleCodeExporter]

Please install and test 3.1.2 from the downloads section.

Original comment by fschm...@gmail.com on 19 Aug 2011 at 9:55

[GoogleCodeExporter]

Original comment by fschm...@gmail.com on 19 Aug 2011 at 10:33

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I've installed the latest version and will inform of the results.  Thanks for 
the good work. :)

Original comment by Ravers...@gmail.com on 19 Aug 2011 at 8:35

[GoogleCodeExporter]

Still no joy.  Receiving updates on battery charge level etc.  But no SMS seem 
to be forwarded.

Emailed a new log.

Original comment by Ravers...@gmail.com on 19 Aug 2011 at 9:54

[GoogleCodeExporter]

On the weekend i was connected the entire time by WiFi.  The connection 
although weak appeared to be stable and while charging i did receive updates on 
the charge status.

I've submitted a new log.  The cell is plugged in and is using 3g as a 
connection.

Original comment by Ravers...@gmail.com on 22 Aug 2011 at 5:22

[GoogleCodeExporter]

I'm running an SGS2 and have this issue too.  i'll try and do some more 
testing, but is everyone who is having the problem using a non standard SMS app 
on their phone?  i vaguely remember it working fine when i used the stock 
samsung SMS app, but when i tried the Handcent sms app it didn't work, and 
right now i'm using the stock google SMS app, and it's not working.  I'll put 
the samsung app back on and give it a test when i get home..

Original comment by seventh....@gmail.com on 25 Aug 2011 at 6:41

[GoogleCodeExporter]

Will we are still waiting for some logs: There is a new beta (3.1.3) in the 
download section which you could try. Please report back if it fixes this issue.

Original comment by fschm...@gmail.com on 27 Aug 2011 at 11:33

[GoogleCodeExporter]

Hi, i tried with the official samsung app, and i started gettng FCs on GTalkSMS 
when receiving SMSs, i grabbed a logcat for you, but noticed you have released 
v3.2, so i installed that and it appears to all work now!  no FCs, and my gtalk 
gets the notification now.  i have only tested it with one sms, but it appears 
fixed.  thanks for your efforts!

Original comment by seventh....@gmail.com on 29 Aug 2011 at 6:21

[GoogleCodeExporter]

3.2 is out there since a few days. We already have the first report that the 
issue seems resolved. Can someone else (dis-)confirm this also? ty

Original comment by fschm...@gmail.com on 30 Aug 2011 at 9:26

[GoogleCodeExporter]

I cannot include a log at the moment, but this fix is NOT working for me. The 
app functions exactly as before. I additionally turned off a setting in GoSMS 
labeled "disable other message notification apps to prevent duplicate 
notifications," yet this did not resolve my issues.

Original comment by epiccynd...@gmail.com on 30 Aug 2011 at 5:10

[GoogleCodeExporter]

It's possible that this can be caused by a misbehaving 3rd party SMS app, by 
breaking the new SMS intent broadcast chain. You can check this by enabling 
debug log and looking for messages like
gtalksms - SmsReceiver: got new sms intent, calling RetrieveMessages
when a new SMS arrives. If you don't see them, then GTalkSMS is not notified 
about incoming SMS. Try removing the 3rd party app, reboot your phone and check 
again.
What we need are full system logs from the time a new SMS arrives.

Another important question: Is someone experiencing this *not* using a 3rd 
party SMS software?

Original comment by fschm...@gmail.com on 31 Aug 2011 at 10:54

[GoogleCodeExporter]

Sorry i've been busy with other things.  After reading about the 3rd party app 
possibly being the problem i realized i was using GoSMS.  So to test i 
uninstalled GoSMS and low and behold GtalkSMS started working normally.  There 
were still plenty of FCs but it did work.  

It sound like 3.2 fixes the FCs.  My only problem is that the default SMS 
client on SGS2 is pretty bad.  On my Xperia X10 i also used GoSMS and it worked 
just fine.

Original comment by Ravers...@gmail.com on 31 Aug 2011 at 2:34

[GoogleCodeExporter]

Same here, GoSMS. So is this a bug with GoSMS only, or all 3rd party clients on 
SGS2? Going to try out other apps, as default SGS2 SMS is bad as mentioned.

Original comment by mreg...@gmail.com on 31 Aug 2011 at 2:44

[GoogleCodeExporter]

Is there any option in GoSMS that breaks the SMS notifications chains ? (like 
stop other SMS application notifications ?)

If I remember well we maybe able to change the GTalkSMS priority in the SMS 
chain.

Original comment by Florent....@gmail.com on 31 Aug 2011 at 2:44

[GoogleCodeExporter]

There's an option to Enable notifications in GoSMS and it asks you to disable 
the built in SMS apps notifications settings to prevent multiples.

Original comment by Ravers...@gmail.com on 31 Aug 2011 at 3:50

[GoogleCodeExporter]

I've send an email to the GoSMS developers:
---
Hi,

GoSMS stops the SMS_RECEIVED broadcast chain with the latest version. This 
breaks some Apps, like the one I'm involved in development:
http://code.google.com/p/gtalksms/issues/detail?id=203

Others are also complaining about this behaviour: 
https://groups.google.com/forum/#!topic/android-developers/uRQsgHFdiTo
http://stackoverflow.com/questions/6594526/broadcastreceiver-not-triggered-for-s
ms-received-on-galaxy-s-ii

So I'd like to ask you gently to either change this behaviour or document the 
"android:priority" that you set for the SMS_RECEIVED intent filter in the 
manifest.

Why do you abort the broadcast anyway?

- Florian
---

Until then, you could try if handcent ( 
https://market.android.com/details?id=com.handcent.nextsms ) or one of the many 
SMS clients do work.

Original comment by fschm...@gmail.com on 1 Sep 2011 at 7:41

[GoogleCodeExporter]

Hi,

Any news from the GoSMS team?

Original comment by jfre...@gmail.com on 15 Sep 2011 at 8:08

[GoogleCodeExporter]

I've uploaded the 3.2.1 version with the higher SMS receiver priority.

Can you try if it works ?

Thanks

Original comment by Florent....@gmail.com on 19 Sep 2011 at 4:52

• Changed state: UserFeedBack

[GoogleCodeExporter]

Just installed.  Will post back :)

Original comment by Ravers...@gmail.com on 19 Sep 2011 at 5:00

[GoogleCodeExporter]

I have the same issue with GoSMS ... installed the new beta... no luck with 
notification.

Original comment by cazwell...@gmail.com on 19 Sep 2011 at 5:10

[GoogleCodeExporter]

After some new investigations I've found that :
"Go SMS Pro's priority is maximal 2147483647 (2^31-1). You can set this value 
too. If priorities are the same Android OS will serve "older" app, the one you 
have installed first. I say this from my experience I don't have google's say 
on the matter."

So I can build a new version with the max priority but user will have to 
uninstall GoSMS and reinstall it (and maybe do the same with GTalkSMS before 
reinstall GoSMS).

For me it's still a GoSMS issue. I'd advise, for the GoSMS users, to leave a 
comment on the GoSMS market page about the SMS receiver priority until they fix 
it. 

Original comment by Florent....@gmail.com on 19 Sep 2011 at 8:49

[GoogleCodeExporter]

Yes the new beta didnt work for me either.  BUT i will give the uninstall of 
gosms a try.  I appreciate the efforts!

Original comment by Ravers...@gmail.com on 19 Sep 2011 at 8:54

[GoogleCodeExporter]

You have to wait for the next beta with the highest value.
I'll try to do that tomorrow.

Original comment by Florent....@gmail.com on 19 Sep 2011 at 8:56

[GoogleCodeExporter]

Thanks for jumping on this... maybe GoSMS will relax on the priority a bit. If 
theirs is broken... then it doesn't make sense for you to break your app as a 
work around.

Original comment by cazwell...@gmail.com on 19 Sep 2011 at 9:34

[GoogleCodeExporter]

I've change the priority on the Beta version 3.2.2 (available on the download 
section).
Unlike GoSMS, GTalkSMS doesn't break the SMS chain and all other application 
are notified.

So to be sure :
1 - Uninstall GoSMS
2 - Install new version of GTalkSMS (3.2.2 or higher)
3 - Reinstall GoSMS

If it doesn't work try to uninstall both application and install GTalkSMS first.

Thanks

Original comment by Florent....@gmail.com on 20 Sep 2011 at 1:44

[GoogleCodeExporter]

I'm still having issues... I uninstalled GoSMS... uninstalled GTalkSMS... 
Downloaded and reinstalled the new GTalkSMS... and tried running it without 
GoSMS and am not getting sms notifications in Pidgin. Haven't seen anyone else 
post on this, so I'm wondering if it's just me.

Original comment by cazwell...@gmail.com on 20 Sep 2011 at 9:28

[GoogleCodeExporter]

I uninstalled and cleared settings for both GoSMS and GTalkSMS.  Reinstalled 
GTSMS first and then Go.  Still no SMS being forwarded.  I do get battery 
notifications and notification on items being sent.  Everything but new SMS 
being forwarded.

Original comment by Ravers...@gmail.com on 20 Sep 2011 at 9:32

[GoogleCodeExporter]

This ^^

Original comment by cazwell...@gmail.com on 20 Sep 2011 at 9:40

[GoogleCodeExporter]

Ravers can you confirm that GTalkSMS is still working if you don't install 
GoSMS ?

Cazwell do you receive other notification as phone calls ? Can you send 
commands ?

Original comment by Florent....@gmail.com on 20 Sep 2011 at 10:08

[GoogleCodeExporter]

Everything else works fine. Battery updates, commands that I send... ie. taking 
a picture with the camera, searching text messages, searching contacts. I even 
get an update when the reply contact has changed... Just not the actual text 
messages. It's a great app however at what it is doing. 

I have been using DeskSMS as well... it works flawlessly... even creates sms 
messages under different contacts in pidgin which is pretty sweet, but it 
doesn't do any of the other great things your app does.

Original comment by cazwell...@gmail.com on 21 Sep 2011 at 5:51

[GoogleCodeExporter]

I uninstalled GoSMS and your application works perfectly.  

Original comment by Ravers...@gmail.com on 21 Sep 2011 at 6:02

[GoogleCodeExporter]

mine is working without GoSMS as well!! BUT... I really want GoSMS... do we 
know exactly what the issue is with GoSMS? They seem to be updating all the 
time on it... we can ask them to fix what's not playing nice maybe... or is it 
GtalkSMS that has the quirk?

Original comment by cazwell...@gmail.com on 21 Sep 2011 at 11:45

[GoogleCodeExporter]

Android issues an intent broadcast when a new SMS arrives. Apps can register 
for such broadcasta via so called BroadcastReceivers. These receivers can have 
an priority which determines the order the receivers of the different apps are 
called. It is also possible that an app aborts the broadcast chain by 
cancelling it, so that apps with an lower priority won't receive the broadcast.
GoSMS seems to have its sms receiver registered with the highest priority and 
they cancel the broadcast, maybe to prevent the SMS from showing up in the 
vanilla SMS client.
Registering the own receiver with the highest priority is a little selfish and 
prevents us from placing our receiver in front of the others. There seems to be 
nothing we could do in our code to prevent this, it's GoSMS which doesn't play 
by the rules. Maybe Handcent does it better.

Original comment by fschm...@gmail.com on 22 Sep 2011 at 12:06

[GoogleCodeExporter]

GoSMS use to work though.  A matter of a couple months ago.  It seems more to 
be an issue since i switched from my Xperia X10 to the Galaxy S2.  Just an FYI 
though.  The vanilla SMS client does still recieve all sms and keeps them 
stored.  GoSMS just appears to act as a skin almost to the vanilla client.  For 
example if you encrypt an SMS in Go.  It appears unencrypted in the vanilla 
client should you open it up to view.  

Anyways much thanks for your efforts.  I'll forego GoSMS for the time being 
because the benefits provided by GtalkSMS are far greater than what Go brings 
to the table.

Original comment by Ravers...@gmail.com on 22 Sep 2011 at 2:56

[GoogleCodeExporter]

Just wanted to chime in... I switched to Handcent... and have the exact same 
issue. I can confirm that GtalkSMS works when GoSMS is uninstalled perfectly. I 
installed Handcent and lost the text message feature of GtalkSMS... I then 
uninstalled and reinstalled GtalkSMS and still no joy. Does handcent have the 
same priority situation that GoSMS has?

Original comment by cazwell...@gmail.com on 22 Sep 2011 at 3:37

[GoogleCodeExporter]

I was having this problem with Handcent. Turn off Handcent's "Default Messaging 
Application" option and you should be all set. GTalkSMS may need to be 
restarted. You can turn off the default SMS app's notifications to avoid double 
notifications. I didn't notice a difference in Handcent's functionality set up 
like this other than GTalkSMS and my SMS to Gmail backup program working again. 
Good luck to everyone else!

Original comment by Marie.F....@gmail.com on 22 Sep 2011 at 4:44

[GoogleCodeExporter]

You are genius Marie!! Worked a charm... this is the perfect compromise... I'd 
take either GoSMS or Handcent, but really don't like the default messaging app 
either way.

So to be clear...

- GTalkSMS is working 100% on it's own.
- GoSMS DOES break it, and there appears to be no work around at this time.
- Handcent has an option under Settings > Applications settings > Default 
Messaging application > Disable ... If you select Disable then Handcent works 
fine and GtalkSMS works fine!!

Original comment by cazwell...@gmail.com on 22 Sep 2011 at 5:23

[GoogleCodeExporter]

Handcent DOES work... strange since its almost an exact copy of GoSMS...or the 
other way around

Original comment by Ravers...@gmail.com on 22 Sep 2011 at 5:48

[GoogleCodeExporter]

Either way... I'm a happy man ;) - Thanks for a great app!! ... now if there 
were just a way to have sms messages go to their own contact and we could reply 
with out having to put the "reply" or "sms:#contact#:#message#" command... 

speaking of reply... is there any way to create a "r:#message#" as a shorter 
command?

Original comment by cazwell...@gmail.com on 22 Sep 2011 at 5:54