• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps not closing after exiting them??

ThatonedudexP

Well-Known Member
I've had my Showtime for over a month, but I just activated it yesterday. On my old Proclaim, if I was playing a game and pressed the home button, I could click the task manager app (came with the phone), and it would most likely show that game as active. If I was in a hurry, I could press the stop button and close it immediately. Well..... when I first started using my Showtime, I couldn't find the task manager app. After I activated it, it popped up out of nowhere. The weird thing is, it seems like whenever I exit ANY app on the phone, even ones that came with the phone, they won't stop running! I.E. After I made a call and looked in my contacts yesterday, I went to the task manager, and it showed them as running although they weren't even in use. Every time I exit Google Chrome, according to the task manager, it stays running as well. FYI, when I say exit an app, I mean click the back button, not the home button. All these running apps I'm not even using absolutely murders my RAM. What confused me is with my Proclaim, there was a section in settings under applications labeled 'running apps' where you could find out what apps were using the phone's RAM, and in the task manager app there was a section labeled 'active apps'. (So, obviously two separate areas.) With my Showtime there's still a section under applications in settings labeled 'running apps', but in the task manager, they changed the 'active apps label' to 'running apps'. Now, there's two sections of running apps, and they aren't the same... :confused::confused::confused: Is anyone else having this problem with apps not closing after exiting them? Oh, my battery will only charge to 98%. Is anyone having that issue as well?
 
With the apps, 9 times out of 10 they will remain in memory even though you exited them using the back button. This is generally because the app has some service process active such as push notifications. You can disable notifications, and when you exit the app with the back button, it will generally be removed from the running apps list. However, Android has this nasty habit of turning them into a cached process in the event the app gets used again it can start it more quickly. A couple of options that you have (which both require a rooted device) is 1. Use an app like Greenify to force apps into hibernation, which can help free up memory, or 2. Use an app like Rom Toolbox to adjust minfree values. I don't recommend the latter unless you know exactly what you're doing, as setting minfree values too high could cause serious instability or even render the device useless.
As for the battery issue you described, this is pretty common across a vast majority of devices and is generally nothing to be concerned about.
 
"Not used RAM is useless RAM"
A process remaining in memory doesn't use processor power, that's why it doesn't consumed battery. Its remaining in memory even saves battery power when the app is restarting.

This post contains a nice explanation ... :)
Stuntman said:
A task that is taking up RAM does not affect performance. If it did, Android would have removed these tasks from RAM. The reason they use RAM in the first place is so that when you launch them, they would launch faster because they are already in RAM. This would improve your performance.

Having more free RAM may not improve your performance. If there is unused RAM, Android tries to anticipate what tasks you are likely to launch in the future and loads them into RAM.

Harry
 
Back
Top Bottom