Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - hgmichna

#1
Troubles & Questions / [SOLVED] mapItems subfolders
September 10, 2022, 14:49:58
I used to have subfolders in Locus/mapItems on my previous phone, running Android 11. Locus Maps handled these without problems.

Then I got a new phone, a Google Pixel 6, running Android 12. Knowing about the new rules, I copied the content of Locus/mapItems into Android/data/menion.android.locus/files/Locus/mapItems .

Locus Maps could use items in this internal mapItems folder, and it saw and showed the subfolders as well. But when trying to enter any subfolder to make items in it visible, none were there. I could still see all the item files in a file manager (I use X-plore), so the files were actually there, but Locus Maps apparently did not see or show them.

Then I received the update to Android 13. Since then X-plore also no longer sees anything inside Android/data/ , so I am now unable to even delete them.

I have since uninstalled Locus Maps entirely to clean up the mess. I could import most of the data (tedious work), but I still have no way to have subfolders in mapItems. Without subfolders, mapItems are difficult to handle when there are many.

What's the current situation with Android 13? How about allowing to change mapItems to an external folder, like Locus/mapItems, akin to some other folders that can be moved to an openly visible place?

[SOLVED]

Only some days after writing the above I learned that there is still one simple way to read and write in Android/data, an MTP connection to a computer. I connected my new phone via USB to a PC running Windows 11, allowed data moving, and could easily copy folders into Android/data/menion.android.locus/files/Locus/mapItems , using the computer's keyboard and mouse.

Locus Maps then handled these folders and their content, GPX files, just as easily as on my previous phone, so no problem any more.

Why it didn't work in the beginning, when the subfolders should already have been in place, remains a mystery. Anyway, as long as MTP does the trick, I'm happy.
#2
[Edit: Found the cause, problem mostly solved. See below.]

I got a new phone, a Pixel 6, still running Android 12. On that I get these errors when a freshly recorded track is auto-exported.

  • setTitleColor, code: 0
  • Error: UsbInterface, code: 12561

I can then manually export the track without any problem, which is my current workaround.

But perhaps somebody wants to look into this. Is there anything I can do to help pinpoint the defect?

Everything else seems to work fine, except that I have lost all maps over the phone change. Not too bad, I can re-download them. Thanks for the good work! I like Locus Maps.

Hans

Edit: Apparently I found the cause. There are two different places where the auto-export path can be entered. They differed in my new installation. The location in the settings was still sdcard/Locus/export, while in the manual export I had already entered storage/emulated/0/Locus/export. Therefore the latter worked with manual export, while the auto-export attempted to use the old path. I did not get the idea that the path setting exists in two different places.

After changing to the new path, auto-export worked fine in the first test.

This solves the problem for me, but I think, Locus Maps should still be changed to show a more meaningful error message when the export path does not exist. Also I would recommend to avoid the two different path settings. I think, auto-export should always use the same path that is set for export. I think, to have a different setting for manual and auto export is practically never needed, but has a high potential for confusion.
#3
Troubles & Questions / Low-power tracking
November 16, 2015, 11:34:54
What is the best way to record a track while riding in an airliner?

The main problem is power consumption if the GPS is kept active all the time. Since airliners fly absolutely straight at constant altitude and with mostly constant speed, there is harly any need to have more track points than one every two minutes. Perhaps even one every five minutes would suffice.

I think the nicest solution would be to have an automatic adjustment of the track point frequency, depending on the regularity or irregularity of the movement, but I think Locus currently does not have this.

Perhaps it could be a possible improvement to add something like automatic low-power tracking. My personal wish would be that the phone checked its movement, using as little power as possible. When it detects movement, it could then adjust its track point frequency accordingly. For example, if I keep moving in a straight line at constant speed, the track point frequency could be very low.
#4
This has been reported before at least once, in 2011. I cannot save the track I just recorded and get the error message, "Unknown problem with track saving!"

Locus/data contains a number of folders, 5 files whose names begin with a period, and these two files:

  • databasefavorites.sqll-journal
  • dbtracks.sqll-journal
There are no *.sqll files in Locus/data. I have deleted the two .sqll-journal files, but still get the same error.

I normally have automatic export switched on, but switching it off does not help. My impression is that Locus is unable to write to a database.

I cannot exit Locus, unless I delete the current track, which I do not want to do. I will keep trying workarounds and hope for a good idea before Android kills the still running Locus.
#5
When the phone is connected to a computer via USB, using MTP, the exported files are not visible before the phone is rebooted. Solution from

https://code.google.com/p/android/issues/detail?id=38282

When writing files that should be accessible via USB MTP by the user:

For each file:

sendBroadcast(new Intent(Intent.ACTION_MEDIA_SCANNER_SCAN_FILE, Uri.fromFile(file)));

Otherwise the files remain invisible.

Current workarounds are to reboot the phone or to rename the export folder using ES File Manager and, if that is not enough, disconnecting and reconnecting the phone. There may be other workarounds.