I can't trust Locus Pro anymore
Maybe similar to what joeloc is talking about - but I had 2 Locus crashes during a tracklog that was just under 4 hours.
Unlike joeloc they luckily didnt happen in the background but instead happened as I opened Locus Pro to check my distance traveled and see what POIs were about. Twice Locus just crashed.
This has been happening with 2.7.x versions for me and I am now gutted to say I have to take my S.E. k750i out with me and a seperate GPS module using trekbuddy to record the track I walk as I simply do not want to walk 4 hours and risk not having a .gpx at the end of it.
Here are a few things I have noticed the last few weeks that are really troubling me about Locus. I state these things only as feedback as I think Locus is superb but recently have honestly considered stopping using it.
1. Seems to use more battery than other releases prior to 2.7.x
2. Importing a gpx file often causes it to crash and I need to open Locus again and try to re-import the gpx. This opening and immediate crash can happen 3 or 4 times before the gpx file finally imports correctly.
3. I never have more than 3 (at the very most) POIs open at any one time in Locus when I am out and about logging my route... but sometimes when just clicking the 'points' tab - Locus will just crash as it did twice yesterday when I was performing very simple operations.
4. When Locus crashes whilst logging a route... it restarts itself which is great... but please please please can it be made to automaticly resume logging because at the moment it puts the logging into 'pause' mode when it restarts and its very easy to forget to take it off pause. It would be so much better if after a crash it resumed logging.
Well, that my recent experiences on long walks with Locus. Its gone from being an app I used to look forward to using to one I really like but dread how its doing to act.
I would appreciate any advice or ideas on the above. Is it worth me installing catlog again and trying to sort out some crash reports?