So me and my buddy both have a Gnex...
I tend to not really use the task button on the nav bar too much to swipe away tasks.
My buddy on the other hand likes to kill apps off EVERY SINGLE TIME he leaves an app. And i mean EVERY time, as soon as he leaves it he swipes its ass.
I think thats a bit much.
Ive always been under the impression that any kind of task killer can do more harm than good, as it slows things down when you reopen an app as it has to load it from scratch again.
My friend argues that your supposed to do it because thats the the button and feature is there for.
I would have thought that it was just there for in case you want to manually free up ram for what ever reason, or quickly jump between apps.
So whos doing the right thing and whos doing the wrong?
there is no right or wrong for this.. its all personal preference
i usually just keep it there until i kno i have reach like 10+ apps, then i just swipe them away cuz i dont want my list to be that long...
but when u say close every app every time.. i only do that when i kno it keeps running in the background sucking my cpu and battery ex. Facebook app
then i will swipe away every time i dont need it, while others i just keep it there
"task manager" its not a good definition for what it does
in real its show u the list of the last used apps and when u swipe away an app, u ONLY remove it from that list...it doesn't ( correctly ) kill anything
the real important thing, is that when u want exit from an app then press the back button to leave the app...the home button instead leave the app "running" in its state
andQlimax said:
"task manager" its not a good definition for what it does
in real its show u the list of the last used apps and when u swipe away an app, u ONLY remove it from that list...it doesn't ( correctly ) kill anything
the real important thing, is that when u want exit from an app then press the back button to leave the app...the home button instead leave the app "running" in its state
Click to expand...
Click to collapse
swiping away from multi-tasking UI DOES kill the app.. or u can say kill the activity, but if the app has a process, it will still be there.
but it definitely kill the app activity
From a simple test it doesn't kill any app for me.. try checking the apps running with quick system info or a similar app
Inviato dal mio Galaxy Nexus con Tapatalk 2
andQlimax said:
From a simple test it doesn't kill any app for me.. try checking the apps running with quick system info or a similar app
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
its been discussed in here xda (try the search button), AND from google android developer (her g+ post)
IT DOES KILL believe it or not
its purely personal preference when it comes to swiping away the tiles/icons/whatever, but he needs to realize that all he's doing is slowing down the resume/relaunch times of his apps, not to mention wasting minutes of his day swiping them away for (effectively) no reason. He's not going to see increased performance or battery life from constantly OCD closing the apps.
martonikaj said:
its purely personal preference when it comes to swiping away the tiles/icons/whatever, but he needs to realize that all he's doing is slowing down the resume/relaunch times of his apps, not to mention wasting minutes of his day swiping them away for (effectively) no reason. He's not going to see increased performance or battery life from constantly OCD closing the apps.
Click to expand...
Click to collapse
That...
And if there is an obnoxious app that he's killing...one that auto-starts itself again...
It'll waste battery as it restarts.
(These obnoxious apps should be avoided anyway, obviously.)
king23adrianc said:
its been discussed in here xda (try the search button), AND from google android developer (her g+ post)
IT DOES KILL believe it or not
Click to expand...
Click to collapse
it does not kill
u must use the search
its a list of recent used apps..u can remove apps from that list..not killing anything..and this is how should work
andQlimax said:
it does not kill
u must use the search
its a list of recent used apps..u can remove apps from that list..not killing anything..and this is how should work
Click to expand...
Click to collapse
lol whatever u say. i bet u didnt do any search
king23adrianc said:
lol whatever u say. i bet u didnt do any search
Click to expand...
Click to collapse
we can go on forever, but im sure about what im talking about..u are disinformed
are we talking of the same thing? pressing the ics built in multitasking button (on a stock rom) doesn't allow u to kill apps, only to remove it from that list
u can test it urslef in lot of way..also im not sure if u are trolling, but anyone here can confirm what im saying
i'm not going to reply again in this post
andQlimax said:
we can go on forever, but im sure about what im talking about..u are disinformed
are we talking of the same thing? pressing the ics built in multitasking button (on a stock rom) doesn't allow u to kill apps, only to remove it from that list
u can test it urslef in lot of way..also im not sure if u are trolling, but anyone here can confirm what im saying
i'm not going to reply again in this post
Click to expand...
Click to collapse
seems like ur trolling more cuz it has been proved it does kill the activity of an app when u swipe away in multitasking ui
try searching stuff before u say anything
http://forum.xda-developers.com/showthread.php?t=1445065&highlight=kill
edit: there are lots of videos on youtube of people posting it kills from swiping away
showing the difference between pressing home after opening the app, then swipe away, the app has to reload again. cuz it kills the activity
andQlimax said:
it does not kill
u must use the search
its a list of recent used apps..u can remove apps from that list..not killing anything..and this is how should work
Click to expand...
Click to collapse
Umm yeah, it does. It kills activities, but not associated services. Try it out first.
RogerPodacter said:
Umm yeah, it does. It kills activities, but not associated services. Try it out first.
Click to expand...
Click to collapse
Related
I have tried to use this to stop the drm services from starting. I install and check all options to stop them from starting up. They still start up on reboot even though I check the option to not restart.
What can I use or how can I stop there since I seem to not need it.
mynewepic10 said:
I have tried to use this to stop the drm services from starting. I install and check all options to stop them from starting up. They still start up on reboot even though I check the option to not restart.
What can I use or how can I stop there since I seem to not need it.
Click to expand...
Click to collapse
Anyone have an idea?
mynewepic10 said:
Anyone have an idea?
Click to expand...
Click to collapse
Did you seriously just double post AND quote yourself simultaneously?
Is that another way to bump?
mynewepic10 said:
I have tried to use this to stop the drm services from starting. I install and check all options to stop them from starting up. They still start up on reboot even though I check the option to not restart.
What can I use or how can I stop there since I seem to not need it.
Click to expand...
Click to collapse
So I don't know the exact behavior of every single Task Manager, nor do I know what you mean by stopping the DRM(Digital Rights Management?) services.
For one, that sounds like an issue associated with pirateing, which is not tolerated for discussion here at XDA Devlopers.
And so to probably answer your question:
Especially with an Eclair 2.1 version of Android, Task Managers are not able to kill processes immediately as they are created. I know the one that I use only kills the Auto-Kill listed apps when I turn the screen off. So your Task Manager may not be able to successfully kill the aforementioned DRM process.
Hope that helps. Don't pirate. At least don't make it obvous...
Just use titanium backup to freeze the drm services. And he's not wanting to stop it fire piracy issues, its a known issue that drm services cause a huge battery drain on our phones
Sent from my SPH-D700 using XDA App
What i do is, i created a custom shortcut to settings - running services. Tap the icon, click the process. No extra killers needed. I do it once per boot.. and, having tried a million other methods, this works the best.
Doesn't freezing it in titanium cause the same problems as if it was removed?
To cyan crayon: do you have an epic?
..and just realized were replying to a post that's 3 months old.. selffail.
Sent from my SPH-D700 using Tapatalk
decalex said:
To cyan crayon: do you have an epic?
Click to expand...
Click to collapse
Yes, I have an Epic. If you use the desktop website you'll see it in my sig.
I haven't come across this DRM process issue yet, although I've only had my Epic for about two weeks. Regardless of the fact, when I do see problems I might be able to help with I will do my best to contribute.
Edit: Let me attempt to clarify what I have said.
I never guessed to check my processes, and whaddya know it's right there staring me right in the face.
The thing is task managers like Task Manager (which is what I use) only can target running apps. In case that wasn't apparent.
This process is starting along with the Android System, so unless you decide you don't want the system to start when the phone boots, it will start it every time.
The point is that task managers like Task Manager, cannot, and will not terminate processes other than its own, because (obvously for security reasons) the API for that behavior does not exist.
/lecture ^-^"
And I would imagine freezing it would cause issues. Just like decalex said. It does perhaps have a purpose.
Sent from my Epic4G using Tapatalk
decalex said:
What i do is, i created a custom shortcut to settings - running services. Tap the icon, click the process. No extra killers needed. I do it once per boot.. and, having tried a million other methods, this works the best.
Doesn't freezing it in titanium cause the same problems as if it was removed?
To cyan crayon: do you have an epic?
..and just realized were replying to a post that's 3 months old.. selffail.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I've never had any issues withe my phone at all, other than the known dk28 bugs and even then the worst bug is the occasional wfi error running midnight rom and I have tianium freezing all drm services. And I use the media player for about 7.5 hours of my day and pandora for about another hour with the occasional movie playing during breaks if I'm super bored lol
Sent from my SPH-D700 using XDA App
CyanCrayon said:
Yes, I have an Epic. If you use the desktop website you'll see it in my sig.
I haven't come across this DRM process issue yet, although I've only had my Epic for about two weeks. Regardless of the fact, when I do see problems I might be able to help with I will do my best to contribute.
Edit: Let me attempt to clarify what I have said.
I never guessed to check my processes, and whaddya know it's right there staring me right in the face.
The thing is task managers like Task Manager (which is what I use) only can target running apps. In case that wasn't apparent.
This process is starting along with the Android System, so unless you decide you don't want the system to start when the phone boots, it will start it every time.
The point is that task managers like Task Manager, cannot, and will not terminate processes other than its own, because (obvously for security reasons) the API for that behavior does not exist.
/lecture ^-^"
And I would imagine freezing it would cause issues. Just like decalex said. It does perhaps have a purpose.
Sent from my Epic4G using Tapatalk
Click to expand...
Click to collapse
[How] to remove the omadrmconfigservice.drm to get more battery life on epic:
http://forum.xda-developers.com/showthread.php?t=794010
Do you really think that someone that knows how to pirate would ask for advice/assistance on how to do it in this forum?
brickwall99 said:
[How] to remove the omadrmconfigservice.drm to get more battery life on epic:
http://forum.xda-developers.com/showthread.php?t=794010
Do you really think that someone that knows how to pirate would ask for advice/assistance on how to do it in this forum?
Click to expand...
Click to collapse
>.> There are some morons out there...
And you beat me to linking that.. ^^
I have seen it posted by many users that swiping away apps in the mutitasking list does not kill the app. This is untrue according to Romain Guy. He states that it does indeed kill the app.
https://plus.google.com/105051985738280261832/posts/GfwRYCC42uX
Neal Sanche - On Ice Cream Sandwich does the swipe gesture in the recent tasks list do anything to the tasks? Does it kill them or just simply remove them from the list?
Jan 5, 2012
Romain Guy - +Neal Sanche It kills them
Jan 5, 2012 +5
Simple way to test this:
Reboot your phone, check your battery %, open Facebook and close it. Check your battery % after around an hour.
Now do the same, but this time swipe Facebook out of the task list, the drain will be much less.
Any time I get abnormally high battery drain, every single time i've forgotten to swipe away facebook.
I had always had my suspicions that people were wrong about it not kill apps because in the browser if you swipe it away then the browser starts over fresh when you open it.
My experience with the phone says otherwise. For example, do this:
- create a play/pause control widget with widgetsoid (free on the market)
- open Google Listen and start listening any podcast
- pause it, and then swipe Listen away from recent apps
- now go to your homescreen and push play on the widget......magic!
I think something still runs at the backstage even if you swipe away the app. Of course that might depend on the app, and who know if also on the Kerne/ROMl you are running.
I've noticed the GPS icon appearing for no reason after running Facebook.
Then when swiping away Facebook the GPS icon stops.
Sent from my Galaxy Nexus using XDA App
the swipe only kills tasks in the foreground, to test, run a music app like Google music, then remove it from the list, it'll continue to play. it's not really a good feature, useful for some apps but if Google wanted the ux to be more consistent and intuitive then this is a prime example of one they failed at
the right way to do this would be to treat it like a force kill, but with a confirmation for ones running a background process
It kills them... Swipe away the XDA app.. Swipe away the browser... It starts fresh..
as for the person that suggested the music not starting over.. You can pause a song, restart your phone and it will be paused at the same spot.. So that's why that doesn't restart when swiped away.
Sent from my GalaxyNexus using XDA App
wonshikee said:
the swipe only kills tasks in the foreground, to test, run a music app like Google music, then remove it from the list, it'll continue to play. it's not really a good feature, useful for some apps but if Google wanted the ux to be more consistent and intuitive then this is a prime example of one they failed at
the right way to do this would be to treat it like a force kill, but with a confirmation for ones running a background process
Click to expand...
Click to collapse
If you read in the link I posted, they go on to explain why things like music can continue to play. Honestly I don't really feel like pulling that information out for you, but the link is there so the information is there for you.
mysterioustko said:
If you read in the link I posted, they go on to explain why things like music can continue to play. Honestly I don't really feel like pulling that information out for you, but the link is there so the information is there for you.
Click to expand...
Click to collapse
you don't seem to get my point, it's not about what Google wants, it's about user expectation. it's clearly a task killer and it doesn't behave the way you expect a task killer yo behave. this is why people love apples crap - it works the way you expect it to. obviously Google wants the function to work differently, so they need to presnt it differently so people aren't confused
that was a big point from duartes, that people don't love android, and yet they still don't really get
it fully. hopefully jelly bean picks up where ics has failed so aaple can go back to the little **** hole it belong in
wonshikee said:
you don't seem to get my point, it's not about what Google wants, it's about user expectation. it's clearly a task killer and it doesn't behave the way you expect a task killer yo behave. this is why people love apples crap - it works the way you expect it to. obviously Google wants the function to work differently, so they need to presnt it differently so people aren't confused
that was a big point from duartes, that people don't love android, and yet they still don't really get
it fully. hopefully jelly bean picks up where ics has failed so aaple can go back to the little **** hole it belong in
Click to expand...
Click to collapse
So basically you still have not read anything on that link.....
I see a debate team in the making whahahaaha
But seriousley.... the artical is inspired on appel ios..... i think its a little different
Then ics...
But i see the general meaning about it,ics recent app key doesnt kil procceses of the android system thus doesnt show it,right? And not important for the user
But in all fairness.... my ics recent app key doesnt kill annything though
Verstuurd van mijn GT-P1000 met Tapatalk
demon2112 said:
I see a debate team in the making whahahaaha
But seriousley.... the artical is inspired on appel ios..... i think its a little different
Then ics...
But i see the general meaning about it,ics recent app key doesnt kil procceses of the android system thus doesnt show it,right? And not important for the user
But in all fairness.... my ics recent app key doesnt kill annything though
Verstuurd van mijn GT-P1000 met Tapatalk
Click to expand...
Click to collapse
lol nah there can't be a debate if a person chooses to ignore the facts. BTW, I didn't mean the article, I meant read the comments on that particular post. They break down how the app killing works from the recent apps list. It doesn't work exactly like killing a task would in the "manage apps" area. It depends on the app that you are killing.
mysterioustko said:
lol nah there can't be a debate if a person chooses to ignore the facts. BTW, I didn't mean the article, I meant read the comments on that particular post. They break down how the app killing works from the recent apps list. It doesn't work exactly like killing a task would in the "manage apps" area. It depends on the app that you are killing.
Click to expand...
Click to collapse
i stand corrected.... download the app......active app... its widget looks like a chip
instal it.... pop the widget on home and open browser,clise it with home key and open market and close it aswell with home key....the widget will show that there are 2 active apps....open recent app key and swype away....when widget refreshes it says 0 apps........voila..it truly is a killer that key.......
oke im confinsed....its realy a killer...now evereyone can check for them selves
Verstuurd van mijn Galaxy Nexus met Tapatalk
mysterioustko said:
lol nah there can't be a debate if a person chooses to ignore the facts. BTW, I didn't mean the article, I meant read the comments on that particular post. They break down how the app killing works from the recent apps list. It doesn't work exactly like killing a task would in the "manage apps" area. It depends on the app that you are killing.
Click to expand...
Click to collapse
difference is i understand the facts, you don't seem to understand at all my point. you talk just like a developer who doesn't understand why the user can't see your way to do something when the reality is, its the end user that's the most important. you even agree that it's not a real task killer but you can't see why that's a bad thing b because you think everyone who uses android really gives a ****. the only thing the end user will see is that it's "broken" for some apps. im fully aware of how the task killer works in android yet you keep thinking that's the topic. feel like im talking to a brick
im not sure why this concept of meeting expectation is so hard to grasp
as i said before, if Google wants it to work a certain way they need to present the function differently so the user doesn't expect differently, such as not showing apps that it won't close anyway, or allowing force close through a confirmation
It actually does kill the apps... sometimes. If anyone would have bothered to search around, this has already been discussed in detail. If an application is dormant, swiping it away from the recent apps screen will kill it. If an application is not dormant and actively using system resources, it will not kill the application.
2 posts up people!!!!
and get the proof for yourselves!
Verstuurd van mijn Galaxy Nexus met Tapatalk
Swiping away Google Talk doesn't kill it.
Swiping away Pandora doesn't kill it.
Swiping away Google Talk doesn't kill it.
Swiping away Groupme doesn't kill it.
Swiping away Terminal Emulator doesn't kill it.
Swiping away Maps doesn't kill it.
Yeah...I think I have convinced myself that its not a task killer. The same tasks killed by swiping away are the same ones that hitting the back button kills in any other Android OS. Business as usual, and depends on how the app is coded. I didn't use a third party anything to check. I looked under running in Manage Apps.
pks check with that app and report back plz
Verstuurd van mijn Galaxy Nexus met Tapatalk
demon2112 said:
pks check with that app and report back plz
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I am not gonna use a third party app for what I can see in Running. For all I know (and its likely) the third party app is incorrect.
adrynalyne said:
I am not gonna use a third party app for what I can see in Running. For all I know (and its likely) the third party app is incorrect.
Click to expand...
Click to collapse
+1. All of you are talking about using crappy third party apps to check if swiping away an app kills it and preaching the results as gospel, none of you even knew how to check if an app is legitimately terminated. Smh. Swiping away apps in recent doesn't terminate it. All apps are coded differently. Learn about the OS before making claims of how a part of it operates in opossition to what its creators have stated.
Sent from my Galaxy Nexus using XDA App
What's a good app or way to close all apps at once?
Sent from my Nexus 4 using xda app-developers app
mario24601 said:
What's a good app or way to close all apps at once?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Press the Home button.
irishtexmex said:
Press the Home button.
Click to expand...
Click to collapse
lol apps dont close when you press the home button smart one. and op if you click the multi-window button(the one on the right of home button) you can swipe them all away really fast but dont really know about all at once
FaDeGFX said:
lol apps dont close when you press the home button smart one. and op if you click the multi-window button(the one on the right of home button) you can swipe them all away really fast but dont really know about all at once
Click to expand...
Click to collapse
Yes was hoping for an all close at once type app. Had that on iPhone thought might have something similar.
Sent from my Nexus 4 using xda app-developers app
There are 3rd party app killers in the play store. Check there...
There was a stock task manager...but I guess Google removed it for JB
Sent from my Nexus 4 using xda app-developers app
App killer
Cyanogenmod 10.1 has a button on the multitasking menu to do that. But it's kinda pointless except to clear the list of recently used apps. Android, if my understanding is correct, automatically fills the memory with tasks so killing apps is worse than pointless since you're just causing the system to prioritize unused background processes over the ones that you use more often.
Sent from my Galaxy Nexus using xda premium
irishtexmex said:
Press the Home button.
Click to expand...
Click to collapse
You should listen to this guy. I know you're coming from a different OS, so you aren't aware of how Android deals with memory. The system is very good at multitasking. Apps that have been idling in the background will be pushed out and won't consume resources or ramp up your CPU. By killing those apps, you force the system to have to reload and process resources necessary to start the app. Android will keep enough of the resources to quickly fire up the app, but restrict activity so that your battery is pretty much unaffected.
An analogy if you need it: Android will bookmark and close whatever you were reading. That way, you can move the book around or leave it on the shelf and quickly pick it up and continue from the last page you were on. You are requesting that the system instead just closes the book, and buries it in a box with other books, and which is located in the attic. It takes more resources to find the book and locate the page again. Just let Android do its thing. Any popular dev will tell you the same thing.
TL;DNR - Don't use a task killer, you will get far better battery life and performance if you let the system deal with system resources.
FaDeGFX said:
lol apps dont close when you press the home button smart one. and op if you click the multi-window button(the one on the right of home button) you can swipe them all away really fast but dont really know about all at once
Click to expand...
Click to collapse
Don't listen to this guy. He used the phrase "smart one," which I haven't heard since I was in elementary school (and I thought it was un-clever and uselessly sarcastic then). He also thinks that swiping away apps from the recents menu kills them. This is not how Android works. AOKP devs will not implement a recents menu that actually does let you swipe to kill apps because it's a useless feature that does more harm than good (zero benefit, actually). Just trust that your system knows how to handle its resources.
TL;DNR - Swiping away apps from the recents menu doesn't kill them. Stop trying to kill apps; only do so if they're unresponsive.
If u really want it, aokp has this feature
Sent from my Nexus 4 using Tapatalk 2
reboot?
Hung0702 said:
You should listen to this guy. I know you're coming from a different OS, so you aren't aware of how Android deals with memory. The system is very good at multitasking. Apps that have been idling in the background will be pushed out and won't consume resources or ramp up your CPU. By killing those apps, you force the system to have to reload and process resources necessary to start the app. Android will keep enough of the resources to quickly fire up the app, but restrict activity so that your battery is pretty much unaffected.
An analogy if you need it: Android will bookmark and close whatever you were reading. That way, you can move the book around or leave it on the shelf and quickly pick it up and continue from the last page you were on. You are requesting that the system instead just closes the book, and buries it in a box with other books, and which is located in the attic. It takes more resources to find the book and locate the page again. Just let Android do its thing. Any popular dev will tell you the same thing.
Click to expand...
Click to collapse
Let's say I start loading a web page and quickly jump to another app before it's loaded, then when I return to Chrome the page is ready and waiting. Doesn't this imply that apps are not just simply bookmarked and closed, but may remain active in the background? I am asking, not saying btw.
1234568 said:
Let's say I start loading a web page and quickly jump to another app before it's loaded, then when I return to Chrome the page is ready and waiting. Doesn't this imply that apps are not just simply bookmarked and closed, but may remain active in the background? I am asking, not saying btw.
Click to expand...
Click to collapse
Foreground apps are told that they are no longer in view, but are allowed to keep running if they wish. The OS will stop them if the memory is needed - which with 2GB is not very often on the nexus 4!
So Hung0702 was wrong on the last page when he said:
Apps that have been idling in the background will be pushed out and won't consume resources or ramp up your CPU
Click to expand...
Click to collapse
It seems as though background apps can use resources and may have a negative impact on battery. Now I have got to the bottom of this I also want a clear all button!
1234568 said:
So Hung0702 was wrong on the last page when he said:
It seems as though background apps can use resources and may have a negative impact on battery. Now I have got to the bottom of this I also want a clear all button!
Click to expand...
Click to collapse
Yes, they can keep using resources in the background. However, they will usually not keep the cpu awake unless they have an actual background service, so they will not stop the device from sleeping. As far as I know this is not enforced, but most apps will release the wakelock when told to pause by the OS (because the app is now hidden). This means they shouldn't have much impact on battery life.
You can see what is currently running by going to Settings -> Apps and select the Running tab. The recent apps list is not the same - most will have actually closed when you hid them.
Is there a way to have ram manager or the phones system itself keep the messages and calendar and contacts always ready to open right away?
Ram manager doesn't do this even though they are on my Whitelist. Also what's the best battery life settings people use?
Thanks!
Alpinestars96 said:
Is there a way to have ram manager or the phones system itself keep the messages and calendar and contacts always ready to open right away?
Ram manager doesn't do this even though they are on my Whitelist. Also what's the best battery life settings people use?
Thanks!
Click to expand...
Click to collapse
Android today, to me, doesn't need any of that stuff, just don't clean your recent apps list. Next time you wanna open the same app, hold down Home button, pulls up your recent apps. The apps you left open will be there until you remove it. Battery is different for everyone and every ROM/Kernel. This should have been in Q&A for future reference.
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
joeyhdownsouth said:
Android today, to me, doesn't need any of that stuff, just don't clean your recent apps list. Next time you wanna open the same app, hold down Home button, pulls up your recent apps. The apps you left open will be there until you remove it. Battery is different for everyone and every ROM/Kernel. This should have been in Q&A for future reference.
Click to expand...
Click to collapse
Ok thanks, I kniw about the the recent apps menu but sometimes my apps will close take longer to re open. I was wondering if I can make apps stay open in tbe background and never close
Alpinestars96 said:
Ok thanks, I kniw about the the recent apps menu but sometimes my apps will close take longer to re open. I was wondering if I can make apps stay open in tbe background and never close
Click to expand...
Click to collapse
Sounds like you have too many apps sucking up ram already, causing lag. Only certain apps stay open, like ones you don't sign out of(Facebook, Twitter, and many more)
This is double edged sword. You keep apps open to make them open quickly and minimize delay but keeping them open hinder battery life. Is it really taking that long to open apps? I would look into why that is rather than figuring out how to keep them open.
Alpinestars96 said:
Ok thanks, I kniw about the the recent apps menu but sometimes my apps will close take longer to re open. I was wondering if I can make apps stay open in tbe background and never close
Click to expand...
Click to collapse
Skeeredfitless said:
This is double edged sword. You keep apps open to make them open quickly and minimize delay but keeping them open hinder battery life. Is it really taking that long to open apps? I would look into why that is rather than figuring out how to keep them open.
Click to expand...
Click to collapse
No it doesnt take long to open I was just wondering how if thrre was a way
Alpinestars96 said:
No it doesnt take long to open I was just wondering how if thrre was a way
Click to expand...
Click to collapse
The only thing I can think of is to flash a TW ROM that allows 1 or 2 apps to stay open on one screen, like MSG&CHUBBZ, WICKED SENSATIONS, or MOAR ROM. Most TW based ROMS have this multiwindow feature which will alow you to keep one open, then open another on the same screen if you like.
joeyhdownsouth said:
The only thing I can think of is to flash a TW ROM that allows 1 or 2 apps to stay open on one screen, like MSG&CHUBBZ, WICKED SENSATIONS, or MOAR ROM. Most TW based ROMS have this multiwindow feature which will alow you to keep one open, then open another on the same screen if you like.
Click to expand...
Click to collapse
Ok thanks everyone!
I dunno if other people feel the same way but don't you hate it that you have to scroll all the way to the left to press the clear all apps button? Is there a way to make that show up on the right instead?
Yes, bad design ...
I've submitted a request to google via settings/about phone/send feedback about this device to move the clear apps button to be placed next to screen shot and select options when you open up the recent screen.
It is annoying when if like me you have the habit of clearing apps down, although I read somewhere that Google would preferer you to not clear recent apps so they load quicker when next opened and that their learning adaptive battery preferences help snooze the apps in the background and learns when you are likely to use them next so it so they are ready for you. I'm sure if I'm wrong I'll be corrected about the info.
I mean, it's pointless having it there lol, it's like they sat down and asked each other, would would be the most inconvenient place to put this!
m1ckbr1t said:
I've submitted a request to google via settings/about phone/send feedback about this device to move the clear apps button to be placed next to screen shot and select options when you open up the recent screen.
It is annoying when if like me you have the habit of clearing apps down, although I read somewhere that Google would preferer you to not clear recent apps so they load quicker when next opened and that their learning adaptive battery preferences help snooze the apps in the background and learns when you are likely to use them next so it so they are ready for you. I'm sure if I'm wrong I'll be corrected about the info.
Click to expand...
Click to collapse
What you read is apparently true actually. I saw the same answer when searching around.
orlans21 said:
What you read is apparently true actually. I saw the same answer when searching around.
Click to expand...
Click to collapse
Argh that's good, so I never dreamt about it Thanks for confirming
There is little to no reason to actually clear this list. It may help clear up some RAM, but the phone has so much that it truly does not matter.
Apps will go into suspended state after not being touched after some time.
stuff said:
There is little to no reason to actually clear this list. It may help clear up some RAM, but the phone has so much that it truly does not matter.
Apps will go into suspended state after not being touched after some time.
Click to expand...
Click to collapse
I know this but it's habbit for me and others alike, I just like them to be closed been doing it since I got my very 1st android a million years ago also it's a little OCD to clear things off, for me it is..... I sometimes get frustrated with myself because I'll clear an app that I've just been on and know I'm going back to it but still close it....
Left is weird for me as well
m1ckbr1t said:
I know this but it's habbit for me and others alike, I just like them to be closed been doing it since I got my very 1st android a million years ago also it's a little OCD to clear things off, for me it is..... I sometimes get frustrated with myself because I'll clear an app that I've just been on and know I'm going back to it but still close it....
Click to expand...
Click to collapse
This is a bad habit, Google is doing you a favour by making it more difficult.
Clearing the apps will actually make the phone slower and waste more battery. Because it has to load every app from scratch, every time. Every app will take a few seconds longer to open, CPU will be stressed harder, doing tasks it already did a couple hours and would not need to do again if apps were not cleared up.
Obviously the CPU re-doing tasks will consume more battery and the phone will likely die before the end of the day and people will come here and complain about the battery being bad.
Apps being kept in memory is done for a reason and it is the best practice. It's how it's done in every OS, especially Linux.
In iOS, for instance, even if you clear the apps from the list, it won't actually clear everything from memory. and this is the best practice. If the app is misbehaving, go into settings and force kill it. Otherwise, you want the app to be in mem cache.
Do yourself a favour and drop this bad habit.
Teio said:
Do yourself a favour and drop this bad habit.
Click to expand...
Click to collapse
Agree. At first coming from my S8+, I missed clearing recents just out of habit to keep things organized when switching apps. Now however, I'm finding switching apps via swiping left/right on the bottom of the screen on the P6P to be super convenient. I hardly ever even open recents anymore, and if I need to remove a rarely used app from there it's much more practical to remove one with a swipe than all of them. Get out of the bad habit and save yourself some battery and loading time
The only time I ever clear an app from Recents is when a single app is giving me issues.
Agreed, I dropped this habit a while back as it really doesn't serve any purpose to clear them for the aforementioned reasons!