Intermittent problem on android: "A Network Error Occur

[dispatch]

Hi guys,

I still do have this problem, and I've used numerous different ROMs on my Atrix(1) (both official and unofficial, 2.2, 2.3, etc...) as well as tested different versions of the SS android client, but still have the 'network error' I originally reported. I easily eliminated DNS as a problem by testing with static IPs (and for cnliberal's situation, I would especially recommend trying this -- obviously you could create two different server connections [one for LAN and one for WAN] although I'm sure that's not what you want).

The newest SS client also seems to 'skip' a lot more for me when downloading and listening.

I've resolved to just dealing with it as I can not even ascertain if it's a SS client, server, or Android issue.

Sorry I can't help more.

[cnliberal]

...
I easily eliminated DNS as a problem by testing with static IPs (and for cnliberal's situation, I would especially recommend trying this -- obviously you could create two different server connections [one for LAN and one for WAN] although I'm sure that's not what you want).
....

I'm not sure what you're getting at here with regards to static IPs. I have my Ubuntu server at home with an internal static IP, and I have my Comcast cable internet connection (50Mbps/10Mbps) that is _not_ using a static IP. The router is a pfSense router that is using DynDNS to give me a DNS name on the internet. That IP address hardly ever changes. Using a feature built into pfSense, I can make a single connection entry in the SS Android client for my Home Server (using the DynDNS name). That works internally or externally. The issue is that the java process spikes to 100% usage and stays there. I can't see a rhyme or reason behind it doing that. I'm not thrilled. I don't want to give up on SS but Google Music does "just work". I really don't like having my music in the cloud though.

[dispatch]

I might've been conflating your problem with someone else's (or my) DNS problem. My bad. I don't have the java problem on my Windows box...

[bemymonkey]

The issue *does* seem to be related to networking. Went on a trip over the weekend through a few areas with bad coverage and had the error about 10 times within about 36 hours... with spotty reception throughout.

At home or in the city, with WiFi or good HSPA reception, I only get the error once every few days.