Android app doesn't connect

[brianjcohen]

I have no problem accessing my subsonic install remotely; I have port 8888 forwarded and the web interface works great. The android app, different story.

For server address, i put in http://{my dyndns.org address} and my username/pass is correct. As I said, my port is 8888. I'm assuming from some stuff I read that the app is hardcoded to look on port 8888, but even if I make my address http://{my dyndns.org}:8888 it still doesn't work.

The error, when I try to Test Connection, is "Connection failure. Socket is not connected."

This is on Android 2.0 (motorola droid).

[gamhead]

Looks like they accept ip addresses but not dns entries (probably because they are trying to sell their own dyndns effectively..)

Not impressed..

[reddragon72]

I have a Nexus One and it works perfectly. My fiancee has the Samsung Behold 2 and it shows the same error you are getting. So we have

Nexus One = 2.1 T-mobile good to go
Samsung Behold2 = 1.5 T-mobile Socket error
Droid(yours) = 2.0 Verizon socket error

can anyone else chime in with this? We need a tally to see what is going on.

[wattershed]

I'm using dyndns.org as well with a nonstandard port, and my Samsung Moment (1.5, Sprint) is able to connect fine.

The ports available for use might be carrier/handset/android version-specific. I don't know if there's been a lot of research into that before but as more apps like this come along that could be a point of contention with consumers and carriers.