Related
I was wondering if there's any way to prevent android from killing programs immediately after i press the home button or switch to other programs.
For example, I'm browsing the Web when an sms comes in. Using home button (long pressing) I switch the task to answer and when I come back, the browser is gone and i have to load the page again (although it reloads in the same state).
It's really annoying. Reloading a webpage is not a problem but what about playing games?
I'm running InsertCoin 1.5, have about 80- 90MB RAM unused. And I doubt that I had RAM shortage
Thanks for reply
Your brought up that old horse (debate) on why the android OS does or does not need task managers. Yes, the wonderful engineers at android, developed a platform unlike windows, manages processes (by some opinions) way better than Windows. When you switch screens, it freezes the process, and holds it until you come back. When the phone starts to run out of allocated memory, it starts to kill the (less used) processes.
Now, I've heard of allocation of process levels to cause some apps to continuous run, which would be an interesting development for some dev to take on. You can select what apps you'll like to constantly run even if you switch screens. This would help those who would want to quickly drain their battery for OS calibration purposes.
If I find such a solution, ill report back.
Sent from my HTC Vision using XDA Premium App
Android should never kill the 2nd process in line (aka the Browser when switching to SMS), unless you're extremely short on RAM. In low RAM conditions, it will kill the farthest from recently used app in order to free up RAM.
How often do you notice this? is it always killing the app you switch from? Because this isn't correct (unless you're literally out of RAM as I said).
martonikaj said:
Android should never kill the 2nd process in line (aka the Browser when switching to SMS), unless you're extremely short on RAM. In low RAM conditions, it will kill the farthest from recently used app in order to free up RAM.
How often do you notice this? is it always killing the app you switch from? Because this isn't correct (unless you're literally out of RAM as I said).
Click to expand...
Click to collapse
Like i said. I had plenty of free RAM. So it's unlikely that I have RAM shortage.
I spent the morning examined things. Just figured I it out:
Flash this over and I have 3 apps in line.
Combine with Perfect task switcher, I got what i wanted.
Also, I noticed that switching by long pressing HOME button and choosing apps cause the app to restart while using BACK button won't
I don't know if this is Android behavior or my device's issue
But anyway, I got it sorted out
Thanks you u guys
I'm running CM7. Long pressing home and switching between numerous apps I've never had an app close on me. Must be a ROM/device combination situation for you...
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 have the LG G4 with T-mobile and I frequently stream music with Slacker. I have noticed quite a few times that is the music app is streaming in the background (and the screen is off), the application will close completely and stop playing. This does not appear to happen when the app is in the foreground. I do not have any task killing applications installed and I was wondering if others had seen behavior like this? Any thoughts on how to prevent this from happening?
Thanks!
Same to me but with endomondo
What is probably happening, well has to be getting killed by the garbage collector, but why could be a few things.. if it's doing it when your screen is off its the device going into deep sleep and slacker is not pushing a persistent enough service to give it a higher priority to keep the device awake when the screen is off which there wouldn't really be much you can do besides using an app like Tasker or a robot To 4 + device awake while the screen is off and there's probably some other apps that will do it too. That's one way to test and at least find out if that's what's going on. And another likely reason would be simply the phone is being pushed into out of memory situation and Android is killing off everything which would only happen if you had a **** pile of apps running and I still don't see slacker having a low enough priority to be killed so quickly. I would have to know a little more about what all you have running on your device at the time it is being closed
Through my ancient eyes comes the certainty of decay... LG G4 & L 70
Hello everyone, I still have a working LG G4, I have the root with android 6.0 (stok, and if possible I would like to keep it as it is the only "stable" after various tests), I have an application that I would always like to run, even in background without being interrupted. I tried to ignore the energy savings for the app in question, but when the screen is closed after 1/2 hours the application is closed (I assume from the system). Having the root can I find a reliable task manager that makes me choose which apps ALWAYS run in the background (as if they were displayed on the screen) and which not?
To remedy the problem, I'm always keeping the screen on but so I don't think I'll go on for long ..
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.