Location won't stop after saying stop or restart

[GoogleCodeExporter]

I can't seem to get gtalksms to stop sending location updates. I sent "stop" at 
least 20 times and even restarted the application. It continues to send 
location updates periodically. 

Original issue reported on code.google.com by samgarfield on 11 Feb 2011 at 4:09

[GoogleCodeExporter]

same issue here... Using last version

Original comment by jameslop...@gmail.com on 6 Mar 2011 at 2:41

[GoogleCodeExporter]

Could you please generate an app log the next time this happens to you: 
http://code.google.com/p/gtalksms/wiki/GenerateAppLog

Thxs

Original comment by fschm...@gmail.com on 7 Mar 2011 at 7:51

[GoogleCodeExporter]

I think this issue may happen exclusively on "first load" after starting 
gtalksms for the first time, or when the location availability is changed (e.g. 
by turning on/off location services through items such as Tasker or widgets).

My environment:
#1- Using same account as my google account
#2- Droid X
#3- 2.2

Started gtalksms, played around with commands for a bit.  Then found "where".  
My GPS was not turned on at the time so I started where, then switched to 
desktop using SwitchPro to turn on GPS, then switched back to gtalksms.  
gtalksms hadn't sent any location updates prior to turning on GPS (expected 
behavior).  Once it started though it didn't stop, and this even persisted 
through backing out of the application, starting/stopping in the application, 
etc. 

However, it did stop after killing the application with ATK, and restarting it 
after that point.    Now where/stop works as normal.

As an important point, it would be nice to change the interval of the location 
updates.

Original comment by arimat...@gmail.com on 9 Mar 2011 at 4:14

[GoogleCodeExporter]

Could you test if issuing the "exit" command stops location updates? Note that 
this (should) also exit gtalksms on the phone.

Original comment by fschm...@gmail.com on 10 Mar 2011 at 12:38

[GoogleCodeExporter]

I'm not sure it's issue or not  but same for me  HTC desire, i found some  
thing maybe help you , in the GeoCmd.java 

find the execute method , add few lines like below 

    @Override
    protected void execute(String cmd, String args) {
        if (cmd.equals("geo")) {
           geo(args);
        } else if (cmd.equals("where")) { 
            if (args.equals("stop")) { // added a stop cmd
                send(getString(R.string.chat_stop_locating));
                stopLocatingPhone();
            } else {
                send(getString(R.string.chat_start_locating));
                startLocatingPhone();
            }
        }
    }

then you can sopt the locating service with command "where:stop"

Original comment by eggcaker@gmail.com on 14 Mar 2011 at 8:07

[GoogleCodeExporter]

stop command do the exact same thing as your where:stop implementation.
So I don't think that's fix the bug

Original comment by Florent....@gmail.com on 14 Mar 2011 at 8:38

[GoogleCodeExporter]

Do you still have the issue ?
If yes, can you give us some logs else I'll close this bug.

Original comment by Florent....@gmail.com on 10 Jun 2011 at 11:12

[GoogleCodeExporter]

Original comment by Florent....@gmail.com on 10 Jun 2011 at 11:12

• Changed state: UserFeedBack

[GoogleCodeExporter]

I have the same issue with the 'exit' command. sometimes the command is 
executed and may Galaxy Tag (jabber.org Account) shuts the service down. 

But in most cases the Service runs until i reach my Tablet and exit with the 
widget or the App.

Original comment by patr...@kodal.at on 28 Jul 2011 at 10:52

[GoogleCodeExporter]

Please send us an app log if you encounter this issue in GTalkSMS 3.X

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

[GoogleCodeExporter]

Original comment by Florent....@gmail.com on 11 Feb 2012 at 6:00

• Changed state: Invalid