Since I noticed this behaviour last night, I've been obsessively watching various apps start and stop on their own. On the App Manager's "Running" tab, I keep seeing several apps start and stop on their own, despite the fact that I've turned off any network-related syncing or listening options in their individual settings.
Also, there seem to be far too many apps in the Cached Processes screen, most of them I haven't run at all for a long time.
Is this behaviour normal? (Android's, not my obsessing...)
I'm worried that something else is going on in the background and killing my battery. Or worse, scanning my system. (Though I did run an antivirus without any problems being detected.)
Thx.
I recently asked a similar question regarding lowering background processes allowed. Whether background and cached apps affect battery. I learned it is a trade off between using more battery to restart or pull from cache. I opted to do a heavy debloat and freeze certain apps or processes I don't need. I also use cool tools to watch my memory and CPU info and battery monitor widget pro to monitor mA and CPU temp. I enjoy trying to max out efficiency. I didn't see my post anymore in the last few pages but if its further back the guys linked me to some great info about processes. Sorry for not linking thread. I will when I get a chance. Hope it helps you too.
Bubba Fett said:
I recently asked a similar question regarding lowering background processes allowed. Whether background and cached apps affect battery. I learned it is a trade off between using more battery to restart or pull from cache. I opted to do a heavy debloat and freeze certain apps or processes I don't need. I also use cool tools to watch my memory and CPU info and battery monitor widget pro to monitor mA and CPU temp. I enjoy trying to max out efficiency. I didn't see my post anymore in the last few pages but if its further back the guys linked me to some great info about processes. Sorry for not linking thread. I will when I get a chance. Hope it helps you too.
Click to expand...
Click to collapse
Thanks! I'll take a look in your post history to see if I can find it.
I'm less concerned with whether or not the apps are actually running or cached, what worries me is that they all seem to be constantly starting and stopping for a few seconds. Watching the Running apps screen I can see many different apps cycling over and over. The process starts, goes on a few seconds, then stops. Then another one pops up. Then another, etc etc.
I looked back about a dozen pages and couldn't find it anymore but I think it was diablo009 that gave me links to some really helpful stuff he had written. I'm not super proficient in maneuvering the forums but maybe you can find his posts with that info another way. Good luck.
Not sure if it loads my signature when posting from phone. But if it does, check Android Memory Management link in my signature.
Sent from my SAMSUNG-SGH-I747 using xda premium
Bubba Fett said:
I looked back about a dozen pages and couldn't find it anymore but I think it was diablo009 that gave me links to some really helpful stuff he had written. I'm not super proficient in maneuvering the forums but maybe you can find his posts with that info another way. Good luck.
Click to expand...
Click to collapse
(This is the one I found.)
I'm aware of that RAM usage with Android from similar articles I read last year, but it was really the automatic starting and stopping of processes/services that bugged me. I think it might just be a situation where if the app's on your phone there's nothing you can do about it if you've granted network access permissions. I probably naively assumed that if you granted those permissions where would be settings to disable network access within the apps.
Some of my observations:
An app prefetched into memory does not use CPU.
A prefetched app could be wiped from memory if more RAM is needed. After the memory intensive app quits, this could be loaded back.
If an app is used frequently, it would be one of the prime candidates to be considered for prefetching.
An app loaded (not prefetched) uses CPU based on its work, like it could be a daemon looking for updates.
Sent from my SAMSUNG-SGH-I747 using xda premium
diablo009 said:
Some of my observations:
An app prefetched into memory does not use CPU.
A prefetched app could be wiped from memory if more RAM is needed. After the memory intensive app quits, this could be loaded back.
If an app is used frequently, it would be one of the prime candidates to be considered for prefetching.
An app loaded (not prefetched) uses CPU based on its work, like it could be a daemon looking for updates.
Click to expand...
Click to collapse
The last one is what I am worried about. There are apps that are starting processes and then stopping repeatedly. A couple dozen different ones, including ones I have barely ever used. I've looked at some of those apps' settings and disabled any notifications or update checking, basically anything network related, but they keep showing up in my running apps/processes list throughout the day.
Not sure how Google market checks for app updates. It could be querying installed apps at regular intervals to check for their versions to compare to versions in market.
Sent from my SAMSUNG-SGH-I747 using xda premium
diablo009 said:
Not sure how Google market checks for app updates. It could be querying installed apps at regular intervals to check for their versions to compare to versions in market.
Click to expand...
Click to collapse
That's one thing I wondered about, but I have Google Play updates off. I guess it's possible that it still checks, though.
Thx for the reminder! I'm going to double-check my Play settings just in case something was reset during an update.
You could try something like Rom toolbox pro to stop startup programs if you use them infrequently. I have had a few issue stopping certain apps but a little tweaking and it works well. Juice Defender also has the option for disabling apps from accessing data/wifi or neither. I don't know about the process though. Thanks for spotting your name Diablo and helping out. Great info on the topics.
.Arkham said:
Since I noticed this behaviour last night, I've been obsessively watching various apps start and stop on their own. On the App Manager's "Running" tab, I keep seeing several apps start and stop on their own, despite the fact that I've turned off any network-related syncing or listening options in their individual settings.
Also, there seem to be far too many apps in the Cached Processes screen, most of them I haven't run at all for a long time.
Is this behaviour normal? (Android's, not my obsessing...)
I'm worried that something else is going on in the background and killing my battery. Or worse, scanning my system. (Though I did run an antivirus without any problems being detected.)
Thx.
Click to expand...
Click to collapse
I agree that if you don't use it, uninstall if you are able. Otherwise just disable it. This is unusual though. I randomly go into cached processes and only the things I use or that the system needs are there. On a rare basis something additional might pop up.
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)
Every time I check my running apps maps is there and it does not want to stop. Since maps is a battery hog I uninstalled it. Why is it always running? What is the best way to control this and other apps so they will start and stop as directed. The market is also runs from time to time. Maps might be started by the network location service. Do I have to edit the init file or?
Sent from my PC36100 using XDA App
Android is not like Windows, killing apps is actually more counterproductive than it is helpful. There is plenty of documentation and explanations about this so I won't bore you, just look it up.
I haven't ran a task killer since about it week after I got my phone, and I noticed that my phone ran better without it, and my battery lasted longer.
Stop constantly worrying about what is running in the background and enjoy your phone.
If you don't want to believe it, you can try an app such as Autostarts. It should do what you're asking.
(from... Evo/MIUI/Tapatalk)
There is a paid app called startup manager that I've used for a LONG time to take a lot of apps out of the boot up process.
Maps would be one of them.
HipKat said:
There is a paid app called startup manager that I've used for a LONG time to take a lot of apps out of the boot up process.
Maps would be one of them.
Click to expand...
Click to collapse
Maps has a lot of receivers and start up conditions, get Gemini App Manager, and Autorun Manager. Using both of these and you will be able to stop it from starting on its own. With Gemini, you can change all it's start up conditions(package added/removed, boot, connectivity changed, etc), and you can disable/enable receivers with AutoRun manager.
conductive said:
Everytime I check my running apps maps is there and it does not want to stop. Since maps is a battery hog I uninstalled it. Why is it always running? What is the best way to control this and other apps so they will start and stop as directed. The market is also runs from time to time. Maps might be started by the network location service. Do I have to edit the init file or?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Does it show up on your list of battery usage? Mine is always running but never shows up on the list... Running apps don't take battery unless they are actually using the CPU...
i had that problem too. what i did was go into the ALL tab n kill it to stop it. if i killed it from the RUNNING tab it would just restart. don't know y but thats how it worked for me...
If i keep tying to rapid kill maps it will eventully die. However, I might inadvertantly kill something else in the process.
I just do not see any reason that I need to be consistantly mapped. I will have to look at the battery consumption and the app managers are interesting. I have not used a task killer in quite some time. I would think that anything that runs this much has to bun some battery and responsiveness along the line somewhere.
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
Anyone know how I might go about diagnosing why my phone has been running much warmer than usual? Just browsing Facebook (posts, not video) for about 5 minutes with brightness around 25% the temp was up to 41 degrees. It happened earlier today when I was just using Chrome, and it happens most days now. The issue began when I updated to 11.2.8.8 (the very next day), and the phone overheated several times the first few days, evidenced by the system warning about temperature, then recovering several minutes later. I haven't seen the system warning since then, but it's frequently above 40 degrees just doing everyday tasks. Oddly, I haven't noticed it overheating when playing games.
I usually run Omega kernel, which has always run cooler than stock during both normal use and heavy gaming, but this issue has occurred with both stock and Omega, so it's not kernel-related. The only magisk modules I have installed are debloater (for YouTube only), font manager, and systemless hosts, so that's not it either.
Maybe some app going haywire (how to find it? Nothing in battery usage) or some system behavior that changed in 11.2.8.8? Anyone else have this issue or find what's causing it?
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
TheKnux said:
That's just how this phone is. It was worse when the phone released before all of the updates. They've been slowly trying to fix it with each update. The 888 is a hot *****.
Click to expand...
Click to collapse
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
terlynn4 said:
I remember having that complaint when I first got it, especially when gaming, but it's been fine for me since like April, until this last update. And with Omega several degrees cooler. So there has to be something new causing it....
Click to expand...
Click to collapse
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
TheKnux said:
What version of Omega are you on? What build of OOS? AA, BA, DA? Are there any unusual rogue apps that you've noticed running more than usual?
Click to expand...
Click to collapse
Latest version of Omega (8/7) since yesterday, but was having the same issue on the previous build (7/30). I'm on OOS 11.2.8.8 BA.
I haven't noticed any apps using more battery than expected, but I guess that might be part of my question... If there are any, what's the best way to find them? I'm not seeing any useful info in BBS or anything in GSam I wouldn't expect, except overall battery drain is a bit higher when it's been running hot. I do have a lot of apps installed and should probably clean up what I don't use, so I guess that's a place to start.
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
blackhawk said:
Find which apks are using the battery.
Google system apks are prime suspects.
Trash apps like FB, WhatsApp, LinkedIn... none of that junkware runs on my device, ever.
Examine all startup apks closely, take out the trash.
Power management can end up causing excessive battery usage, try turning it off.
Track down each battery hog and deal with it on a case by case basis rather than the flip a switch shotgun approach.
I use Karma Firewall's logging feature to help track down offenders.
Dependencies... sometimes the source of the high usage is hidden. What apks and services are running? What apks are using what services and why? What's apks are getting cached first when you clear them all? Any memory leaks?
Play with it... Androids wuv attention
Click to expand...
Click to collapse
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
terlynn4 said:
Good ideas. I just installed Karma Firewall and will see if it turns up anything.
How do you manage startup apps and running services? I used to use Servicely, but with Android 11 I find that even when I disable apps at startup they still start on their own, and it seems to use more battery than it saves. I've since disabled all apps of that kind and just let Android manage things itself. The only thing I do is go to individual apps and turn on battery optimization and disable background data if not needed, and I keep apps I don't use often in Icebox, including Facebook, which is the only social media type app I have. (Uninstalling FB isn't an option unfortunately.)
What do you mean by "which apps are getting cached first when you clear them all?" and how might I find it there are memory leaks?
Click to expand...
Click to collapse
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
blackhawk said:
Karma's logging feature doesn't work in 10 and above I believe, I run Pie. See what you got though. It will still block apk internet access though and uses almost no battery.
The battery optimization option can cause erratic behavior and I never use it. Close apps when done with them. Brave browser for instance will run in the background until closed.
Developer options>running services memory leaks show up as an apk who's memory usage just keeps increasing with time. It can get quit large. These are rare and poorly coded programs. More common on Windows.
Keep an eye though for memory hungry apps as they may be using excessive power but not always. Small memory users can be worse. Dependencies, sometimes a apk or service keeps making repeated requests because of a disabled apk or service.
Killing Goggle play Services and Playstore when not needed will help battery life.
Google backup Transport, Framework and Firebase are always disabled on my device.
All carrier, manufacturer, and Google feedback are disabled.
I have a Samsung device and I use its Device Care app to clear the cached apks. Then watch as they repopulate. You'll need an app that does this. In running services you can disable a suspect apk and see how long it takes to come back. I find that Device Care is more effective though and that ability has let me track down some misbehaving system apks saving me a reload.
FB is weaponized and a proven liability. Known data miner. Purveyor of disinformation and dissent. It has ruined countless lives and careers. It deliberately makes you have load the app to be able to send messages. If this last year hasn't taught you what you need to know...
I used it for one month 15 years ago and knew what it was back then. It's far worse today.
Don't feed the beast.
Click to expand...
Click to collapse
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
terlynn4 said:
Thanks for the info, it's interesting. However, if you're running Pie & not even using a OnePlus device, none of this is going to be applicable to my issue which is specific to OOS 11.2.8.8 on this particular device, only present since last month's update.
Re: FB - I'm required to use it for my job (well, second job), and I need it on my mobile device in order to do that job, so it's not going away. Freezing it when not in use is the best I can do.
Click to expand...
Click to collapse
You cross platform OS version and manufacturer to find solutions. I have a lot of posts here but few asking for help because I do the above or just keeps at it until I work it out as it's my issue.
*shakes head*
You've painted yourself into a corner.
@terlynn4 I use BatteryGuru because it uses root to find rogue apps that are draining battery unnecessarily. Give it a go and see if that helps pinpoint the problem at all.