This object is in archive!
Export to local path not possible
Solved
Hi,
I never used it but I just mentioned that it's not possible to export a folder with waypoints to the local storage. There is now folder structure visible. The import dialog shows the local storage.
Wolfgang
The same problem 
Good day Wolfgang,
unfortunately I do not perfectly understand where is a problem. May you attach me here some screenshot or better step-by-step instructions I may follow to simulate an export problem? Thank you.
Good day Wolfgang,
unfortunately I do not perfectly understand where is a problem. May you attach me here some screenshot or better step-by-step instructions I may follow to simulate an export problem? Thank you.
When I do an import of a folder I'm able to choose a path. But when I choose export I have a blank path with a pen at the right side. When I click on this pen the normal file dialog opens but the local data store is empty. I can't choose any local resource.
Hope these two screenshots show the difference. If not I'll try to make a screenshot of every step.
When I do an import of a folder I'm able to choose a path. But when I choose export I have a blank path with a pen at the right side. When I click on this pen the normal file dialog opens but the local data store is empty. I can't choose any local resource.
Hope these two screenshots show the difference. If not I'll try to make a screenshot of every step.
Good day Wolfgang,
really interesting. May you please try to tap on SD card icon (that should display root of device) or more easy tap on top three dot menu and choose "Base directory" that display Locus Map root directory or "Storages" that should display list of available memories in device. This does not solve reason why this happen, but should help to solve it. Hope this helps!
If you find any steps I may follow to simulate this problem, please write me, thank you!
Good day Wolfgang,
really interesting. May you please try to tap on SD card icon (that should display root of device) or more easy tap on top three dot menu and choose "Base directory" that display Locus Map root directory or "Storages" that should display list of available memories in device. This does not solve reason why this happen, but should help to solve it. Hope this helps!
If you find any steps I may follow to simulate this problem, please write me, thank you!
Hi Menion,
maybe it's an Android 7.x problem both of my devices have it.
The SD card icon did not help, that's what I already tried. But the three dots menu is a god choice. I didn't mention it yet here. Here both options work Storages and Base dir. But when I then navigate higher then "sdcard" it's once again the same problem.
Hi Menion,
maybe it's an Android 7.x problem both of my devices have it.
The SD card icon did not help, that's what I already tried. But the three dots menu is a god choice. I didn't mention it yet here. Here both options work Storages and Base dir. But when I then navigate higher then "sdcard" it's once again the same problem.
Good day Wolfgang,
Unfortunately I'm unable to simulate this problem.
If you find a while, you may try to download this Locus Map Free Beta test version, simulate problem and close app. In Locus/logs directory should be some text logs, so send me them, thanks!
Good day Wolfgang,
Unfortunately I'm unable to simulate this problem.
If you find a while, you may try to download this Locus Map Free Beta test version, simulate problem and close app. In Locus/logs directory should be some text logs, so send me them, thanks!
Hi Menion,
sorry for my late replay I was on tour the last days....
I have on all my three Android 7 devices the same problem.
Attached the log file.
If you need more info/ tests let me know!
Thanks Wolfgang
Hi Menion,
sorry for my late replay I was on tour the last days....
I have on all my three Android 7 devices the same problem.
Attached the log file.
If you need more info/ tests let me know!
Thanks Wolfgang
Good day Wolfgang,
thank you for your logs. Based on reports of some other users, I believe this problem is already fixed.
We just published new 3.25.3 version on Google Play so please give it a try.
Thank you and sorry for a complications.
Good day Wolfgang,
thank you for your logs. Based on reports of some other users, I believe this problem is already fixed.
We just published new 3.25.3 version on Google Play so please give it a try.
Thank you and sorry for a complications.
Hi Menion,
sorry for my wrong answer yesterday I thought it's another thread :( So the log file is wrong.
I updated to the latest version today. It's better now. The latest path is saved but it's still possible to navigate higher than the top/root path.
It's no problem for me because usually I don't need this function and I know now the workaround with the three dot menu if it happens.
Thanks Wolfgang
Hi Menion,
sorry for my wrong answer yesterday I thought it's another thread :( So the log file is wrong.
I updated to the latest version today. It's better now. The latest path is saved but it's still possible to navigate higher than the top/root path.
It's no problem for me because usually I don't need this function and I know now the workaround with the three dot menu if it happens.
Thanks Wolfgang
Hello,
funny, I also thought that this topic is about problems with attachment and completely forget on our unsolved issue with filepath. As I see, in log is anyway what I expected to contains. Anyway as you wrote, there exists a workaround and it also looks for me like some device-specific problem.
Have a nice evening,
Menion
Hello,
funny, I also thought that this topic is about problems with attachment and completely forget on our unsolved issue with filepath. As I see, in log is anyway what I expected to contains. Anyway as you wrote, there exists a workaround and it also looks for me like some device-specific problem.
Have a nice evening,
Menion
Replies have been locked on this page!