2013-11-02, 02:20
(2013-10-25, 19:18)freakoutguy Wrote: Do I have to uninstall my XAF build and install your custom XBMC build (as outlined) and follow all tyhe outlined steps for this to work, or can I just create the playercorefactory file as recommeded by you and edit ?
It depends on your issues. My xml is probably the same as the one from the XAF build anyway. My fix will not magically fix issues you have with MX Player, it only fixes the fact that MX Player refuses to start in the latest xbmc.
I do not exactly know what the XAF build does, but the fact that the binary is twice as big as a regular build prevent me from using it on most my devices. For the rest, the choice is yours.
(2013-11-01, 21:09)Romout Wrote: Hi wololo,It is possible streaming files requires a different intent for MX Player or VLC... but I am not sure. Keep in mind this is basically my first time looking in the xbmc code, and my first time compiling anything for Android, so I am definitely not an expert.
This is my first post on this forum. I have tried your patch build binaries with an Amerry Android Stick (V2). I have taken your playercorefactory.xml and wanted to stream files from my NAS using Samba. As XBMC always used the internal player, I figured out that your xml does mention known problems of MXPlayer concerning Samba and therefore routing SMB to DVDPlayer. I changed that to the MXPlayer but that instantly dropped me back to the desktop when ever I wanted to start a movie. I then switched to VLCPlayer with the same outcome.
Now here comes the interesting part: I added a player configuration for the android gallery with exactly the same behavior (drop back to desktop) but I would have expected that to work as it actually does work using ES Explorer + Network/Samba connection to my NAS. I have chosen the gallery to view the very same movie and it did run like a charm.
Do you have any further ideas on how I could overcome that issue?
