This should find its way to you via Google Play and a link from an email from HockeyApp if you have subscribed.
Not much to see different here. I'm fairly confident I've killed off another few bugs, and a few that I'm less sure of. Basically I'm still hunting down stability. So please keep submitting the crash reports - I am diligently working through them.
We weren't requesting the highest accuracy of GPS fixes from Android, so I think Google Services at times may have been throwing up less than perfect data. Strangely enough it can even obscure the data to protect your privacy, so even though the GPS may have a very accurate position, it may well move it before it passes it to OMN unless we set the right permissions. I'm hoping this is the zig zagging that has been reported a few times resolved.
@Andrew - I'm expecting no change for you with this. I will be looking into that very soon.
You can download from here:
All maps now downloaded ok by following your map repairing instructions. This was done in Beta 34. Wonderful! I’ve installed 35 using Hockey and it is looking good ( though as you know it still has find issue present) . Regarding install process I could see version 0.35 on Google Play when 0.34 was installed but only UNINSTALL and OPEN buttons were presented to me, and not UPDATE hence I went Hockey route. Next time I’ll try OPEN since It occurs to me now that I didn’t try that.
A wish list subject: I’d like to be able to view the publish date(s) and version(S) of any map(s) I’m looking at on screen be it from device storage or online.
Using 35 from Google Play Store.
I created a tracklog whilst driving this morning. As with yesterdays test the tracklog from IpBike is smooth and follows the road. The tracklog from OMN is again jagged. The car odometer reports 17 miles (27 km), IpBike reports 27.2 and OMN 31.1km. I have attached the OMNB tracklog (timed 9:11) Interestingly when you plot this on the map the points frequently only show either an East West movement or a North South movement. Looking further at the OMNB trackpoints they all show the final digit of the 12 digit grid ref as either a 0 or a 5.
I then used OMNB and OMNC to record a tracklog whilst walking. The two tracklogs sit comfortably on top of each other except at the occasional change of direction where the corner cutting in the log is slightly different - accounted for by the timing of the recording of the trackpoints. OMNB reports distance as 17.04km and OMNC reports distance as 17.8 km. When I planned the route the distance was 16.5 km. OMNB is set to record every 25 metres or 60 seconds whilst OMNC is set to record every 25 metres or 15 seconds (sorry I thought I had set them up the same). Empirically I have found in the past, when walking, that it was necessary to set OMNC to record every 25 metres (with no time dependant features). Most of the distance discrepancy between the planned route and both OMNB and OMNC are down to time dependant recording occurring when I had stopped. e.g. OMNC recorded 0.9km whilst I was sat having lunch. These tracklogs show a full range of the final digit of the 12 digit grid reference. I have attached the OMNB GPX (timed 9:48). When I stopped the tracklog on OMNB I got an OMN has stopped error but the tracklog was complete.
I have looked back at yesterday's cycle ride and again OMNB's trackpoints all end with either a 0 or 5 for the final digit of a 12 digit grid reference. That was also recorded whilst running IpBike.
It points to OMNB misbehaving when IpBike is also asking for gps info.