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.

Messages - DougPeterson

Pages: [1] 2 3
Troubles & Questions / Re: Phone Compatibility with 3.38+
« on: June 12, 2019, 12:05:46 »
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.

Troubles & Questions / Phone Compatibility with 3.38+
« on: June 05, 2019, 01:17:12 »
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

Troubles & Questions / Re: Geocache Logs Time Now All 12:00 PM
« on: March 31, 2019, 17:54:57 »
That was indeed the problem. I must have unwittingly checked it. That is a much better explanation than it simply stopped working.

Troubles & Questions / Geocache Logs Time Now All 12:00 PM
« on: March 30, 2019, 12:26:29 »
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

OnePlus One
Android 6.0.1
Kernel 3.4.110
Cyanogen OS version 13.1.2

Troubles & Questions / Locus Crash with GSAK Import
« on: March 30, 2019, 12:15:11 »
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

I installed 3.30.1. The problem was fixed. Thanks for the quick attention to it.

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

Troubles & Questions / Re: Losing Points after Locus Crashes
« on: September 27, 2014, 13:50:57 »
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.

Troubles & Questions / Losing Points after Locus Crashes
« on: September 27, 2014, 03:17:42 »
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.

Troubles & Questions / Re: Vector maps not working anymore
« on: May 02, 2013, 04:27:22 »
The 2.11.1 update has fixed the problem.  Thank you for the quick fix.

Troubles & Questions / Re: Vector maps not working anymore
« on: April 30, 2013, 05:43:22 »
The version of the mapsforge-mapfile-writer.jar was 0.24.  I updated to 0.40.1 of osmosis and 0.30 of mapsforge-mapfile-writer.jar and it created a file that Locus worked with.  0.40.1 was the latest version of osmosis that would work with mapsforge-mapfile-writer.jar.  Newer versions of osmosis failed with this plugin.

Thank you,

Doug Peterson

Troubles & Questions / Re: Vector maps not working anymore
« on: April 30, 2013, 03:14:59 »
I posted a similar problem at ... ith_2_11_0

I had created the province maps from a larger country map.  The country map was current and still worked fine in Locus.  I created the province maps using osmosis 0.39.

Thank you,

Doug Peterson

Troubles & Questions / Re: Duplicate Vector Map Entries
« on: March 07, 2013, 04:41:09 »
I had the problem well before 2.9.x.  I was just setting up a new tablet and decided to check to see if there had been a response to my posting.  I think what happened is that in setting up my tablet I added the directory with out realizing that Locus would find the mapsVector under Locus without needing the entry.  I removed it and the duplicate entries disappeared.  Thank you,

Troubles & Questions / Duplicate Vector Map Entries
« on: March 01, 2013, 02:26:53 »
This situation occurs with my Samsung Galaxy Tab 2 7 tablet but not on my Samsung Galaxy S phone.  I tried to configure both devices identically.  I do not know what version this started with or if it has been this way all along.  I should have asked about this some time ago.  

Each of the maps in my vectors maps directory shows up twice in the Maps - Vector selection list.  If I delete the map both entries go away.  If I put the map back two entries show up again.  I have tried deleting all the maps.  I have the Locus directory on my external sdcard.  I removed the initial Locus directory on my internal sdcard.

Add-ons / Re: Addon GSAK database
« on: February 10, 2013, 05:15:40 »
I had hoped to leave a feature request but see by a prior post it may not be responded to.  I will leave it just in case.

I store Waymarks in my GSAK database.  They do not show up in Locus through the GSAK addon.  I can create a GPX and import them but avoiding that is the point of this addon.  It would be nice if they are included through the addon.

Thank you,

Doug Peterson

The Author had stopped the development due to his being too busy elsewhere. However, the code of the add-on is open for development by somebody else:

Pages: [1] 2 3