Quite a lot of tidying up in this one.
On loading map definitions for Manage Maps, if you have say a 50k subscription, then all other maps of 50k apart from the demo maps will be dropped. When/if you subscription expires, the maps that were hidden would become available again as they have not been removed from your account.
On turning off the GPS, the stats fields now go blank, rather than showing stale data.
Pause / Stop a tracklog now turns the GPS off. You can turn it back on to centre yourself without resuming the tracklog.
Settings->Main Map Screen, you can now set how many rows of data the Stat bar has in its Standard and Expanded format.
If you double tap on a stats cell on the stats bar, you can now select 'No Data / Clear' to clear a cell.
Rename/Delete only listed sometimes in GM - fixed.
Grid Reference not updating - fixed.
The aggressive scrolling could show white squares - feedback please, I think its much better, but I think I have still seen the issue once. It certainly feels better on my device.
If OMN fails to startup three times in a row, it will give you the option to reset. The reset will clear off the database / settings and you will need an internet connection to get going again for the initial sync. Its not perfect, but it should catch corrupt database or settings files which will mean users won't need to uninstall and loose their map data downloads. If a user can't startup, he can't get to settings->reset, so this hopefully helps with these types of issues.
I think if I can get the list done below we are just about there.... any other showstoppers people are aware of?
What are we working on:
Blue/White screen at startup - we have new code in place, we are now awaiting some graphics from our artist to make the startup a nicer experience.
Some verify issues that I am looking into.
A crash on first use of GPS after installation.
Some feedback on re-starting tracklogs.
User feedback on 'verify pending' on larger maps - its calculating what to do without telling you, and it can take a while.
You can download from:
Google Play: https://play.google.com/apps/testing/com.anquet.omn2
** this takes a little while to come out. HockeyApp email notifications will come out once the build completes.
@Ernie - yes I have the crash reports, although these ones aren't that helpful as to what happened. However, it would appear we have some libraries which we use with updates that were reported in your crash reports, so we have updated those this morning.
@David - thank-you.
@Paul - I think you probably have an old setting for Grid Reference, so just update it by double tapping on it. If you re-start OMN, is the judder always there?
@Cliff - it sounds very much like your system was not in a stable state. I presume if you turn off wifi now, it starts up fine? It will only need wifi if it needs to sync, which should only be on failed startups, or initial installation. I'm glad the input screens are now all good for you. If you haven't run a sync from GM, then your tracklogs would have only been locally stored, and in which case the reset has most likely lost them. I've been thinking about an automatic sync, but its a case of when to run it, as we need an internet connection. Heights of 5000+ feet seem very wrong. Are you sure you weren't looking at ascent? That's still quite an ascent!
@Cliff - on saving the gpx files, they save into the database on your local device. A sync would have copied the data to Anquet Cloud, but that currently needs the user to hit the Sync button in GM. Unfortunately the reset you have done will have killed off the local database, and the subsequent sync brought your data down from Anquet Cloud. In this instance I'm afraid to report the data has been lost.
We shouldn't be getting failed startups. OMN should startup fine wifi or no wifi. However, if the main database or settings files get corrupted somehow, then its possible that OMN won't start up. This would have in the past led to us asking a user to uninstall/reinstall, and that would wipe the map downloads as well, which is awkward. So we have brought in this bit of code, which offers to remove the settings/database files, hence not requiring an uninstall/reinstall. But users just shouldn't be seeing this code in normal usage.
This does of course raise some issues in my mind. The obvious change in due course would be to split the database into two parts, so that route data could hopefully be less prone to issues.
May well have always been an issue but:
Power saving enabled on phone.
Track Logging started.
Carried on walking
Tracklog had stopped recording points while locked, but restarted when unlocked.
I have had this problem with other GPS loggers while power save enabled but NOT consistently !
Samsung 7 , Android 7.0, data storage to SD card
@Paul - many thanks.
@Rob - that's an interesting one, that I'm pretty sure we can't code around. If we could, all the apps would, and the power saving mode would be of no use. My guess is we can probably detect it, and let the user know and ask him to whitelist us. I believe you can turn it off per app in Settings->Battery. https://android.gadgethacks.com/how-to/android-basics-disable-doze-app-standby-for-individual-apps-0168960/
The problem we will have, is that for most people, they don't turn this on, but it kicks in at 15% battery or similar level, and if they aren't looking at the app, then we can't let them know.
The only way I can see to do this, is to ask for the permission at installation, or the first time they try to record a tracklog, but some users will baulk at giving that, but at least they will have been warned!
Can you try giving it a green card using the link above, and let me know if that is certainly the cause on your device?
@Peter - when you say the screen had to catch up - were you faced with a blue screen at any point, or just simply a map screen? Could you have nudged the screen before closing the phone? If the mode is 'off-centre', then on coming back to life, it would still be off-centre. Normally we are listening for a GPS fixing every half second or so, so I would expect the screen to show up, and then within about 1 second to have had a further GPS fix, and on that fix if the system was set to be on centre, for the map to catch-up. Could that explain what you were seeing?
Many thanks chaps,
@Peter / @Paul - I think I have found the issue. Many thanks.
Beta 66 is now up: