Develop Bugs

New Samsung apps in the marketplace

Several new apps showed up in the Samsung Zone last night:
Video Call
Basically what it sounds like, a 3G-based video calling app. Unfortunately, it apparently requires a FFC, so all it does on the Focus is display an error message and quit.
RSS Times
A pretty nice Google Reader app
AllShare
Samsung's DLNA media sharing app. But again, on the Focus all it does is display a "not supported" error and quit.
FunShot
An interesting-looking (haven't played with it yet) photo editor with some "funky" effects.
MiniDiary
A diary app with text, voice, drawing and photo support.

I'd have thought OEMs would be allowed to only target certain devices for their apps, so either they can't and theyre for the omnia w (etc) or we might be inline for some driver updates...

I use Minidiary which is a good app... we cannot use vedio call app but i think its prety amazing specially cos we can make vedio calls to iphone and android phones even if they dont have this app...
i want to upgrade to omnia W phone, but i will loose all my texts and have to unlock all levels again from begining in my xbox games.. which is the only thing preventing me from switching phones..

There is also an Advanced Text Message app if you tap on "more from Samsung.." but it doesn't work either.

They should let the video call app work on phones with no ffc. At least we can see the other person or we might use a mirror.
Working dlna would have been very good.

singularity0821 said:
There is also an Advanced Text Message app if you tap on "more from Samsung.." but it doesn't work either.
Click to expand...
Click to collapse
I can't see that one on my Focus, but I do see the new high fidelity positioning app, which is the first new app from Samsung that installs into the settings screen. It has two settings, one that increases GPS accuracy by using other sensors such as accelerometer and compass, and one that enables use of GLONASS (for users in Russia).

RoboDad said:
I can't see that one on my Focus, but I do see the new high fidelity positioning app, which is the first new app from Samsung that installs into the settings screen. It has two settings, one that increases GPS accuracy by using other sensors such as accelerometer and compass, and one that enables use of GLONASS (for users in Russia).
Click to expand...
Click to collapse
I downloaded that app. Interesting how it installs itself in your settings. My question is, what if we want to uninstall it? How do we? Holding it down doesnt give us the option.

albertleao said:
I downloaded that app. Interesting how it installs itself in your settings. My question is, what if we want to uninstall it? How do we? Holding it down doesnt give us the option.
Click to expand...
Click to collapse
Well, I know this isn't the same, but you can just disable it...

albertleao said:
I downloaded that app. Interesting how it installs itself in your settings. My question is, what if we want to uninstall it? How do we? Holding it down doesnt give us the option.
Click to expand...
Click to collapse
if you can sideload the xap this worked for me.
get XAPDeployX.exe
load Zune and have phone plugged into USB
start XAPDeployX.exe
load the app you want to remove from settings page
check options "force uninstall if application is already installed"
click deploy. at some point XAPDeployX will tell you that it found and successfully uninstalled the existing application.
right then you unplug the phone, just in time before it installs the new one.
voila, the app is gone from settings.

albertleao said:
I downloaded that app. Interesting how it installs itself in your settings. My question is, what if we want to uninstall it? How do we? Holding it down doesnt give us the option.
Click to expand...
Click to collapse
There is really no need to uninstall it. It takes up very little space, and if neither option is turned on, it does nothing.

RoboDad said:
There is really no need to uninstall it. It takes up very little space, and if neither option is turned on, it does nothing.
Click to expand...
Click to collapse
not if you are anal like some of us that can't bare the fact that there is something stray in the settings page

derausgewanderte said:
not if you are anal like some of us that can't bare the fact that there is something stray in the settings page
Click to expand...
Click to collapse
Oh, I am. OCD is my life . I just look at it as Samsung providing an app to install a Mango setting that didn't make it through development in time for the official Mango update. In other words, if the setting had been part of the Mango firmware update, there would be no way to "uninstall" it without uninstalling Mango, right?
In fact, I wouldn't be surprised if the setting is automatically included in future Samsung firmware updates.

Casey_boy said:
I'd have thought OEMs would be allowed to only target certain devices for their apps, so either they can't and theyre for the omnia w (etc) or we might be inline for some driver updates...
Click to expand...
Click to collapse
Werent we like Xbox friends before? did you just unfriended me from your xbox?

Purple11 said:
Werent we like Xbox friends before? did you just unfriended me from your xbox?
Click to expand...
Click to collapse
Huh?! No idea what you're talking about!

YouTube in the background?

Is there a way to keep YouTube running music in the background as I'm exploring other apps? Coming from a pre there was a patch for this
Sent from my Galaxy Nexus using XDA App

Already a multiple page thread on this.

Never been possible on android and probably never will be.

noobdeagle said:
Never been possible on android and probably never will be.
Click to expand...
Click to collapse
It was doable before, but not anymore with the new update
Sent from my HTC Vision using Tapatalk

martonikaj said:
Already a multiple page thread on this.
Click to expand...
Click to collapse
Sorry, my bad.
Not used android before, I will also assume there isn't a hombrew/overclocking/patching repository and app like preware?
Also no way to enable flash in the background when flash becomes available?
Sent from my Galaxy Nexus using XDA App

Seems pretty silly having multi-core processing without the ability to multitask, doesn't it?

DirkGently said:
Seems pretty silly having multi-core processing without the ability to multitask, doesn't it?
Click to expand...
Click to collapse
You don't know much about Android, do you?
Android does have ability to multitask. It is just an effective multitasking. Applications can be left 'running' without them actually running. They are written in memory and kept there, without taking battery, until they are called back and continue on from where they left off. But Android also allows applications to open services in the background, triggered by specific time or event or by an application, that allows them to work while the application is not in focus. Many music players are done this way. Also a lot of apps synchronize in the background in this manner.
It is entirely the application developers decision to do what is best for the specific application. Android 4.0 gives all the tools the user needs. This is not Windows desktop where every working application and process takes processing power to keep running.

Would be awesome then if someone made a YouTube app that worked in the background
Sent from my Galaxy Nexus using XDA App

It'll never happen for the same reason that not all videos are viewable on mobile. You're using the service to watch something, not listen.

rmoney said:
You're using the service to watch something, not listen.
Click to expand...
Click to collapse
Not really. There are many people who use youtube for music playlists.

mcgon1979 said:
Not really. There are many people who use youtube for music playlists.
Click to expand...
Click to collapse
i know a jailbroken iphone has an app for that

iOS supports background audio in the browser and youtube app. I was hoping that ICS will support it.

Swiping away in task list DOES kill the task

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

Ram manager ??

So do you guys find it necessary to have a ram manager to free memory or no ?

No, ics have a good system to manage ram.

No. Creates more issues than it solves.

+1 for no. Watchdog has always been a must have for me, but it hasn't yet had to call out an app on my SGN.

No. Don't use automated tools to kill tasks and free up memory... in Android, free memory is wasted memory. You make your phone work harder when you interfere with its built-in memory management.

I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.

EP2008 said:
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
Click to expand...
Click to collapse
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.

adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Funniest thing I read all day and its true

adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk

EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App

EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Android does not operate like windows. Apps listed as "Running" are actually only loaded in ram and are not using cpu cycles or battery power. Android loads them in ram in order for them to start/be available more quickly to the user. If Android needs more ram for a task, it will remove any thing it needs to in order to free up more ram. You are wasting battery power and cpu cycles by "killing" those apps/service. If you think of ram as a memory stick you will realize that once something is loaded there, it doesn't take any power to keep it there.
Good luck
Good luck

jordanishere said:
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
System services should obviously not be messed with, but disabling autostarting services that you don't use is generally not a problem. It may take more power/time to start up apps that use those services (since they will have to be manually started), but if it's an app that you use infrequently it may be worth doing.
Intelligently tuning what services are allowed to autostart themselves is NOT the same as indiscriminately killing apps chasing after "free memory".
Personally, I wouldn't terminate services, but only modify which ones are allowed to automatically start up with the OS.

codesplice said:
if it's an app that you use infrequently it may be worth doing.
Click to expand...
Click to collapse
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App

EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
you basically proved what he said was true

I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.

jordanishere said:
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Eh, usually there's not much benefit to be had - but preventing a service from auto starting when you might not use its app for the entire time Android is booted won't cause any problems. You're essentially "freezing" the service while still allowing it to be used on demand .

WiredPirate said:
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
Click to expand...
Click to collapse
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN. Not necessarily a technical response, but just my experience.

Wow, the ignorance on XDA is staggering.
A RUNNING SERVICE is not the same as a cached app or background process.
Why the heck would anyone want 3 or 4 running services in the background when they don't need them running?
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk

EP2008 said:
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Less an Android flaw and more related to how developers wrote those apps. Otherwise I think we are in agreement though.

codesplice said:
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN.
Click to expand...
Click to collapse
why?
10char

Close all?

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.