Related
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
gupta.anurag08 said:
Can anyone suggesr me which is the best task killer available in the market..m using task killer from rhythm software..
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm running on the Advanced Task Killer, I do not have any issues with them. What's your problem?
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Yeah, ATK is the best task killer app I've been using
gupta.anurag08 said:
I tried 2 3 task killers and all were showing different 'available memory'
Sent from my X10i using XDA App
Click to expand...
Click to collapse
It is because different task killer have different security policy, which allow them to show the system apps or not. So, in the lower security policy, you can see more running apps and gain more memory after kill them
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Nope, that is the reason why i have to use task killer
For me, it help me save much of battery
Since I stopped using a task killer my battery is better.
Don't use a task killer for a week and watch the difference.
gupta.anurag08 said:
So u mean to say that we shud not use task killers?
Wat if i exit a game in btw then wat happens..will it get automatically killed??
Sent from my X10i using XDA App
Click to expand...
Click to collapse
yes and yes!
if your phone requires the resources, it will kill tasks that are no longer required. its all automatic. let it do it itself and you will have a much happier phone
AND better battery life, because the android OS is not continually restarting processes that your task killer deems unnecessary. I would trust the actual OS over a 3rd party app. It is designed that way for a reason (see my previous post).
mrtim123 said:
i do have a question. why are you using a task killer?
I'm not having a dig at people that use them, but more trying to educate people that they are not required
"free memory" is not indicative of a healthy system in linux based machines.
please remember the way in which linux based OS's (which Android is) handles memory. Basically, if you have a heap of free memory it is simply wasted, the OS is not running any more efficiently. It is actually slower.
Here is a quick overview. Written for the desktop computer perspective, but translates over to a mobile phone OS quite well.
"Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time."
Read more here - http://www.linuxhowtos.org/System/Linux Memory Management.htm
Click to expand...
Click to collapse
The idea is absolutely right if memory is being used for apps you are likely to open frequently. ATK allows you to unselect the apps you want to keep running. That way you can unselect the ones you use the most and then use the widget to kill everything else.
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
There are advantages in both approaches and I find a mixed combination (available with ATK) makes it best, although the user need to use some common sense to do it right. Killing everything means the system will be more responsive but regularly used apps will take longer to start up. Not killing means the apps you use a lot "startup" faster when you use them repeatedly (as in fact they never stop running) but after a bit the system will lag when using other apps and may need to use pagefile/swap to atone for the lack of free RAM. That causes page faults which make the system even slower.
The iphone developers aren't complete idiots for killing every app. They have a priority for system responsiveness and they did achieve it at the cost of background running apps. I like the possibility to choose what I want to keep running and kill the apps I'm not likely to use again and it's one of the reasons I picked android.
A little Offtopic to both ifanboys and ihaters:
I never owned any apple product as I think of them as over priced. That said I think the iphone has great merit and I doubt very much we would have Android if the iphone didn't pave the way. Besides I jailbreak my brother's 3G and made it multitask enabled. Now it runs apps in background and there is little diference between it and my android. Except for the extra 200€ it cost, the lower hardware specs and expensive service provider contract my brother pays for a mandatory 24 months, while my X10 cost ~65% initially and came free of any contract.
well said, PCO
pco.vaz said:
I notice when I press the home screen many apps don't kill them selfs and after a while I have loads of apps running and the system starts to lag, specially when I try to run something else.
Click to expand...
Click to collapse
Thats what I and others have found, which is why some people choose to use one, myself included. Someone posted a link to an article last week with similar information posted here about the OS handling itself, but the comments section of the article were full of comments similar to what pco and myself have said, so it's all down to personal preference whether or not you choose to use one.
I did use a task killer for a while, then stopped. Personally my phone is better without. I have nothing except weather that updates automatically, I do it manually when I need it.
It is one of those things, just like on a laptop, everyone has different configurations and usage patterns that results will vary.
Sent from my X10i using XDA App
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
gavriel18 said:
Don't apps exit when you keep hitting the back button? And for games doesn't hitting exit shut down the app?
I thought its a feature that apps don't close when you hit the home button?
Click to expand...
Click to collapse
The browser for instance doesn't. Same with many other. I think it's up to each individual developer to program that behavior for his app.
I got Visual task switcher and I notice lots of apps just stay running forever.
Task killer caused probs for me. A daily switch off doesnt hurt, but have run mine for 7 days and been ok. Even a bberry cant do that!
Sent from my X10i using XDA App
Guys, don't use home button to exit apps.
Will just send them in background.
Use the back button... this won't exit (most of) the apps but will put them in a "sleep" state so, next time when you will use it, it will load faster.
So, again, home button will put the app in background, still running.
Test it with an audio player for ex.
Or a browser... send it in background with home button and the player will still play or the browser will still have that page loaded.
With back button, after all views are "closed" the app will close too (well, put in sleep state).
I use ATK only to kill the apps i use once in a while ... the rest of the stuff, is always in memory.
My X10 has usually about 25Mb free
Actually I used ATK to kill application that need to connect to internet, and in my case there is extra charge payment. But after i used ATK I don't notice that the battery live is longer. So I ever ask someone in my thread about after ATK kill applications and so forth....
And somebody told me to quit using ATK and now I realize that the battery last longer than before.
But one thing still bother me is:
Setting - Wireless control - mobile network - mms & data (no checklist)
means: I can not access internet and receive or send mms either.
Actually I only need MMS, not internet.
May be somebody can help me solve this problem.
Thanks.
But my conclusion:
NO NEED ADVANCE TASK KILLER.
After I uninstall ATK, my phone still running smooth and the battery last longer.
May be we just need best Cache cleaner. But I still trying some of that.
@pco.vaz
I don't want to be mean, but you are wrong.
Even those iOS versions that are not multitasking enabled keep apps in memory. Leaving an app on an iPhone resets its UI state and halts its processes, but parts of the app are left in the memory. You can see the difference in loading speed if you decide to reopen it.
There were apps that could show memory usage and clean it on the App Store, but Apple removed them. You can still get them through Cydia and see for yourself how memory management on iTouch devices actually works. Basically the iPhone goes as low as 3-4 megs of free memory and handles it in smiliar way as Android.
On both Android and iOS, apps that are in background are paused after a while and do not use processor cycles. Memory they keep occupying is overwritten if needed by another process.
I do not recommend using task killer to people who do not know what they are doing exactly. Killing even simple processes often causes phone instability and drains battery faster, as others have already said.
If you feel your phone is stalled, perform a simple reboot. There are apps that run in background (in most cases you are warned about this) or are poorly coded that could cause this behavior. Other than that, inbuilt application manager is able to force close apps pretty well, if you need to kill a single app causing problems
Today I (supposedly) disabled lowmemorykiller by putting zero in minfree and adj files. I already have swap partition set up (size 1 GB) in a class 10 SDHC card.
Then I proceeded to open all the apps that I have installed and set them in a different state from default (like opening its settings, opening a file in case of officesuite etc).
These things happened:
1. After a max limit, older apps started to vanish from task manager to make space for newer apps
2. used swap space did not exceed 122 MB
3. when I tried to return to very old apps, some of them retained their last state giving an illusion of multitasking but a text message I was typing disappeared, did not even get saved as draft. ALL web browsers were killed. Some reloaded pages from internet, Opera Mini and Easy Browser failed to save last state (they always fail, so does Adobe Reader) so they were back to home screen with all opened tabs lost.
4. After an incoming call, when I returned to all the apps a second time, I found that all but the lightest of apps had lost their last states.
After setting minfree to zero and enabling swap with 60 swappiness Android is still killing apps without my permission.
<rant> I usually have less than 10 apps open and some of them can be memory intensive. Multitasking is better than default now, but still kinda random. I can't ever be sure that if I open this document now, I won't find my previous 20 minutes of research session lost upon returning to browser (history is messy for retrieving long sessions and very short in case of Opera Mini. Even Chrome browser sometimes crashes and gets reset not to mention always reloading all pages while Android Browser in ICS only renders crashes. My data limit is 3 GB/month). The three major handheld OS right now are Android, iOS, WM7 so don't tell me to stop whining and change OS; there is nowhere to go. At least Android is open source and there is a chance of someone legally implementing proper (like in PC) multitasking in it except multiple instances of same app which will probably be a little too much to ask for from a community but seeing that browsing the web is my main concern and all browsers already support multiple tabs, it will not be a deal-breaker for me</rant>
So my question is, how do I stop this T1000 Ninja Edition? Throw it into the chasm of Mount Doom?
On a serious note, any help will be appreciated. If you can't solve it but know what is killing my app sessions, please explain that.
SO I have come to the conclusion that ICS's maximum limit of Background apps is 18. As long as the app is not older than 19, it should be visible in task manager and should be in memory. I have set swappiness to 100 and use of swap memory increased to 221220. I'll put further pressure on it to see how it behaves when lots of tabs are open but I am afraid that 100 swappiness will make the device crash if too many tabs are open. It has already started to suddenly reboot time to time.
Edit:
It does not work that way. Android seems to really have its own will in this matter. There is no rule found by me so far that can predict when an app will be unloaded from memory. It seems time plays a role too.
At least iOS and WP7 clearly state that they do not support multitask. Google is the worst of all.
Edit:
Chrome Browser is not loading the pages from internet upon being recalled from task manager. It is loading the pages from swap but looks just like loading over 3G. Any changes in the actual pages are not being reflected until I manually hit reload. Not sure if other browsers will follow suit.
It 'just a habit of many displaying applications in the background to go on the Android Market and install a task killer for fear that some application in the background throughout the battery consumption and slow down the phone memory consuming.
First Step
Android is the son of Linux and not Windows, Windows programs make sense that clean and optimize your memory, not in linux and behaves the same way if you have 10 or 100MB of free memory.
How to manage Android applications
Android applications and processes have defined 3 stages:
1) Running
2) Break In
3) Stopped
Each application runs in its own process when Android starts the process need to be made and ends when no longer needed, it lives in its own world and its code running is isolated from the rest with a Virtual own machine, it is assigned an ID whose permissions are visible to the user and 'application.
If an application needs to share files with another application creates a unique ID to save memory with a single Virtual Machine she shared.
Services are active as long as they need as well as activities that require the data connection and every process of Android. To understand whether an application or any process needs to connect and see if there are updates that it is active so that makes this operation.
It is not good or terminate these operations because the process will start all over again immediately active or when we are going to open an application it will take longer to open.
All processes are terminated when there is no longer needed or when the memory required by other processes.
If a user leaves a task for a long time, the system deletes all activities except the root, and when the user returns to the task it is like you had left.
An application is running when in fact you're running and is the first system plan
When it is no longer at the center of the 'attention but can still be visible is paused and can be killata by the system in case of need for extreme lack of memory
Finally, the application is blocked, but retains all the information is no longer visible on the screen and is in the background, can be killata from Android for any other activity that requires memory.
Summing Android is designed to kill the tasks when
You need more memory
They finished their work
Are not used for a long time
Kill process "by hand" can lead to side effects such as non-receipt of messages, slowdowns, crashes, etc. widget
The majority of applications closes with the BACK button and in any case by pressing the HOME Android close the task after it has been in the background for a certain period of time.
The majority of services running in the background using very little memory when they are not doing something so all other processes (reporting, etc.)
Domada: But why do I open google maps, facebook etc. mail.
These programs are not actually "open" if you notice are all programs that need a network connection, when you turn on the phone they do nothing but check for updates and notifications and then close.
If these activities killiamo happens that most of them will re-open to start all over again or take longer to open when we need them, or worse, will not give us accurate and up to date or will not work properly as well as make a lot more processor.
stempox said:
It 'just a habit of many displaying applications in the background to go on the Android Market and install a task killer for fear that some application in the background throughout the battery consumption and slow down the phone memory consuming.
First Step
Android is the son of Linux and not Windows, Windows programs make sense that clean and optimize your memory, not in linux and behaves the same way if you have 10 or 100MB of free memory.
How to manage Android applications
Android applications and processes have defined 3 stages:
1) Running
2) Break In
3) Stoppati
Each application runs in its own process when Android starts the process need to be made and ends when no longer needed, it lives in its own world and its code running is isolated from the rest with a Virtual own machine, it is assigned an ID whose permissions are visible to the user and 'application.
If an application needs to share files with another application creates a unique ID to save memory with a single Virtual Machine she shared.
Services are active as long as they need as well as activities that require the data connection and every process of Android. To understand whether an application or any process needs to connect and see if there are updates that it is active so that makes this operation.
It is not good or terminate these operations because the process will start all over again immediately active or when we are going to open an application it will take longer to open.
All processes are terminated when there is no longer needed or when the memory required by other processes.
If a user leaves a task for a long time, the system deletes all activities except the root, and when the user returns to the task it is like you had left.
An application is running when in fact you're running and is the first system plan
When it is no longer at the center of the 'attention but can still be visible is paused and can be killata by the system in case of need for extreme lack of memory
Finally, the application is blocked, but retains all the information is no longer visible on the screen and is in the background, can be killata from Android for any other activity that requires memory.
Summing Android is designed to kill the tasks when
You need more memory
They finished their work
Are not used for a long time
Kill process "by hand" can lead to side effects such as non-receipt of messages, slowdowns, crashes, etc. widget
The majority of applications closes with the BACK button and in any case by pressing the HOME Android close the task after it has been in the background for a certain period of time.
The majority of services running in the background using very little memory when they are not doing something so all other processes (reporting, etc.)
Domada: But why do I open google maps, facebook etc. mail.
These programs are not actually "open" if you notice are all programs that need a network connection, when you turn on the phone they do nothing but check for updates and notifications and then close.
If these activities killiamo happens that most of them will re-open to start all over again or take longer to open when we need them, or worse, will not give us accurate and up to date or will not work properly as well as make a lot more processor.
Click to expand...
Click to collapse
I know I'm likely to get criticised by some for saying this but some of us have to use task killers.
My phone has an average of 140 mb free after it boots up. Add to that apps that stay in ram even when you close them and you can have as little as thirty or fourty mb free.
I've seen apps such as facebook and tapatalk, and even some games, taking up ram even though I don't want them used once I exit from them...and when my phone gets to around fifty mb free or less it can get slow and unresponsive.
A quick kill of un needed apps makes the os perform as it should again.
It's nice to say android clears up ram as needed, and it does, but try playing a decent hd game when your ram is low and, unless you kill some apps first, you're left with a black frozen screen while it tries clearing some ram. In some cases your phone can be unusable for a while, on mine when this happens the capacitive buttons stop responding to keypresses.
Now on ics with 1 gb ram this isn't an issue but for those of us with less ram and / or an older os it is.
Ideally we could configure non system apps so that if we don't want them in ram when finished with them then they cannot auto restart.
It is a simple fact that two identical phones will perform differently if one has lots of free ram and one has most ram in use, I use an on demand task killer so that apps that stay around on exit can be stopped from eating ram and slowing my phone down so for me a task killer is not pointless specifically because it frees up ram so that something memory intensive can be run without slowing my system while android tries to make room for it.
So while I agree with the theory, in practice task killers can be useful or at least on demand ones can.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
I agree with how Linux handles its applications. I switch between WinXP and Ubuntu and the overall way tasks are utilized are similar, but linux does a better job at handling running applications. On windows i have Chrome open and with 9 tabs open im hitting 1.5 gb ram used. Same situation on linux i find myself hitting around 500mb of ram used. Im sure this applies to android as well.
On a side note i find that people who "Kill Tasks" are just running them because they can and are usually fixated on seeing a large amount of ram free. It just adds another reason to stay on their device. Just my opinion.
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
gruntparty said:
On a side note i find that people who "Kill Tasks" are just running them because they can and are usually fixated on seeing a large amount of ram free. It just adds another reason to stay on their device. Just my opinion.
Click to expand...
Click to collapse
I use one to make sure my phones already low ram does not drop so low my phone becomes slow, which it does when you get to even just fifty mb free ram left. And to kill those applications which do not exit properly.
On an android phone that has 512 mb ram if ram gets eaten up the phone goes slow, and I know it is not just me because other users with similar setups have same issues. So I think it is too general an assumption to say we all use task killers for say a cosmetic rather than practical reason though I'm sure some do.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
Markuzy said:
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Unfortunately this only stops apps auto starting at boot and once you have used an app and exited it, a lot stay in ram.
Some restart when killed some don't but when your phone is on permanently as many are, having low ram can quickly be a problem.
I think part of that is the phone manufacturer as 512 mb ram, with just 140 mb free at boot, is rubbish on a dual core 3D phone but whatever the cause I find killing tasks helps make phone run better.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
I used to kill tasks when i was on Android 2.1 an 2.3, but since 4.0 i feel my phone gone strangely fast, and i don't need to use task killers anymore. Phone is LG GT540, so...
lewymaro said:
I used to kill tasks when i was on Android 2.1 an 2.3, but since 4.0 i feel my phone gone strangely fast, and i don't need to use task killers anymore. Phone is LG GT540, so...
Click to expand...
Click to collapse
I used to love my gt540. Didn't know you could run ics on it though, good phone for the price but didn't like the resistive screen though the phone itself can take some serious punishment and still keep working.
I love lg for their build quality, pretty hard to break them with dropping etc, but unfortunately they do bad with the software side.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
Good topic, I don't like the task killer!
Sent from my GT-I9100 using Tapatalk 2
In general, yes task killers are bad. But occasionally it IS necessary to kill an app. Sometimes an app will freeze. Then it needs to be killed to be able to use it again. But you can easily just go into Settings > Applications > Manage Applications, find the app and then Force Stop it. So there's no real need to have a task killer. Although I do like to have Watchdog on my phone, as it shows the amount of available CPU cycles being taken up by each app, so you can make sure background apps aren't using too much CPU. (It does also show RAM usage, but it sorts apps by CPU usage, by default at least).
Linux has nothing to do with the management of an application, the applications under Android are sandboxed in java and there is this dalvik machine that takes care of everything.
I don't get why people keep mentioning this kernel over and over, also for the biggest part of its history Android did not use a real linux kernel with vanilla flavour, only recently the Android kernel was merged with the linux kernel mainline.
This is one of the very first Google video about Android http://www.youtube.com/watch?v=Mm6Ju0xhUW8
edit: In this series of videos there are also references to memory management and app management.
Markuzy said:
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
You are right
I do the same thing
In cm9 you can enable auto close apps with long press back button
So I don't need a task killer
Sent from my LG-P500 using xda premium
Not sure if it is wrong, just would like to get some explanation of this. Phone has bit less than 1GB ram available for apps and default behavior of Androuid should be to use it all for caching recently run proceses, because there is no difference if memory is free or taken - it uses same power.
I have Viper ROM 1.06 and using Nik3r kernel, tested with and without dataswap mod (128MB). Even tried to tweak Viper settings for minfree setting, using Multitasking ultimate profile. And still the same behavior. When I check available memory, it always sits around 750 used out of 980MB. Regardless what and how many apps I run.
Problem is, that when phone is not used for some time I see almost every time apps starting instead of fast switching from memory. Its mainly visible for me on FBReader, which I use to read ebooks every time I have little spare time. I pull phone from pocket, start FBReader and voila, it is starting from scratch loading book. Its 2-3s, but still. its relatively small app, shouldnt be killed most of the time thanks to system policies on free ram.
When I try to play with phone and run as many apps (start FBReader, home and run Chrome+load 2 tabs, run Camera, run Viber, run Tapatalk and back to FBReader) to force it to close my FBreader from memory, everything works fine and it swaps back in immediately. Even though checking Apps tab in settings shows memory usage about 750-800/980, not fully stuffed with cached apps (think its not showing correct numbers? Or not showing memory taken by apps in empty state?). But anyway. I give up, turn off my phone and let it be for some time. Then I check for example for SMS and would like to continue reading my book. And FBReader is loading as if it was closed. Why?
Seems to me like phone does cleaning of cached stuff in memory after some time when it is not used? Cant say precise when it happens, it just annoys me to see that system shows all the time around 750/980MB used and still is unable to keep my app in memory for longer period when it works fine if I test it directly.
Any ideas/tips/explanation?
Hi, I have the same issue with the fb messenger (chat heads)
I
Android still shut down and it doesn't restart...
Any idea ?
Sent from my ARCHOS 80 COBALT using xda app-developers app
hi all,
i have the V30+ and it sometimes closes apps for no reason, examples:
1. playing candy crush and then i get a watsapp message, i go to watsapp and answer and then go back to the game and it reloads, the game was removed from memory.
2. driving with waze while the screen is off (using sound only on long straight roads) and it just closes.
any ideas? is there a setting or something or is it a bug?
In recent apps window you have little pin and you can pin an application that will not be closed.
I've noticed the same thing. It almost seems random. Sometimes I'll tab out from Pokemon to Discord and tab back and the game will have closed, sometimes it will still be running. I have set the battery settings for power saving exclusions on certain apps and those apps are still randomly closing. I am wondering if there is another setting somewhere?
I don't like the pin option because I want to be able to manually close the apps as I need. If I un-pin it to manually close it, I have to remember to re-pin it next time I open it to keep it from closing unexpectedly? This is also assuming that the pinned app doesn't close in the background anyway.
Pinned apps are still closing when in background. When opening 'recent apps' the app appears to be still there, but when selected it has to reload from scratch. Something is killing backgrounded apps.
bump. I also have this issue. I would like a fix
have exactly the same issue. Power saving exclusion ON for an app. Switched to another app such as browser or whatsapp, switched it back and the app that excluded from Power Saving was killed.
Mine is a H930DS with 4GB ram. When looking in Settings > Memory I usually have less than 900MB free. Is it a normal free memory level?
jvw said:
have exactly the same issue. Power saving exclusion ON for an app. Switched to another app such as browser or whatsapp, switched it back and the app that excluded from Power Saving was killed.
Mine is a H930DS with 4GB ram. When looking in Settings > Memory I usually have less than 900MB free. Is it a normal free memory level?
Click to expand...
Click to collapse
Android is designed to use 100% memory.
Sent from my LG-H932 using XDA Labs