This object is in archive!
I can't see Locus directory when I mount my new phone with USB on Windows
Not a Problem
I've been using Locus Maps for some time on a LG tablet running Android 5.1 and have accumulated some offline vector maps. I just got a new Nexus 5x phone running Android 6, and have installed Locus Pro on it. I had in mind to transfer some of my maps from the old device to the new one, and to that end have mounted both using USB on my Windows PC.
However, although I can see the Locus directory on the old device, I can't see it on the new one. I can see some other directories in Internal Storage, like Android, Music, DCIM, etc., but not Locus. But I know it must be there, because I can see it via Settings->Storage & USB->Explore. So why can't I see it on Windows, as I can with my tablet? How can I copy these files?
The same problem 
Good day Mr. Candlin,
please check directly in Locus Map > Menu > About application > About applicaton > first tab. Here at bottom is a path, that Locus now use as root directory.
Also maybe this discussion may be helpful in this case: http://forum.locusmap.eu/index.php?topic=5162.0
Good day Mr. Candlin,
please check directly in Locus Map > Menu > About application > About applicaton > first tab. Here at bottom is a path, that Locus now use as root directory.
Also maybe this discussion may be helpful in this case: http://forum.locusmap.eu/index.php?topic=5162.0
Yes, it says /sdcard/Locus, and I believe /sdcard is what I have mounted in Windows albeit with another name of "internal storage". In any event, I can see all the other folders in /sdcard as on the phone, but not Locus. The tablet has the same location, but the directory is visible in that case.
Yes, it says /sdcard/Locus, and I believe /sdcard is what I have mounted in Windows albeit with another name of "internal storage". In any event, I can see all the other folders in /sdcard as on the phone, but not Locus. The tablet has the same location, but the directory is visible in that case.
Important question here is, if you really do not see only Locus directory or you do not see all directories in same directory as Locus. Because I see no real reason, why just one directory should be hidden.
I'm searching little bit and seems there is a lot more people with similar issue, like: http://android.stackexchange.com/questions/117469/android-folder-does-not-show-up-in-windows-7 or here http://android.stackexchange.com/a/83651/25899 and many more.
So I'm sorry, you have to deal with it with any alternative method (like AirDroid), because this is not problem directly connected to Locus itself. Thank you for understanding.
Important question here is, if you really do not see only Locus directory or you do not see all directories in same directory as Locus. Because I see no real reason, why just one directory should be hidden.
I'm searching little bit and seems there is a lot more people with similar issue, like: http://android.stackexchange.com/questions/117469/android-folder-does-not-show-up-in-windows-7 or here http://android.stackexchange.com/a/83651/25899 and many more.
So I'm sorry, you have to deal with it with any alternative method (like AirDroid), because this is not problem directly connected to Locus itself. Thank you for understanding.
No, it's just the Locus directory. However, those links you provided provided some insight. It seems it has to do with the MTP protocol having an outdated notion of the directory structure (even if you weren't using it at the time the directory was created). I had success with one of the suggestions to reboot the device, which seems to have the effect of triggering a rescan. Apparently, this can also be done programmatically, which may be worth considering when you create the directory.
No, it's just the Locus directory. However, those links you provided provided some insight. It seems it has to do with the MTP protocol having an outdated notion of the directory structure (even if you weren't using it at the time the directory was created). I had success with one of the suggestions to reboot the device, which seems to have the effect of triggering a rescan. Apparently, this can also be done programmatically, which may be worth considering when you create the directory.
Hi, you are correct. Here is already reported, and not yet fixed issue on Google support site: https://code.google.com/p/android/issues/detail?id=38282 .
Probably best answer how to solve it seems to be here: http://stackoverflow.com/a/14074407/836138 . Some rescan from code is partially possible anyway it looks that it still cause troubles on 5.x devices. Stupid ...
Anyway glad it's solved now for you.
Hi, you are correct. Here is already reported, and not yet fixed issue on Google support site: https://code.google.com/p/android/issues/detail?id=38282 .
Probably best answer how to solve it seems to be here: http://stackoverflow.com/a/14074407/836138 . Some rescan from code is partially possible anyway it looks that it still cause troubles on 5.x devices. Stupid ...
Anyway glad it's solved now for you.
Yes, it's solved for me now. Thank you for your attentive responses.
Yes, it's solved for me now. Thank you for your attentive responses.
Replies have been locked on this page!