Something wrong with playlist syncing

[TeutonJon78]

Well, apparently, it's not quite working.

On the Android 12 device it worked correctly. On the Android 15 device it still only synced a subset of the playlists that were selected.

Samsung Android 15 seems to be the common factor so far for the two of us having issues.

[ACardAttack]

Well, apparently, it's not quite working.

On the Android 12 device it worked correctly. On the Android 15 device it still only synced a subset of the playlists that were selected.

Samsung Android 15 seems to be the common factor so far for the two of us having issues.

Yep, can get it to work on Android 10 but not 15.  I end up just syncing to my old phone, and then uploading those playlists to the cloud and download them on my current phone

It wouldnt be so bad if the playlists that arent synced stayed on device if already there, but they seem to disappear/get deleted

[BoringName]

I was going to suggest maybe Musicbee could change to using ADB copying instead of MTP.

There is an app here that implements it - Link

The source code is there and I can't see any limitations listed for using it.

But I just noticed USB debugging needs to be enabled on the phone for ADB to work so maybe not that practical.

[ACardAttack]

But I just noticed USB debugging needs to be enabled on the phone for ADB to work so maybe not that practical.

I imagine most people who are using musicbee to wirelessly sync and keep music library would be able to turn on debugging quite easily

[TeutonJon78]

But I just noticed USB debugging needs to be enabled on the phone for ADB to work so maybe not that practical.

I imagine most people who are using musicbee to wirelessly sync and keep music library would be able to turn on debugging quite easily

Giving any 3rd party code ADB access isn't really a great idea though.

What is most likely the best option would be using something like an FTP SFTP/SSH server on the phone (of which there are a few) and then using something on Windows to map that as a drive letter (of which there are a few). Then you could just easily sync as a Virtual Device. And since it's using basic Windows FS stuff, it avoids all the stupid MTP problems, and it also avoids some of the wifi sync issues by reversing the direction. But you would lose play count/rating merging, if that matters to anyone.

[TeutonJon78]

OK, now that Samsung has released it's first update to the S25 phones with A15 I thought I'd try again. I also used the latest 3.6.9189 patch.

And it synced all the playlists correctly now! So, like we suspected, it seems it was more of a Samsung bug than an issue with MB after Steven made the other fixes.

[psychoadept]

I apologize it's taken me so long to get back to this. I can report that with MusicBee 3.6.9202 P, on three consecutive syncs I got 17/17 playlists, 16/17 playlists, and 1/17 playlists. It looks like I'll have to try one of the workarounds suggested.

[sulecen]

Hey there,

I was having a very similar problem with Musicbee saying it had synced all my playlists to my DAP running android, and when I looked in the file explorer, multiple playlists were not there. I have some playlists that are several thousand songs, and a couple of those were not carrying over, and then randomly some of the smaller ones. Also another weird behavior was that the syncing process would slow to a crawl once it got to syncing the actual playlist files themselves once all the music had been copied over.

I changed one setting and suddenly the issue has been fixed so I want to share it. I changed the playlists being synced to the DAP from .m3u files to .m3u8 files, and they suddenly work fine every time and they get moved over almost instantly. Not sure if this might help but I wanted to share since this thread is what started me playing with setting trying to figure out what was going on.

[heidl]

Hey there,

I was having a very similar problem with Musicbee saying it had synced all my playlists to my DAP running android, and when I looked in the file explorer, multiple playlists were not there. I have some playlists that are several thousand songs, and a couple of those were not carrying over, and then randomly some of the smaller ones. Also another weird behavior was that the syncing process would slow to a crawl once it got to syncing the actual playlist files themselves once all the music had been copied over.

I changed one setting and suddenly the issue has been fixed so I want to share it. I changed the playlists being synced to the DAP from .m3u files to .m3u8 files, and they suddenly work fine every time and they get moved over almost instantly. Not sure if this might help but I wanted to share since this thread is what started me playing with setting trying to figure out what was going on.

I just got a brand new Samsung Galaxy S25 and had the same sync problems as everyone here. Syncing music files was lightning fast and stable as you would expect, but as soon as it began copying playlist files, it was a slog. Even with the latest patched version 3.6.9245. But when I changed the playlist format from M3U to M3U8 it worked like a charm. It took merely seconds and all 60 playlists were copied successfully  

[heidl]

I must have laughed too soon, because the next sync again resulted in a painfully slow sync process for the playlists, as well as numerous error messages.

The requested value cannot be determined. (Exception for HRESULT: 0x802A0006)
The shutdown function has already been called for this object or for the object that is the owner of this object. (Exception of HRESULT: 0x802A0002)

   Has anyone had similar errors and been able to fix them permanently?