search

tomahawk-player / tomahawk-android

Tomahawk's Android Music Player
GNU General Public License v3.0
691 stars 260 forks source link

Doesn't seem to work with ownCloud/Ampache #22

Open Decoherent opened 8 years ago

Decoherent commented 8 years ago

Well, I know this is for a beta client connecting to a beta service, but here goes anyway. I've got ownCloud running with its Ampache support, and the Android Tomahawk app doesn't seem to work correctly with it. It seems to log in correctly, all albums/songs are displayed correctly, but trying to play any song just shows the animated line on the top for a few seconds, then goes to the next song, until there aren't any songs left. I've successfully used this server with the "Just Player" Android app and Tomahawk on Windows. Is there some way to collect additional data to see if I can figure out where the problem lies?

mrmaffen commented 8 years ago

Hi, sorry for the late response. I'll test this and see if I can reproduce the issue. You can always check your device's log yourself by installing adb (Android Debug Bridge) and running "adb logcat". Filtering by "ampache" will give you the output of the javascript Resolver which hopefully contains some relevant error messages.

kinncj commented 8 years ago

The tomahawk desktop app can connect and list my music, the android app seems to connect but cannot list my music.

kinncj commented 8 years ago 
02-14 21:36:12.045  2043  2043 I Keyboard.Facilitator: onFinishInput()
02-14 21:36:12.722 29946  3666 E CollectionDb: tracksCurrentRevision - no tracks in table!
02-14 21:36:13.053  2043  2043 I Keyboard.Facilitator: onFinishInput()
mrmaffen commented 8 years ago

Are you using a https connection with your ampache media server? Which version of tomahawk-andorid are you using? A simple http connection with the latest nightly does work on my device.

kinncj commented 8 years ago

built the master branch. yes HTTP with self-signed cert. as far as I could see, you're using JS to the ampache client, and AFAIK there's no way to ignore the self-signed cert on xmlhttprequest

On Tue, Feb 23, 2016 at 11:04 AM, Enno G. notifications@github.com wrote:

Are you using a https connection with your ampache media server? Which version of tomahawk-andorid are you using? A simple http connection with the latest nightly does work on my device.

— Reply to this email directly or view it on GitHub https://github.com/tomahawk-player/tomahawk-android/issues/22#issuecomment-187765136 .

-- Kinn Coelho Julião Toronto - ON/Canada

mrmaffen commented 8 years ago

Please try to establish a simple insecure http (not https) connection and see if the issue goes away. Pretty sure this is in fact related to your self-signed cert being ignored by the Android system.

kinncj commented 8 years ago

Yes, as I mentioned

you're using JS to the ampache client, and AFAIK there's no way to ignore the self-signed cert on xmlhttprequest

rseek commented 8 years ago

it seems I have the same problem :(( both on Android and with linux desktop client.

Any plans to support self-signed certs?

e-alfred commented 8 years ago

You could try to add your certificate to the cert store on each system like that: https://unix.stackexchange.com/questions/17748/trust-a-self-signed-pem-certificate

If you can, using Letsencrypt or a free cert from Wosign or StartSSL would be a better idea though.

DroWnThePoor commented 8 years ago

I have this working flawlessly on my Linux client.I can also connect with Just Player on Android, but the interface isn't great.On my first attempt to connect with Tomahawk on Android it showed one unknown artist and this never changed.I cleared the connection settings and retried and got nothing at all.Hope we can fix this issue.

e-alfred commented 8 years ago

On all the other platforms Tomahawks Ampache support works well. On Android it doesn't, but it would have the best interface out there compared to all the other (unmaintained) Ampache clients on Android.

This bug is also a problem:

https://github.com/tomahawk-player/tomahawk-android/issues/26

theli-ua commented 8 years ago

So, is this bug essentially about trusting self-signed certificates? as mentioned here its not trivial to make those work without adding certificate to system store @DroWnThePoor did you try to add your certificate to system trusted store? did it work for you?

DroWnThePoor commented 8 years ago

Sorry this was a bug I filed a while ago. I ended up getting the Android-Client to work, however, A number of artist/tracks aren't showing up in the Ampache collection. On my one device, it's especially the tracks. It appears that only tracks beginning with a number or the letter A are showing up, and the rest it's like it can't resolve. On that particular device I can't run ADB to get more information about what's going on. Any ideas?