Crash after importing any M3U file through 3rd party file manager about auxio HOT 1 OPEN

Since Auxio needs the path of an M3U file to generate relative M3U paths, it uses some really cursed hacks that decodes the path information from the URI given. It's pretty brittle and was only designed with the native file manager.

• I can likely handle 3rd party file managers as content://{file manager's package name}/file/{URL encoded path to the file, starting with :///storage/emulated/ }
• content://media/external/file/1000014949 is likely a MediaStore entry of some sort. Need to research this.
• I doubt I'll be able to support Google Drive files, those have no real "path" information. Maybe I could support them in an absolute path form only, but then I would have to indicate that I had to do that. I'll likely just leave them unsupported since #322 will make that redundant anyway.

from auxio.