Is there a way to prevent android from closing my apps so efficiently? Having my browser closed in the middle of a long forum post because of an incoming call is very annoying. Or trying to switch to the browser for instructions on how to configure an app, and then switching back to find the app has closed and I have to start over...
I have danger SPL, JACxROM, ext3, compcache with backing swap, etc... 85mb free on the phone. There's no reason to be closing things so quickly.
I never seem to have that problem with 92MB linux swap. Rebooting your phone once and a while does wonders to the speed also.
Hi,
It appears that any time I reboot the phone, it starts with all applications loaded.
Unless I go to Advanced Task Killer and kill all, my phone is very slow. Also free memory jumps from about 90M to 150M after the kill.
Does anyone know ho to stop that from happening? Is there some kind of startup list that can be edited?
I am using rooted UCJH7 but no other tweaks and fixes.
Thanks
You could have just searched the market for 'startup'.
There are quite a few startup editor apps in the market, I haven't tried any, but most of the reviews seem pretty hit or miss. Just search "startup" in the market.
Well android handles memory management really well. Those apps load up and take a very small amount of memory and when you open the app it will increase the memory usage and when you close it it will run in the background again and take up very little memory. The fact the apps are open in the background shouldn't slow down your phone. The fact you have 90mb free is good. This isn't windows mobile where the more free memory you have the faster your phone is. There are apps u can use to see if your apps are running in the background or foreground when your not using them. If they are running in the foreground and taking up alot of memory then there's a problem. Hope i explained the memory management well enough.
And btw for future reference, read the stickies. You posted this in development. Should be posted in Q and A
jasonyump said:
Well android handles memory management really well. Those apps load up and take a very small amount of memory
Click to expand...
Click to collapse
The fact remains, free memory almost doubles after I kill them.
>The fact the apps are open in the background shouldn't slow down your phone.
The fact is that they do slow down the phone a lot.
The problem is that it seems that all applications get fired indiscriminately. And the question is if someone with some knowledge of Android internals can shed some light on that.
I will post specific numbers on memory after I reboot it next time.
alexnoalex said:
Hi,
It appears that any time I reboot the phone, it starts with all applications loaded.
Unless I go to Advanced Task Killer and kill all, my phone is very slow. Also free memory jumps from about 90M to 150M after the kill.
Does anyone know ho to stop that from happening? Is there some kind of startup list that can be edited?
I am using rooted UCJH7 but no other tweaks and fixes.
Thanks
Click to expand...
Click to collapse
i too thought so initially. but when i started observing, i observed that the apps that load up at start up are generally the apps that i frequently used.
Good day!
Im new to xda-developers forum, just found a link in youtube while watching some stuff about galaxy note.
I have not discovered my galaxy note thoroughly yet coz its still new to me. Just wondering, the usage of memory without running any apps will go about 60%-70% percent. My temporary solution for this is to run task application and kill all exciting apps. Just wanna ask what kind of problem this may be?
No need to get alarmed by that. That's the way Android runs: it keeps apps in cache, so you can access them faster. When there's too much of them cached, the system kills off some apps.
chasmodo said:
No need to get alarmed by that. That's the way Android runs: it keeps apps in cache, so you can access them faster. When there's too much of them cached, the system kills off some apps.
Click to expand...
Click to collapse
thank you for your reply.
in this case, i cannot access on other apps that i'll run. just manually kill all the apps every-now-and-then.
Just remember: free memory is wasted memory. This is true for almost every piece of computing machinery out there.
inkanyamba said:
Just remember: free memory is wasted memory. This is true for almost every piece of computing machinery out there.
Click to expand...
Click to collapse
Thank you.
the only thing is, when i access on other apps like games. loading on the apps takes longer or even it crashes. maybe its because of the memory allocation of the apps or just there is no enough memory space to allocate the app.
JoshuaTumanda said:
Thank you.
the only thing is, when i access on other apps like games. loading on the apps takes longer or even it crashes. maybe its because of the memory allocation of the apps or just there is no enough memory space to allocate the app.
Click to expand...
Click to collapse
While what the other member said is true, unused memory is wasted memory, but the issue is exactly that. Android ends apps that you may be running to be able to open more apps, which I find bad.
While it is normal to find the amount of ram you have said already loaded and being used, I still don't like it.
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
But still, I hope ICS fixes this issue. I don't need 200 of the 1 gig of ram in use, what I would like is to have 300 or so free to be able to multitask normally.
zkyevolved said:
While what the other member said is true, unused memory is wasted memory, but the issue is exactly that. Android ends apps that you may be running to be able to open more apps, which I find bad.
While it is normal to find the amount of ram you have said already loaded and being used, I still don't like it.
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
But still, I hope ICS fixes this issue. I don't need 200 of the 1 gig of ram in use, what I would like is to have 300 or so free to be able to multitask normally.
Click to expand...
Click to collapse
Thats exactly my point. Thank you!
zkyevolved said:
There are times that I'm trying to multitask and I open an app and right away jump back into the previous app to find that Android OS has decided to close it, within 3 seconds of hitting the home button. It makes multitasking a little harder. But there are ways around this .
Click to expand...
Click to collapse
can you please elaborate on the workarounds so that Android doesn't kill the background apps especially opera mobile
So I grabbed the new marshmallow OTA for my s6 active and I noticed that almost every application is forced closed if I have more than one app running. So music playing in background gets closed. Even the background app to talk to my Gear S2 gets closed.
Anyone else see the same problem? I guess the next step is to try a factory reset. But I really don't want to go down that road.
Nevermind. Looks like Dolphin has a memory leak. Memory usage spikes to almost 1GB when loading a page.
Is there a way to stop background apps from closing when navigating away from them?
If flicking between a few apps they are going back to the starting screen so are being closed when navigating away. I have searched Google and it looks like a bug Nokia are aware of but is there a workaround to stop this behaviour?
I tried switching on Background activity cleaner and setting just one app to be blacklisted as per a thread I found but this does not work and still all background apps are being closed
With 6GB of RAM you would have thought there could be plenty of apps left to run in the background without too much performance issues