Jump to content

Odd Twitter problem


Recommended Posts

Posted

For the past 2 days I have only been able to get Twitter clients to connect over WiFi, if I try over 3G/2G I get a connection error using either Twidroid or TweetCaster. Twidroid just says it had a connection error but TweetCaster gives a bit more info & says "A network error has occurred. Unexpected character in stream".

They are both fine if I connect to WiFi. TweetCaster was a new install this morning whereas Twidroid has been on there for a while.

I can connect OK via the TwitterGadget client in iGoogle from the browser.

Anybody else come across a similar problem.

Posted
For the past 2 days I have only been able to get Twitter clients to connect over WiFi, if I try over 3G/2G I get a connection error using either Twidroid or TweetCaster. Twidroid just says it had a connection error but TweetCaster gives a bit more info & says "A network error has occurred. Unexpected character in stream".

They are both fine if I connect to WiFi. TweetCaster was a new install this morning whereas Twidroid has been on there for a while.

I can connect OK via the TwitterGadget client in iGoogle from the browser.

Anybody else come across a similar problem.

Try search for "Twidgit" on the marketplace its the one Google heavily advertises and works flawlessly with Pulse.

Posted
Try search for "Twidgit" on the marketplace its the one Google heavily advertises and works flawlessly with Pulse.

Thanks - Twidgit works perfectly, pity the others don't.

Guest gavinlew
Posted

No problems on my Pulse (1.7 Vanilla) with either of the 2 original apps - Twidroid PRO (for widget support) or Tweetcaster free / Vodafone UK contract SIM.

Posted
No problems on my Pulse (1.7 Vanilla) with either of the 2 original apps - Twidroid PRO (for widget support) or Tweetcaster free / Vodafone UK contract SIM.

my twigee seems to work fine, a little slow now and then, but no major problems.

Guest mark2410
Posted

i think i found the problem and solution, i noticed seesmic was doing the same for me but when i used twitdroid it worked. that made me think it had to be the network (ie tmobile) being dicks and blocking traffic. on twitdroid i always selected us SSL and thats why it was still working. seesmic had no such option.

hope that helps

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.