View Issue Details

IDProjectCategoryView StatusLast Update
0010264MMASynchronizationpublic2013-08-30 19:10
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.1 
Target Version1.0.4Fixed in Version1.0.4 
Summary0010264: Storage location is often misidentified
DescriptionI have 2 devices with multiple storage locations and:
1) MMA always only lists a single storage location as a possible destination
2) MMA consistently misidentifies the storage. e.g.
-On an Xperia Pro with music stored on an external SD card, the location is identified as 'MK 16a Internal Storage'
-On a Samsung Galaxy Captivate with music stored internally to the device, the location is identified as 'Samsung SGH-I896 - External SD card'
TagsNo tags attached.
Fixed in build146

Activities

marek

2012-12-20 13:05

developer   ~0034055

Recognition of storages depends on parsing of system files that contains information about storages. Could you please send me these files from problematic devices?

I need these two files:
/system/etc/vold.fstab
/proc/mounts

rusty

2013-06-20 17:46

administrator   ~0036586

Tested 143, and the situation is better, though still a bit off:

-Xperia Pro now correctly identifies the External storage location (perhaps because it's been since upgraded to ICS), BUT it no longer displays the internal storage location within MMA (not such a big deal, because there's not much internal storage available).
-Samsung Galaxy Captivate shows:
 . SGH-I896 External SD Card 1 (for external memory)
 . SGH-I896 External SD Card 2 (for internal memory), instead of correctly identifying it as internal memory

Requested files are uploaded to the ftp server.

marek

2013-06-26 10:43

developer   ~0036662

Fixed in build 146

Well the issue was only for gingerbread androids. Devices with removable storage was misidentified as devices with internal storage and vice versa.

We should clarify what is external storage and what is internal storage. Samsung Captivate is a device that have both. Internal storage is external storage that isn't removable and is build-in. But still it has a path that looks like external storage(e.g. /mnt/sdcard ) and it behaves like external storage. Captivate's sd card is the "real" external storage because it is removable. It has similar path with /mnt/ or /storage/ (e.g. /mnt/sdcard/external_sd for Captivate).

So Captivate should have Internal Storage and External Storage. I assume that you have GB on this device.

But Xperia doesn't have any internal storage. It is a removable external storage (microsd card slot).

Each device has some system internal memory that can be used only by system, for storing apps, etc. We cannot use it as storage for media and it isn't generally accessible...it is something different.

peke

2013-06-28 19:56

developer   ~0036675

No regressions on my ICS phones Left resolved for Rusty to confirm

rusty

2013-06-28 20:06

administrator   ~0036676

Last edited: 2013-06-28 22:05

Tested build 146 with SGH-I896 running GB and the cards are still both identified as external in MMA (even though they're correctly identified in MMW) even when I navigate via the Sync Server. Do I have to do a clean uninstall?

Note also: with build 146 MMA automatically enables synchronization to internal SD card (that was labelled as external)

marek

2013-07-01 11:49

developer   ~0036697

Unfortunately yes, the names are stored in xml files. So please uninstall and delete all StorageInfo.xml files (from both storages).

But still it might be incorrectly detected. If your issues persist, please download modified apk from FTP (/MMA/bugs/bug10264/MediaMonkey_1.0.4.0146x.apk) and run app. Send logs right after startup. Thanks

rusty

2013-07-26 03:59

administrator   ~0037005

I retested with 151 and found that MMA does identify the different locations differently, but still incorrectly:
Internal: MMA:External SD Card ESexplorer: sdcard
External: MMA:Internal Storage ESexplorer: external_sd

Interestingly, I'd performed the first sync operation over usb, and MMW identifies both locations identically as Samsung Captivate.

Should I generate a log with 152? or go back to 146?

marek

2013-07-26 12:19

developer   ~0037010

Please use build 146x. There are some specific logs that will be helpful. Thanks

rusty

2013-08-02 19:30

administrator   ~0037066

Uploaded debug log 943PDB3EKO

marek

2013-08-26 09:34

developer   ~0037264

I didn't find the log. Upload probably failed. But backup of log is stored as /MediaMonkey/logs/log-943PDB3EKO.zip on device. Please attach it here. Thanks.

rusty

2013-08-26 17:42

administrator   ~0037275

posted log to ftp.

marek

2013-08-27 10:19

developer   ~0037295

Are you sure that storages are incorrectly recognized ?

I see in log:
Storages:
 Name:Internal Storage,Root:/mnt/sdcard,Id:0,
 Name:External SD Card,Root:/mnt/sdcard/external_sd,Id:1

So it looks that it recognize it correctly. Also vold file you sent me has the same info:

# internal sdcard
{
    ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
    discard = disable
    asec = disable
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0

# externel sdcard
{
    ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
    asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2

rusty

2013-08-30 19:10

administrator   ~0037398

Seems to be working correctly in 162. I'm not sure if it's due to test error previously, or to some other related fix, but it's working as expected.

rusty

2013-08-30 19:10

administrator   ~0037399

Verified 162.