REALLY kill various apps

[The Real Bev]

They should ALL be required to have an easy way to kill them
deliberately. I wondered why my Pixel2 was such a heavy battery-user
even in airplane mode with location and bluetooth turned off and NO
RECENT ITEMS (I flicked everything 'up' that I had been using) showing
in the <little square> window.

It takes the phone minutes to turn off and then on, but RESTART goes
pretty quickly and seems to kill whatever was running in the background
invisibly and eating battery.

When I want something off I want it OFF. I don't care how long it takes
to restart an app -- generally only a few seconds.

--
Cheers, Bev
I remember when everybody posted to Usenet with their real,
deliverable e-mail address. Of all the sins committed by the
spammers, destroying the viability of the open Internet was the worst.
(Shmuel (Seymour J.) Metz, news.admin.net-abuse.email)

[Gremlin]

The Real Bev <bashl...@gmail.com> news:rj13lp$34b$1...@dont-email.me

Sat, 05 Sep 2020 22:32:23 GMT in comp.mobile.android, wrote:

> They should ALL be required to have an easy way to kill them
> deliberately. I wondered why my Pixel2 was such a heavy
> battery-user even in airplane mode with location and bluetooth
> turned off and NO RECENT ITEMS (I flicked everything 'up' that I
> had been using) showing in the <little square> window.
>
> It takes the phone minutes to turn off and then on, but RESTART
> goes pretty quickly and seems to kill whatever was running in the
> background invisibly and eating battery.
>
> When I want something off I want it OFF. I don't care how long it
> takes to restart an app -- generally only a few seconds.

If you know of an app that actually does as you and I both want,
please post about it. I'm presently using KillApps v1.19.2 by
Ouadban Youssef (I got it from the google app store) and it seems to
work well for the most part; but a couple of chrome updates ago it
couldn't kill the browser anymore. That's since been corrected, but
worth mentioning in the event it doesn't play well with one or more
of your apps. The free version is limited in the sense you can't
kill any system apps. I'm still running the free version. What
little advertising there is is only visible when your on the main
settings page, anyway. What app(s) if any do you use?




--
The cyber stalker, liar, and troll known as Michael Glasser (Snit) view below:
<https://web.archive.org/web/20181028000459/http://www.cosmicpenguin.com/snit.html>
<https://web.archive.org/web/20190529043314/http://cosmicpenguin.com/snitlist.html>
<https://web.archive.org/web/20190529062255/http://cosmicpenguin.com/snitLieMethods.html>
<https://www.imgpaste.net/image/9tI2X> - <https://ibb.co/NTCVpvN> - <https://gofile.io/d/kE7vxh>
The cyber stalker, liar, and troll known as David Brooks (BoaterDave) view below:
<https://tekrider.net/pages/david-brooks-stalker.php>

[Arlen Holder]

On Sat, 5 Sep 2020 15:32:23 -0700, The Real Bev wrote:

> When I want something off I want it OFF. I don't care how long it takes
> to restart an app -- generally only a few seconds.

Hi The Real Bev,

I sympathize with your plight, and that of all Android users on this!

At times, I've had this same problem, and haven't solved it to my
satisfaction.

Sure there are drastic methods (e.g., reboot or disable), but all I really
want is a "ps -auxww" and then a "kill -9" of the pid.

I think I asked, in the past, and got no satisfaction on this...
o Let me run a check on dejagoogle for the comp.mobile.android newsgroup...

Ah, found it:
o What's a good way to kill jobs that persist in the background (without having to reboot)?
<https://groups.google.com/forum/#!topic/comp.mobile.android/Did0Rd3mRmo>

As I recall, we got no satisfaction on the question...
--
Maybe this time around we'll get a better solution to the problem set.

[John B.]

On Sat, 5 Sep 2020 23:24:12 -0000 (UTC), Gremlin <nob...@haph.org>
wrote:

>The Real Bev <bashl...@gmail.com> news:rj13lp$34b$1...@dont-email.me
>Sat, 05 Sep 2020 22:32:23 GMT in comp.mobile.android, wrote:
>
>> They should ALL be required to have an easy way to kill them
>> deliberately. I wondered why my Pixel2 was such a heavy
>> battery-user even in airplane mode with location and bluetooth
>> turned off and NO RECENT ITEMS (I flicked everything 'up' that I
>> had been using) showing in the <little square> window.
>>
>> It takes the phone minutes to turn off and then on, but RESTART
>> goes pretty quickly and seems to kill whatever was running in the
>> background invisibly and eating battery.
>>
>> When I want something off I want it OFF. I don't care how long it
>> takes to restart an app -- generally only a few seconds.
>
>If you know of an app that actually does as you and I both want,
>please post about it. I'm presently using KillApps v1.19.2 by
>Ouadban Youssef (I got it from the google app store) and it seems to
>work well for the most part; but a couple of chrome updates ago it
>couldn't kill the browser anymore. That's since been corrected, but
>worth mentioning in the event it doesn't play well with one or more
>of your apps. The free version is limited in the sense you can't
>kill any system apps. I'm still running the free version. What
>little advertising there is is only visible when your on the main
>settings page, anyway. What app(s) if any do you use?

Not to start an argument but are the apps actually "running" or are
then just in memory? I ask as Linux certainly retains a lot of apps in
memory that are "Sleeping" and apparently not using power and as
Android is based on Linux it might be the same.

As an example using Linux Mint, at the moment, I find that I have some
89 functions listed of which 82 are sleeping and 50 were labeled as
"polling" or in other words they are there in memory, sleeping at the
moment, but wake up periodically to see if anyone wants them.

--
Cheers,

John B.

[Arlen Holder]

On Sun, 6 Sep 2020 00:24:12 -0000 (UTC), Arlen Holder wrote:

> o What's a good way to kill jobs that persist in the background (without having to reboot)?
> <https://groups.google.com/forum/#!topic/comp.mobile.android/Did0Rd3mRmo>

Here is a quick summary based on the dejagoogle record of my old thread:

<https://groups.google.com/forum/#!original/comp.mobile.android/ScA7PlwKeYs/T4MxR349AgAJ>
Gremlin

If you know of an app that actually does as you and I both want,
please post about it. I'm presently using KillApps v1.19.2 by
Ouadban Youssef (I got it from the google app store) and it seems to
work well for the most part; but a couple of chrome updates ago it
couldn't kill the browser anymore. That's since been corrected, but
worth mentioning in the event it doesn't play well with one or more
of your apps. The free version is limited in the sense you can't
kill any system apps. I'm still running the free version. What

little advertising there is only visible when you're on the main

settings page, anyway. What app(s) if any do you use?

<https://groups.google.com/d/msg/comp.mobile.android/Did0Rd3mRmo/YIv3oREXCAAJ>
Joe Beanfish

There are app killing apps that will continuously kill all or specified
background apps. But IME and anecdotally, they don't really do any good
and actually may backfire because those apps that want to run in the
background will just keep relaunching, making things worse than if they
were just sitting there quietly.

Also, a lot of apps these days contain "services" that don't show up
in standard "resident apps" lists and run in the background regardless
of whether you ever launch the app (think of linux daemons). IDK if
there's anything to be done with those except to uninstall the app.

<https://groups.google.com/d/msg/comp.mobile.android/Did0Rd3mRmo/HxCdUsdPAgAJ>
Joe Beanfish

For Android 10

Settings->Apps->[choose the app]->Battery->Force stop

It was similar or the same for Android 9.

For apps that keep restarting themselves, you're actually using more
power to keep killing and relaunching them than to just let them
sit there quietly.

<https://groups.google.com/d/msg/comp.mobile.android/Did0Rd3mRmo/cTqNh0JQAgAJ>
Ned Latham

Better yet:
Settings->Apps->[choose the app]->Battery->Uninstall
(Android 9)

<https://groups.google.com/d/msg/comp.mobile.android/Did0Rd3mRmo/rL3DvYFjAgAJ>
Yakker

The OP wanted to kill jobs in the background, not give them a funeral.

Try the app Force Stop Apps. It generates a list of background apps. You
can choose apps to add to an ignore list. You then workk through what you
do want closed on app at a time. All it does from there is open settings at
the choice to Force Stop or uninstall. The only advantage over the manual
method is you don't need to check for what is running. Whey you finish and
Exit, The App give you the option to stop itself.

<https://groups.google.com/d/msg/comp.mobile.android/Did0Rd3mRmo/f7har8QzAgAJ>
On Tue, 18 Feb 2020 02:21:51 -0000 (UTC), Arlen Holder wrote:

> I've installed Greenify and am testing it as we speak:
> <https://i.postimg.cc/HkmSks4V/permission12.jpg>

UPDATE:
I have not found "Greenify" to be useful for killing silently running apps.
<https://i.postimg.cc/ydJJGkxw/pskill01.jpg>
<https://i.postimg.cc/NFmKgS1D/pskill02.jpg>
<https://i.postimg.cc/X7KrtMN7/pskill03.jpg>

Hence, the technical question remains unsolved:
o *Is there a graceful way to view & kill running apps in Android 9*?

Today, yet again, I ran into this problem of not having a good way to run a
"ps" process status & then "kill -9 <PID>" to kill any specific app running
in the background that won't die of normal means by its own GUI.

Here's the scenario of today:
a. Earlier I ran the "Open Tracks" program to create a GPX track.
b. Then I swiped (many times during the day) to kill all running apps.
c. Yet Open Tracks is _still_ running (it says it's "Paused").

Well, I want to _kill_ Open Tracks (not just "Pause" it)!
o There's no exit in the program itself anywhere!
<https://i.postimg.cc/ydJJGkxw/pskill01.jpg>

When I longpress on the notification that OpenTracks is running,
o The only choices are to "Stop notifications", but that's just cosmetic.
<https://i.postimg.cc/NFmKgS1D/pskill02.jpg>

Of course, I can hit the (i) information icon in that notification
o And then press the Android Draconian "Force Stop" button
<https://i.postimg.cc/X7KrtMN7/pskill03.jpg>

But that only works for apps that bother to notify us they're running.
o And, it clearly warns that this is not the right way to kill an app.

So what _is_ the right way to kill an app anyway?
o Isn't there a graceful way to view & kill running apps in Android 9?
--
Usenet is so much more valuable, and pleasant, when people share ideas.

[Arlen Holder]

On Sun, 6 Sep 2020 00:34:59 -0000 (UTC), Arlen Holder wrote:

> <https://groups.google.com/forum/#!original/comp.mobile.android/ScA7PlwKeYs/T4MxR349AgAJ>
> Gremlin
> If you know of an app that actually does as you and I both want,
> please post about it. I'm presently using KillApps v1.19.2 by
> Ouadban Youssef

I'm not at all sure why this post from Gremlin didn't show in _any_ of my
feeds (I accidentally found it in the dejagoogle record), where I simply
ask for a more explicit pointer to the app by name:
<https://play.google.com/store/search?q=killapps&c=apps>

It's likely this one, I think (note it's called "killall" & "killapps"):
o KillApps : Close all apps running, by Tafayor Tech
<https://play.google.com/store/apps/details?id=com.tafayor.killall>

However, the search found too many to list, for example:
o KillAll, by soynerdito
<https://play.google.com/store/apps/details?id=com.chocodev.killall>

And plenty, reputedly, of others to test:
o Force Stop Apps (No root), by Boot Studio
<https://play.google.com/store/apps/details?id=com.force.stop.app>

o Advanced Task Manager, by Infolife
<https://play.google.com/store/apps/details?id=mobi.infolife.taskmanager>

o Background Apps and Process List: Find, close apps, by Vishnu NK
<https://play.google.com/store/apps/details?id=io.github.visnkmr.bapl>

o AppKiller - Close All Apps, by DP Soft
<https://play.google.com/store/apps/details?id=com.dp.appkiller>

o App Task Killer - Kill apps running in background, by Entsien
<https://play.google.com/store/apps/details?id=com.killrunningapps.taskkiller>

o Kill Apps: Close All Running Apps, by Stylist Manager App
<https://play.google.com/store/apps/details?id=stylistapp.killapps.appclosestopper>

o KillerApp Advanced Task Killer, by MCStealth Apps
<https://play.google.com/store/apps/details?id=com.mcstealthapps3.killerapp>

o Ultra Task Killer, Night Wind
<https://play.google.com/store/apps/details?id=com.nw.ultrataskkiller>

This list goes on forever but it's likely none do what we want.

I had already tested "Greenify" which failed to work as desired.
(See my other thread for the details and screenshots.)

o I'll test out this KilLApps 1.19.2.409 on Android 10 (Moto G7)
com.tafayor.killall, GSF Dependent, Has ads
<https://play.google.com/store/apps/details?id=com.tafayor.killall>

Given I prefer to be GSF Independent with no ads, I'll also try:
o Close ALL Applications, by Artefatos, br.com.artefatos>
<https://play.google.com/store/apps/details?id=br.com.artefatos>
--
Usenet allows us to pool our limited resources to help each other.

[The Real Bev]

Camera
ES File explorer
Several GPS walk/bike path-tracking apps (NOT OSMand, which is a REAL
gobbler)
Gallery
A couple of snore-recording things
Bank check-deposit
Quite a few others on a sporadic basis, but I always get rid of ALL OF
them when I'm done with them. Or so I thought.

> Not to start an argument but are the apps actually "running" or are
> then just in memory? I ask as Linux certainly retains a lot of apps in
> memory that are "Sleeping" and apparently not using power and as
> Android is based on Linux it might be the same.

I have no idea. It's just annoying when I lay the thing down, come back
in two hours and see 70% battery remaining when I haven't done anything.

> As an example using Linux Mint, at the moment, I find that I have some
> 89 functions listed of which 82 are sleeping and 50 were labeled as
> "polling" or in other words they are there in memory, sleeping at the
> moment, but wake up periodically to see if anyone wants them.

I found a lot of services etc. that had been in memory for quite a
while, but no indication of what, if anything, they might be using
battery power for.

Asking the battery what's been using it is generally useless. The
result it provides is only a small part of the decrease in battery power.


--
Cheers, Bev
"If you like to stand on your head and spit pickles in the snow, on the
Internet there are at least three other people just like you."
- Langston James Goree VI

[The Real Bev]

On 09/05/2020 05:34 PM, Arlen Holder wrote:

> Here's the scenario of today:
> a. Earlier I ran the "Open Tracks" program to create a GPX track.
> b. Then I swiped (many times during the day) to kill all running apps.
> c. Yet Open Tracks is _still_ running (it says it's "Paused").
>
> Well, I want to _kill_ Open Tracks (not just "Pause" it)!
> o There's no exit in the program itself anywhere!
> <https://i.postimg.cc/ydJJGkxw/pskill01.jpg>

Have you tried Open GPS? It looks really useful, except it just shows a
straight line between the start, some point on my walk and then a
straight line back home. I've saved FOUR such tracks. I'd really like
that app to work, but this is just weird and I can't find a setting that
would seem to control this. Why would anyone want it? It's not even
the FARTHEST point from my start that it defines as the turnaround point.

> So what _is_ the right way to kill an app anyway?
> o Isn't there a graceful way to view & kill running apps in Android 9?

...or A10.

[John B.]

On Sat, 5 Sep 2020 19:35:09 -0700, The Real Bev <bashl...@gmail.com>
wrote:

It might just be your phone. Try shutting off, restart, start no apps,
no wifi, bluetooth, location or other functions that might require
power, lay the phone down and come back in two hours and check the
battery. I have an older model Samsung - read smaller - that I use on
bicycle rides solely to make or receive calls, and with no apps
started by me the battery still runs down. Although not in two hours
:-)

I did check how Android handles memory and it seems, at least from a
rather quick look, it just like Linux in that when an application is
loaded it remains in memory until added memory space is required even
though you are not using it.

You might also download an app like "DevCheck" that will tell you how
much memory is being used. On my phone from a shutdown and restart
with no apps started by me 2.4 GB out of 5.5 GB of RAM is used.
--
Cheers,

John B.

[The Real Bev]

On 09/05/2020 10:22 PM, John B. wrote:

> I did check how Android handles memory and it seems, at least from a
> rather quick look, it just like Linux in that when an application is
> loaded it remains in memory until added memory space is required even
> though you are not using it.
>
> You might also download an app like "DevCheck" that will tell you how
> much memory is being used. On my phone from a shutdown and restart
> with no apps started by me 2.4 GB out of 5.5 GB of RAM is used.

Does memory usage correlate to battery usage? I was under the
impression that unused memory was wasted memory.

--
Cheers, Bev
Some mornings it's just not worth chewing through the straps.

[John B.]

On Sat, 5 Sep 2020 22:51:29 -0700, The Real Bev <bashl...@gmail.com>
wrote:

>On 09/05/2020 10:22 PM, John B. wrote:
>
>> I did check how Android handles memory and it seems, at least from a
>> rather quick look, it just like Linux in that when an application is
>> loaded it remains in memory until added memory space is required even
>> though you are not using it.
>>
>> You might also download an app like "DevCheck" that will tell you how
>> much memory is being used. On my phone from a shutdown and restart
>> with no apps started by me 2.4 GB out of 5.5 GB of RAM is used.
>
>Does memory usage correlate to battery usage? I was under the
>impression that unused memory was wasted memory.

RAM essentially is memory that is accessible by the CPU. To "run" a
program it, or portions of it, are copied from storage into RAM where
the CPU can access the code. But if a program is stopped the code
isn't normally removed from RAM it just lays there and the CPU uses
some other code that has been loaded into a different part of RAM.
Ultimately RAM might become totally filled with code, some of which is
not being used and when the next program is loaded it overwrites
sections of RAM that is not being used.

This is a really simplified description as there is, for example quite
a lot of code loaded into RAM that is used by the operating system
itself and all of the little bits and pieces needed to provide the
phone's basic functions. There would be, for example some code that
watched for the "power button" to be pushed and would turn the screen
on when that happened.

Code in RAM can be, basically, in several categories, code currently
being used, sleeping code that might be used if required and unused
code so simply wiping unused code out of the RAM doesn't really
accomplish anything as it isn't being used anyway.

From an operational point of view unused ram is important in that it
takes some time for code to be copied from storage to RAM where the
CPU can access it and so a large amount of RAM will usually result in
a much faster machine than one where every time some piece of code is
needed it has to be copied from storage.
--
Cheers,

John B.

[Arlen Holder]

On Sun, 06 Sep 2020 14:48:16 +0700, John B. wrote:

> From an operational point of view unused ram is important in that it
> takes some time for code to be copied from storage to RAM where the
> CPU can access it and so a large amount of RAM will usually result in
> a much faster machine than one where every time some piece of code is
> needed it has to be copied from storage.

As a related aside, we discussed RAM usages in the dejagoogle record here:
o How does RAM memory management truly compare between Android & iOS
<https://groups.google.com/forum/#!topic/comp.mobile.android/cR7GdXT1Nxg>

And here:
o Does a smartphone really need 8GB of RAM (the author says if you need
8GB to 12GB of RAM, get a Windows laptop instead)
<https://groups.google.com/forum/#!topic/comp.mobile.android/wdsIpkhNhMI>

My "task-kill" issue is simply that some programs (e.g., Open Tracks) seem
to be designed to run without a GUI available to kill them.

o What's a good way to kill jobs that persist in the background

<https://groups.google.com/forum/#!topic/comp.mobile.android/Did0Rd3mRmo>

In Linux, it's extremely common to search for any given running process:
o ps -auxww (look for all processes using a wide window)
o | grep OpenTracks (then filter out all but the task you're seeking)
o kill -9 PID (then kill that process you found in the ps -aux|grep

All I'd want to do is the same thing... but for Android.
--
Usenet allows us to pool our knowledge to provide solutions for everyone.

[The Real Bev]

On 09/06/2020 01:14 AM, Arlen Holder wrote:
> On Sun, 06 Sep 2020 14:48:16 +0700, John B. wrote:
>
>> From an operational point of view unused ram is important in that it
>> takes some time for code to be copied from storage to RAM where the
>> CPU can access it and so a large amount of RAM will usually result in
>> a much faster machine than one where every time some piece of code is
>> needed it has to be copied from storage.

"Yes, but did she DO it?"

If stuff is just sitting in RAM, is memory being used to store it? Does
it need to be constantly flashed, or is it happy to just sit there
asleep and wait for orders?

> As a related aside, we discussed RAM usages in the dejagoogle record here:
> o How does RAM memory management truly compare between Android & iOS
> <https://groups.google.com/forum/#!topic/comp.mobile.android/cR7GdXT1Nxg>
>
> And here:
> o Does a smartphone really need 8GB of RAM (the author says if you need
> 8GB to 12GB of RAM, get a Windows laptop instead)
> <https://groups.google.com/forum/#!topic/comp.mobile.android/wdsIpkhNhMI>
>
> My "task-kill" issue is simply that some programs (e.g., Open Tracks) seem
> to be designed to run without a GUI available to kill them.
> o What's a good way to kill jobs that persist in the background
> <https://groups.google.com/forum/#!topic/comp.mobile.android/Did0Rd3mRmo>
>
> In Linux, it's extremely common to search for any given running process:
> o ps -auxww (look for all processes using a wide window)
> o | grep OpenTracks (then filter out all but the task you're seeking)
> o kill -9 PID (then kill that process you found in the ps -aux|grep

'top' is a lovely program, and it can be configured SOOO many ways.

> All I'd want to do is the same thing... but for Android.

I conclude that people (or developers, at least) don't really care about
how quickly the battery runs down. It's not like we're out in the
middle of the desert with no way to recharge... Oh, wait, we DO have
portable charging units that are bigger than the phone. Never mind.

FWIW, maybe 5 years ago there were places on the main roads in Death
Valley with no cell coverage. Friends broke an axle in a pothole near
one. Once again we need to rely on the kindness of strangers to pass on
the Help! message...

[Ken Blake]

On 9/6/2020 8:40 AM, The Real Bev wrote:

>> As a related aside, we discussed RAM usages in the dejagoogle record here:
>> o How does RAM memory management truly compare between Android & iOS
>> <https://groups.google.com/forum/#!topic/comp.mobile.android/cR7GdXT1Nxg>
>>
>> And here:
>> o Does a smartphone really need 8GB of RAM (the author says if you need
>> 8GB to 12GB of RAM, get a Windows laptop instead)

Great idea! Does he a recommend a laptop that will fit in my pocket?

--
Ken

[Anssi Saari]

The Real Bev <bashl...@gmail.com> writes:

> They should ALL be required to have an easy way to kill them
> deliberately. I wondered why my Pixel2 was such a heavy battery-user
> even in airplane mode with location and bluetooth turned off and NO
> RECENT ITEMS (I flicked everything 'up' that I had been using) showing
> in the <little square> window.

Killing apps like that doesn't do much. As you discovered. There's a
developer setting to do same too, if you like. Called "Don't keep
activities".

As for stuff running in the background... Well, good luck with
that. I've tried to use battery monitors like Better Battery Stats or
GSam battery monitor but they usually can't tell me what it is that's
hogging the battery. That was more of a problem in my old HTC 10 phone,
HTC put in some weird stuff which was probably the problem.

On my current phone (Oneplus 6) I've had the opposite issue: nothing
runs in the background. I had to turn off the most arduous background
killer features Oneplus ships and seem to have decent balance now.

[Mark Blain]

The Real Bev <bashl...@gmail.com> wrote in
news:rj13lp$34b$1...@dont-email.me:

> They should ALL be required to have an easy way to kill them
> deliberately. I wondered why my Pixel2 was such a heavy
> battery-user even in airplane mode with location and bluetooth
> turned off and NO RECENT ITEMS (I flicked everything 'up' that I
> had been using) showing in the <little square> window.
>
> It takes the phone minutes to turn off and then on, but RESTART
> goes pretty quickly and seems to kill whatever was running in the
> background invisibly and eating battery.
>
> When I want something off I want it OFF. I don't care how long it
> takes to restart an app -- generally only a few seconds.

For me, step 1 is to find out what's actually running in background,
and whether stopping it, changing that app's settings/restrictions,
temporarily disabling or even uninstalling it improves battery life.
https://www.bestusefultips.com/view-running-processes-and-cpu-usage-
in-android-oreo/
You could try the power saver/battery saver settings, but that can
have unwanted side effects. I like to work app-by-app before I make
wider changes.
https://support.google.com/pixelphone/answer/6187458?hl=en

[The Real Bev]

On 09/06/2020 09:32 AM, Anssi Saari wrote:
> The Real Bev <bashl...@gmail.com> writes:
>
>> They should ALL be required to have an easy way to kill them
>> deliberately. I wondered why my Pixel2 was such a heavy battery-user
>> even in airplane mode with location and bluetooth turned off and NO
>> RECENT ITEMS (I flicked everything 'up' that I had been using) showing
>> in the <little square> window.
>
> Killing apps like that doesn't do much. As you discovered. There's a
> developer setting to do same too, if you like. Called "Don't keep
> activities".

OOOOH! I just found and tried that! We'll see...

> As for stuff running in the background... Well, good luck with
> that. I've tried to use battery monitors like Better Battery Stats or
> GSam battery monitor but they usually can't tell me what it is that's
> hogging the battery. That was more of a problem in my old HTC 10 phone,
> HTC put in some weird stuff which was probably the problem.
>
> On my current phone (Oneplus 6) I've had the opposite issue: nothing
> runs in the background. I had to turn off the most arduous background
> killer features Oneplus ships and seem to have decent balance now.

--
Cheers, Bev
"A democracy cannot exist as a permanent form of government. It can
only exist until a majority of voters discover that they can vote
themselves largess out of the public treasury."
-- Alexander Tyler (Unverified)

[The Real Bev]

"Location services stop when your screen is off."

That's a killer right there! It might explain the
point-to-point-to-point GPS display -- I seem to remember turning on the
battery-saver function for a while, and then realizing that I don't want
that. Crap, those midpoints might be where I took a picture... I need
to try that app again.

[Arlen Holder]

On Sun, 06 Sep 2020 19:32:17 +0300, Anssi Saari wrote:

> Killing apps like that doesn't do much.
> As you discovered.

I'm gonna agree with Anssi Sarri, The Real Bev, and others.

However...
o What if you have _one_ app you want to kill?

Like Open Tracks?
o <https://f-droid.org/en/packages/de.dennisguse.opentracks/>

Or like OSMAnd~ sometimes?
o <https://f-droid.org/en/packages/net.osmand.plus/>

Given I use GPS only when necessary, both have a tendency to live longer
than I want them to, in terms of me closing down the app (but they live on
until reboot).

How would you close just those specific apps?
--
Usenet allows normal people to pool our resources to solve issues.

[123456789]

The Real Bev wrote:

> Arlen Holder wrote:

>> Does a smartphone really need 8GB of RAM (the author says if you
>> need 8GB to 12GB of RAM, get a Windows laptop instead)

I don't *need* my 8GB of RAM, but it sure helps make for a smooth speedy
phone.

> I conclude that people (or developers, at least) don't really care
> about how quickly the battery runs down.

Depends on the phone's design and use. I generally get 3 days out of
mine but perhaps its 4100 mAh battery helps out a bit...

> FWIW, maybe 5 years ago there were places on the main roads in Death
> Valley with no cell coverage.

Lots of places with no coverage in the deserts of my state. Unprepared
people occasionally die there. Course unprepared people sometimes die in our
city mountain park trails too, especially in summer, even with cell
coverage. (My back porch thermometer currently says 114F)...

[John B.]

On Sun, 6 Sep 2020 08:40:18 -0700, The Real Bev <bashl...@gmail.com>
wrote:

>On 09/06/2020 01:14 AM, Arlen Holder wrote:
>> On Sun, 06 Sep 2020 14:48:16 +0700, John B. wrote:
>>
>>> From an operational point of view unused ram is important in that it
>>> takes some time for code to be copied from storage to RAM where the
>>> CPU can access it and so a large amount of RAM will usually result in
>>> a much faster machine than one where every time some piece of code is
>>> needed it has to be copied from storage.
>
>"Yes, but did she DO it?"
>
>If stuff is just sitting in RAM, is memory being used to store it? Does
>it need to be constantly flashed, or is it happy to just sit there
>asleep and wait for orders?

I'm not sure but I believe that RAM requires a constant supply of
power whether it is used or not. I know that when calculating power
requirements a constant is used for RAM based on size.

>
>> As a related aside, we discussed RAM usages in the dejagoogle record here:
>> o How does RAM memory management truly compare between Android & iOS
>> <https://groups.google.com/forum/#!topic/comp.mobile.android/cR7GdXT1Nxg>
>>
>> And here:
>> o Does a smartphone really need 8GB of RAM (the author says if you need
>> 8GB to 12GB of RAM, get a Windows laptop instead)
>> <https://groups.google.com/forum/#!topic/comp.mobile.android/wdsIpkhNhMI>
>>
>> My "task-kill" issue is simply that some programs (e.g., Open Tracks) seem
>> to be designed to run without a GUI available to kill them.
>> o What's a good way to kill jobs that persist in the background
>> <https://groups.google.com/forum/#!topic/comp.mobile.android/Did0Rd3mRmo>
>>
>> In Linux, it's extremely common to search for any given running process:
>> o ps -auxww (look for all processes using a wide window)
>> o | grep OpenTracks (then filter out all but the task you're seeking)
>> o kill -9 PID (then kill that process you found in the ps -aux|grep
>
>'top' is a lovely program, and it can be configured SOOO many ways.
>
>> All I'd want to do is the same thing... but for Android.
>
>I conclude that people (or developers, at least) don't really care about
>how quickly the battery runs down. It's not like we're out in the
>middle of the desert with no way to recharge... Oh, wait, we DO have
>portable charging units that are bigger than the phone. Never mind.
>

Well, reading the specs for a new phone I don't remember ever seeing
anything about how long the battery lasted :-)

>FWIW, maybe 5 years ago there were places on the main roads in Death
>Valley with no cell coverage. Friends broke an axle in a pothole near
>one. Once again we need to rely on the kindness of strangers to pass on
>the Help! message...
--
Cheers,

John B.

[123456789]

123456789 wrote:

> The Real Bev wrote:

>> I conclude that people (or developers, at least) don't really care
>> about how quickly the battery runs down.

> Depends on the phone's design and use. I generally get 3 days out of
> mine but perhaps its 4100 mAh battery helps out a bit...

There's always someone that has one bigger than yours. And size does
matter... ;)

"It looks like Motorola is about to announce a second entry in its
budget G9 phone lineup, just weeks after it revealed the Moto G9
Play....and a massive 5,000 mAh battery."

<https://www.theverge.com/2020/9/7/21425804/motorola-moto-g9-plus-news-features-64-megapixel-quad-camera-5000-mah-battery-play>

[nospam]

In article <rj8ug2$r2$1...@dont-email.me>, 123456789 <12...@12345.com>
wrote:

> > Depends on the phone's design and use. I generally get 3 days out of
> > mine but perhaps its 4100 mAh battery helps out a bit...
>
> There's always someone that has one bigger than yours. And size does
> matter... ;)
>
> "It looks like Motorola is about to announce a second entry in its
> budget G9 phone lineup, just weeks after it revealed the Moto G9
> Play....and a massive 5,000 mAh battery."
>
>
> <https://www.theverge.com/2020/9/7/21425804/motorola-moto-g9-plus-news-feature
> s-64-megapixel-quad-camera-5000-mah-battery-play>

as you say, there's always someone that has one bigger than yours, this
time it's a lot bigger.

<https://www.theverge.com/circuitbreaker/2019/2/26/18241117/energizer-po
wer-max-p18k-pop-huge-battery-phone-mwc-2019>
I told you MWC 2019 would be a show where things got weird, but
even I didnšt anticipate a company being wild enough to build a phone
with an 18,000 mAh battery.

[123456789]

nospam wrote:

> 123456789 wrote:

>>> Depends on the phone's design and use. I generally get 3 days out of
>>> mine but perhaps its 4100 mAh battery helps out a bit...

>> There's always someone that has one bigger than yours. And size does
>> matter... ;)

>> "It looks like Motorola is about to announce a second entry in its
>> budget G9 phone lineup, just weeks after it revealed the Moto G9
>> Play....and a massive 5,000 mAh battery."

>> <https://www.theverge.com/2020/9/7/21425804/motorola-moto-g9-plus-news-feature
>> s-64-megapixel-quad-camera-5000-mah-battery-play>

> as you say, there's always someone that has one bigger than yours, this
> time it's a lot bigger.

Then again maybe not this time...

"The phone with the biggest battery in the world has been canceled"

<https://www.phonearena.com/news/phone-biggest-battery-in-the-world-canceled-energizer_id115688>

> <https://www.theverge.com/circuitbreaker/2019/2/26/18241117/energizer-po
> wer-max-p18k-pop-huge-battery-phone-mwc-2019>
> I told you MWC 2019 would be a show where things got weird, but

> even I didn¹t anticipate a company being wild enough to build a phone

[nospam]

In article <rj94bo$f8m$1...@dont-email.me>, 123456789 <12...@12345.com>

wrote:

> >>> Depends on the phone's design and use. I generally get 3 days out of
> >>> mine but perhaps its 4100 mAh battery helps out a bit...
>
> >> There's always someone that has one bigger than yours. And size does
> >> matter... ;)
>
> >> "It looks like Motorola is about to announce a second entry in its
> >> budget G9 phone lineup, just weeks after it revealed the Moto G9
> >> Play....and a massive 5,000 mAh battery."
>
> >>
> >> <https://www.theverge.com/2020/9/7/21425804/motorola-moto-g9-plus-news-feat
> >> ure
> >> s-64-megapixel-quad-camera-5000-mah-battery-play>
>
> > as you say, there's always someone that has one bigger than yours, this
> > time it's a lot bigger.
>
> Then again maybe not this time...
>
> "The phone with the biggest battery in the world has been canceled"

yep. nobody wants to carry a brick.

however, energizer did think it would be a good idea...


>
> <https://www.phonearena.com/news/phone-biggest-battery-in-the-world-canceled-e

> nergizer_id115688>
>
> > <https://www.theverge.com/circuitbreaker/2019/2/26/18241117/energizer-po
> > wer-max-p18k-pop-huge-battery-phone-mwc-2019>
> > I told you MWC 2019 would be a show where things got weird, but

> > even I didn1t anticipate a company being wild enough to build a phone

[visiblink]

The Real Bev <bashl...@gmail.com> Wrote in message:

I use Ghost Commander to kill apps. It works well for killing
Android apps on BlackBerry 10 too.


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

[Arlen Holder]

On Sat, 5 Sep 2020 15:32:23 -0700, The Real Bev wrote:

> They should ALL be required to have an easy way to kill them
> deliberately. I wondered why my Pixel2 was such a heavy battery-user
> even in airplane mode with location and bluetooth turned off and NO
> RECENT ITEMS (I flicked everything 'up' that I had been using) showing
> in the <little square> window.
>
> It takes the phone minutes to turn off and then on, but RESTART goes
> pretty quickly and seems to kill whatever was running in the background
> invisibly and eating battery.
>
> When I want something off I want it OFF. I don't care how long it takes
> to restart an app -- generally only a few seconds.

Woo hoo!
o I found a simple way to kill background audio in a couple of steps!
<https://i.postimg.cc/2yz3rw2N/pskill05.jpg>

Most apps die gracefully when you hit the square button & sweep them away.
o And almost all apps will die when you expressly press its "exit" command
<https://i.postimg.cc/wTj3rw1h/pskill04.jpg>

Yet some still run (e.g., nav) or play (e.g., audio) in the background.
o Either because you can't exit - or you background it as shown above

That's nice when you _want_ navigation or audio playing in the background.
o But sometimes you want _kill_ those background apps (sans rebooting)

It turns out there are _plenty_ of ways to kill background apps, e.g.,
o Developer options <https://i.postimg.cc/JzrfLbpb/pskill01.jpg>
o App info <https://i.postimg.cc/sD3JTyf2/pskill02.jpg>
o Home button <https://i.postimg.cc/KYTLZscV/pskill03.jpg>
o Notification X <https://i.postimg.cc/mrnhQ8qH/audio08.jpg>
etc.

For more information, please see these related threads:
o REALLY kill various apps
<https://groups.google.com/forum/#!topic/comp.mobile.android/ScA7PlwKeYs>

o What's a good way to kill jobs that persist in the background (without having to reboot)?
<https://groups.google.com/forum/#!topic/comp.mobile.android/Did0Rd3mRmo>

o Samsung Galaxy S5
<https://groups.google.com/g/comp.mobile.android/c/qTMDmHP9ToI>
--
Together we can find the simplest solutions to all issues we want to solve.