I set four calibration points, but when I attempt to create the image map I get the orange box with the phrase: Problem with custom directory for 'mapItems'.
This object is in archive!
Problem with custom directory for 'mapItems'
Solved
I just installed Locus Pro on a fresh Samsung Galaxy Tab A (2016) running Android 7.0. I downloaded a local offline map, then I downloaded an image map. I set four calibration points, but when I attempt to create the image map I get the orange box with the phrase: Problem with custom directory for 'mapItems'. The mapItems directory is in the default location the installation placed it, which is under the Locus directory. I loaded a gpx file into the mapItems directory from within Locus (Map items + function), and it copied and loaded it just fine.
Files:
Screenshot_2018...
The same problem 
I just tried the same process on a Moto Z Play running Android 8.0.0 and it worked perfectly (other than having to deselect 'Optimize Map'). The directory structure of the two installs appears identical.
I just tried the same process on a Moto Z Play running Android 8.0.0 and it worked perfectly (other than having to deselect 'Optimize Map'). The directory structure of the two installs appears identical.
I have the same problem when calibrating an image map. All works fine up to the point where the map should be stored to the MapItems folder. I get the same error message.
This used to work flawlessly before, I have many calibrated maps in this folder. I never changed the folder.
I'm on Android 5.1.1.
I have the same problem when calibrating an image map. All works fine up to the point where the map should be stored to the MapItems folder. I get the same error message.
This used to work flawlessly before, I have many calibrated maps in this folder. I never changed the folder.
I'm on Android 5.1.1.
I confirm the problem. :-(
I confirm the problem. :-(
I confirm it too...
I confirm it too...
Good day Kevin, others,
sorry for this stupid issue. I was fixing a different problem and this is an unwanted side-effect.
How crucial is this feature for you? Because it is only a known serious problem in the latest version, I planned a new version after few weeks. In this case, I may create a special version for you here or just give here previous version 3.33.2? Let me know. Thank you for understanding.
Good day Kevin, others,
sorry for this stupid issue. I was fixing a different problem and this is an unwanted side-effect.
How crucial is this feature for you? Because it is only a known serious problem in the latest version, I planned a new version after few weeks. In this case, I may create a special version for you here or just give here previous version 3.33.2? Let me know. Thank you for understanding.
Happy to know it will be fixed in a couple weeks, and it's not something dumb I have done. Can't speak for others, but I can wait a few weeks.
Happy to know it will be fixed in a couple weeks, and it's not something dumb I have done. Can't speak for others, but I can wait a few weeks.
I installed version 3.32.2. Problem solved. I can wait.
I installed version 3.32.2. Problem solved. I can wait.
I have the same problem, usually I need this functionality once in a month.
But today is that time of the month :(.
How do I find the previous versions' apk?
I have the same problem, usually I need this functionality once in a month.
But today is that time of the month :(.
How do I find the previous versions' apk?
Oki guys, thanks all. I'll try to speed up update little bit, but good to know for me, that it is not too hot.
Thanks and have a nice day.
Oki guys, thanks all. I'll try to speed up update little bit, but good to know for me, that it is not too hot.
Thanks and have a nice day.
First time I (try to) use map calibration and ... just found this issue ! But I will wait as well. Very nice that I could spot the problem with this Help Desk forum !
First time I (try to) use map calibration and ... just found this issue ! But I will wait as well. Very nice that I could spot the problem with this Help Desk forum !
The problem is still present in current Beta...at least on my device.
The problem is still present in current Beta...at least on my device.
beta 3.34.1.2. Calibrator creates a map.
beta 3.34.1.2. Calibrator creates a map.
Look here, especially here.
Look here, especially here.
Is this still going to be fixed? I actually used it often. Thank you for any info.
Is this still going to be fixed? I actually used it often. Thank you for any info.
Yeah but I used to use this setting all the time and suddenly it doesn't work anymore? Note that the custom directory is "/sdcard1/Android/data/menion.android.locus.pro/MapItems" which should be writeable (at least by locus pro). Ok I see locus beta shouldn't be able to write it.
I think there really was a problem in pro, you fixed it in beta, but my test can not work because the directory is set to a pro-writable directory in locus beta (as I wrote before, I think I didn't use this feature in beta before)...I'll wait for next pro then...
Yeah but I used to use this setting all the time and suddenly it doesn't work anymore? Note that the custom directory is "/sdcard1/Android/data/menion.android.locus.pro/MapItems" which should be writeable (at least by locus pro). Ok I see locus beta shouldn't be able to write it.
I think there really was a problem in pro, you fixed it in beta, but my test can not work because the directory is set to a pro-writable directory in locus beta (as I wrote before, I think I didn't use this feature in beta before)...I'll wait for next pro then...
when do you expect the problemm will be solved ? thanks
when do you expect the problemm will be solved ? thanks
I've just download 3.35.0 and it's work fine now
thnaks for the job
I've just download 3.35.0 and it's work fine now
thnaks for the job
Also solved for me in 3.35.0
Also solved for me in 3.35.0
Replies have been locked on this page!