Hi,
Try to also set:
Force Relative paths
Use Linux Folder Separator / instead of \

Also try to Set that Playlist are saved in Root of USB and that music is in other folders. It is possible that folder can't contain more than 999 files or in worst cases 255 files.

I have a 2023 Honda CRV Sport Turing. I do not play the USB sticks I create with MM, with MM in my Car. I use the USB button, that access the music and playlists directories. I also use Android Auto, but, most of the time I play USB sticks with the Honda USB function and FM radio. I am having problems; my best guess is that I have exceed some kind of limit. Please see https://garyjohnson53.wordpress.com/201 ... honda-crv/

MediaMonkey Options Portable Device Sync

Not set
Force Relative paths
Use Linux Folder Separator / instead of \
Use extended M3U

set
Use Unicode (UTF-8 encoding)

Thank you, I got it finally.
I had the correct setting already for export. For unknown reason there were a few lists (7 of 21) still having the windows format.

Hi,
Standard export have Windows in mind and you need Linux and relative format.

No need uploading the files. I found out that some of them have lines with #exif at start.
I deleted the lines and now the Playlist folder is readable.
Why is the standard export format with these lines and not just the relative path?

Hi,
You can supply ZIP-ed sample of few playlists that MMA do not read in Support Ticket and I'll be glad to look at them and see why MMA do not read them.

Update: I have since moved the library to the Android radio's hard drive instead of a USB stick, but even in this variant the playlist folder with 22 playlists is not recognized. When I refer to the folder, there is a message that it is empty.
This had not happened to me with smartphone and tablet, however, I have synchronized both with MMW.
Unfortunately, this does not work with the car radio, because the laptop has Linux installed (Windows only in the home).

Is there an explanation or possibly even a solution? At the moment I helped myself by creating the playlists manually. But for the future it would be good if MMA can also read playlists directly.

Thank you, @Pete . I will remain patient. As I said, I can use MMA from smartphone via Bluetooth or Android Auto, including all playlists. I am glad that MediaMonkey is available. It has a much better UI for me - also in MMA - than any other app, i. e. Power Amp (that I mentioned).

Hi,
No, As in order to unify settings both MMA, MM5 depend on Partition ID to track moving removable storage across devices.

We plan to make OTG database more permanent eg. that Storage DM is located on Device itself so that when you plug Storage in any other device it will not need to go thru whole Scanning process on restart.

Downside is that it is still on to do till all major issues and stable version gets out.

Unfortunately we are in minority and need to wait.

I joined beta testing now.
Also I checked OTD with a tool that says it works on my android radio. However, that is meant for moving or copying files only I suppose, but not for full support of playing music with MMA, right?

Meanwhile I found out that MMA is scanning all music files and then displaying them, but without getting the cover images. And next start of device scanning starts again.
Playlists still are not seen yet.

I asked myself what solution Power Amp might have to be able to add the usb music library and playlists with all cover images.
@Pete, you wrote that the problem is changing of ID. Is it difficult to relate on certain device name instead? I.e. I called my usb-stick "Music auto". And it is displayed with this name in android file manager and in MMA too.

Hi,
Yes, MMA 2.0 Beta is very very stable.

@Pete Should I get beta for that device to help with the troubleshooting?

In any case, thank you very much for your comments.
I'm curious to see what happens with MMA on the device. It's not a huge problem for now because I can play MMA via Bluetooth and via Android Auto.

Hm... Interesting Based on https://fixyourandroid.com/about/what-i ... oid_Kernel kernel 4.9.117 is from Android Pie (8) era.

Interesting thing is that on XDA I can't find Android 12 MTCx ROM only up to Android 10 and some Android 11 tries. Also 2GB RAM/32GB ROM points to older Devices SOC eg. I have 4GB/32GB PX5 device from 2016. interesting really.

Anyway if it works then enjoy. I cann't clam anything unless I have device in my hands, but I have seen fair share of fake info on Android Head Units. Generally if it works for you then enjoy.

I installed the app and run it. Also I clicked on "validate". It is green colored and seems to be valid.
Do you want the result displayed here or as PN?
Here is the first output:



However, the app says display is 9.2 inches and in reality it is 8.