It would appear that the last beta was certainly forward progress.
On my phone, this one appears a further big step forward.
There were three things that were hitting performance, which have all now been resolved:
1. Stats bar was updating far too often - it now updates twice per second.
2. Stats bar was almost fully recreating itself on each update to scale the font correctly, yet a lot of the logic was not required.
3. We were in certain circumstance ending up with multiple background threads recording multiple tracklogs - which were all updating the main thread leading to some confusion in trackpoint numbering, and also a performance hit.
I've also managed to eek out a bit more performance from the draw routines, so things feel slightly smoother for me now, and a LOT smoother if the stats bar / tracklog recording was in use..
On coming to the foreground we now update the tracklog straight away.
I'm still seeing the odd freeze on coming to the foreground, but it appears much better and much less frequent for me.
I haven't looked at the issues of the stats figures for speed, altitude and vertical accuracy yet.
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.
Installed from GP with no problems.
Definitely better performance for me, with large gpx files performing well now, before they were sluggish.
Managed to crash it while long pressing on large route - report sent.
Stats bar performance very snappy
I'll try some track logs tomorrow.
Installed from GP without issue. Have run a 10 hour tracklog without problem.
Ran a track log overnight to see how app would behave - Still running in the morning and the track started recording as left the house to walk the dog.
Stopped the track and started new track. Good result, but walk was only a mile long.
Distance stat working nicely, with the accuracy looking about right.
App crashed when I browsed Icon Manager, no log generated
Hi chaps, well this is certainly looking better.
@Ted – thanks.
@Nigel –The blue screen is OMN re-loading itself, that isn’t an issue if the tracklog was still recording – if it was, you should see the notification in the notifications area. Which version of Android are you running? It sounds like on your phone, the tracklog is recording fine, it’s just the performance on coming back to the foreground which is the issue?
Android has a light sleep, deep sleep, and frankly it can close us down. Then when you click back, if it has closed us down, it shows a photo of us as we were before we were closed (this is often why people report seeing the map of where they were before they turned the screen off) and then re-loads us.
On coming to the foreground with no GPS running, or GPS running, the only differences are: starting the GPS up if we aren’t recording a tracklog, and secondly, copying across any recorded waypoints whilst the app was not in the foreground. If you push OMN to the background, with GPS off, and come back in say an hour to it having played with other apps (which is likely to use memory and hence Android will close down OMN), your speed of re-opening is completely fluid?
Yet the tracklog into town was fine. Can I just check you only have OMN installed once? You don’t have the GP and the HA versions both installed? I ask, as you paused the tracklog, then ‘Started’ to come home, whilst it should have been ‘Resumed’. Sorry it sounds like I’m being pernickety, I’m not meaning to, but I’m trying to understand what happened. When you got home, and turned on, , the blue screen looks like it was loading up from not running – and you then found a second segment in the tracklog, but no points recorded?
@PaulQ / @Roger / @David – many thanks.
@Paul – I think we have the crashing issues behind us now. I will take a further look at the lifecyle work to see if I can further improve it. I’m wondering if the slow coming back to life is somehow a stats calculation getting fired off each time a trkpoint is added to the track. I will investigate that next. I also think, if you want to move to Android 7, please do.
Many thanks chaps,
Use tracklog over 3 hour walk today, didn't mess it about with pause or working in background but stopped and checked route, changed zoom and scrolled around map during walk. Stopped tracklog at end, saved, cleared and reloaded and everything worked as wanted. No attempts force issue with running other apps or too much chopping and changing admittedly. I am sure if you try hard enough it will crash/freeze but progress in last two betas is great. Fingers crossed it is meeting my need now. Thanks Colin.