[lraed74]

I just upgraded to 4.1 for my Verizon 7250. After doing this, I'm not sure if this is the cause but now Google Talk keeps giving me an error and wont log in. Either is a "command Failed" or "message que overflow"

I've taken GT off and reloaded but that has no affect and keeps doing the same thing, the only thing I can think of is maybe the 4.1 upgrade for Verizon?

Have others in general had this problem or other Verizon people that just upgraded and using GT?

Thanks!!

[KonTiki]

Originally Posted by lraed74

I just upgraded to 4.1 for my Verizon 7250. After doing this, I'm not sure if this is the cause but now Google Talk keeps giving me an error and wont log in. Either is a "command Failed" or "message que overflow"

I've taken GT off and reloaded but that has no affect and keeps doing the same thing, the only thing I can think of is maybe the 4.1 upgrade for Verizon?

Have others in general had this problem or other Verizon people that just upgraded and using GT?

Thanks!!

Just to go on the record with this since we spoke yesterday, I am running Sprints version of 4.1 OS and had no trouble with Google talk at all, as a matter of fact I was even able to do the setup where I could get AIM and yahoo on it as well, but alas since I seldom used it I actually took it off yesterday. But the point is that it may be related to Verizons build since Sprint is newer.

[lraed74]

where can you get the sprint 4.1? As for the AIM setup, did that use data or txt message?

[lraed74]

I have unloaded/reload the OS (Sprint/Telstra/Verizon 4.1) to see if it was the new Verizon upgrade or not. I had been using Telstra 4.1 beforehand anyway with no issues.

After that I reloaded Google Talk each time and keep getting the same messages now, either 'command failed' or 'message que overflow'.

The big reason I want to get GT working again is that I could leave it logged on (using an aim transport) all day and never affected the batter. I was using verichat for the day and with mild chatting, it ate the battery right up.

I'm not really sure why I'm having this issue but if others have, please let me know and thanks.

[fliedlice]

Originally Posted by KonTiki

Just to go on the record with this since we spoke yesterday, I am running Sprints version of 4.1 OS and had no trouble with Google talk at all, as a matter of fact I was even able to do the setup where I could get AIM and yahoo on it as well, but alas since I seldom used it I actually took it off yesterday. But the point is that it may be related to Verizons build since Sprint is newer.

X2 except I still use mine!

[yellowhaze]

I'm having this issue as well. It ran well for about 2 weeks then errors started popping up. For me, the message overflow error cleared up after I deleted contacts in my gmail account that were associated with an aim gateway I dropped. Haven't figured out how to get rid of the command failed error.

The only thing coincidental was this all happened around the same time a bunch of these servers updated the PyAim transport. I'm not sure if this had anything to do with it. This all started for me about a week ago.

[yellowhaze]

Ok I got Google talk working again with the AIM transport.

1. Clean Install of Gtalk (deleted service books and modules)
2. Unregistered from all Jabber transports
3. In Gmail contacts, deleted all contacts created by Jabber transports
4. Resgistered on a new server (one that I had not tried before) for the aim transport
5. Logged into Gtalk

These are steps I took. I think that you can get away with steps 2-4. I'm starting to think that it has something to do with a discrepancy between the contact lists stored on the gateway server and the list in Gmail. I'm also thinking that if you ask a jabber server admin to nuke your registration data then repopluate your contact list, this might work as well.

I need to get some sleep now...

[lraed74]

I just figured that all out yesterday, kind of a pain though. I did register with the same transport and all works good now. The part I kept missing was the contacts that were still listed in Gmail, I even went one step further (which probably wasnt needed) and deleted all my SN's in AIM and added them again. I'm just happy that its going again. If this comes up again for others, the steps you listed out will be helpful!

What is the PyAim for btw, I saw that on my AIM list and wondered where it came from?