On Fri, Jun 04, 2021 at 04:27:38PM -0700, 'P Wat' via OsmAnd wrote:
>
>On Friday, June 4, 2021 at 6:19:44 PM UTC+1 Xavier wrote:
>
>> On Fri, Jun 04, 2021 at 04:07:20AM -0700, 'P Wat' via OsmAnd wrote:
>> >[image: OsmAndPowerDrainScreenshot_20210530-184241.png]Has OsmAnd power
>> >consumption been creeping up?
>> >I first noticed the problem several months ago, but have only recently had
>> >the opportunity to analyse it.
>> >Just normal daily use receiving mail, texts, making the odd phone call,
>> >running Osmand as a map, the consumption is OK. Battery lasts all day, and
>> >more.
>> >Running OsmAnd for navigation (route instructions, etc) it eats my battery
>> >in an unacceptable time, eg 45 minutes.
>>
>> First question: Is the phone today the same phone from "a couple of
>> years ago"?
>>
>> Second question: If it is the same phone, is it *also* the same battery
>> from "a couple of years ago"?
>>
>> Also, if it is the same battery (which would also mean same phone) then
>> the batterie's capacity will have dropped in the interveaning years, so
>> the battery will be less able to stand up to heavy current usage now as
>> compared to a couple years ago.
>>
>Hi Xavier.
>Thanks for your lucid response. Questions understood, and the reason for
>them.
>1) Phone - IS the same as a couple of years ago.
A reasonable comparison then.
>2) Battery - IS the same as a couple of years ago.
>"Aha! There's the problem"; I hear you cry. And I understand your logic,
>(where you're coming from). I am an engineer and am cognisant of the
>problems of aging batteries, diminished capacity, reduced current delivery,
>and such. However, in defence of the battery in this instance, I am
>reasonably confident that it is still giving respectable delivery. Daily
>drain under normal circumstances is so far not unduly reduced since new.
Yes, but, daily drain without the GPS receiver running will be lower
than daily drain plus the current pulled by the GPS receiver. One
possibility is that the additional current draw trips your battery over
a knee where it can't handle the load.
>Clearly you are technically aware so I'll refer back to parts of my
>original post:-
>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.
Yes, that does imply a reasonable capacity does remain. Although using
Osmand as just a map, without navigation also running, will likely not
toggle on the GPS chipset as much, so the current drain will naturally
be lower.
>b) " Battery lasts all day, and more." This phone model does have an
>unusually high capacity battery. It can still easily do 24 hrs between
>charges, but is generally charged overnight.
Also implies a reasonable capacity does remain. Does not rule out a
critical current draw level above which the battery is unable to cope.
One possible test to determine if the drain is caused by the GPS
chipset, or by Osmand, might be to install this app briefly:
https://f-droid.org/en/packages/com.android.gpstest.osmdroid/
And run it (with Osmand off, to remove Osmand usage from the picture)
under a similar senario and time as the navigation where you saw the
drastic drop in your posted screen shot.
If you get a similar drastic drop in the capacity curve, then that
points to the battery possibly having a critical current level above
which it cannot cope.
If you don't get a drastic drop with the alternate app, then that would
implicate Osmand as a potential cause.