0019122: Required changes on MM5 side (USB synchronization with Android 11) - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0019122	MMW 5	Sync	public	2022-05-27 10:17	2024-07-26 00:29

Reporter	martin	Assigned To
Priority	urgent	Severity	major	Reproducibility	have not tried
Status	closed	Resolution	fixed
Platform	Android	OS	-	OS Version	11
Product Version	5.0
Target Version	5.0.4	Fixed in Version	5.0.4

Summary	0019122: Required changes on MM5 side (USB synchronization with Android 11)
Description	Check storageInfo.xml in Android\data\com.ventismedia.android.mediamonkey\files\files if storage is <type>read-write limited</type> then check whether there is <folder>MediaMonkey</folder> if yes MMA has access and we can sync via MediaMonkey folder else use AppSpecific (Android\data\com.ventismedia.android.mediamonkey\files\files) for sync instead and do not create MediaMonkey folder
Additional Information	Example: <storages version="1.4" storageGuid="40722583-49d3-3433-b211-d937eca572a7.0.8d13e570-60f2-47d8-a7b5-0e2a71706993"> <storage> <title>Internal storage</title> <path>/storage/emulated/0</path> <prefix>primary:</prefix> <guid>40722583-49d3-3433-b211-d937eca572a7.0.8d13e570-60f2-47d8-a7b5-0e2a71706993</guid> <info>Android/data/com.ventismedia.android.mediamonkey/files/files/storageInfo.xml</info> <type>read-write limited</type> <current>1</current> <appFolder>/Android/data/com.ventismedia.android.mediamonkey/files</appFolder> <folder>MediaMonkey</folder> <folder>Android/data/com.ventismedia.android.mediamonkey/files</folder> </storage> </storages>
Tags	No tags attached.

Fixed in build	2650

Ludek 2022-05-31 12:38 developer ~0068348	Fixed in 5.0.4.2650

martin 2022-09-01 14:51 developer ~0069140	Tested with Android 11 and MM 5.0.4.2661. MediaMonkey folder was created by MM5 during USB sync although MMA does not have permission. I tried sync a video file via sendTo>Galaxy Tab(sync) and the file should be sent to AppSpec folder/Video, but was created on the root of storage where MMA does not have permission.

Ludek 2022-09-02 10:40 developer ~0069151	Please generate debug log for me with DbgView started prior to MM5 start.

Ludek 2022-09-02 15:16 developer ~0069155 Last edited: 2022-09-02 15:22	As discussed/solved offline with Martin: 1) he can no longer replicate the issue, i.e. it was one time issue related to MTP inaccessibility of Android\data\com.ventismedia.android.mediamonkey\files\files\storageInfo.xml folder where MM5 taken cached data from \MediaMonkey\files\storageInfo.xml.mmw instead 2) I can't replicate too, works fine with son's Samsung A32 phone powered by Android 12 and MMA 2.0.1024 3) MediaMonkey folder is still created by MM5, but it is just for MM5 purposes a) it needs to preserve copy of original storageInfo.xml there as storageInfo.xml.mmw so that the profile isn't lost after MMA inistall/re-install, it would result in duplicate profile creation , see 0013119 for details b) it stores own /meta_files/ there including metadata to sync between more MM5 instances (without a need to have MMA installed), i.e. is related to cloud sync and #14105 and #14521

martin 2022-09-03 12:46 developer ~0069157	Re 3) a) On uninstallation, MMA users can check "Keep Xy MB of app data" and then "storeageInfo.xml" persists also when MMA is uninstalled(since Android 10). So a duplicate profile is not created in this case. Also for "read-write-limited" storage (primary storage since Android 11) storageInfo.xml.mmw is used only in one case when a user grants permission to MediaMonkey folder. If the permission is not granted, then a duplicate profile is created even though a backup exists in MediaMonkey folder. However, for case 3)b) it still makes sense to have MediaMonkey folder.

peke 2024-07-26 00:29 developer ~0076438	Verified 3040 With Android 14 and had no issues, also reviewed/checked user reports and had not found such related to this bug. Closing as Fixed.