Back to Top

Comm Err: Socket is not Connected

8 posts / 0 new
Last post
lee
Offline
Last seen: 4 years 8 months ago
Joined: 02/02/2010 - 11:48
Comm Err: Socket is not Connected

This error continuously appears on my Moto Droid... Data connect is active, any ideas?

Lee

eric
Online
Last seen: 2 min 52 sec ago
Joined: 11/06/2008 - 22:02
Log file

Most likely you don't have a network connection at the time the update is occurring. You could get the whole story by emailing the log to yourself (or me). There's a menu option in DC to send log.

Are you able to update ever, or does this just happen occasionally? It does happen for me now and again when the cell connection flakes out or the connection is flipping from wifi to cell or vice-versa.

Nobilis
Offline
Last seen: 3 years 10 months ago
Joined: 12/25/2010 - 18:25
Same problem on Samsung Intercept

19 times out of 20 (I'm still trying) my downloads fail with the following message:

Detail: java.net.UnknownHostException: (domain name, such as www.podtrac.com)

Cause: The network is not connected via wifi or mobile

I have full wifi connectivity (in the same room with the wifi router) and 4 bars of 6 on the 3g network. The application is able to update the feeds, so I know it can access the sites.

Nobilis
Offline
Last seen: 3 years 10 months ago
Joined: 12/25/2010 - 18:25
Here's the full

Here's the full data:

DETAILS:
DoggCatcher Version: 1.1.1740
Device: Samsung Intercept
Android Build: 2.1
Carrier: Virgin Mobile

SUMMARY: Unable to download episodes

STEPS TO REPRODUCE:
1. Touch an undownloaded episode to start it downloading

WHAT HAPPENS: Download fails

WHAT SHOULD HAPPEN: Download should succeed

FREQUENCY: 22 times out of 23 so far

SEVERITY: Critical

eric
Online
Last seen: 2 min 52 sec ago
Joined: 11/06/2008 - 22:02
Error message

I assume your getting the socket is not connected error.

That message is coming from android code so that truly is the problem. If you are interacting with the device while this is happening (meaning it's not going to sleep), then you are having networking problems and there are more clues in jnavas' post.

You may be experiencing a problem that the device is going to sleep while it's downloading, so devices can do this. There's a preference way down the bottom, something like 'keep device from sleeping', I think it's in advanced. That can help prevent devices going to sleep when downloads are occurring.

battre
Offline
Last seen: 3 years 6 months ago
Joined: 04/15/2011 - 16:56
Locking network

I get the same error message for quite some time:

Event: Download
Result: Failure
Description: tagesschau 20:00 Uhr, 13.04.2011
Detail: java.net.UnknownHostException: tagesschau.vo.llnwd.net
Cause: The network is not connected via wifi or mobile

I believe, however, that this is not Android's fault but Doggcatcher's. The point is that you need to acquire the correct locks.

This post http://stackoverflow.com/questions/3037303/wake-lock-does-not-seem-to-work explains that one needs to acquire a PARTIAL_WAKE_LOCK on the PowerManager *AND* a wifi lock from the WifiManager. This solved downloading problems with another developer's android app that tried downloading large files when the device was connected to the charger.

Best regards,
Dominic

eric
Online
Last seen: 2 min 52 sec ago
Joined: 11/06/2008 - 22:02
Locks

DC does get both of those locks but some devices handle the partial_wake_lock differently. You can set the preference 'prevent sleep during download'. This gets a stronger lock but requires that the screen remain dim.

JNavas
Offline
Last seen: 2 years 4 months ago
Joined: 11/08/2010 - 10:59
UnknownHostException

This error means that DNS name (e.g., example.com) lookup is failing.
Possible causes:

  • Invalid domain name. Since you can update feeds, this is the most likely cause.
  • Remote DNS server problem.
  • Poor connectivity. (Even when wireless is working there may be Internet backhaul problems.)

Possible solutions:

  1. Feed data may be bad. Since you can update feeds, this is the most likely cause.
    What is the feed name and/or URL?
  2. If on 3G switch to Wi-Fi, and vice versa.
  3. Reboot the mobile device.

Hope that helps,
John