Related
Hi,
We all knew that we should not use task killer to kill apps, because when we hit the back button, the app will not active anymore ... but it will still occupy some memory (RAM).
When Android OS needs more RAM it will remove in-active apps to free some.
Related article: http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (GOOD READ)
We should not panic when we see a huge list of apps when we start task killer.
Ok, got it there ...
Now, I installed this app called Quick System Info (FREE):
http://www.cyrket.com/p/android/org.uguess.android.sysinfo/
Which you can use to see what kind of processes are still running or apps that are still occupying RAM. It could show you the amount of RAM and CPU resources that are being used by each app.
So, I went to the Quick System Info -> Processes, hit the "menu" button -> Preferences and set like this:
- Update Speed = Low
- Show Memory Usage [checked]
- Show CPU Usage [checked]
- Sort by = CPU Usage
- Direction = Descending
Go back and watch ...
Surprisingly, I saw "Market" app is eating 1% CPU resources once in a while ... again and again ...
Hey, I thought it (Market app) is suspended in the background? I don't have it active, I pressed the back button when I finished with it.
Why is it eating 1% CPU from now an then in the background?
Obviously, this will drain battery power for something that I don't need.
Any thought?
I am now wondering if I install other kind of process monitoring app, and see if the suspended Quick System Info is also eating CPU resources
Why should we not use task killers? I`ve used them on android for the last year otherwise like you say background tasks use resources slowing up the system.
Obviously dont close any system important apps but I`m always closing down background apps that I no longer require.
1% every now and again? I really wouldn't worry about that to be perfectly honest. The impact on battery life will be incredibly small, so much so I doubt you'd even notice if you weren't watching it like a hawk.
By far the biggest drain on battery life remains all of the wireless stuff (wifi, bluetooth and 3G internet) followed closely by the screen itself. Turn those off when not in use and the miniscule drain of suspended tasks won't be an issue.
I'm sure if Google thought suspended tasks would be an important factor in battery drain they would've designed it differently to start with.
Read this article
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
paulruk said:
Why should we not use task killers? I`ve used them on android for the last year otherwise like you say background tasks use resources slowing up the system.
Obviously dont close any system important apps but I`m always closing down background apps that I no longer require.
Click to expand...
Click to collapse
It does every minute or so, and so far I found only this app (Market).
I just found out this morning before went to work, so I don't have time to inspect more.
Too bad I cannot see CPU TIME (the amount of time the process took 100% of cpu resources).
Noiz said:
1% every now and again? I really wouldn't worry about that to be perfectly honest. The impact on battery life will be incredibly small, so much so I doubt you'd even notice if you weren't watching it like a hawk.
By far the biggest drain on battery life remains all of the wireless stuff (wifi, bluetooth and 3G internet) followed closely by the screen itself. Turn those off when not in use and the miniscule drain of suspended tasks won't be an issue.
I'm sure if Google thought suspended tasks would be an important factor in battery drain they would've designed it differently to start with.
Click to expand...
Click to collapse
that 1% would be it occasionally checking in with the market to see if any updates have been released for the programs you have installed, so that it can give you a notification when the update is released.
i would imagine that is what it is anyway.
and yes, 1% every so often is negligible, and if you killed just that process, i doubt you would notice any difference.
gogol said:
Surprisingly, I saw "Market" app is eating 1% CPU resources once in a while ... again and again ...
Hey, I thought it (Market app) is suspended in the background? I don't have it active, I pressed the back button when I finished with it.
Why is it eating 1% CPU from now an then in the background?
Obviously, this will drain battery power for something that I don't need.
Any thought?
Click to expand...
Click to collapse
I am not sure about this..
Have you noticed that you will get a notification if there is an update to application that is installed in your phone?
I think the marketplace doesn't have a push notification yet. So it periodically will check whether there is any update to the installed application.
Allright, that might be it ... the Market is checking for apps aupdate.
And most probably 1% is not much (I don't know how to measure this and translate it to battery life time). 1% every minute ... hmmm
1 hour of 1% cpu per minute = X % of battery life.
If we have N processes?
N = email check, weather check, friendstream check, RSS check, whatnot check
I`ll give you an example why I use a task killer.
Sometimes I use an app that goes online every few minutes and notifies me of any updates. I can 100% be certain this app even when in the background uses enough cpu to cause the phone to slowdown. Dont ask me why, maybe bad programming but this is the exact reason why I need a task killer to get rid of it.
Once its gone the phone is fine again. it happends on a few apps I own, so when I finish with them, I kill them.
I wouldnt recommend a task killer that kills everything, you just need to be selective.
That is a perfect example for using task killer
What I wrote in the first post is about using task killer to just kill apps without knowing anything.
In the past, I just select all and KILL ... Then the HTC Sense got reloaded
I was scared it could corrupt my phone ... lol.
paulruk said:
I`ll give you an example why I use a task killer.
Sometimes I use an app that goes online every few minutes and notifies me of any updates. I can 100% be certain this app even when in the background uses enough cpu to cause the phone to slowdown. Dont ask me why, maybe bad programming but this is the exact reason why I need a task killer to get rid of it.
Once its gone the phone is fine again. it happends on a few apps I own, so when I finish with them, I kill them.
I wouldnt recommend a task killer that kills everything, you just need to be selective.
Click to expand...
Click to collapse
Yes thats a bit extreme killing everything.
I`ve also used startup auditor in the past. That stops some apps loading at startup , for example footprints, never use it so I kill it before it gets a chance to load up. Have to be careful what you limit though as some tasks are used by others.
That Startup Auditor is interesting, does it work as expected?
Or you encountered some quirks or issues with it?
Yeah, I don't quite like with the way Android startup (or HTC?), for example: FM radio ... it also started automatically after reboot.
paulruk said:
Yes thats a bit extreme killing everything.
I`ve also used startup auditor in the past. That stops some apps loading at startup , for example footprints, never use it so I kill it before it gets a chance to load up. Have to be careful what you limit though as some tasks are used by others.
Click to expand...
Click to collapse
gogol said:
That Startup Auditor is interesting, does it work as expected?
Or you encountered some quirks or issues with it?
Yeah, I don't quite like with the way Android startup (or HTC?), for example: FM radio ... it also started automatically after reboot.
Click to expand...
Click to collapse
Seems to work fine, not sure what help it is though hehe, in terms of speed/memory savings. I stop the radio , bluetooth,google talk and footprints. But I also use it to start some apps automatically.
I found this list of what you can/can`t disable. You can still run them after startup, just they wont load automatically when you start the phone.
safe
Google Partner Setup
Network Location (if not using apps which need geolocation regularly. ie. Gmaps, GeoTag, etc.)
Bluetooth Share (if not using BT device)
Email (if not using email service other than Gmail)
Messaging (if using 3rd party sms app, ie. Handcent SMS. or if infrequent texter)
Calendar (if calendar is not used regularly)
Calendar Storage (if calendar is not used regularly)
Voice Dialer (if not used)
Google Talk Service (if GTalk is not used regularly)
Maps (if GMaps is not used regularly)
unsafe
Clock
Media Storage
Android System
Gmail Storage
Sync Feeds
Dialer
System Updater (not sure about this one)
My Uploads (not sure about this one)
Download Manager (not sure about this one)
I understand the rationale behind not killing tasks, but i checked out the bbc news app earlier, and it runs a service (i could see it via a task manager). I couldn't then kill the service by using the bbc app. Should I be not killing services, and if so, aren't I going to end up potentially running several services unneccessarily?
I don't think there's any harm in killing services if you really want to, but the OS is supposed to do a good job of killing services if another application is in need of the resources being taken up by something you haven't actually used for a while.
Some seem desperate to kill every task possible to save an extra few minutes of battery life though.
moshbeard said:
I don't think there's any harm in killing services if you really want to, but the OS is supposed to do a good job of killing services if another application is in need of the resources being taken up by something you haven't actually used for a while.
Some seem desperate to kill every task possible to save an extra few minutes of battery life though.
Click to expand...
Click to collapse
I'm happy with the OS doing that sort of thing, but I want control over services which use battery and consume data.
task managers actually end up costing you more battery, having that constantly killing tasks causes them to restart using the CPU which drains the battery. much better to just back out of an app and leave in "idle"
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
hager420 said:
task managers actually end up costing you more battery, having that constantly killing tasks causes them to restart using the CPU which drains the battery. much better to just back out of an app and leave in "idle"
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Doesn't really address my question specifically about services, and the data/battery they consume. If I load the BBC news widget/app and it fires off a service to keep the news up to date, then I quit, but I can still see the service running (not sleeping or whatever) then it's using my battery and potentially still get data and I want it to stop. Have you used the BBC news app? Can you see the service running after you've quit the front end? How would you stop it? How about malicious apps?
Since reading that task killers are 'bad' I've got rid of all mine, but I dedided to keep jkAppSwitch on my long press of the search button. Mainly I use it for switching between apps easily but it can be used to manually kill things so that's cool, I rarely kill apps now since what I read here but in special needs circumstances I have that power.
Two birds with one stone and all that.
oursoul said:
Since reading that task killers are 'bad' I've got rid of all mine, but I dedided to keep jkAppSwitch on my long press of the search button. Mainly I use it for switching between apps easily but it can be used to manually kill things so that's cool, I rarely kill apps now since what I read here but in special needs circumstances I have that power.
Two birds with one stone and all that.
Click to expand...
Click to collapse
Since my post, I've been playing with Fring, and I've stopped now and logged out. I look at the running services and I can see:
Process: com.fring
CallService
Started by application: touch to stop
Well, I don't want to have to fiddle with settings and kill stuff. I've logged out, then quit (pressed back - there's no 'quit' other than 'log out'). This isn't the only app that does this. I understand entirely the deal with Android managing apps, but it seems that this "service killer":
menu/settings/applications/running services
is required if you want to save cpu time, battery and possibly bandwidth. Should I have to do this? Or is this app badly behaved?
can automatically stop certain programs from auto-starting? I downloaded the wonderful Elixir 2 program and it showed me (and yes, I know that the OS would have showed as well), that apps like Stocks, First Aid, and Trillian were loaded/running even though I had not started these apps since the last reboot.
Is there a way to stop rogue apps from autostarting?
Why do you need to stop them? What makes you think that they shouldn't start?
???
Well, I am not sure WHY they need to start, but I am sure that they take up memory. "First Aid" is certainly an app that can start up when needed, no need to run in the background. Same for the others.
That said, the original question remains. Anyone know of an app that can adjust the autostart of apps that have no business starting automatically?
Haven't tried it but may be worth a look:
http://www.appbrain.com/app/autorun-manager/com.rs.autorun
Interesting
First - Thank you for responding to the question! I have downloaded and run the app. It certainly professes to do what I was asking. Stopped some apps from loading, but others seem to be more persistent (does Titanium Backup need to run on boot? MyBackupPro? Don't think so). Thank you!
Read the hundreds of posts on task killers. Unless you are having a problem with a particular app, it is best left alone. If the memory being used for the app in question is "needed", android will kill it on its own.
Deleted because I realized I do not need to stoop to respond to nonhelpful posts (but really, people. when is "read random amorphous posts which are not on topic" a response).
only came across 2 apps that run constantly in background vs cached like their supposed to. Fbook and okcupid. autostart managers sorta work but they break functions
In a perfect world, every app on your device would start at boot and reside in RAM. I've never understood this idea that killing apps somehow conserves resources or saves power, because it does neither. In fact, it does the OPPOSITE. For instance, Trillian: Do you REALLY want to kill it whenever you're not using it, only to reopen it the next time you want to use it? That eats about 4 times more power than just leaving it running. NOTHING your cpu does eats more power than reading and writing to NAND. RAM should be as full as possible all of the time with as many apps as are recently or likely to be used. RAM operations consume FAR less power than NAND operations. Unless the app is simply an abusive piece of crap, like Amazon's market and music apps, there's usually a reason for them to run. Titanium Backup never starts unless it's got a reason to, in my experience, such as scheduled auto-backup operations. The better question to ask is why apps are starting at boot, not "Where can I get one more resource-hogging app to whip bad behavior into shape?"
loonatik78 said:
In a perfect world, every app on your device would start at boot and reside in RAM. I've never understood this idea that killing apps somehow conserves resources or saves power, because it does neither. In fact, it does the OPPOSITE. For instance, Trillian: Do you REALLY want to kill it whenever you're not using it, only to reopen it the next time you want to use it? That eats about 4 times more power than just leaving it running. NOTHING your cpu does eats more power than reading and writing to NAND. RAM should be as full as possible all of the time with as many apps as are recently or likely to be used. RAM operations consume FAR less power than NAND operations. Unless the app is simply an abusive piece of crap, like Amazon's market and music apps, there's usually a reason for them to run. Titanium Backup never starts unless it's got a reason to, in my experience, such as scheduled auto-backup operations. The better question to ask is why apps are starting at boot, not "Where can I get one more resource-hogging app to whip bad behavior into shape?"
Click to expand...
Click to collapse
I agree with this 100%.
Yes But
Yes - I get all that, but it bugs the heck out of me that some of these apps feel the need to auto run and worse still, are classified as "self restarter" by the recommended app.
On a cold power-up (I charge with the power off), and without running any apps (in response to the Titanium reference above), the following apps not only started, but restarted when stopped: Appstore, Ebay, Elixir, Mortplayer Audio Book, MyBackup Pro, ROM Manager, Stocks, Titanium Backup, Trillian, Wordsmith, and XDA. Mind you, I am not including apps that SHOULD start up (swype, timeriffic, lookout, etc).
Why any of those apps start on power-on is beyond me, and why almost all of them are set by their respective authors to restart if they are shut down, is even more perplexing. Hence my desire to try to reign them in, especially since they are taking 20MB each of RAM. That's the story
jdmba said:
Yes - I get all that, but it bugs the heck out of me that some of these apps feel the need to auto run and worse still, are classified as "self restarter" by the recommended app.
On a cold power-up (I charge with the power off), and without running any apps (in response to the Titanium reference above), the following apps not only started, but restarted when stopped: Appstore, Ebay, Elixir, Mortplayer Audio Book, MyBackup Pro, ROM Manager, Stocks, Titanium Backup, Trillian, Wordsmith, and XDA. Mind you, I am not including apps that SHOULD start up (swype, timeriffic, lookout, etc).
Why any of those apps start on power-on is beyond me, and why almost all of them are set by their respective authors to restart if they are shut down, is even more perplexing. Hence my desire to try to reign them in, especially since they are taking 20MB each of RAM. That's the story
Click to expand...
Click to collapse
Got me on a few of those, but other ones make all kinds of sense. Any app store sort of app is going to start to authenticate with the service. Amazon is known to do this abusively. The same would probably apply with audio books. MyBackup Pro is probably assuming there's a scheduled function to perform. Stocks is just part of Sense and it doesn't go away. TiBU has never started on any device I've had it on unless 1 of 2 things was the case; I ran the widget or had something scheduled. Trillian SHOULD start up because it's a chat client. If it's not running, it's not much good as a chat client. Not sure what Wordsmith is. XDA will start because it's set by default to sync on a regular basis if you're signed into it.
I don't know what to tell you. You're probably never going to find a way of permanently killing an app connected to a market, and if you do, whatever you use from that market probably won't work right. The best I can say is figure out why those apps you listed do what they do. There's probably a reason that can be fixed or better understood. Some, like Trillian, will self-start no matter what because failure to do so is a MUCH more aggravating issue than the app starting with nothing to do.
only 2 I have that aggravate me is Fbook and okcupid. understandable if both run and autostart for push capabilities but I've disabled sync and push and still runs in background vs cached in background like it's supposed to
dyetheskin said:
only 2 I have that aggravate me is Fbook and okcupid. understandable if both run and autostart for push capabilities but I've disabled sync and push and still runs in background vs cached in background like it's supposed to
Click to expand...
Click to collapse
I don't think Facebook is worried about their app being accused of greatness or winning development awards!
loonatik78 said:
In a perfect world, every app on your device would start at boot and reside in RAM. I've never understood this idea that killing apps somehow conserves resources or saves power, because it does neither. In fact, it does the OPPOSITE. For instance, Trillian: Do you REALLY want to kill it whenever you're not using it, only to reopen it the next time you want to use it? That eats about 4 times more power than just leaving it running. NOTHING your cpu does eats more power than reading and writing to NAND. RAM should be as full as possible all of the time with as many apps as are recently or likely to be used. RAM operations consume FAR less power than NAND operations. Unless the app is simply an abusive piece of crap, like Amazon's market and music apps, there's usually a reason for them to run. Titanium Backup never starts unless it's got a reason to, in my experience, such as scheduled auto-backup operations. The better question to ask is why apps are starting at boot, not "Where can I get one more resource-hogging app to whip bad behavior into shape?"
Click to expand...
Click to collapse
True however some of the apps that are residing in RAM, pop up and do updates and checks that do eat data and cpu than if they were killed. Most apps don't do this and typically it's bad to kill apps because the act of killing it uses CPU and especially the act of that app starting back up uses more CPU.
----
RAM is not an issue so don't even consider it one, even if your RAM is full it doesn't matter. This doesn't run like Windows does where things slow down if you don't have enough RAM.
Most apps that use resources in the background I uninstall, but for others (I think I only do this to 1 app) you can use "autostarts" to disable them from starting upon launch, or stopping them from starting upon other events that may trigger an app to automatically start
https://market.android.com/details?id=com.elsdoerfer.android.autostarts&hl=en
It has much more control over when apps automatically launch than the other app I saw posted on the main page- also it doesn't kill them, just prevents them from starting so it's not like an app killer.
Hope this was what you were looking for.
Let it be
Just let the programs start to let the phone fully awaken
Then kill the apps with any klling apps app task killers and so on
gutiejor said:
Just let the programs start to let the phone fully awaken
Then kill the apps with any klling apps app task killers and so on
Click to expand...
Click to collapse
No. Don't do this.
POQbum said:
True however some of the apps that are residing in RAM, pop up and do updates and checks that do eat data and cpu than if they were killed. Most apps don't do this and typically it's bad to kill apps because the act of killing it uses CPU and especially the act of that app starting back up uses more CPU.
----
RAM is not an issue so don't even consider it one, even if your RAM is full it doesn't matter. This doesn't run like Windows does where things slow down if you don't have enough RAM.
Most apps that use resources in the background I uninstall, but for others (I think I only do this to 1 app) you can use "autostarts" to disable them from starting upon launch, or stopping them from starting upon other events that may trigger an app to automatically start
https://market.android.com/details?id=com.elsdoerfer.android.autostarts&hl=en
It has much more control over when apps automatically launch than the other app I saw posted on the main page- also it doesn't kill them, just prevents them from starting so it's not like an app killer.
Hope this was what you were looking for.
Click to expand...
Click to collapse
I use autostarts also on startup and when I'm running I use auto memory manager both great apps
I have been using Autostarts for a long time now and am very pleased with it.
gutiejor said:
Just let the programs start to let the phone fully awaken
Then kill the apps with any klling apps app task killers and so on
Click to expand...
Click to collapse
I read that this is a bad habit carried over from pre-froyo days where memory management was different and this was recommended then. I don't have a link but trust me and don't just kill stuff like that.
Sent from my ADR6300 using Tapatalk
From my searching, even on other sites, supposedly this topic has been beaten to death, yet I can't seem to find much about it.
Basically, I would like to keep apps, like Facebook, Email, and Amazon Video, etc., from running until I start them up. Then I would like for them to close, and stay closed, when I'm not using them. In essence, act like a typical app.
All I have been able to find is that you can use a Task Killer to achieve this. But, the average opinion seems to be is that the TKs uses as much, if not more, resources repeatedly killing the constantly restarting apps as just letting the apps "run". Basically, I've yet to find out if it is or isn't possible to keep these apps from constantly restarting on their own.
The reason I want to make these changes is that when my memory gets full, my Fire will lock up, or slow down, for 30 seconds or so... sometimes longer. Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed... and never did the CPU go above 600Mhz (which is the min I have it set to).... which means it wasn't an issue with the CPU being overloaded.
So does anyone know of a way to keep these persistent apps from being persistent?
BTW, I'm running a pretty standard rooted Fire that I just re-did using the KFU v9.6 and all the "goodies" with it, like the GoLauncher.
TIA
PBFred said:
Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed...
Click to expand...
Click to collapse
It's true that, under normal circumstances, you shouldn't worry about it. It sounds like your system is simply lacking in memory because it has some high priority tasks eating it all away (Carousel + GO Launcher are probably hogging up a bunch already).
Seeing how you're running rooted Stock with Go Launcher and a bunch of other applications - have you considered switching to Modaco? It's based on Stock...
PBFred said:
So does anyone know of a way to keep these persistent apps from being persistent?
Click to expand...
Click to collapse
To answer this question, other than applying memory scripts, some task killers can be set to autoclose a pre-defined list of apps when you press a widget button - this may interest you. Look into the settings/options of the task killer you're using.
Maybe give this a shot?
https://play.google.com/store/apps/details?id=com.rs.autorun&hl=en
PBFred said:
From my searching, even on other sites, supposedly this topic has been beaten to death, yet I can't seem to find much about it.
Basically, I would like to keep apps, like Facebook, Email, and Amazon Video, etc., from running until I start them up. Then I would like for them to close, and stay closed, when I'm not using them. In essence, act like a typical app.
All I have been able to find is that you can use a Task Killer to achieve this. But, the average opinion seems to be is that the TKs uses as much, if not more, resources repeatedly killing the constantly restarting apps as just letting the apps "run". Basically, I've yet to find out if it is or isn't possible to keep these apps from constantly restarting on their own.
The reason I want to make these changes is that when my memory gets full, my Fire will lock up, or slow down, for 30 seconds or so... sometimes longer. Supposedly, the O/S is designed to keep as much in memory as possible and it supposedly frees up memory quickly, from apps that you aren't using, when needed. In my experience this is definitely not the case... especially when I click the Task Killer button and my Fire instantly returns back to normal speed... and never did the CPU go above 600Mhz (which is the min I have it set to).... which means it wasn't an issue with the CPU being overloaded.
So does anyone know of a way to keep these persistent apps from being persistent?
BTW, I'm running a pretty standard rooted Fire that I just re-did using the KFU v9.6 and all the "goodies" with it, like the GoLauncher.
TIA
Click to expand...
Click to collapse
Just let the OS do what it was designed to do, which is manage the apps and memory automatically. Any interference with that setup will only be a detriment to performance and battery life.
These are not full-featured Operating Systems like what is running on your desktop. Android (and iOS, and even Win8 Metro) automatically manages free memory, running processes, and stopping/starting of apps.
If you try to mess with this, it will cost you battery life and performance as the OS will continue to attempt to maintain it's designed status-quo by restarting apps that you've killed, and reassigning memory that you've freed up.
Task killers are only handy if you have an app that runs away and won't allow itself to be shut down (happens less often with every release/update), and even then, just cycling the device is more than enough to clean that up.
tl;dr Task Killers - Don't.
taskillers worked great in cupcake and donut... Using them In ics is just abusive.
PETA (peeps for ethical treatment of Android)
Sent from my HTC One S using xda premium
AlexDeGruven said:
tl;dr Task Killers - Don't.
Click to expand...
Click to collapse
This may be a dumb question, but I've read that kind of synopsis several times. With the release of ICS however, we have the option of killing previously running apps via the multitasking bar. What's the difference?
BleedsOrangeandBlue said:
This may be a dumb question, but I've read that kind of synopsis several times. With the release of ICS however, we have the option of killing previously running apps via the multitasking bar. What's the difference?
Click to expand...
Click to collapse
It's mostly in the way the OS talks to the task at hand. A Task Killer simply yanks the rug out from under the application in question, whether it's in a safe-to-stop state or not, and disregards any background services an app might be using. In many cases, the OS interprets this as a crash and attempts to get the app back into a 'normal' state.
ICS's task management politely asks (for lack of a better term) the app to stop and take any of its background processes with it. Sometimes, only the very foreground part of the app closes, sometimes the entire application and all services stop. But at the very least, you don't have the constant kill-recycle cycle that occurs with task killers.
ICS's method is much preferred, if not necessarily needed in most cases. I use it as a convenience to keep the list of recent apps clear.
androidcues said:
taskillers worked great in cupcake and donut... Using them In ics is just abusive.
PETA (peeps for ethical treatment of Android)
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
For memory management, yes. For killing wakelock abusers - they still have a reason for existing there.
Mainly Facebook. Facebook STILL holds excessive wakelocks on a regular basis (although it's not as bad as the perma-wakelock it held a year ago), and is the primary reason I keep Advanced Task Killer around.
Never use an autokiller though.
Only use a task killer for managing identified misbehaving apps that you just have to keep around for some reason (like Facebook). Never use a task killer for memory management reasons - only use it on apps that are using excessive background CPU or wakelocks. (usually, apps that are high on the ****list in Settings->Battery.)
There are programs like 'Gemini Task Manager" that will let you edit/modify the automatic startup settings for any particular app. At the very least it will let you see what apps may be causing problems on your device. As far as I know it only edits the startup to keep them from running in the first place rather than constantly killing them when they do like some task managers.
Thanks for all the info. It appears that just leaving it the way it is is what I should do... especially since 95% of what I use the Fire for is for reading books. But I am a Windows/Cisco Sys Eng, so I like to tinker with all my tech devices whenever I can.
That being said, it seems to me that if these "persistent apps" were on a Windows O/S, they would be running as a Service. And if you know Windows, you would know that Services can be set to restart if they are stopped by any means, except through the Service Manager Console itself (or the command line, if you really know Windows). But I have no clue if Linux/Android has the equivalent of Windows Services. I would have to believe that full-fledged versions of Linux/Unix does, but maybe not Android. Just a thought... and maybe it is something people have overlooked when trying to keep these "persistent apps" from being persistent.
Typically, in Windows, you would never ever think of running Facebook as a Service... but you easily could if you wanted to. And it appears that Amazon really wants Facebook, and several other apps, to be running at all times, for no apparent reason.
Oh well, if I had a 2nd Fire, I would "hack" the hell out of it. But since I don't, and I read a lot, I'll just be happy with what I got. And honestly, even after having the Fire since the first day it came out, I'm still loving it.
PBFred said:
Thanks for all the info. It appears that just leaving it the way it is is what I should do... especially since 95% of what I use the Fire for is for reading books. But I am a Windows/Cisco Sys Eng, so I like to tinker with all my tech devices whenever I can.
That being said, it seems to me that if these "persistent apps" were on a Windows O/S, they would be running as a Service. And if you know Windows, you would know that Services can be set to restart if they are stopped by any means, except through the Service Manager Console itself (or the command line, if you really know Windows). But I have no clue if Linux/Android has the equivalent of Windows Services. I would have to believe that full-fledged versions of Linux/Unix does, but maybe not Android. Just a thought... and maybe it is something people have overlooked when trying to keep these "persistent apps" from being persistent.
Typically, in Windows, you would never ever think of running Facebook as a Service... but you easily could if you wanted to. And it appears that Amazon really wants Facebook, and several other apps, to be running at all times, for no apparent reason.
Oh well, if I had a 2nd Fire, I would "hack" the hell out of it. But since I don't, and I read a lot, I'll just be happy with what I got. And honestly, even after having the Fire since the first day it came out, I'm still loving it.
Click to expand...
Click to collapse
It's still completely different system paradigms. In mobile OSes, background services are typically in a paused state when not actively in use, where in full-featured OSes, they can be in any one of several states.
As to the fb service running, that has nothing to do with Amazon. That's just the fb mobile developers not knowing what they're doing.
Sent from my Amazon Kindle Fire using Tapatalk 2
I've been using this phone for about 3 weeks, and I've noticed it seems to have a very aggressive low memory killer or a rogue task killer. I haven't installed any task killers or battery savers that should be doing this, so it seems to be system behavior.
If I airplane mode my phone, by the time I reconnect it, it has almost always killed DNS66. I can pause Pandora and just leave the phone laying on my desk. When I come back it will have killed Pandora. The last straw was today when it killed Rocket Player while it was actively playing.
The only device I've ever seen kill an active app only has 1 GB RAM. The last phone I used only had 2 GB RAM and it handled background apps way better than my Nokia 6.1 is.
Has anyone else seen this, or better yet, do you know how to stop it?
I have a TA-1045 running Pie on the Dec 2018 security patch. No root, no mods, no task killers - just bone stock behavior. The only non-Play store app I have is DNS66.
Have a look at
https://dontkillmyapp.com/
runekock said:
Have a look at
https://dontkillmyapp.com/
Click to expand...
Click to collapse
Excellent! Just killed that battery protection app. Can't wait to fire up adb and get rid of it entirely. I can't believe Nokia thought end users would desire this kind of behavior.
If this works out, you just saved me a phone. I was not going to put up with this much longer.
runekock said:
Have a look at
https://dontkillmyapp.com/
Click to expand...
Click to collapse
Well that didn't work. Force closing the battery protection app like suggested in that link didn't change aggressively killing off idle apps. The package manager adb command exits with success, but the battery protection app is still on the phone ruining its memory management.
Have you managed to get this phone to work properly with respect to background apps? Did you make any other modifications or do any other debloating?
Otherwise this is a pretty decent phone. Smooth enough and plenty fast for everything I use it for. The camera is a little sub-par, but no complaints for what I paid for it. Gotta skimp somewhere for a price point that low. However, sometimes it feels like this thing has a mind of its own, and its mostly due to how aggressively it kills off tasks. They aren't even always what I'd call idle, like a paused media player or a DNS server not currently in use. It is really disappointing. This isn't what I expected out of an Android One device.
The Nokia 6.1 belongs to my father, and this problem hasn't bother him, so I haven't tried anything myself.
Maybe you need to be rooted to uninstall the task-killer? But then, I don't know a way to root the phone, either.
runekock said:
The Nokia 6.1 belongs to my father, and this problem hasn't bother him, so I haven't tried anything myself.
Maybe you need to be rooted to uninstall the task-killer? But then, I don't know a way to root the phone, either.
Click to expand...
Click to collapse
You're probably right since it is installed as a system app. It is just odd that the package manager command exits with Success. You'd think it would throw a Permission Denied or Only Root can do that error.