Messages

I should add that Oruxmaps was  - again - the most accurate tracker of all the tools that ran in parallel.



I carefully measured yesterday's hike in basecamp and qmapshack, and the track length registered by Oruxmaps was spot on - no other GPS tool came that close (viewranger was good, too).

Version 7.2.14 worked alright during my walk yesterday (nearly one and a half hours). As inaccurate as Android may be showing battery consumption, the pattern appears to be reproducible - Oruxmaps draws more battery power than any other GPS tracking tool running at the same time (except runtastic sometimes), unfortunately.



I guess, I will check that older version 7.2.12b again - maybe it was just that 0 seconds time interval setting that I had changed to 2 seconds that had given me straight lines - battery consumption was lower with that version, if I am not wrong.

Is this version 7.2.14  more recent (improved) than the test version you sent me?



I noticed, there is a difference in classes.dex.





I already told you, that your test version 7.2.14 T worked alright so far (my latest walk was about one and a half hours long, and Oruxmaps worked well, but also that it seems to me that battery consumption has considerably risen (of all the various GPS apps that I ran in parallel, Oruxmaps is number 1 now in power consumption, while before it was rather runtastic). The battery issue is not my main problem, if only the straight lines no longer appear, I am quite satisfied.

"stop apps that consume power" is globally disabled.



So, you suggest, I set the time interval to 0 again? Well, that's what I used before (and when Oruxmaps still worked).



Okay, this is easy, I will set it back to 0 then - hopefully, Oruxmaps will work again (the distance setting 5 meters instead of 20 should do no harm, I guess).

If sometimes, e.g. every 20 minutes or so, (during your hike) you turn on the screen, your test is not of much use - sorry to say so.



Only if you keep your screen turned off for let's say 45 minutes or more, it is plausible to conclude that Oruxmaps works alright and would not give any straight lines.



Of course, if your normal usage pattern is to look at the screen every few minutes, then Oruxmaps may really be useful to you - but not as a test for other people who keep the screen off during the whole hike, for instance.

(honor 6x, 7.2.12b)



I get straight lines again, after exactly 30 minutes! :-(



The difference to before:

I changed the time interval in the GPS settings from 0 to 2 seconds.

What does 0 as a time interval mean?



I had also changed the way distance from 20 to 5 meters.





Another change that may be relevant:

A recent system update to version BLN-L21C432B374.

Though even with this new version everything had worked like before (before I changed the above settings!).





At any rate, the system update to version ...B374 seems to be even more harmful to background processes:



GPS tracking apps (that worked with version B372 without any straight lines) are useless now:

- Osmand (each and every tracking session fails)

- Mapy.cz (sometimes fails)

- Oruxmaps fails again after changing the above settings





The only reliable GPS apps I have appear to be:

- viewranger

- locus map

- runtastic



Not a single problem with those 3 apps so far.

Nobody facing the scenario to import hundreds of tracks?

And then being forced  to put a check-mark before each and every track - instead of having a simple "mark them all" option?



Alternative would be (what I mentioned):

being able to zip all gpx files and import the zip (only one check mark needed, of course) and getting that zip unpacked into all the single gpx files.





@Orux



Any interest in something like that?

Thanks.

I had another walk, only 45 minutes (but longer than those 30 minutes I talked about).



With all power saving settings disabled (especially "close power intensive apps") and this time, running as the sole app on my smartphone, tracking did not stop after 30 minutes (no straight line!).



Fused locations provider was enabled. Might check without that next time...





version 7.2.12b, honor 6x

I hope, it is time for some optimism...



Today, I was on a long walk and only turned on the screen of my Honor 6x after 2 and a half hours:



Oruxmaps was still tracking!





I used 7.2.12b, fused locations provider enabled (if that mattered), and the difference to my previous tests was:



I had disabled the setting to close power intensive apps.





Simultaneously, I ran several other tracking apps - so I should really repeat my experiments with only Oruxmaps running.

But leaving the screen on is no solution - it eats the battery way too fast.

Well, I discovered something I had not noticed before:



(Honor 6x)

In the history of power intensive apps that were automatically closed, I found Oruxmaps (and the time matches the 30 minutes screen off time I mentioned!). I had the power intensive warning for Oruxmaps disabled, but obviously, this just turns off the notification, but not the shutdown action itself...



I'd like to keep the setting "close power intensive apps" enabled, but aren't there any settings to create exceptions to the rule?

Let's say: close power intensive apps, but don't do it for Oruxmaps etc.?





Next time, I will make a longer walk/hike with the "close power intensive apps" disabled! Maybe, I'll have better luck with Oruxmaps then...



But again my question:

Is it possible to leave the feature enabled and create an exception to the rule?

Hi,



my Honor 6x firmware version is: BLN-L21C432B372.

Well, sorry to say so, but I used 7.2.12b again today (with fused locations provider enabled), and once again, tracking stopped after 30 minutes of screen off time.



If that matters: I had several tracking programs open, besides Oruxmaps.

They all worked alright and recorded the whole track.



Perhaps, I should try it with only Oruxmaps running - but I doubt, this would improve anything.





It might be interesting to also note that this time, I used two smartphones (Honor 6x, see above), but also an old Vodafone 858 (which is Huawei U8160), the latter with Android 2.3.7.

On the Vodafone 858 I also had several tracking programs running, including Oruxmaps (6.5.0).

All the tracking apps (old runtastic, old Locus, old viewranger versions) did a good job, but even here Oruxmaps did not record the whole track! I took care not to turn on the screen for at least 45 minutes.





--edit--



I found a long thread about similar problems: The app Strava seems to have the same issues on Huawei phones.

The version 7.2.12b worked better for me (than 7.2.13c), indeed. But the results were not consistent, I had tracking working alright, and other times, it stopped with that version, too. Of course, I didn't use any power saving mode and I didn't permit automatic shutting down of the app because of high battery usage.



Unless, there is another new version, I am willing to start testing 7.2.12b again. Because as long as Oruxmaps is still tracking and doesn't start to produce straight lines, it appears to deliver very accurate tracking. Moreover, it is much faster than for instance Locus when shifting and rebuilding map display  (Locus is very slow there).



Hopefully, this issue can be resolved.

Unfortunately, none of those versions, including 7.2.13c, work for me.



Those who said that it worked, did you test it long enough?

I found that tracking stops after exactly 30 minutes screen off time.



It doesn't matter if I enable "huawei bug" or not.



My phone is Honor 6x with current firmware state (Android Nougat, latest official firmware).





It is sad, but as long as this issue is not resolved, Orux maps is not usable to me - all the other tracking apps I have on my phone do work (Locus, runtastic, osmand, osmtracker, viewranger).