trooperj3 wrote:I Have installed V1.10.4 on my Samsung S6 and I'm very happy as it seems to work fine. I am now trying to install V1.10.6 on my Samsung Galaxy 10.5 but am having difficulty creating directories for the maps, tracks, routes and waypoints. I thought it would be a similar process to creating the directories on my S6 where I connected my S6 to my laptop and created the necessary directories via my laptop.
Unfortunately this is not proving to be the case with the Samsung Tablet. Although I can create the directories on the tablets SD card via my laptop they are not displayed when viewed by the Tablet to use those folders to store the maps etc in.
Can anyone advise me how to either create the necessary new directories directly on my Samsung (I couldn't see any option to so when asked to create directories when setting up MM Tracker initially) or to do so via my laptop where they are actually displayed on the tablet.
Thanks for your help.
Regards
trooperj3
Trooperj3
There are issues with getting mmtracker to hold onto the directories you have set up. This seems to be a problem with the way the app accesses file structures. The app author uses one method to set the main 'maps' folder and another method for other folders holding tracks, waypoints, etc. The maps folder gives access to the full internal and removable memory but the access to memory when selecting the other 3 directories is limited to internal memory. Why? God knows.
You should create a Maps folder (or any name you prefer) on the removable card (or internal if you wish) and then point the program to this folder when selecting the 'maps' folder. For the other directories you should try to point to a folder in internal memory, any will do. The newest version of the app has a kitkat workaround (kitkat = android 4.4) but in practice it would be better to try to use internal memory if you have any issues with the external sd-card.
I found that sometimes the app forgets what you chose previously, which is very frustrating as it asks you to set these folder paths every time you run the app. This is an issue with later versions of Android (4.2 upward I think). You should try different folders for these paths until you get one that it likes and so stop the continuous 'set paths' request at startup.
This app was originally written for Android 2.x so 4.x devices might have problems.