Why do Play Counts &c. not sync?

[Red Maw]

Okay so I read this from the FAQ

What does bi-di synchronization do?
It causes tracks from defined directories on the device to be kept synchronized with MMW. Metadata and playcounts for any track on either sync list are synchronized regardless of whether this is enabled.

I sync my S3 over USB and it does not sync play counts or anything. Anyone have an idea as to why it is not working?

[Peke]

Unless you are using MMA on S3 MMW do not know how to sync things back

[Red Maw]

Sorry for the long delay, got busy and kinda gave up on MMA for a while.

I thought it was obvious but I am trying to use MMA on my phone (S3), which is why I posted the question here. I just tried again with the latest version of MMA from the Google playstore and it still does not sync 'Last Played' at the very least. Is there a minimum version of MMW required to make this work (I am still on 4.0.7.1511)?

[dtsig]

Yes I believe that you will want to be using the beta for better sync with MMA. I am getting great results on the sync with my g3, mma (last few betas) and mmw (last few betas)

[Lowlander]

You need MediaMonkey 4.1 (in beta) for syncing back played stats.

[Red Maw]

It's a shame that 4.1 beta is completely broken. Going to try and collect some debug data before I re-image my system but it's not looking good.

Edit: Can't reproduce the catastrophic failures now that debugview is running. Funny how these things work :\

[Lowlander]

I don't know how 4.1 is completely broken as it has been running without much issue (which is mostly syncing) for months here. Debug logs are essential in these cases.

[Red Maw]

Figured out it only occurs when it tries to sync my S3. Got a debug report, but like I said in the thread I just made in the MMW beta section I don't see any place to upload it here.

[rusty]

Hi Red Maw,

Please upload the log to mediafire (or a similar service), and submit it via a ticket on our eSupport system, or via a PM to me.

MMW 4.1 has been pretty stable for a couple of months now, and we're not able to replicate the problem, so hopefully the debug log will let us get to the bottom of the issue.

Thanks.

-Rusty