duvu / gtalksms Goto Github PK

What steps will reproduce the problem?
1. I prefer the UI of Google Talk rather than Pidgin.
2. Sky Chat customers can chat to Google talk customers.
3. I haven't been able to locate the host details of Sky Chat

What is the expected output? What do you see instead? Use my Sky Chat account 
rather than using Pidgin or setting up a new gmail account. I haven't noticed 
that any notifcation request like battery get broadcast to all my buddies.

What version of the product are you using? On what operating system? 
SonyEricsson Xperia X10 Android 2.1


Please provide any additional information below.
This is an enhancement I would love to see.

What steps will reproduce the problem?
1.Start GTalkSMS
2.Stop GTalkSMS

What is the expected output? What do you see instead?
I expect the "GTalkSMS stopped" message to display for a few seconds and then 
disappear. However, it stays indefinitely.

What version of the product are you using? On what operating system?
1.5. I'm on an HTC Incredible 2.1, rooted

Please provide any additional information below.

This didn't happen with older versions. The only way to get rid of the message 
is to reboot the phone.

What steps will reproduce the problem?
1. Use the sms command with a phone number containing hyphens - ie. 
sms:123-123-1234
2.
3.

What is the expected output? What do you see instead?

I would expect an sms to be sent to that number.  Instead in GTalk, I get a "No 
match for "xxx-xxx-xxxx" followed by "SMS delivered"

What version of the product are you using? On what operating system?
GtalkSMS v.0.2.3

Please provide any additional information below.

Please excuse the long report - but it is probably necessary to explain such a 
large patch (which I've attached as a hg 'bundle' against the current trunk)

I noticed some strangeness in how TalkMyPhone (and hence GTalkSMS) works with 
its service, particularly related to the lifetime management and how other 
parts of the program interact with it.  To give a few practical examples:

* The UI thread is blocked while the xmpp connection is established or torn 
down.  In extreme cases, Android will notice this and offer to force-close the 
"hung" process.

* It is possible to see exceptions raised by the various calls to 
unbindService() due to the service never having been previously bound in that 
context (let me know if you want a specific example to see this)

* Similarly to above, the ActivityManager log will sometimes write a 
stack-trace with an error messaging saying our activity leaked a 
ServiceConnection.

I decided to have a go at fixing that :)  I made some significant structural 
changes which I'll outline below:

* The service is implemented with a thread+queue system along the lines of 
'IntentService' (but alas, IntentService itself wasn't flexible enough to use 
directly).  All interaction with the XmppManager now happens on a worker 
thread.  Nothing on the main thread blocks at all meaning the UI is noticeably 
snappier.

* All communication with the worker thread is done using Intent objects.  The 
'instance/getInstance()' statics have gone (yay!) - everyone who used to use 
that now uses Intents.

* All communication from the worker thread to the rest of the system is done 
using broadcast receivers.  Eg, the XmppListener class has been removed and 
replaced with generic broadcasts when connection-status changes, a message is 
received or presence changes.  The service no longer needs to delegate to other 
listeners - android manages all that for free.

* I removed the CallReceiver class and arrange to hook up telephony 
notifications only when our service is running, preventing the GTalkSMS process 
from starting every time a call is received just to notice we are not connected 
and to do nothing.

* The above all enables the service lifetime issues to be made much cleaner.  
stopService() and onDestroy() are never explicitly called - android can kill 
the process when it is necessary.  The service isn't 'destroyed' (although it 
is 'stopped') when it is disconnected, meaning activities can bind to the 
service in the "usual" way without fear the service went away just because the 
connection died.

* The XmppManager state of "QUIT" has been removed as it is no longer 
necessary.  A new state of WAITING_TO_CONNECT has been added which indicates an 
automatic connection attempt is pending (due to either lack of network 
capability or a retry cycle).  The service remains in the foreground while in 
this state to avoid premature stopping of the service.

Another side-effect of this set of changes is that if the XmppManager does 
hang, it doesn't cause the entire app to hang - just the worker thread gets 
stuck.  A side-effect of this though is that android will no longer offer the 
"force close" dialog as the app's main thread is still working perfectly.  This 
is still a better result when taking the widget into consideration, where a 
hang is much more noticeable.

The attached patch set is very large, but I think very worthwhile.  I 
understand it may take a little time to go through all the changes - please ask 
me if you need any clarification.  I'm also happy to remerge the patches should 
other changes be made on the trunk while this is being reviewed.  FWIW, I have 
tested it quite thoroughly.

When I use the ring function, the volume is not max.
But some time if i loose my phone at night at home when everyone is sleeping, i 
don't to wake up everyone...

so i think a command ring xxx to ring à xxx% volume level and ring 0 to 
vibrate only.

The following patch adds a hidden diagnostic feature - if in the main screen 
you long-press the "back" key, a dialog appears that allows you to extract the 
GTalkSMS log (with AndroidRuntime errors too) and send it as a message (eg, as 
an EMail)  The intention is that we can use this ourselves, or ask people 
reporting specific problems to do it.  Of note:

* It was originally copied from android-log-collector - I first tried to use 
that application directly but failed.

* We need a permission to read the device logs.

* We default the "to" address as empty and include in the instructions that the 
user should send it to themselves then attach it to a gtalksms issue.

* We might want to add some extra logging around things like connection state 
etc.

Let me know what you think...

What steps will reproduce the problem?
1.Receive a sms through GTalk
2.Send a reply with the reply command
3.Wait... wait... wait... 

What is the expected output? What do you see instead?

With the method sms:name:text, the message is sent without delay.
But with the reply:text command, it takes a while. More than 5' to send the 
message. And sometimes the "Message" app on android is FTC.

What version of the product are you using? On what operating system?
GTalk SMS 1.6.1 (same problem with 1.5)
HTC Desire HD with Froyo 2.2.1

Thanks for help
Very useful app !!

Wouldn't it be awesome if you could use GTalkSMS to send any console command 
from your computer and the console output got piped back to you?

:D

What steps will reproduce the problem?
1. typing "help" is an unknown command 

What is the expected output? What do you see instead?
"help" should be an alias for ? and produce the same output

What version of the product are you using? On what operating system?
GTalkSMS-v1.7-signed-aligned.apk 

Please provide any additional information below.

What steps will reproduce the problem?
1.Choose to hide notification Icon
2.Click start-stop gtalksms

What is the expected output? What do you see instead?

Expected : a display of the current state connected or disconnected

Actual : no display at all of the current state

What version of the product are you using? On what operating system?
1.00 from the market

It would be nice to be able to send/read exchange mail in the same way as you 
can with the sms. 

I tried getting gtalksms to respond in any way to my commands, but its always 
silent. "ring" also does not work. When sending a URL I noticed it disconnects 
and then reconnects. I see this in the log

01-09 12:02:05.104 D/gtalksms( 5030): Xmpp packet received

01-09 12:02:11.264 W/System.err( 5030): java.lang.NullPointerException
01-09 12:02:11.264 W/System.err( 5030): at 
org.jivesoftware.smackx.provider.XHTMLExtensionProvider.parseExtension(XHTMLExte
nsionProvider.java:84)
01-09 12:02:11.264 W/System.err( 5030): at 
org.jivesoftware.smack.util.PacketParserUtils.parsePacketExtension(PacketParserU
tils.java:378)
01-09 12:02:11.264 W/System.err( 5030): at 
org.jivesoftware.smack.util.PacketParserUtils.parseMessage(PacketParserUtils.jav
a:107)
01-09 12:02:11.264 W/System.err( 5030): at 
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:272)
01-09 12:02:11.264 W/System.err( 5030): at 
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:44)
01-09 12:02:11.264 W/System.err( 5030): at 
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:76)
01-09 12:02:11.284 W/gtalksms( 5030): xmpp disconnected due to error: 
java.lang.NullPointerException
01-09 12:02:11.284 V/gtalksms( 5030): broadcasting state transition from 2 to 0
01-09 12:02:11.354 V/gtalksms( 5030): broadcasting state transition from 0 to 4

Please let the user change the battery level notification interval. 5% is in my 
opinion to often. I sometimes just want to be informed when the device is fully 
loaded.

What steps will reproduce the problem?
1. Receive MMS
2.
3.

What is the expected output? What do you see instead?

I expect nothing (although a notification for an MMS would be nice), however 
GTalkSMS disconnects from jabber and then reconnects which is reflected in my 
GTalk client.

What version of the product are you using? On what operating system?

v0.3.1


Please provide any additional information below.

What steps will reproduce the problem?
1. Enable "Format result" option
2. receive a bold result with a ":" character at the end.
3.

What is the expected output? What do you see instead?
The expected output is a result in bold. Instead I see the smiley :* on gatlk.

What version of the product are you using? On what operating system?
v1.7.1 on HTC Desire Android 2.2

Please provide any additional information below.
This issue can be corrected by using a non-breaking space (U+00A0) between the 
":" and the "*".

What steps will reproduce the problem?
1.Turn off mobile data connection, while gtalksms is running.

What is the expected output? What do you see instead?
Gtalksms freezes, output is "Application GTalkSMS (in process 
com.googlecode.gtalksms) is not responding. [Force close / Wait / Report]"

What version of the product are you using? On what operating system?
Gtalksms 1.3.2 on Android 2.2 (Htc desire)

Please provide any additional information below.
Gtalksms doesn't freeze, when it is running on wifi and after turning wifi off.

GTalkSMS goes offline after some time. Pressing Start/Stop reconnects the 
jabber presence:

Jabber Client Log:
[17:13:05] My Droid is now Available (GTalkSMS - 97%)
[17:19:01] My Droid is now Offline

adb logcat:
01-09 16:28:46.121 V/gtalksms( 3459): connection established
01-09 16:28:46.121 V/gtalksms( 3459): broadcasting state transition from 1 to 2
01-09 16:28:46.129 D/gtalksms( 3459): handled action 
'com.googlecode.gtalksms.action.NETWORK_CHANGED' - state now 2
01-09 16:28:46.129 D/gtalksms( 3459): setupListenersForConnection
01-09 16:28:46.133 D/gtalksms( 3459): widget onReceive 
com.googlecode.gtalksms.XMPP_CONNECTION_CHANGED
01-09 16:28:46.137 D/gtalksms( 3459): onStart: _serviceHandler.sendMessage
01-09 16:28:46.551 D/gtalksms( 3459): handling action 
'com.googlecode.gtalksms.action.HANDLE_XMPP_NOTIFY' while in state 2
01-09 16:28:46.551 D/gtalksms( 3459): handled action 
'com.googlecode.gtalksms.action.HANDLE_XMPP_NOTIFY' - state now 2
01-09 16:28:46.551 D/gtalksms( 3459): handling action 
'com.googlecode.gtalksms.action.HANDLE_XMPP_NOTIFY' while in state 2
01-09 16:28:46.551 D/gtalksms( 3459): handled action 
'com.googlecode.gtalksms.action.HANDLE_XMPP_NOTIFY' - state now 2
01-09 16:28:46.551 D/gtalksms( 3459): handling action 
'com.googlecode.gtalksms.action.HANDLE_XMPP_NOTIFY' while in state 2
01-09 16:28:46.551 D/gtalksms( 3459): handled action 
'com.googlecode.gtalksms.action.HANDLE_XMPP_NOTIFY' - state now 2
01-09 17:19:05.387 I/gtalksms( 4319): service created
01-09 17:19:05.387 E/gtalksms( 4319): onStart: Intent null

Can you add an option that only make the app only use Wifi?
I don't want the app wasting my data considering there is no time I'll be using 
the app without Wifi.

What steps will reproduce the problem?
1. receive a call

What is the expected output? What do you see instead?
GTalkSMS crash

Please use labels and text to provide additional information.
v1.6

The stack error:
java.lang.IllegalArgumentException: URI: 
content://com.android.contacts/phone_lookup/, calling user: 
com.googlecode.gtalksms, calling package:com.googlecode.gtalksms
at 
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:144)
at 
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)
at 
android.content.ContentProviderProxy.bulkQueryInternal(ContentProviderNative.jav
a:330)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:366)
at android.content.ContentResolver.query(ContentResolver.java:250)
at 
com.googlecode.gtalksms.data.contacts.ContactsManager.getContactName(ContactsMan
ager.java:32)
at 
com.googlecode.gtalksms.receivers.PhoneCallListener.onCallStateChanged(PhoneCall
Listener.java:30)
at 
android.telephony.PhoneStateListener$2.handleMessage(PhoneStateListener.java:319
)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.os.HandlerThread.run(HandlerThread.java:60)

After moving around various apps, an existing Widget may stop responding to 
presses and to status updates.  Another symptom of it is that the widget text 
is blank instead of "Free" - you can tell if the widget still works by seeing 
if it has any text.  I can repro it on a 2.2 emulator by:

* Add the widget to home and use it.  Note it has text and works.
* Start Messaging app.
* Press Home.
* Widget now has no text and pressing it has no effect.

This is a different problem to the recently introduced problem when the widget 
failed to see the 'disconnected' state - I noticed it the first time I tried 
the widget, but only dug into it today.

At this stage I've no idea why...

GTalkSMS create a chat room for all incoming SMS.
The room is the same for a contact.
No more command to send sms, just put text as a conversation.

Hi, 

"battery" and "batt" don't seem to work on my device.

HTC Hero GSM.
Froydvillain 1.7.1 (based on Android 2.2.1)

What steps will reproduce the problem?
1. send anything like "." or "blah" or "help" or even something useful like 
"sms:<someone's name>:<something>"
2. gtalksms goes offline, then gets back online
3. gtalksms does not perform the selected command or throw up an error message

What is the expected output? What do you see instead?
i expected a list of commands, a sent SMS, or an error that it was an invalid 
command

What version of the product are you using? On what operating system?
1.7. android 2.2 HTC incredible

Please provide any additional information below.

this didn't use to happen. gtalksms effectively no longer works on my phone

Attaching a patch that adds 2 new preferences - one to allow auto-connection 
when a charger is connected and the other to allow disconnection when not 
charging.  (The version I sent by private mail to Florent didn't have the new 
file - doh!)

Originally requested for TMP in 
http://code.google.com/p/talkmyphone/issues/detail?id=56

What steps will reproduce the problem?
1. start gtalksms at home with wlan, xmpp contact comes online
2. disable wlan
3. gtalksms xmpp contact goes offline but the app thinks its still connected.

What is the expected output? What do you see instead?
Gtalksms contact with goes offline for a short period of time and reapers 
online after the reconnection/network switch. Worked for me with 1.3.2

What version of the product are you using? On what operating system?
1.4
Samsung Galaxy S with Froyo 2.2.1

Please provide any additional information below.
I am using a separate xmpp account for gtalksms, both accounts aren't gtalk 
accounts. 

I did some experimenting with a Locale Preference per Application, so that the 
user can choose a Locale other then the system default. This patch is the 
result.
It works fine on the emulator, although a restart of the MainScreen Activity 
and the Service is required for the changes to take effect.

Feel free to comment and use/discard the patch.

What steps will reproduce the problem?
1. Enable formatting in 'Application Settings' by enabling 'Format chat 
respones'.
2. Type in '?' to ensure that formatting is working. The command names are in 
bold in this help text.
3. Receive a SMS from a contact. No formatting appears. SMS from 
<contact>:<message>.

What is the expected output? What do you see instead?
I expected the 'SMS from <contact>:' to be in bold to be able to easily 
distinguish the actual message from the contact. 

What version of the product are you using? On what operating system?
1.5

What steps will reproduce the problem?
1.Send message
2.Receive message
3.use "markAsRead" or "mar" command to mark message as read

What is the expected output? What do you see instead?
I suppose the notification (about unread message) should disappear, but instead 
nothing happens.

What version of the product are you using? On what operating system?
gtalksms 1.3.2 on Samsung Galaxy S running Android 2.1

Please provide any additional information below.
I'm using jabber.org account on gtalksms and I'm communicating with it with my 
gmail-account. I receive the message from gtalksms saying "Mark ****'s sms as 
read" but nothing happens.

There's also possibility that I'm missing something here and using this feature 
incorrectly.

What steps will reproduce the problem?
1. Send SMS via sms:<name>:<message>

What is the expected output?
The correct name of the contact.

What do you see instead?
The name of a contact whose name doesn't match the name given, nor the number 
displayed.

What version of the product are you using: v1.5

Please provide any additional information below.
The number displayed is the right one, it is just the name that is off. The 
correct person receives the SMS as well.

What steps will reproduce the problem?
I'm not quite sure what exactly triggers it, but I assume it's either caused by 
trying to send a message, trying to mark a message as read, or receiving an SMS 
- all while locked.

What is the expected output? What do you see instead?
I see a "Sorry! Application GTalkSMS (in process com.googlecode.gtalksms) is 
not responding." when unlocking the screen.

What version of the product are you using? On what operating system?
v1.6 on a HTC Hero, Android 2.1.

What is the expected output? 
Google Talk Client (Gtalk, Pidgin, etc) receives a file transfer request for 
MMS in the chat window.
Optionally, if this isn't possible, or as an extra option, the MMS is sent to 
an email address the gtalksms is communicating with.

What do you see instead?
Currently a disconnection occurs when I receive an MMS. I notice this when I'm 
connected to wifi. 

What version of the product are you using? On what operating system?
gtalksms 1.5 on Android 2.2 HTC Incredible / Windows 7 Ultimate with Pidgin 
client.

What steps will reproduce the problem?
1. Create separate Jabber and Google accounts and configure as recommended.
2. Sign into Pidgin and initiate gtalksms connection on phone.
3. Confirm 2-way communication between phone and laptop: all commands 
functional.
4. Send multipart (ie long) SMS via "SMS:*contact*:" command from Pidgin.  
5. Confirm message sent in entirety on phone.
6. Confirm message (not) received in entirety with contact.

What is the expected output? What do you see instead?
Expected output: SMS reported sent and delivered in Pidgin.  Recipient receives 
message in its entirety.
What I see instead: SMS reported sent and delivered.  Recipient receives only 
the first part of the multipart text.

What version of the product are you using? On what operating system?
gtalksms v1.7.1 on Oxygen 2.0RC6 'Gingerbread' for HTC Desire (GSM).  Pidgin 
v2.7.9 on laptop PC (Windows 7 Professional 64-bit)

Please provide any additional information below.
Problems occurred whilst connected to Vodafone UK EDGE network with good 
connection strength.  Laptop PC was connected to the HTC Desire's WiFi Hotspot 
with WPA2-PSK encryption.  No opportunity to test on HSPA/3G network, or test 
using separate phone & computer internet connections due to constraints at 
current geographical location.

Thanks.

see attached patch

What steps will reproduce the problem?
1. Reply to a sms within the client with the phone that has been locked due to 
inactivity.


What is the expected output? What do you see instead?
The expected output is that the client immediately (or at least within a 
minute) receives "Sending SMS to <contact>" notification in the chat window and 
the phone fires off the SMS to the contact. 

What I see instead is a delay. Sometimes more than a few minutes or so. When I 
receive an SMS, it has always been instantaneousness. My phone vibrates and I 
already have the SMS on my chat window. Whether the phone had its screen off or 
not, receiving SMS is instant.

However, when I send the SMS with a "cold" phone, a phone that is locked (not 
security lock) and the screen dark, it takes a few minutes at times or I give 
up and open up the phone to the homescreen. 

However, when I see that I'm not getting the "Sending sms to <contact>". I turn 
the screen on the phone and the SMS proceeds to send I receive the expected, 
SMS sent, SMS delivered. 


What version of the product are you using? On what operating system?
gtalksms: 1.6 (donate version). Phone: HTC Incredible 2.2. Desktop: Windows 7. 

Please provide any additional information below.
I've attached a screenshot that shows the timestamps. The first red circle 
shows how fast the Send SMS occured, while the 2nd circle did not send the SMS 
until I finally opened up the phone from its inactive state.

I can recreate this scenario pretty much every time.

I want to be able to turn gtalksms on and off from Tasker (specifically), but 
I'd image locale users would appreciate this too. 

Specifially, this would allow me to turn gtalksms on when Tasker puts my phone 
on silent when I get to work, and turn it off when I leave work, but I can 
imagine it would be useful to other people in other ways. 

What steps will reproduce the problem?
1. Set the options to have individual chat window per SMS conversation.
2. Opens up a chat conference.
3. Other people are somehow able to enter this chant conversation.

What is the expected output? What do you see instead?
Only allow you and the SMS recipient to occupy the room. I see other people 
entering the conversation window and they were able to chat to me and 
potentially my SMS contact. 

What version of the product are you using? On what operating system?
1.7.1

What steps will reproduce the problem?
1. Sign into Gtalk on phone.
2. Communicate with gtalksms via external client.

What is the expected output? What do you see instead?

When communicating externally, messages sent and recieved are not duplicated on 
the phone unless the conversation is started by the other end and has yet to be 
answered.

However in this case ALL chat is relayed to gtalk on the phone.

What version of the product are you using? On what operating system?

v1.7

Please provide any additional information below.

Using notify to "main gmail" and notify with a separate jabber account.

If you attempt to mute the jabber account on the phone it will propagate the 
mute to all clients as a block.

Unmanaged exception in EditIntegerPreference

java.lang.NumberFormatException: unable to parse '7866647688' as integer
at java.lang.Integer.parse(Integer.java:438)
at java.lang.Integer.parseInt(Integer.java:422)
at java.lang.Integer.parseInt(Integer.java:382)
at 
com.googlecode.gtalksms.tools.EditIntegerPreference.setText(EditIntegerPreferenc
e.java:30)
at 
android.preference.EditTextPreference.onDialogClosed(EditTextPreference.java:142
)
at android.preference.DialogPreference.onDismiss(DialogPreference.java:384)
at android.app.Dialog$ListenersHandler.handleMessage(Dialog.java:1047)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:871)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:629)
at dalvik.system.NativeStart.main(Native Method)

I have "Application connection" notification disabled, but Gtalksms keeps 
sending "Stopping outgoing actions" when it gets disconnected or when stopping 
the service.

Froydvillain 1.7.1 (Android 2.2.1)

What steps will reproduce the problem?
1. use "cmd:logcat" (or any other command that doesn't immediately terminate)

What is the expected output? What do you see instead?
Ideally, expect 2 things:
* logcat lines are printed as they become available
* gtalksms continues to work as normal

Instead, I see:
* gtalksms appears to be hung and no longer responds to commands.  Debugger 
tells me it is blocking to read the process output.

What steps will reproduce the problem?
1. Set up using the same gmail address for sending/receiving, as instructed in 
the wiki (all settings/addresses verified). gtalksms shows it is "connected" in 
notification bar
2. In Pidgin, using my gmail account I added myself as a contact, I show up in 
my conacts list.

What is the expected output? What do you see instead?
When I issue commands to the device, Pidgin throws an XMPP message error (Code 
503). Also when receiving an SMS the phone did not seem to send any 
notification to Pidgin.  

What version of the product are you using? On what operating system?
Version 1.0 of the app, Pidgin version 2.6.5

What steps will reproduce the problem?
1. Deactivate the status notification icon
2. Go back to the home screen

What is the expected output? What do you see instead?
I would expect GTalkSMS to continue running in the background and keep my 
connection alive. Instead I see it going offline immediately.
If I activate the icon the connection will be kept alive.

What version of the product are you using? On what operating system?
1.3.2 on Cyanogenmod (Froyo) 6.1 stable

Would like to have the program run and stay connected without the icon :)

What steps will reproduce the problem?
1. Set tasker up with context - WiFi Connected, enter task as action intent to 
connect Tasker and exit task to disconnect, as per the wiki on public actions
2. Connect to WiFi network
3. Wait any amount of time [possibly sending messages]

What is the expected output? What do you see instead?
I'd expect to see this very temporarily if it drops out of signal, but it stays 
until I force close GTalk from the applications menu.

What version of the product are you using? On what operating system?
1.7, Oxygen ROM 2.0RC6 (based on AOSP 2.3)

Please provide any additional information below.
It's a bit of a pain, because it obstructs the on screen keyboard and any 
widgets on my home screen, and generally anything I try to use on my phone. 
Can't use gtalksms until it's fixed - really big shame.

I don't know if it's possible but it would be fine to Start the GPS by command 
to know the exact position with the where command...

Here is my proposal of a German translation. Comments welcome :-)

When receiving and reading a SMS with GtalkSMS, it's would be great to mark it 
as open / read. So when people are having a conversation through GTalkSMS, they 
don't have several unread messages on the phone. Or at least when user had 
reply to message with the reply command (So you can check if the user has read 
the GTalk message and wasn't offline/disconnected).

Thanks for the app though, it's great. :)

At least on the same devices for which issue 8 (Gtalksms freezes after turning 
off mobile data connection) was a problem...

* Connect via 3g network (ie, with wifi disabled)
* Enable wifi - 3g network is dropped.
* GtalkSMS hasn't dropped the 3g connection so still thinks it is connected - 
but fails to respond to chat requests (as the connection is dead).  It should 
have disconnected then reconnected on the wifi network.
* Explicitly stopping GTalkSMS does work as expected.

The problem is our handing of the NETWORK_CHANGED action - we no longer attempt 
to close an existing connection when the network has become not available.  In 
*most* cases, this isn't a problem - the XmppManager's connection listener sees 
an error state as the network drops, so the right thing happens.  Sadly though, 
on the devices where this bug exists, we do *not* see an error condition - so 
the new handling of NETWORK_CHANGED leaves the (now dead) connection around, 
but it never receives any messages.

So in short, we need to disconnect when the network is not available.  Also 
note one other bit of confusion around the xmpp state in the retry handler.  
While we are waiting for a retry, the state is set to CONNECTING (which it 
isn't - it is waiting) and once we have given up on retries the state is left 
in WAITING_TO_CONNECT (which it isn't - it has given up.)  This causes some 
problems when handling, for example, the TOGGLE action - it does nothing when 
in the state CONNECTING, so pressing the widget does nothing.

I've spent some time on this and can't make it work correctly in all cases 
using the current scheme.  I think we really need to rework the state 
management - I'm thinking along the lines of:

* The xmpp manager has 2 states - the "desired" state and the actual connection 
state.

* The states CONNECTING and DISCONNECTING remain as "temporary" states - ie, 
the actual state will never be one of these values except *during* a call to 
start() or stop().

* We drop the WAITING_FOR_CONNECTION state - this is implied by having a 
desired state of CONNECTED, but an actual state of DISCONNECTED.

The devil is in the detail, but I'm out of time for today...

What steps will reproduce the problem?
1. Connect gtalksms over 3g.
2. Activate wifi. My access point is primarily WPA2-Personal encrypted, the 
SSID for me is synapse
3. gtalk will start throwing a "login failed" popup over anything active.

What is the expected output? What do you see instead?
gtalk should tolerate the introduction of a wifi point. Instead, it errors out 
with a "login failed" error, even when already logged in. Didn't seem to occur 
in earlier builds.

What version of the product are you using? On what operating system?

1.4

Starting gtalksms after wifi is enabled appears to work.


Please provide any additional information below.

Integration with tasker is very easy - we just need to make our intents 
'public' and some instructions that should probably go onto the wiki.

Regarding making the intents "public" - in the attached patch, along with 
exposing .GTalkSMS.TOGGLE and .GTalkSMS.SEND, I renamed ACTION to CONNECT as 
this more accurately describes what it does. I figured that if we are going to 
start documenting these intents, we might as well make them as reasonable as 
possible :)

Once this patch is in place, the following instructions would be valid:

= GTalkSMS public actions =

There are 3 Android 'actions' which GTalkSMS handles.  Any application on the 
system can send these actions and have GTalkSMS perform a corresponding 
command.  For example, the 'Tasker' application can be used to send these 
actions in response to many different things happening on the phone.

== Public Actions ==

.GTalkSMS.CONNECT: Connects or disconnects the xmpp connection.  By default, 
the request is considered a connection request, but an extra called 
'disconnect' set to 'true' will cause it to be considered a disconnection 
request.  If xmpp is already in the requested state, no action is taken.

.GTalkSMS.TOGGLE: Toggles the current connection state (ie, disconnects if 
currently connected, and connects if disconnected.)  If GTalkSMS is in a 
'waiting' state (ie, with a yellow icon), it will become disconnected.

.GTalkSMS.SEND: Sends a message over xmpp - the message itself must be in an 
extra called 'message'.  No action is taken if xmpp is disconnected - if you 
want to force connection first, just send a .GTalkSMS.CONNECT action before the 
send action.

= Working with Tasker =

You can send commands to GTalkSMS by using a Tasker 'Action Intent' - when 
Tasker presents its list of Actions, select "Misc Action", then "Action 
Intent".  Note the following:

* When tasker prompts for the 'Action', enter one of the strings above - eg, 
'.GTalkSMS.SEND' - without the quotes but *with* the leading period/dot.

* The Category should remain at its default of "None", and the optional Data 
field should be left blank.

* One of the Extra fields should be used if the action requires an 'extra'.  
You enter a string in the format 'name:value' - eg, 'message:hello' could be 
used for a .GTalkSMS.SEND action.  The second Extra field can be left blank as 
no GTalkSMS action require multiple extras.

* The Target field must be changed to 'Service'.

Sadly since 1.5 or so, gtalksms fails to achieve a permanent xmpp connection. I 
am using a 2 Account Setup where both accounts are no gtalk but pure xmpp 
accounts on my server. Also I am usually letting gtalksms run all the time. 
Which has worked fine and stable a few versions ago.

There a 2 things which I can observe:
- the gtalksms service shows up in the android service list, but gtalksms fails 
to reestablish the xmpp connection, also pressing the start/stop button in the 
gtalksms menu fails to reestablish the connection. In this situation the memory 
footprint of the gtalksms service is around 12MB which is more than double as 
usual.
- the gtalksms service just vanishes (I am not using any automatic app/service 
killer)

I have attached the output of the new loging function. There is one particular 
line which came to my attention: "xmpp got an unexpected normal disconnection"
Looking at the source, it seems that this should not happen.

What version of the product are you using? On what operating system?
Using the donate 1.6.1 Version of GTalkSMS on a Samsung Galaxy S with 2.2.1 
(Samsung FW JPY)

Please provide any additional information below.
Version: 1.6.1
Kernel info: 2.6.32.9
root@SEP-51 )
#1 Mon Dec 20 15:55:57 KST 2010

--------- beginning of /dev/log/main
01-07 15:00:24.613 W/gtalksms(28399): xmpp got an unexpected normal 
disconnection
01-07 15:00:24.613 V/gtalksms(28399): broadcasting state transition from 2 to 0
01-07 15:00:24.625 D/gtalksms(28399): widget onReceive 
com.googlecode.gtalksms.XMPP_CONNECTION_CHANGED
--------- beginning of /dev/log/system
01-07 16:03:37.055 D/gtalksms(28399): Download begins
01-07 16:03:37.055 D/gtalksms(28399): Downloading 
url:http://gtalksms.googlecode.com/hg/AUTHORS
01-07 16:03:37.668 D/gtalksms(28399): downloaded in0 sec
01-07 16:03:37.668 D/gtalksms(28399): Download begins
01-07 16:03:37.668 D/gtalksms(28399): Downloading 
url:http://gtalksms.googlecode.com/hg/Donors
01-07 16:03:37.879 D/gtalksms(28399): downloaded in0 sec
01-07 16:03:37.883 D/gtalksms(28399): Download begins
01-07 16:03:37.883 D/gtalksms(28399): Downloading 
url:http://gtalksms.googlecode.com/hg/Changelog
01-07 16:03:38.188 D/gtalksms(28399): downloaded in0 sec