why MPE scans all memory and all sdcard in multisync?

[maratsh]

why the program scans all memory and all sdcard if in multi-synchronization settings I specified to scan only a few folders, and only those folders program should synchronize?

[FJ]

Maybe you enabled "Refresh all file lists" in multisync, you can disable this option, its not needed

[sergeirichard]

May I ask, what does "Refresh file lists" actually do, and is it worth doing this on a regular basis? I find it adds about a minute to a Multi-sync.

As I am syncing the whole of the phone memory anyway ("External Storage", not system storage or memory card), is it redundant?

[FJ]

This feature maked sense on old SonyEricsson phones. With these phones it took alot of time to browse throught the folders, with this feature the filelists were loaded in one swap and then you could browse in the filebrowser of MPE much faster. In Android there is no need to use it

[sergeirichard]

That's good to know, thank you!

While I have your attention... I have a Galaxy Note which I use to draw and write, in a number of different apps. So I create a lot of files that I want to back up very regularly, and came to the conclusion that rather than set up individual File-sync jobs for every app I do or will ever use for creative work, it is simpler to set up one for the entire storage part of the phone's memory.

It works very well; once the initial backup is done an incremental sync only takes a couple of minutes. There's just one irritation: A handful of errors caused by filepaths that break the length limit in Windows. I don't think anything important fails to sync; they seem to break the limit because the files themselves have enormous names, certainly not created by humans. But I don't want to have to check every time, and errors are always worrying.

The best thing I've been able to do is move the database to the root of the drive as this shortens filepaths considerably. But some errors still occur. Is there a better workaround?

[FJ]

I know about this bad issue. MyPhoneExplorer can read/write maximal paths to 256 characters. The issue relies on a old Windows API which is used by MPE and its hard to change this API. But i am aware of it

[sergeirichard]

Thanks for the prompt reply. I am in awe of your software, and have raved about it on my blog - here and here. Android phone makers - Samsung in particular - owe you a great debt.

Could I suggest one short-term solution: An option to skip files that break the filepath limit. It doesn't actually fix anything, but at least one could avoid getting the error messages.

[FJ]

this would be even more confusing the users. by the way: i will implement a autostart option

[sergeirichard]

I never imagined the developer would actually be reading that...

[sergeirichard]

A postscript:

On examining more carefully, I realised that all the enormous filenames seemed to be created by a single app: Google Currents, a magazine-style newsreader. It's not something I'll miss, and since removing it (and reporting the bug) things have been going smoothly.