Android N no play

[daneren2005]

I was able to fix my issue with it constantly skipping tracks as others did by clearing the cache/data, but I'm having issues casting to a Chromecast now after the update to Android 7.0 on my Nexus 6P. I have tried other services and I can cast fine if I use device proxy, but if I try and cast without device proxy enabled, I simply get "failed to load" and the track never plays. This behavior is the same on both a gen 2 chromecast and a chromecast audio. Did anyone else run into a similar issue and come up with a solution?

No you are first person to report that. In fact, that makes no sense as far as I understand the code. The device proxy option is to get around issues with your server, and NOT issues with the device (it basically pretends your device is the server). If it works with your device that would seem to mean that there is nothing wrong with the device's end of equation and the Chromecast is rejecting connections from your server directly. Are you sure you didn't change anything else on your server such as ciphers or changing from http to https which might be causing issues?

[wildwoodashes]

I was able to fix my issue with it constantly skipping tracks as others did by clearing the cache/data, but I'm having issues casting to a Chromecast now after the update to Android 7.0 on my Nexus 6P. I have tried other services and I can cast fine if I use device proxy, but if I try and cast without device proxy enabled, I simply get "failed to load" and the track never plays. This behavior is the same on both a gen 2 chromecast and a chromecast audio. Did anyone else run into a similar issue and come up with a solution?

No you are first person to report that. In fact, that makes no sense as far as I understand the code. The device proxy option is to get around issues with your server, and NOT issues with the device (it basically pretends your device is the server). If it works with your device that would seem to mean that there is nothing wrong with the device's end of equation and the Chromecast is rejecting connections from your server directly. Are you sure you didn't change anything else on your server such as ciphers or changing from http to https which might be causing issues?

derp, this was a problem on my end with configuration after deleting the cache/data. I've resolved it now I believe. Sorry for the false alarm...

[daneren2005]

Out of curiosity what setting dis you have setup wrong? I'm curious what could have caused that.

[wildwoodashes]

I have a redirect from sub.MYURL.com to the IP of my server internal to my network using dnsmasq on my router in addition to a URL redirect with my registrar from sub.MYURL.com to http://www.MYURL.com:4040. I had entered http://sub.MYURL.com:PORT# in the server field. This works fine to playback files with dsub and works fine on a browser but it seemed to cause a problem when trying to cast to a Chromecast. My solution was to just use http://www.MYURL.com:PORT# in the server field.

[gorman]

Reading this, I worry. Having recently bought a Nexus 6P and being currently populating the music library (I use Madsonic as a way to access ALL my music but keep most of what I listen to cached locally, 128GB model) I wonder... if I would update to Nougat would I need to redo the whole process?

[daneren2005]

Reading this, I worry. Having recently bought a Nexus 6P and being currently populating the music library (I use Madsonic as a way to access ALL my music but keep most of what I listen to cached locally, 128GB model) I wonder... if I would update to Nougat would I need to redo the whole process?

Yes wiping the cache will mean you have to restart caching everything. I apologize but I really have no idea why this is even a problem in the first place. AFAIK the MediaPlayer instance can't access the files to play them for some reason. DSub has permissions to access the files, but when I tell the MediaPlayer to play it it just refuses to with a generic error. There doesn't appear to be anything I can change to fix this and starting from scratch is the only fix I have been able to find. Even DSub clearing it's own cache didn't do anything, so there must be something unique cached wrong at the system level which I can't change.