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

Messages - DougPeterson

#1
I have attached a test GSAK database which I tested on both phones. As with my other databases, it works on my old phone but not on my new phone. I also double checked that I had identical configurations for the add-on. The distance I had set was 6 km. I checked with 1 km as well as setting logs to zero. The results were the same.

The caches are centered around N 50° 05.250 E 014° 25.283. A few are out a greater distance, up to 70 km.
#2
I will create a small test GSAK database. I will test it on my old phone and then on my new phone. I will also double check my configuration for the add-on in both phones.
#3
I am just setting up a new phone. When I run the GSAK Add On within Locus Pro I can see the geocache count going up. But when it finishes, the screen remains with a dim background and a blank, white rectangle in the middle. No geocaches are displayed on the map.

My new phone is a OnePlus 7T (Android 11) with Locus Pro 3.54.3.
My old phone where it still works is a OnePlus One (Android 6) with Locus Pro 3.45.1.
In both cases the GSAK Database for Locus is 2.2.3.

Given the amount of geocaching I do and that I manage all of that through GSAK on my PC, the idea of having to do GPX exports and imports across the numerous databases I have is an unpleasant thought.

I was going to try to test the Geoget Add On but it won't start properly so I can't set a database location to be able to test.
#4
It looks like a copy of the providers.xml was created as providers_backup.xml back in 2015. Something must have changed that this file was being processed. I removed the file and the annoyance has gone away. Thanks.
#5
When I start Locus Maps Pro I receive a series of messages in an orange box at the bottom of the screen. This will happen each time I open Locus, as an example:

addMap(10306), duplicate provider, already exist, 10306, ERSI World, Topo

It takes about a minute and a half to cycle through the various map messages. There does not seem to be any issues so it is more of an annoyance.

This began happening with 3.45.1. Having said that the last update I had was a year prior with 3.37.2 as my Oneplus One (Android 6.0.1) was apparently no longer valid for updating, at least until 3.45.1. I was thinking it might get fixed with another update but that did not happen with 3.46.2.
#6
I have tried clearing cache and restarting. Unfortunately that has not resolved the issue. It appears I will no longer be able to update my most useful app.
#7
I have a OnePlus One phone with Android 6.0.1. From the release notes for 3.38.0 it appears 5.0 is now the minimum requirement.
chg: minimum API changed to API21+ (Android 5.0+)

However, my phone no longer shows 3.38 as available to install on my phone, whether that is through the Play Store on my phone or on-line. I cannot install it. Are there some other compatibility issues now?

Thank you,

Doug Peterson
#8
That was indeed the problem. I must have unwittingly checked it. That is a much better explanation than it simply stopped working.
#9
When I was out geocaching last weekend, the log times stopped being the actual time and were being recorded as 12:00 PM. The first few caches had the correct time saved before this behavior started occurring.

The time when the log is being saved is accurate. If I go back in to edit the time of the log it will still show as 12:00 PM after trying to save the corrected time. To the best of my knowledge, nothing below was updated while I was out geocaching.

Locus Map 3.37.1
Geocaching4Locus 2.2.6
Locus - Addon FieldNotes 1.4.5.2

OnePlus One
Android 6.0.1
Kernel 3.4.110
Cyanogen OS version 13.1.2
#10
If I try to run GSAK Database for Locus in area where there will be no caches to import Locus will  stop. I am not sure which version of Locus this started with as it is not a typical situation. It has been present for a number of versions as I test it with each version but have only now reported it.

GSAK Database for Locus 2.2.3
Locus Map 3.37.1

OnePlus One
Android 6.0.1
Kernel 3.4.110
Cyanogen OS version 13.1.2
#11
I installed 3.30.1. The problem was fixed. Thanks for the quick attention to it.
#12
I upgraded to Locus Pro 3.30 this week. I was out hiking and geocaching today. It appears that the distance for Guide On is rounded to a whole number and no longer a decimal. I could not find a setting that would change this back. Is there?

The change makes the distance much less useful. 0.5 miles is much different than 1.4 miles, particularly when hiking, but it is all 1 mile between the two. 0 Miles away when really 0.4 miles away is not very useful.

Thank you,

Doug Peterson
#13
I tried restoring the most recent backup.  I then tried exporting one of the points folders.  No points were exported and the export file was only a few hundred bytes in size.  While Locus was running I checked the database directory.  There was no waypoints database there.

I then tried going back in time through the automated backups.  Eventually I found a backup where the waypoints database worked.  I think a crash from earlier in the week may have partially corrupted the waypoints database.  Visible points show up on the map and can be edited from the map.  All the folders were on the Data screen with point counts but were not usable there.  That is where the crashes occurred.

I have not lost too much data.  I record points for later entry in OSM and was anxious about losing data I had not entered, particularly from vacation trips earlier this year.  Fortunately I automatically export track data so I could just reimport that.  I have changed the automated backup settings now to be daily and for a longer period.
#14
I am experiencing a number of crashes with Locus Pro 3.2.3 on a Samsung Galaxy S3 running Android 4.4.2.  The crashes seem to occur when I am trying to access a point or a points folder and only started occurring in the past few days.  It looks like I installed 3.2.3 on September 8.

After the crash all the points folders have been lost.  There is a small 36 KB waypoints.db file with only empty Favorites and My Points folders showing up under Points Data.  The original file appears to have been renamed waypoints.db.back.  Simply trying to rename the original file does not help any as Locus crashes again.  I have tried restoring a prior waypoints file from a backup but Locus still crashes.  The Tracks database appears to be unaffected by this. 

I have also rebooted the phone but the same behavior is occurring.  I could try reinstalling a prior version of Locus as well as trying to restore an even older waypoints file if that would help.
#15
The 2.11.1 update has fixed the problem.  Thank you for the quick fix.