MediaMonkey forum

Hi,

After latest MMA update (updated on 28th March), MMA can no longer play any of tracks on my SD cards (which is encrypted!). All files are properly listed in Playlists/Tracks/Albums/Folder but once selected they don't have any metadata and are not playing (Just poping up Toast message saying Track is inaccessible). Even when trying to play song directly from file system, it is not working.

When trying to sync with MM (Version 4.1.15.1830) on Windows using USB, sync is failing with message "The media transfer process on Galaxy A5 appears to be frozen. If the issue doesn't resolve on its own within a few minutes, please disconnect the device and reboot it.".

All this songs can be played normally using other apps and were working fine on MMA before latests updates. Also, all other content of SD card can be normally accessed.


Problem is occuring on MMA version 1.3.0.685 running on Samsung Galaxy A5 with Android version 6.0.1. Log is sent through the app with ID U42VDR8RIB.

Looking into this. Thanks.

In the meantime have a look at http://www.ventismedia.com/mantis/view.php?id=13216 . It might give some useful hints.

-Rusty

I have a library of songs saved on my SD card which is where I have been playing songs from within MM up till now on my Samsung 7 edge. Over the weekend, I encrypted my SD card and now MM will not play any of the tracks. It can see all the tracks previously in the library. However, when you try to play a track, it just cycles through the library saying "Skipping inaccessible tracks.

I am running Android version 7.0 with security patch from 3/1/17. MM for Android version 1.3.0.0685.

Hi,
When you browse in MMA using Folder icon do you see the tracks and can play them?

Also do you see any Grayed storage?

Hi,

We've just posted a beta build (1.3.0.691) to the play store which fixes this issue. Can you please give it a try and confirm whether it solves the problem for you?

Thanks.

-Rusty

Hi,
With new build music is playing normally again!

Thanks!

Songs in playlists are still greyed out for me. Phone is encrypted although not sure if that means the SD too. When playing from folder it does work.

Hi Dav3D,

This sounds like a different issue. Can you elaborate a bit?
- Does playback work from Tracks or Artists ?
- Re. the phone being encrypted, are you refering to Settings > Security > Encrypt phone ? Are you saying that the tracks that were synced _prior_ to the phone being encrypted no longer play? Or are you saying that when you attempt to sync the already encrypted phone that synced tracks fail to play?
- Are you using adopted storage for the SD card ?
- What phone / android version
- What version of MMA

Assuming the issue is related to tracks having been synced prior to phone encryption (or prior to storage adoption), a workaround would be to do a clean install and resync.

-Rusty

Hi Rusty, here some answers:

- Playback only works from Folder. Anything else is gteyed out.
- Yes, phone is encrypted. However it has been since day one, and MMA used to work.
- The SD is adopted, when I did it is when issues started.
- Moto G4 Plus with Android 7.0.
- MMA 1.3.0.0695. Although I had the beta until a couple of days ago when I uninstalled and when back to a clean installation to check if that would work.
Finally, not sure if the workaround would work. As mentioned above, I did a clesn install few days ago andI do not sync with MMA but iSyncr.

Hi Dav3d,

- The SD is adopted, when I did it is when issues started.

That's the trigger. Adopted storage should work, but not if it occurs on an existing install. In my testing, doing a clean install solved this--but keep in mind that a clean install involved: uninstalling MMA _and_ deleting the /MediaMonkey directory (from internal memory and the SD card).

I did a clesn install few days ago andI do not sync with MMA but iSyncr.

This will introduce a variety of other problems (missing metadata, failed playlist updates, failed play history synchronization, etc.).

-Rusty

Rusty, you were right. After deleting all MMAA folders and reinstalling, it now works!
Thanks a lot.

I'm also having this problem, but in my case, I switched to adopted (encrypted) SD storage last week on my new tablet, and only afterward did I install MMA Pro (v1.3.1.0720). I then did a USB sync of my music, audiobook and video collection using MMW 4.1.17.1840. Most of the files seemed to transfer over successfully, though with the larger movies, I did get the message "The media transfer process on BNTV450 appears to be frozen. If the issue doesn't resolve on its own within a few minutes, please disconnect the device and reboot it.". Note that I got these messages when connected to two different clients: a Nook 7" tablet and a Galaxy S3. When this happened, disconnecting and rebooting did not help. I eventually had to use wi-fi sync for those large files.

But once all sync'ing was complete, I then found I could not play most of the music I tried. For example, none of the 19 tracks of my ABBA album could be played. I would just get the Toast message "Skipping inaccessible tracks". But a few other tracks I tried in my collection did work. So it's not a universal problem. The videos all work also, and some of these were sync'd with USB and some with WiFi.

Since all the sync'ing was done after a first fresh install of MMA, which in turn was after adopting the SD storage, this is apparently not the case that is discussed in this thread where you can't adopt storage with an existing install.

So after receiving the Toast messages, I created and sent you a debug log: FE6CQAZU44

I will wait to reinstall MMA in case you need to me try anything or provide more information about the current installation.

Can you help?

Thanks,
Dennis

Just checking to see if you received my debug log on this problem...

Thanks,
Dennis

Hi Dennis,
I have checked your log. MMA skips tracks in wma format, which is not supported on android devices. To play these tracks in MMA use sync from MMW with auto conversion to mp3.

Thanks. I've since upgraded to an s7 running Android 7, which apparently does support wma. So I'm good again.

Not sure why the wma's were not converted that one time since I'd never had this problem before.

Best,
Dennis