Android App just doesn't work

[bfd_64]

This is getting pretty frustrating, the whole reason I donated for this thing was because it streamed to my Android phone (HTC Incredible). The problem is that the thing only works once in a while. I have no problems now with the web client, things work fine. Trying to access the server from my phone works maybe 20% of the time and I haven't figured out what the pattern is.

The Test Connection function always works when the server is up. Sometimes I can't get the Artist list, sometimes I can. The biggest problem I have is that I can get the Artist list and an Album list for an artist but I can't get the track listing, it just times out after 4 attempts. The request is getting to the server machine, I can see it on an ethernet trace. So what the heck is the problem? Why does it work in the web browser but not from my phone? Is the interface different? Has anyone else had a problem with their Android phone?

BTW, I am having this problem while my phone is connected to my WiFi, so no routing/port forwarding problems. And like I said, I can see the request coming into the machine on an ethernet trace.

I really wish this whole thing would just work, especially since I sent my money already.

-Bill Dyer

[ccandreva]

All I can say is the Android app works fine for me.

How about some details of your server: OS, version, version of Subsonic, etc ?

[bfd_64]

Running Windows 7, version 4.0.1 of subsonic, Version 7 of the android app. Like I said, everything works fine with the browser interface and when it decides to work the Android app works great. I took a look in the Subsonic log, but there is nothing in there that gives me any clues.

[bfd_64]

So I think I know what my problem is. I went directly to the API and did some tests. It seems that it takes about 45 seconds for the server to respond to a getMusicDirectory.view request for a directory that contains actual music files. I suspect that the timeout on the Android app is 30 seconds or so so I never get the data to the app.

What I am confused about though is that a request for a track listing for an Album through the web interface only takes about 15 seconds, why the difference? I am only guessing, but I suspect that the web interface uses a different API to get at the data.

So, why is the getMusicDirectory request taking so long? I don't expect millisecond response times, but 45 seconds is too long. My music is on a network share, is that causing the problem? I have more than 20K songs in my library, is that an issue? Doesn't seem like the amount of music should matter since I have the id of a single directory that I am requesting info for.

-Bill

[bfd_64]

So, I finally got everything working. Turns out Subsonic does NOT like lots of music directories. I had my music organized into subdirectories alphabetically. I had two sets of these directories, one for lossless music and another for compressed. I was adding 52+ directories to Subsonic and this is what slows it down. I reorganized (thanks MediaMonkey!) everything into a flat directory structure and it works great. Fast as hell now. Not too thrilled about having to rearrange my music directories, but they are all tagged such that I can move them around really easily with MM, so no big deal really.

I really wish that Subsonic could read my MM database, then I could put my music where I wanted and it wouldn't slow things down so much. Oh well, it's a fantastic piece of software as is, so I won't complain too much