CPU Usage in Beta 3.18.6.2

Ulrich Kiermayr shared this problem 3 years ago
Not a Problem

I am not fully sure yet, but it seems the beta has a very different CPU Usage.


For my office trip in the current stable i have

CPU total 4m32s

CPU foreground 24s


On the new beta i had

CPU total 6m49s

CPU foreground 6m49s


What esp. concerns me is, that all the CPU usage is in the foreground. Also the estimated power consmption is more than double from the stable version.


As said, it was a single test, but I'll keep an eye on it.

Comments (1)

photo
1

Good day Ulrich,

this is interesting as there should be no change that should have so huge difference.

Are you 100% sure, that both versions used same configuration, same map (+theme in case of vector maps), same overlays, same other content on map, same time when screen was turned on, etc. etc?


Thank you for your observation. I'll try to test it also little bit.

photo
1

Yes i am - because i imported the Backup from the Pro-version into the Beta just before using it (to make sure the config is identical).


I'll have an eye on that. it was sort of a heads-up in case I am not the only one seeing that.

photo
1

Oki, so configuration should be same. And time when screen was turned on was same as well? "Foreground" means that Locus had to be active, like drawing a map. When screen if off or Locus is on foreground, map is not drawn so it saves a lot of battery. Really can't imagine, what may directly in Locus code, cause such huge difference since latest release.

photo
1

Ok. Seems that it was a problem with the phone caused by an other App, that was updated at the same time.


You can close the ticket.

Sorry for the false alarm ;-)

photo
1

Good day Ulrich. It is interesting that you saw (did you?) CPU usage values directly next to Locus Map application. Anyway glad you found an reason and if there will be something I may help, feel free to write me.

photo
1

I keep detailed CPU usage for most rides. I just tested with 3.18.6.6 but found no obvious change is power consumption from previous rides, so it may be a specific combination of settings. I generally measure ~2%/hour battery level reduced with track recording, and ~3.5%/hour with track recording+navigation (no other apps running, Wifi/ data disabled/ display off except for each 30s navigation commands).

photo