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
Related
Multitasking should be nice and easy, on WP7 it isn't. I don't know whose idea it was to make the screenshots so big, it's a waste of space. I think they should've done multitasking the way they do tabs in IE9.
I also noticed that you can only swipe one app at a time in the multitasking view, so if you want the 5th app, you have to swipe 5 times. I find that very inefficient which is not the goal of multitasking. It wastes time...
Where is the little red x in the top right hand corner to close apps in multitasking view. Instead you have to swipe over to the app, open it hit back and then hold back to get back into multitasking view. What a waste of time...
Anyone else think this multitasking blows?
::missing the days of WM6 task manager::
Going to install Mango today. I'll report my impressions then Hope that it's still rocking
blindpet said:
Multitasking should be nice and easy, or WP7 it isn't. I don't know whose idea it was to make the screenshots so big, it's a waste of space. I think they should've done multitasking the way they do tabs in IE9.
I also noticed that you can only swipe one app at a time in the multitasking view, so if you want the 5th app, you have to swipe 5 times. I find that very inefficient which is not the goal of multitasking. It wastes time...
Where is the little red x in the top right hand corner to close apps in multitasking view. Instead you have to swipe over to the app, open it hit back and then hold back to get back into multitasking view. What a waste of time...
Anyone else think this multitasking blows?
::missing the days of WM6 task manager::
Click to expand...
Click to collapse
Yeah, the swipe thing kinda sucks. You don't need to close no apps though. Just keep in mind how the so called multitasking works. There is actually NOTHING running in the background. Apps you leave remain in a frozen state until you revive them (or not).
this means that a ringer app must like in w7.0 run and the akku power goes low over night?
ahlMAR said:
this means that a ringer app must like in w7.0 run and the akku power goes low over night?
Click to expand...
Click to collapse
Huh?
10 chars
ahlMAR said:
this means that a ringer app must like in w7.0 run and the akku power goes low over night?
Click to expand...
Click to collapse
If you are referring to an alarm app, in Mango it would schedule a task / background agent that will be invoked when the necessary time comes. It won't have to run in the background and use any battery.
dkp1977 said:
Yeah, the swipe thing kinda sucks. You don't need to close no apps though. Just keep in mind how the so called multitasking works. There is actually NOTHING running in the background. Apps you leave remain in a frozen state until you revive them (or not).
Click to expand...
Click to collapse
Currently.
That's what's changing. It is real multitasking in mango but the apps need to be built to utilise it (which they're not at the moment, because we've only just started to build for it).
Whoops.
Casey
i keep pressing the start button for multitasking lol
Casey_boy said:
Currently.
That's what's changing. It is real multitasking in mango but the apps need to be built to utilise it (which they're not at the moment, because we've only just started to build for it).
Casey
Click to expand...
Click to collapse
No its not. There is support for background tasks (periodic or scheduled) which have limitations on how often they can run and their CPU usage. There is also some special support for background file transfers and audio, not sure what else.
Your apps will definitely not continue to run in the background.
As someone said above, there is no true background multitasking. Your apps freeze in the background, and they now have the ability to instantly resume (rather than having to restart completely or take a few seconds to resume) when re-programmed to do so.
There are also special tasks that applications can take advantage of, but it is very restricted, and then you also have your background tasks, which is kinda like "services" on a Windows PC. The background tasks sit in the background and can do certain things, and that can be managed from the settings menu, but they too are still rather limited.
Holding "back" on your phone is just a list of recent applications, it's not something that shows you what is running in the background (because nothing is). Because of that, there is no need for a close button since there is nothing to close really.
I agree the way they do it in IE is more elegant. I also would like the ability to swipe away something. I know that since most of the time something isn't actually running, there is no need, but since it only keeps the last few tasks, I could then potentially keep something open all day by swiping away other cards first.
PG2G said:
No its not. There is support for background tasks (periodic or scheduled) which have limitations on how often they can run and their CPU usage. There is also some special support for background file transfers and audio, not sure what else.
Your apps will definitely not continue to run in the background.
Click to expand...
Click to collapse
Ah ok. Thanks. Must have gotten mixed up between what we can actually do!
I think it would be better if the swipe could make us roll more than one app at a time. Just like in IE; if you want to go down, really down on the page, just swipe up fast.
Oh crap.. dont know how it's called or how to explain in a decent way.
Anyway, I hate having to swipe one app at a time, and I think there is no need to show "Start" in cards.
mikeeam said:
I think it would be better if the swipe could make us roll more than one app at a time. Just like in IE; if you want to go down, really down on the page, just swipe up fast.
Oh crap.. dont know how it's called or how to explain in a decent way.
Anyway, I hate having to swipe one app at a time, and I think there is no need to show "Start" in cards.
Click to expand...
Click to collapse
I've noticed that if you swipe really gently, you can get it to scroll across multiple tasks. It seems really sensitive, and maybe that' just a bug. Sometimes it'll go one at a time, and sometimes it'll swipe across 2 or 3 apps with just the right amount of pressure.
Has anyone here played with the HP TouchPad yet? They use a card like system for multi-tasking too and it has some good ideas. To close a task, you flick the card upwards off the screen and it's killed. I think something like this would work well for WP7.
Also, I'm with everyone else who doesn't like how you can't scroll smoothly across several tasks. I wanna be able to flick across the list quickly.
mikeeam said:
I think it would be better if the swipe could make us roll more than one app at a time. Just like in IE; if you want to go down, really down on the page, just swipe up fast.
Oh crap.. dont know how it's called or how to explain in a decent way.
Anyway, I hate having to swipe one app at a time, and I think there is no need to show "Start" in cards.
Click to expand...
Click to collapse
ken52787 said:
Also, I'm with everyone else who doesn't like how you can't scroll smoothly across several tasks. I wanna be able to flick across the list quickly.
Click to expand...
Click to collapse
I think I found out how to make it scroll multiple tiles consistently. Simply do two swipes very quickly. Once it starts a smooth scroll you can also move back and forth easily without it snapping to each tile.
prjkthack said:
I think I found out how to make it scroll multiple tiles consistently. Simply do two swipes very quickly. Once it starts a smooth scroll you can also move back and forth easily without it snapping to each tile.
Click to expand...
Click to collapse
Nice one! Now it got better.
So it's not a bug. It's a feature. Still, I dont like the "Start" card. It's useless.
prjkthack said:
I think I found out how to make it scroll multiple tiles consistently. Simply do two swipes very quickly. Once it starts a smooth scroll you can also move back and forth easily without it snapping to each tile.
Click to expand...
Click to collapse
Hmm yes that seems to work. It should really be like that all the time though.
Thanks for pointing that out, it's still flawed though. You shouldn't have to make two quick swipes to make it go quickly it should depend on the speed of the swipe.
The cards are also too big, I really hope they change it to the IE tab style which has easily has enough space for the 5 previous tasks we were doing.
Other than that Mango is snappier and everything which is great but they still have a ways to go, their multitasking interface is nothing to be proud of.
I would bet that in the final build (or perhaps sooner) the scrolling through the MT menu will change to only require one swipe as does everything else in the OS.
As far as the style, when I first saw it I was thinking the same thing. When you hold the back button, why not have it look like the tabs in IE with a little "x" in the corner?
Considering it freezes apps, there is no need to really kiil any. But, I do agree that it would serve a good purpose if you didn't want something pushed out of memory and wanted to keep a particular app around for awhile.
Regardless, I like the functionality and thinks it works well as intended.
And, let us remember people, THIS IS SPARTA!!! er... I mean, this is beta.
Things will be fixed, rerendered, optimized further, added, deleted, and so on. So, let's not get in too big a tizzy over what things look like right at this moment. I mean, ya gotta admit, for a beta, this thing is damn good.
I love my Galaxy Nexus, but what's driving me crazy is how it shuts down any app whenever I switch out of it, even if I use the -completely useless so far- multitasking soft key. So for instance I'm waiting for a YouTube video to load, so I temporarily switch out of it to do something else (this is a smartphone isn't it) and come back, and find it reopening the video as if I just did it. Same thing with the browsers. I have 2-3 tabs open, and decided to check out something on the homescreen. Big mistake. When I get back will have to wait for all the tabs to reload.
Anyway to keep apps running in the background?
Sent from my Galaxy Nexus using XDA App
I think YouTube just does that. It has been mentioned before. No problem with the browser.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
If your using a Verizon nexus, it partly has to do with Verizon's cdma network, not just android. Plus it would slow your phones operation down and you would see more force closes due to limited resources.
Edit— sorry everybody, did a little drunk forum trolling last night. Everything I posted was false. The other poster was correct and I deserve all the shame.
Transmitted from my Galaxy Tab 10.1 via Tapatalk
Most likely you have an app running thats killing processes. If you have any task manager/killer remove it immediately.
As far as youtube goes, youtube will NEVER keep a video paused or continue playing if you leave. It saves what you were on, but thats it. few reasons for that.
Now, my experience today and no issues.
Facebook, Browser (4 tabs), NFL'11, and twitter all running and they all saved what i was doing and none of them ever closed.
in fact, 3 hours after, the 4 tabs were still open. I've actually had tabs open for 3 days straight that i forgot to close and the browser just made new ones.
and these are not just text sites. I had the Battlefield 3 battlelog, nfl.com, battlefield wiki, and the verge mobile all on.
My browser will keep pages open for days if I wanted to...strange! You're using stock browser?
Sent from my NookColor using XDA Premium App
stock browser is awesome. especially the inverted mode.
Pretty amateur thread. Come on
Sent from my Galaxy Nexus using xda premium
Stardate Tab 10.1 said:
If your using a Verizon nexus, it partly has to do with Verizon's cdma network, not just android. Plus it would slow your phones operation down and you would see more force closes due to limited resources.
Transmitted from my Galaxy Tab 10.1 via Tapatalk
Click to expand...
Click to collapse
I can't find one fact in your entire statement. What could CDMA possibly have to do with it? Also, you wouldn't see more 'force closes'. When Android runs low on RAM it selects the oldest cached app and ends it, unless it's active.
once again, amateur thread. **** needs to be closed down
TareX said:
I love my Galaxy Nexus, but what's driving me crazy is how it shuts down any app whenever I switch out of it, even if I use the -completely useless so far- multitasking soft key. So for instance I'm waiting for a YouTube video to load, so I temporarily switch out of it to do something else (this is a smartphone isn't it) and come back, and find it reopening the video as if I just did it. Same thing with the browsers. I have 2-3 tabs open, and decided to check out something on the homescreen. Big mistake. When I get back will have to wait for all the tabs to reload.
Anyway to keep apps running in the background?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Do you have Don't keep activities checked in the development part of settings? Go to Settings>Developer Options, scroll all the way down, and look if you've enabled the option I've mentioned above
Sent from my Galaxy Nexus using xda premium
I have this exact same problem, with the browser and even with games.
I have no task manager. I have watchdog which i believe doesnt kill any processes itself and i have juice defender; could that be whats causing this problem?
I keep hearing about this, am I seriously the only one that can swipe apps away from the recent apps and they actually close?
Sent from my Google phone
ChongoDroid said:
I keep hearing about this, am I seriously the only one that can swipe apps away from the recent apps and they actually close?
Sent from my Google phone
Click to expand...
Click to collapse
possibly you are...
because for me and more than 5 of my friends using the same phone, those swiping aways only close the shortcut regardless of the app running in background or not.
DO THE FOLLOWING
1) go to settings, apps, running apps.
2) with that open, hit the multitask button that shows all apps running.
3) swipe away
4) watch it get killed off your running apps list.
5) grow up
Im not sure what all the *****iness is about but the problen I and i believe the OP were having was quite real and serious.
Any time you switched out of an app or game, even if only for a second, when you switched back it would restart the app or game and in the case of the browser reload the webpage.
Now, ive uninstalled watchdog and the problem seems to have gone away.
Is anybody else using watchdog having this problem?
People need to understand that devs put this code INTO THEIR APPS. Killswitches are hard coded into apps to let the system kill them if they have been in the background. A good example is Opera Mobile. It has a low priority that is coded in BY THE DEV.
schizophrenia said:
possibly you are...
because for me and more than 5 of my friends using the same phone, those swiping aways only close the shortcut regardless of the app running in background or not.
Click to expand...
Click to collapse
Not possibly, I know I am. Home key keeps it running, back key caches/closes it. Certain apps perform differently as foreground tasks and some as background tasks. I think some can't be multi tasked like big games and stuff but as previously said that's on the dev side not androids.
Sent from my Galaxy Nexus using xda premium
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
What is known safe to freeze
as listed in titanium backup, I've been able to freeze the following bloat without any issue:
Allshare cast
Allshare play
Allshare service
AT&T * (everything starting with "AT&T" can be frozen)
ChatON
DeviceHelp
Flipboard
Kies* (everything starting with "Kies" can be frozen)
media hub
music hub
my AT&T
news daemon
s suggest
s voice
samsung backup provider
samsung browser syncadapter
samsung calendar syncadapter
samsung cloud data relay
samsung contact syncadapter
samsung snote syncadapter
samsung syncadapters
SNS
stock daemon
swype (keyboard still works fine without swype support)
sysscope
tethering provision
vpn client
weather daemon
weather widget
weather widget main
yahoo finance
yahoo news
YP Mobile
There are many other things that can be frozen - this (so far) is just a list of what I'm currently freezing
AT&T users: The "mobile hotspot" icon that shows up in your app drawer doesn't have it's own app that you can freeze. It appears to be something in the settings.apk (and you probably don't want to freeze that.)
FM Radio
There isn't one. Based on my research, the hardware either doesn't exist or isn't physically connected. No luck with spiritFM either. This matches what international users have found with the n7105 (international LTE note2)
The "mobile hotspot" icon that shows up in your app drawer doesn't have it's own app that you can freeze. It appears to be something in the settings.apk (and you probably don't want to freeze that.)
I'm trying to figure out how to deodex a JB firmware... once I have that, I'll be uploading doing a few minor mods (and uploading them, of course.)
Another reason to go international if you don't have lte in your area.
Jesus AT$T, got bloat?
SGH-I717 Galaxy Note | AOSP/CM/AOKP <3 via Tapatalk II
added note about FM radio, updated post title to reflect that I'm just dumping random "faq" type information in it.
Great info! However personally, I'd wait with freezing apps since android operating systems have a wakelock specifically designated for deleted/frozen apps. Why or what for? No clue, but it's there. I'll wait until I can actually remove them completely. Either way this phone's battery and performance is awesome out of the box, even with bloatware :thumbup:
Sent from my SGH-I317M using xda premium
AlonB. said:
Great info! However personally, I'd wait with freezing apps since android operating systems have a wakelock specifically designated for deleted/frozen apps. Why or what for? No clue, but it's there. I'll wait until I can actually remove them completely.
Click to expand...
Click to collapse
No.. your off base there. deleted_wakelock has nothing whatsoever to do with a frozen app. A wakelock is actually a kernel structure. When an app cleans up after itself, the time it had in wakelock is added to the deleted_wakelocks counter.
Xstop said:
Another reason to go international if you don't have lte in your area.
Jesus AT$T, got bloat?
SGH-I717 Galaxy Note | AOSP/CM/AOKP <3 via Tapatalk II
Click to expand...
Click to collapse
takes 5 min to disable it all forever.. not gonna get up in arms this time
This is still a pretty good excel source for the novice although it is for stock.
Collected way back for SGS2
frewys said:
This is still a pretty good excel source for the novice although it is for stock.
Collected way back for SGS2
Click to expand...
Click to collapse
Thanks for this! I was looking to ask the question in q&a. Would this be pretty close to SGN2?
sent using gNote II.
Thanks for the great info! I'll definitely be doing this soon after I get mine. I'm curious, how much of a difference in memory consumption/speed have you noticed after disabling all this bloat?
skochw said:
Thanks for the great info! I'll definitely be doing this soon after I get mine. I'm curious, how much of a difference in memory consumption/speed have you noticed after disabling all this bloat?
Click to expand...
Click to collapse
Well... I really can't answer that, as I didn't seriously use the phone until after I disabled that stuff.
garyd9 said:
Well... I really can't answer that, as I didn't seriously use the phone until after I disabled that stuff.
Click to expand...
Click to collapse
Ah. well maybe you could run some benchmarks or something, and we could compare with stock scores?
skochw said:
Ah. well maybe you could run some benchmarks or something, and we could compare with stock scores?
Click to expand...
Click to collapse
1. It wouldn't show up in benchmarks, as benchmarks tend to grab exclusive use of the device (meaning the other stuff wouldn't matter.) As well, I don't believe in benchmarks - they are too easily compensated for.
2. By freezing unused services, they'll never start which means the phone doesn't hold them in memory (freeing memory), doesn't use processor cycles to load/reload/execute them which will result in a lower battery usage (depending on the specific service) and allow the phone to "feel" faster in some cases.
3. Finally, freezing stuff that you don't use cleans up the app drawer. Why would anyone want an icon (even if they don't use it) for AT&T's navigation software when google gives us the same thing for free? (Freezing it also prevents someone else from using it if you loan them your phone.)
Of course, the idea of this thread isn't to discuss the merits of freezing bloat (or the merits of urinating when the need arises.) The idea is to let people know what is "safe" to freeze (and give other device information.)
As a guy coming out of the Apple iOS world, I have to say that the only Android device I've held is my wife's Galaxy Nexus on Verizon, and I'm not familiar with the terms "app drawer" or "freezing" apps. Can I ask for a little clarification without sounding like the total noob I am, please?
ohRonaldo said:
As a guy coming out of the Apple iOS world, I have to say that the only Android device I've held is my wife's Galaxy Nexus on Verizon, and I'm not familiar with the terms "app drawer" or "freezing" apps. Can I ask for a little clarification without sounding like the total noob I am, please?
Click to expand...
Click to collapse
(I hope you take this with the humor intended...)
No, there is simply no possible way for you to ask that without sounding like a newbie. However, it's okay... we were all newbies at one time.
"app drawer" - in iOS, every app you install leaves an icon on your homescreen (or one of the homescreens.) That isn't the case with android. In android, YOU decide what your homescreen looks like - you can have app icons, widgets, or just leave them blank. There is usually an icon on the homescreen that lets you access your "app drawer" which contains all the phone apps. On the note2 with default configuration, thats the checkerboard looking icon on the lower right of the homescreen.
freezing - using an application such as "titanium backup", you can "freeze" an app. This is a way to basically completely disable and hide an application without physically uninstalling it. The only effective difference between a frozen app and one that's actually uninstalled is that the frozen app still can be "defrosted" (which restores it to normal.) freezing apps requires that your phone is rooted (which is a topic for another thread...)
ohRonaldo said:
As a guy coming out of the Apple iOS world, I have to say that the only Android device I've held is my wife's Galaxy Nexus on Verizon, and I'm not familiar with the terms "app drawer" or "freezing" apps. Can I ask for a little clarification without sounding like the total noob I am, please?
Click to expand...
Click to collapse
The " app drawer" is the location on android that has your application launch icons (and widges). If you delete the app icon on the desktop you can gain access to the installed app here. You can grab a copy from the tray to deposit on other desktop pages.
The term "freezing" is a method to make installed apps dormant and thus not "call home" or use CPU cycles / memory resources that drain power or use data. These are usually done in preparation in determining what apps to un-install. Un-installing bundled applications may leave you no way to re-install them later, short of re-flashing to stock ROM.
Most folks will attempt to freeze apps to remove "bloatware". Later the storage can be reclaimed by un-installing the apps. By freezing, you can avoid "burning a bridge" you may find you need later.
Dynamite answers, thanks. I'm familiar with that app drawer, just didn't know its name, and the requirement of root for a freezing app will be juuust a bit down the road until I can understand the new OS environment.
PS I am a software engineer from way back, part of the generation responsible for "Are you sure?" and "General Error. Continue?" prompts, so.... I deserve every bit of jazz anyone wants to heap on me.
ohRonaldo said:
PS I am a software engineer from way back, part of the generation responsible for "Are you sure?" and "General Error. Continue?" prompts, so.... I deserve every bit of jazz anyone wants to heap on me.
Click to expand...
Click to collapse
Hmmm... The response, "Hit Any Key to continue..." comes to mind. I'm still looking for the Any Key and have never found it. :laugh:
the builtin application manager can disable some programs... i'm wondering if this is the same as freezing
ShadowVlican said:
the builtin application manager can disable some programs... i'm wondering if this is the same as freezing
Click to expand...
Click to collapse
yes
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.