[Q] sliding out recent apps - General Questions and Answers

I've read that it's not necessary to use a task manager and kill processes/programmes as Android manages itself fine.
But what about sliding out the recent apps list? What does it do and is it good/bad doing it?
Don't know if it matters but I've got Android 4.4.4.

trey77 said:
I've read that it's not necessary to use a task manager and kill processes/programmes as Android manages itself fine.
But what about sliding out the recent apps list? What does it do and is it good/bad doing it?
Don't know if it matters but I've got Android 4.4.4.
Click to expand...
Click to collapse
The recent apps is a way of multitasking on Android devices, this new feature was introduced in Honeycomb and was later improved in newer Android versions.
The purpose of this said feature as said before is to help a user multitask. So if you're browsing the internet and have a specific page up. A minute or so later you get a message so you open the messaging app and make a reply. But now you want to go back to the same app you were one earlier without having to restart, reload or wait for the content to appear.
When sliding a specific app (task) from the recent apps menu, you're basically killing the app. (Removing it from the multitasking menu, it reduces ram consumption as the process for that app has now been shut down or limited. For example if you kill a messaging app, it runs a background service so you can receive messages. When you have the app open or running in the background it opens a new process, when you slide the app away you're removing the background process for it but you're not disabling the server process. (So you will still get messages).
In short form, when you slide an app away from the recent menu, you're killing the apps process. This is good when you don't need or you are not using the app. So if you have you don't need to multitask with a specific app, remove it from the menu and it'll restore ram so it speeds up your device.
Hopefully I helped, if there was something you didn't quite understand. Let me know and I'll try and explain it furthermore.
Krish
Sent from my T-Mobile G1

TheArc said:
Hopefully I helped, if there was something you didn't quite understand. Let me know and I'll try and explain it furthermore.
Click to expand...
Click to collapse
Everything clear, thanks!

Related

Apps randomly starting in the background?

I use advanced task killer and minutes later I see MP3 Store, and Messages running. Before I saw a few others. Are they set to start running in memory for some reason? Not sure if they eat up much juice, but I wonder if I can make a list of certain ones and disable their start up somehow. Is there a task killter that blocks startups?
same here we need something to block these apps
Messages is required to recieve MMS (Even if you use handcent or chomp or something else as your main client). We tried removing that once in the hero forums and it caused ALL sorts of problems and force closes)
The mp3 store is usually ok to remove though.
thecodemonk said:
Messages is required to recieve MMS (Even if you use handcent or chomp or something else as your main client). We tried removing that once in the hero forums and it caused ALL sorts of problems and force closes)
The mp3 store is usually ok to remove though.
Click to expand...
Click to collapse
Thanks codemonk,
Do you know that setting in advance task killer is that says "auto kill level"? It is set to disable now, but what does it do? Thanks.
jeffrimerman said:
Thanks codemonk,
Do you know that setting in advance task killer is that says "auto kill level"? It is set to disable now, but what does it do? Thanks.
Click to expand...
Click to collapse
I'm not sure...I avoid task killers as a rule (I installed one earlier to test something for an earlier thread and uninstalled afterwards once I got my info).
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ - This should provide some good info on it.
The better solution, especially for apps that you don't intend on using, is uninstalling the app (there's a whole thread talking about which ones are safe to remove).
thecodemonk said:
I'm not sure...I avoid task killers as a rule (I installed one earlier to test something for an earlier thread and uninstalled afterwards once I got my info).
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ - This should provide some good info on it.
The better solution, especially for apps that you don't intend on using, is uninstalling the app (there's a whole thread talking about which ones are safe to remove).
Click to expand...
Click to collapse
yeah, that is a great idea. I imagine if I wanted it back I could just install it again. Thanks Codemonk.
Why do you need those apps not running? Android will kill them if it needs more memory.
Why are people obsessed with killing stuff? It's not like your phone runs better with 192mb of free memory vs 163mb...
it actually does, as well as lets the battery last longer since it isnt using as much processing power
Nagrom Nniuq said:
Why do you need those apps not running? Android will kill them if it needs more memory.
Why are people obsessed with killing stuff? It's not like your phone runs better with 192mb of free memory vs 163mb...
Click to expand...
Click to collapse
Let the phone run for a good 12 hours. I was down to 42MB free basically idling and only using Handcent. Killed a few tasks and back up to 175 and everything is snappy again.
I don't like having to use a task killer, I didn't have to with my N1.
maybe there will be an app like Scotty for windows 7. I check and a bunch of bloatware starts on it's own. It's all marketing bs. When there is a nice root stripped down, with all the nice stuff enabled I'll do that.
download startup auditor from the market. great little app to select and unselect which apps you want to load when the phone powers up. only costs $0.99 usd
pyr0path said:
download startup auditor from the market. great little app to select and unselect which apps you want to load when the phone powers up. only costs $0.99 usd
Click to expand...
Click to collapse
So if I leave it to no apps, will it load up with 0 apps running? Will it also prevent apps from randomly starting after phone is already on? Sounds like a nice app.
Unless startup auditor disables the service there is a list of apps that will randomly start up at times. I went into the application settings and apps like MP3 store don't have an option to uninstall.
I have used task killer to kill all apps and within minutes some start again.
"thecodemonk" why do you not use a task killer. I have only had an Android phone about 24 hours now and got a lot to learn.
First thing being how to enable tethering.
I have mine set to "safe" and it auto closes things when screen goes black.
Make sure you "IGNORE" certain apps... like the clock or else your alarm wont work... I almost over slept
I have the following set to ignore:
Messages
Handcent
clock
gmail
Mort Music player
Fastbright
Check out the application "Autokiller." This comes with preset values (optimum, moderate, aggressive, etc.) so that apps will be killed off once your free memory drops below a certain point. This app works great, but it does REQUIRE root to function and must be rebooted to finish applying the settings. Also lists all apps, processes, and services which can be killed off manually as well.
-------------------------------------
Sent via the XDA Tapatalk App on the HTC EVO 4G!
[email protected] said:
Check out the application "Autokiller." This comes with preset values (optimum, moderate, aggressive, etc.) so that apps will be killed off once your free memory drops below a certain point. This app works great, but it does REQUIRE root to function and must be rebooted to finish applying the settings. Also lists all apps, processes, and services which can be killed off manually as well.
-------------------------------------
Sent via the XDA Tapatalk App on the HTC EVO 4G!
Click to expand...
Click to collapse
I've been trying to find AutoKiller, yet I can't find it in the market. Is it here on the forums?
Fixter said:
I've been trying to find AutoKiller, yet I can't find it in the market. Is it here on the forums?
Click to expand...
Click to collapse
It is in market, search "autokiller". Requires root access, but I can confirm it is working fine.
Wanted to add that I am annoyed by programs that I never intend to use running in the background. From recovery I used Android Commander to quickly select and delete every .apk in /system/app that I never wanted to see again.
Helo guys saw this topic and was over at androidcentral and saw this article which talks about an app that would kill any app that autostarts.
won't let me post links as i'm a new user, but go to androidcentral and look for the article about the app autostarts or just google "autostarts"
using task panel to kill the "junk" like amazon and mp3 store- also any program that doesnt attach itself to things like facebook or messages - i use skyfire so i have set that to autokill but leave the "internet" running..
i also use this to switch between apps running.. having to hit back back back or even going to home then program list then finding it is a long process.. for example ...
i get a handcent message - go into the threaded sms- type and im done - holding down the home screen doesnt pop all the programs up - therfor i set task panel up to stay on my status bar and hit it then go to the program i want.

Im Rooted!... Now my apps are always on?

So I rooted this sucker yesterday and have noticed that once I have rooted my apps are always opening on their own... What gives? When I say opening on their own, every time I open task killer their are a ton of apps that are opened that i never even touched. And after I kill them they start showing back up automatically. Also advanced task killer will not kill itself any more I have to manually close the program... anyone else experiencing this? Anyone know how to make it stop?
Stop using task killers would be a good start. You are actually slowing your phone down
Sent from my ADR6400L using Tapatalk
Yes sir, task killers are a joke. Android is the best task management you can have.
___
Sent from my HTC ThunderBolt 4G LTE VIA XDA Premium
Task killers are a bad idea. Let android deal with the memory management itself, there is no need for an app to do this. The apps you are seeing aren't really "apps," they are services, and they were designed to run in the background to deal with certain things. Ditch the task manger and don't worry about the running services unless something is misbehaving.
please listen to these 3...
K sweet thanks guys
Another task killer bites the dust... Sweet!
Our work here is done boys, we can go home now.
Lmao @^ lol
Android has always opened your apps in the background when it feels it wants to. Nothing to do with root, just the way android works.
RogerPodacter said:
Android has always opened your apps in the background when it feels it wants to. Nothing to do with root, just the way android works.
Click to expand...
Click to collapse
Not when it wants to lol, when an app starts a background service. If you want to disable auto run apps on startup check out autostarts. A root app which can stop apps from opening on their own at boot. Some things you don't need to run on boot, if it doesn't have push notifications and it's not something you use regularly no need for it to open and you can disable it to speed up boot.
mjones1052 said:
Not when it wants to lol, when an app starts a background service. If you want to disable auto run apps on startup check out autostarts. A root app which can stop apps from opening on their own at boot. Some things you don't need to run on boot, if it doesn't have push notifications and it's not something you use regularly no need for it to open and you can disable it to speed up boot.
Click to expand...
Click to collapse
no actually android loads up groups of apps at one time, when it thinks it might be needed by the user. open system panel and go thru and check, i have 5-7 apps, all started at say 5:07pm, and were never opened by me. but they are cached in the background. its been this way for a long time.
Stop using a task killer, android... oh wait...

really close facebook

I noticed that Facebook remains in memory even after you close it or not it ever opened.
There is a patch to close it completely or do not open automatically?
MarkAndroid said:
I noticed that Facebook remains in memory even after you close it or not it ever opened.
There is a patch to close it completely or do not open automatically?
Click to expand...
Click to collapse
It's not only the Facebook app, many apps do the same. They start up at boot or other actions. They either remain running (as a service or otherwise) too keep you up to date (notification).
Other than uninstalling, you can use a tool like System Tuner. I think you need root for this. In its task manager, select a process, then scroll the list on the right side down to Receivers. Uncheck the triggers you want to disable. This can potentially render your app unusable, so be careful what you disable.
An alternative, if you do not use the app, but still keep it or cannot install it (useful for apps that came with your ROM) is to freeze them.
MarkAndroid said:
I noticed that Facebook remains in memory even after you close it or not it ever opened.
There is a patch to close it completely or do not open automatically?
Click to expand...
Click to collapse
This might be kind of a hassle.
If you tap on the recent apps list.
Long tap the Facebook app it will give 2 options.
1 is remove from list
2 is app info
Tap app info
Then force close
Some say swiping from the recent apps list closes the service.
I don't believe it does.
At least this may be a way to shut Fbook down.
There's a lot of info about closing down applications on the Google Android developer blogs.
xcal321 said:
It's not only the Facebook app, many apps do the same. They start up at boot or other actions. They either remain running (as a service or otherwise) too keep you up to date (notification).
Other than uninstalling, you can use a tool like System Tuner. I think you need root for this. In its task manager, select a process, then scroll the list on the right side down to Receivers. Uncheck the triggers you want to disable. This can potentially render your app unusable, so be careful what you disable.
An alternative, if you do not use the app, but still keep it or cannot install it (useful for apps that came with your ROM) is to freeze them.
Click to expand...
Click to collapse
Thanks for the reply. My TF700 is root!
The application I would not freeze it because sometimes I use it.
Try system tuner

Issue with apps not running in background - looking for advice

Hi All,
So it appears that after installing 4.4.2 I cannot seem to get Google Play Music or Pandora to run without leaving the app open and in the foreground. I'm not sure if there is a function that has to be enabled to do this in KK, or if it is some mod I did long ago to force kill apps that are in background.
I understand this is a bit of a goose chase, but I was hoping people would be able to suggest things to check to see whether we can fix this problem of mine together or not.
- Could it be something in an Xposed Module? XBlast, GravityBox, etc. have a setting for killing background processes?
- Could it be something in the KitKat system itself that has to be enabled / disabled?
- Could it be the new settings within the apps themselves?
- Could it be a third party app (that I may have installed and am unaware of) killing background processes?
- Other ideas?
Apps run when phone screen is off, and when phone is locked, but if I go into a different app the music stops cold.
Thanks in advance for any thoughts!
Ah yes, this is the curse of Android 4.3+. I read in the Greenify settings that in 4.3 or greater, Android killed off an exploit that allowed apps to increase their priority to stay in memory. In turn, running apps can be killed off when memory is low. Horrible. I've had it across all ROMs and stock as well. I've done as much research as humanly possible to subvert this.
I'm by no means an expert on Android. I have really limited knowledge of how it runs. But I think that information in accurate, because my own personal solutions seem to support it.
Generally what I have done is keep as few running processes as possible. This means no live wallpaper, Greenifying as much as I can, and clearing out any recents frequently. If this fails, I have to restart and things get back on track again.
Go into your developer settings and look at the process stats. If it says memory is critical, you'll need to start trimming down your background processes. I don't quite exactly know how to interpret all the data that is present there, but "critical" seems clear cut at least.
If anyone has more information on this, please add to the convo!
Thanks bud. On the plus side at least I know it's nothing I've done to a setting here or there (other than going ahead and installing KK on the phone, lol).
Why Google/Motorola would make simple things like this worse as updates come out is beyond me... le sigh.
A "simple phone upgrade" to something unlockable with 2+ GB RAM is my best option I guess, lol.
Agreed. Luckily 2 GB is the baseline nowadays, but I feel like I don't want to take the chance and just go for 3 next time.
While we're still on the subject though, which xposed modules do you use? I wonder if they do contribute to RAM usage.
jldr said:
Agreed. Luckily 2 GB is the baseline nowadays, but I feel like I don't want to take the chance and just go for 3 next time.
While we're still on the subject though, which xposed modules do you use? I wonder if they do contribute to RAM usage.
Click to expand...
Click to collapse
Xposed list is pretty lengthy, I'm sure something here is using RAM. And I totally agree with you - baseline 3GB (or more) in my next phone, with a quad or even octo-core processor.
Ah, the days of 1GB and dual-core being top of the line, lol.
Here's the Xposed list:
- AcDisplay
- All Notifications Expanded
- App Settings
- Chrome New Tab
- Disable Location Consent
- GPS Notification
- Google Play Music Listen Later (Just installed recently, haven't set up yet to test it out)
- Google Search API
- Gravity Box
- Handle External Storage
- Hide Apps Xposed (did not work on 4.1.2 since I wasn't running GEL, haven't tested after KK install)
- MinMinGuard
- MinMinLock (Just installed, haven't set up yet, might delete)
- Multi Users
- Notification Mod
- OK Google For 3rd Party Launchers (Just installed, haven't really played with yet)
- Pandora Patcher
- Stop Switch Delay
- Swiftkey Goodness On More Fields
- Swipeback
- Ultimate Dynamic Navbar
- UnToaster Xposed (version 1.1.7 - I couldn't get TiBu to work correctly with the newer versions through 1.2.5)
- Unbeloved Hosts
- XBlast Tools
- Xposed Preference Injector
- Xposed Torch (couldn't get to function correctly after KK installation)
- YouTube Ad Away
- YouTube Allow Fullscreen HDMI
I've noticed that Gravity Box and XBlast do a lot of the same things, I'm thinking I can whittle one down as long as I can find all of my settings within the other.
Using NotiSysInfo to monitor I noticed my RAM usage typically bounces between 85-125 MB free, depending on what is going on in the phone. This is double from what it used to be on 4.1.2 (typically I'd be running with about 40-50 MB RAM free). Knowing this, I'm not so sure the phone is killing the music apps based on RAM usage alone, unless the threshold for free RAM needed has been raised...
...if that is the case, any idea of a good app to lower the threshold for free RAM before the phone starts killing things? I was looking at Auto Memory Manager, but it didn't seem to do the trick keeping music alive in the background.
Sounds like a good idea for another Xposed Module, lol. Do you happen to know the thread for posting up ideas or requests?
LifeAsADroid said:
Sounds like a good idea for another Xposed Module, lol. Do you happen to know the thread for posting up ideas or requests?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/modules/index-collection-xposed-modules-post-t2327541
I think AMM worked for me for a while, but wasn't perfect. Nothing really ever did the trick like a restart... which makes me think that there is a memory leak somewhere, but I could never track it with any app I used. Maybe it is something to do with xposed? I never tested my phone long enough without it.
I haven't had it in a while, and I've done two things since it kept happening consistently the last time: 1) switch from SwiftKey to Google Keyboard. 2) Deactivate Muzei, best wallpaper app ever (RIP). Both apps seemed to consume variably large amounts of RAM.
Another thing I should note is that when frantically googling memory leaks, someone wrote on XDA that Android can only handle so many services running at once, so that when the number is exceeded, it automatically kills one. Possibly, this is the issue with the music.
coolloser said:
http://forum.xda-developers.com/xposed/modules/index-collection-xposed-modules-post-t2327541
Click to expand...
Click to collapse
Thanks a lot, found the thread right after I posted, lol.
jldr said:
I think AMM worked for me for a while, but wasn't perfect. Nothing really ever did the trick like a restart... which makes me think that there is a memory leak somewhere, but I could never track it with any app I used. Maybe it is something to do with xposed? I never tested my phone long enough without it.
I haven't had it in a while, and I've done two things since it kept happening consistently the last time: 1) switch from SwiftKey to Google Keyboard. 2) Deactivate Muzei, best wallpaper app ever (RIP). Both apps seemed to consume variably large amounts of RAM.
Another thing I should note is that when frantically googling memory leaks, someone wrote on XDA that Android can only handle so many services running at once, so that when the number is exceeded, it automatically kills one. Possibly, this is the issue with the music.
Click to expand...
Click to collapse
I found a solution in the "ask Xposed questions" thread listed above. Use the module App Settings and for the apps to stay running in background checkmark "resident". Works perfectly for me now.
I agree AMM is junk. KeepRunning doesn't work that well either. Xposed all the way!
I wonder if this is the same issue I'm having with Hangouts and SMS notifications. It seems that if I have enough going on in the background, Hangouts will stop giving me notifications for SMS. When I go into the app, the new message(s) is there and waiting for me to read it. This to me is a huge problem. I didn't have this issue on CM11. For me, it seems it most always happens if I'm using the Facebook app and viewing a link from Facebook on Chrome. I've now made a habit of checking Hangouts periodically to see if I have any new messages.
cmajpwc said:
I wonder if this is the same issue I'm having with Hangouts and SMS notifications. It seems that if I have enough going on in the background, Hangouts will stop giving me notifications for SMS. When I go into the app, the new message(s) is there and waiting for me to read it. This to me is a huge problem. I didn't have this issue on CM11. For me, it seems it most always happens if I'm using the Facebook app and viewing a link from Facebook on Chrome. I've now made a habit of checking Hangouts periodically to see if I have any new messages.
Click to expand...
Click to collapse
I would try clearing your data for Hangouts. Sometimes notifications won't come in if they are associated with an older android device ID.
I have had nothing but problems with hangouts and the messaging app. I deleted both and am using a third party messing app now. No problems.
Sent from my DROID RAZR HD using xda app-developers app

Alternative SMS apps stop working, only native SMS app stay alive, why?

Hello,
I don't have any problems to receive SMS with the native application.
With other apps (QKSMS, Chomp, etc), it works for a moment, but after the night for example the SMS do not arrive anymore.
If I launch the app, it works for a few hours, but the previously sent SMS are definitely lost.
It's like if the system kills the SMS service as long as it's not the native one. But I thought this was Android to manage SMS reception, not the apps... I find nothing on the Web. Do you have any idea of a solution?
(I don't think it's specific but this happens on my tablet Lenovo Tab4 with Android 7.1 rooted.)
Try removing the SMS app you are using from battery optimization. Settings -> battery -> 3-dot menu (I think that's the location on 7).
Thanks, but already tried. I guess these apps are not designed to stay in memory, just receveid a notification from the system.
I don't understand why it seems that I'm the only one with this problem!
Open the problem app, then go home. Open the recents menu, does the app have a padlock icon? If so, lock it. That should prevent the OS from killing the app.
It seems to work. But I still may can close the app by inadvertence, this is not a real solution. Why am I the only one who must do this? :'(
Thanks for your time, I think it's that or using the default app, no other choice.
Daxorp said:
It seems to work. But I still may can close the app by inadvertence, this is not a real solution. Why am I the only one who must do this? :'(
Thanks for your time, I think it's that or using the default app, no other choice.
Click to expand...
Click to collapse
It's all about battery life. The aggressive methods of killing apps varies from manufacturer and device. Huawei, Samsung, OnePlus and Xiaomi are extremely aggressive at killing off apps. Android 9/10 is more aggressive than 7.
OK, it may be Lenovo the guilty.
I write too fast. It does not work also by locking the app in the recents menu.
So I'm forced to use native application.
Thanks again
PS: I will try by putting a widget of QKSMS, it seems to help...

Categories

Resources