Increased battery usage since 4.31.2

Here is the NMEA recording of a fragment of my ride, taken while Locus was navigating, Strava was recording, everything setup as I usually do.

Could you please also send the GPX of the route so that I can simulate the navigation along it? Thanks

Here you go. This only a piece of my ride, but it should cover the nmea log fully. Thank you for looking into this, I appreciate it!

Thanks a lot for the files. We tested the feature with your data but unfortunately, we didn't reveal anything significant. We'll go on investigating the issue and collecting more data from other users.

I don't use navigation because it uses far more energy (approx. 2x) than simple track recording. I just turn on the screen briefly before any turn (for the displayed route) to check directions manually. I set the screen timeout to 5s. Energy for the screen, especially if sunny, is the biggest use of your battery.

This is based on some tests this year? Because even in the navigation system were done a performance optimizations and battery consumption should not be so bad. Also, there is a well working "Screen on/off control" settings, that is really helpful during the navigation. Maybe just give another try ...

Thanks @Menion. No, I haven't used Navigation mode for many years, so I probably should (will) give it a try, especially now I have an accurate methodology for battery measurements. I do think I can manually turn the screen on at more appropriate times than with the fixed settings of LM. And I simply rely on Android to turn the screen back off after 5s which is quite convenient. I'll add a further comment here in next week.

A quick test (only 30m) - with track recording only, screen off, the current was ~100mA - consistent for over a year. With track recording, navigation, screen on 5s (with about 10 announcements), the current was -160mA.

Current (mA) while navigating+track recording revised to 190mA compared to only track recording of 100mA. A pity I can't just edit my previous post.

We are a little bit offtopic here 😬. Anyway thanks. It is not as positive as I've expected. Will have to look at it even more 😉

Hi Franz, nobody has said that the problem doesn't exist when only one user reports it. We only said that Piotr has been the only one yet. You are the second, thank you. Also, you don't have to find the cause. You can only give as much detailed information as possible about the issue. So, could you please describe in detail when exactly you observe higher energy consumption? What features do you use when the drain takes place?

As for the "darkening in LM4", please start a new topic as this is not relevant for this one. Thanks.

"we've checked the app and we didn't find any "leak" that would cause battery drain. Also, no one else has reported the issue.

For me, that means there is no problem that needs to be addressed.

"So, could you please describe in detail when exactly you observe higher energy consumption?"

Every time I navigate to a point, the power consumption increases. So much so that, despite charging the battery at the same time, its capacity steadily decreases in the car.

Without navigation but with track recording, this is not the case.

If you navigate a route that is not created in the Locus Map route planner, the app has no data regarding the intersections. Therefore, it generates the navigation prompts according to the route shape. The number of prompts can be adjusted in settings >navigation > advanced > frequency of commands. There is no proof that this feature is involved in the battery drain.

This option has been in Locus Map for many years. Maybe you just had it turned off. When you select "none" in the settings >navigation > advanced > frequency of commands, the navigation commands are not generated for imported routes or recorded tracks.

Then I'm afraid I don't understand what's wrong. If you turn navigation on, I suppose you want to hear navigation commands. But you are complaining that "Instead of being able to chat with my fellow passengers in the car, Locus now talks to me." So, what is your desired status of the app?

If you use internal navigation to a specific point, Locus normally uses the router to generate it. Then you should only receive notifications at intersections. If you receive notifications at every turn, then something is wrong. I don't have a route to test it right now. Maybe Michal can test it. But it has little effect on the battery. But actually, this is about the battery

Could you please send a GPX of the route? Thanks. I'll test routing and navigation between its start and destination. As Freischneider wrote, the router generates navigation commands on intersections only.

I'll join the discussion about navigation commands. For example, the planner sometimes doesn't generate commands at key intersections. And yes, "straight ahead" commands have appeared at literally every small intersection in the city. This wasn't the case before. If necessary, I'll record a video. It's easy to reproduce.

I immediately tried to create a route that took into account the shortcomings described. And it didn't work; everything worked perfectly.

But yesterday I was sober and plotted the route in the planner several times, and each time there were shortcomings. It's an interesting story.

You should also note that the planner is BRouter. Then you should also report errors in BRouter. Straight ahead is an important tip. I'm glad that's being mentioned.

I don't have any .gpx files for the routes.

>>>"As Freischneider wrote, the router generates navigation commands on intersections only."<<<

No, the router generates instructions at every turn, every curve. Even where there's no other option! It's been like this for about 4 weeks.

My wife and children can confirm this! They were also annoyed by all the winding roads during our vacation in Greece. “Turn left,” “turn right,” “turn left,” “turn right.”

There was no other option. There was nowhere else to turn. Before the update, Locus said, “Follow the road for 50 km.”

You can share your location and destination, as well as which routing profile you're using and exactly how you're going about it.

I already wrote that.

I select a desired destination at my location.

I press the navigation button.

The menu opens.

I press navigate again.

Then I select car.

Then I press navigate again in the top right corner.

Then I have the route.

Locus apparently does not receive TBT from BRouter.

The TBT are therefore generated using the track shape.

This is not a car route but a bicycle route.

See the attached gpx file WITH the TBT.

This issue has been simulated and fixed. Please wait for the next app version. However, it has not been proven that this also solves the battery consumption problem; it needs further testing.

It's a shame I got flustered last time and didn't save the logcat. But now I'm prepared. As soon as I notice a critical drop in battery capacity, I'll wait until it reaches the minimum and save the logcat. What else can I do to get the most information about the problem?

The system log will certainly help as another source of information. At the moment, we are lacking any relevant data regarding the alleged battery drain.

Hello,

Thank you very much. After the latest update with Beta 4.31.3.6, navigation is working again as it should and as it used to.

Perhaps in future it would be better to listen to users straight away instead of spending three days discussing it.

Sometimes users know what they are talking about. 😉

The battery drained quickly again.

I promised the log code.

I asked the AI ​​to analyze the log code. The output is in the attached file.

The output is completely clear to me and was expected. I'll make some changes to the Locus settings, for example, to record a track every 2-3 seconds instead of every second.

However, what's confusing is that I always use these Locus settings. However, the rapid battery drain doesn't always happen.

I suspect the cause is location data transmission during a poor or nonexistent connection. I'll pay more attention to this in the future. I'll try disabling location data transmission if I notice rapid battery drain. But perhaps Locus doesn't need to send data so frequently when there's no connection?

If you need the full log, where can I send it?

"I suspect the cause is location data transmission during a poor or nonexistent connection."

That can't be right.

I use Locus completely offline and have the same problem.