Stats basic function: Tap on the button top left to open stats. Swipe left to close, or swipe down to expand. Double tap on a cell to get the list of options.
Stats now has the following options:
Accuracy - Reports GPS accuracy.
Altitude - GPS altitude
Direction - Direction of travel
Distance - length of current tracklog. Currently this does NOT also add on the distance from the last trackpoint in the tracklog to the current GPS location. This is on my list to get altered. So distance will only update as each trackpoint is added to the track currently.
GPS Reference - the location reported by the GPS
Speed - speed reported by the GPS
Time - hoping I don't need to explain this one.
Vertical Accuracy - again reported by the GPS, but I have only seen zero on my phone. Its either very very accurate or I have a bug somewhere! Is anyone getting a sensible value?
I think there is still some finessing required. Turn off the GPS, things don't blank currently. I also believe there is some 'stacking' up of data, in that if you stop walking, it takes a few seconds for speed to drop to zero. I think we aren't processing data as fast as its coming in, so we probably just need to drop some values.
Overall though this is taking shape now, and the updates to the screen now feel smooth.
Some large changes which I am sure are for the better. Will they fix the reported issues, on that I just don't know....
First up, I've done some automated testing of sleeping and waking the app, and I have detected and fixed a small memory leak. Certainly good to fix it, but was it enough to crash someones app after 2 hours.... its possible, but I wouldn't have thought so.
So the app works in two parts - the tracklog recording (recorder) and the main app (app). The system was set that the recorder would call the app about updates, and if the app was killed off, we get a warning, and it would disconnect. I've changed this to use the Android broadcast system, so now the recorder just SHOUTS changes, and if the app is alive and running, it hears them and processes them. The upshot is, that a crash in the app should not crash the recorder. Frankly I thought the code before should have avoided this situation, but this certainly furthers the separation. When the app starts up, if will catch up any updates its missed. This happens as the next trackpoint is added. I will try to improve this - you will currently also see this if you put the app to the background, when you bring it to the foreground, the tracklog will update as the system records the next trackpoint.
If the recorder crashes it will restart by itself. Android decides when exactly, and on my phone its about 30seconds to a minute. So if the recorder does crash, it should start back up, although you might get a small gap in the track depending on your settings or you might not even notice. Due to the current separation, the recorder takes distance / time settings when a tracklog is commenced, and won't update the settings whilst recording. This is on my list to alter.
You will also find that the recorder notification now updates telling you which trackpoint is being added.
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.
P.S. 58 got released as Menu->Edit Mode would crash the system - I had been using that to purposefully crash the system and test the recovery. Its back to normal in 58.
Hi Just installed Beta 58 - when I tap the top left menu bar I just get a grey band across the top. If I sweep down the band just gets wider. If I sweep left or right I get nothing. Also has now frozen phone.
Will reboot and see if I can get a screenshot
Ok, certainly still some issues, but also some good forward progress.
I’ve made good progress today, but not quite ready for the next beta. Speed issue was the stats page continually running too much maths deciding what size fonts to use, and updating too frequently.
@David – I think the double taps weren’t working, as it was simply in a loop re-drawing itself too much. The height adjustment is on my list, but a little way down currently.
@David / @Steve / @Roger – we do need a way to further refine the number of rows and remove data selections.
@Ian – this beta redraws on adding the next trackpoint, hence the delay. The next beta has this fixed.
@Roger – I think the overlay works, it just needs more work – add enough rows, and it becomes the old stats page and will cover the complete map. We just don’t have those settings yet.
5600 pts is a decent size track. From a fresh start, no GPS, and load the track, the system is responsive on your phone still?
Speed – I’ve been seeing similar, I noticed it yesterday whilst in the car. That’s on my list as well, although I get that straight from the GPS library!
@Tony – double tap on one of the cells, and you can set it. We need a default setup which we don’t currently have.
@Paul – encouraging to be moving forward. I have in fact found some more issues and fixed them today. I will be looking at the numbering issue tomorrow morning I hope.
Regarding segment 1 - The update on the app coming to the foreground will be in the next beta. Regarding segment 2, I’m not sure if the fix for 1 will resolve the white. I *might* know what caused the segment 3 issue, and I feel that the segment 4 issue was just a follow-on issue from 3.
I’m going to keep concentrating on the stability and usability. Then I will turn to incorrect values and how to update the interface further.