Nothing knew about this observaton. Here is a unanswered message I posted from 4 years a go.
??? ---------- Forwarded message --------- From: Barry Evans <Unknown> Date: Wednesday, 31 May 2017 at 07:20:39 UTC+10 Subject: OSMAnd 2.6.3 battery use To: Osmand <Unknown> OSMAnd 2.6.3 is hammering the battery on my Samsung S7 running Android 6.2- see attached screenshots I have not run OSMAnd in earnest for a few years. Earlier versions running earlier Samsung phones lasted much longer. What is happening? I have a lot of experience with smartphones and how to save battery life, but I have never seen anything quite like this. Today my battery just fell off a cliff and shut down at zero in the blink of an eye while navigating using OSMAnd Any ideas? On Thursday, 12 August 2021 at 10:59:21 UTC+10 Barry Evans wrote: > I have noticed OSMAnd using more and more power over the past few years. A > couple of years a go I updated my phone (Samsung S8) JUST to try and get > better battery life when using OSMAnd. Alas, even when knew, OSMAnd in > navigation mode just ate through the battery of my S10. I can run other > gps-based software which TRACK my ride all day, but OSMAnd in NAVIGATION > mode lasts just a couple of hours max. It's also slow to render the (off > line standard OSM) maps when moving so you are on to junctions before turn > instructions appear. Which makes me think the navigation engine is burning > CPU/battery? > I'm a long time paid supported of OSMAnd and recommend it to everyone, but > I now find myself adding a caveat about battery life. I've tried turning > everything off that runs in the background, but it makes little difference. > Looking at my message, it seems what I should do is just set OSMAnd to > JUST record my track (without Nav) and see what battery life is like then? > Certianly when I have the OSMAnd app open and displaying on my phone, > without nav or record, battery consumption is much better, but still much > more than other apps (that just record a track while displaying an off- or > on- line map. > > On Saturday, 5 June 2021 at 21:57:03 UTC+10 Greg Troxel wrote: > >> >> "'P Wat' via OsmAnd" <osm...@googlegroups.com> writes: >> >> > a) "Just normal daily use receiving mail, texts, making the odd phone >> call, *running >> > Osmand as a map*, the consumption is OK". To which I could add >> listening >> > to radio for several hours per evening, and other usage. >> >> It sounds like you are saying that having OsmAnd open, using the GPS, >> and displaying the position does not seem to cause excessive drain. >> If I followed you, it is having OsmAnd compute routes and follow the >> route. Is that what you mean? >> >> I have not really noticed increased drain, but I always use external >> power when navigating in the car, and rarely use it on foot. I have >> noticed my phone seeming a bit hot when taking it out of the car on >> arriving. >> >> It would be good to have some kind of CPU time usage metrics for the >> app (as a system tool to watch; I don't mean to suggest this be part of >> OsmAnd). >> >> >> -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/cf0c8f13-aaf8-4175-9f7f-9d17d32f2a05n%40googlegroups.com.
