Related
Any one else notice their Hero slowing down?
Mine's gotten to the point where it takes a few attempts at even unlocking the home screen....
Yeah, started to put some apps on the phone the first night I had it ( Friday) and when I started 'Sky map' to see what it was like the poor old phone had a major moment and wouldn't do much at all.
I had read up on this so installed taskiller and just killed the app -it was fine after that-
I believe it will be sorted soon, there is a firmware update just about to be released (hopefully) that addresses this issue.
I bought TasKiller Pro, since it lets you have unlimited amounts of Ignored apps. Then I just:
* Go into TasKiller and Ignore TouchFlo, Touch Input, com.htc.dcs (whatever that is, it's always on) and all other apps you don't want to kill when you clean up (Babbler, ConnectBot etc... whatever you fancy)
* Put the TasKiller widget on the desktop next to the TasKiller app icon.
* Whenever I notice a slowdown I just press the widget button and it kills all processes / programs except the ones I've ignored. It immediately speeds up the phone
This isn't an iPhone, this actually lets you start multiple programs at the same time and since the cpu isn't event capable of playing smooth MP4 videos (unless they are 480x360), there isn't a lot to spare.
When I woke up this morning, i made a ConnectBot connection to screen to open irc, surfed a couple of webpages, wrote a couple of mails, started babbler for facebook and eBuddy for MSN and the slowdown on the desktop was visible. When I was done I clicked the TasKiller "Kill all" button and the phone was smooth as butter again.
The moral of the story: If you start a lot of programs at the same time, it WILL slow down the phone. Nothing you can do about it. The iPhone "never" slows down, because it's the equivalent (almost) of a Hero with only one app running at any one time. Given those conditions, the Hero would be just as smooth as the iPhone too!
Still, I hope sincerely for some optimization with the forthcoming update.
You need to look into how the Android OS works.
there are two types of running apps.
Applications and services.
With applications, when you press the home button the application is suspended and can no longer use memory or cpu, Android can reclaim this memory when it needs to.
Second is services, these run in the background. These do use cpu and memory while you are doing other things. So if you have a lot of apps that uses services running then it may slow down.
I have found that usually the slowdown is because when you click home and then suspend the widgets that update are suspended and so when you unsuspend they wake up and start to refresh and that causes the slow down. Tip #1 when clicking home to put the phone into standby dont click standby for about 5 secs and see if it helps.
hi i have only just got the hero and was wondering how to close apps properly. i have noticed that when you hold the home key for a while a window pops up showing some apps ...is this how you close them? or is simply pressing the home key shutting them .
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
foxmeister said:
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
Click to expand...
Click to collapse
Most Task Killers free up memory thats used by background apps.
so basicly back out of the app and let android do the rest of the worring. thanks for advise
risterdid said:
Most Task Killers free up memory thats used by background apps.
Click to expand...
Click to collapse
Yes, but the point is that Android itself will start killing applications if it starts to run low on resources. (see http://developer.android.com/guide/topics/fundamentals.html)
Regards,
Dave
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
MercuryStar said:
Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Click to expand...
Click to collapse
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
kendong2 said:
you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
kendong2 said:
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I do notice this too. There is a general 'sluggishness' with my Hero when there are lots of app sleeping/running/hibernating/whatever in the background. As soon as I kill off a few unwanted ones, all the menus scroll faster and home screens change quicker.
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Micksta said:
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Click to expand...
Click to collapse
exactly, you can tell easily if it is one motion or looks like it is "skipping frames". even it is only because it takes the device some cpu cycles to kill other apps, it does make a difference. like i said a rather cosmetic one, since it doesn't really effect the general usage. nevertheless i like to know what is running and what's not, and so far im running good with advanced task manager free.
WOW i didnt expect a massive response for my question but i thank you all for your responses
MercuryStar said:
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
Click to expand...
Click to collapse
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
Just as a matter of interest, do you use swapper or AppsToSD?
My phone never gets into the situation you've described, but even though I do have the full version of TasKiller, I almost never use it, and I don't see a need at present to use AppsToSD.
In addition, I'd imagine that having a swap partition would cause an issue with Androids own memory management, since I guess it can't distinguish between real and "virtual" memory. So where a "non-swap" device would start killing processes, a "swap" device would just continue on regardless because it thinks it still has physical memory available.
Regards,
Dave
Yesterday I downloaded "Advanced Task Killer Free"... anyone who has experiences with this? Is is better than just "Task Killer" or is it just an updated version of "Task Killer" ?
thanks!
have been using atk free for a while (lol 2 weeks since i got the hero) now, i really like it. its advantage over all other task managers IMHO: it has an ignore list, things you ignore are not shown in the running tasks list. in the list you have check boxes, where you can select the tasks that will be killed, and this list is remembered. for example "htc sense" is on my ignore list, but "music" is only checked, so i can uncheck it when i don't want to kill it while listening to music. next time i want to kill music i just have to tap the checkbox, no dealing with the ignore list here...
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Sausageman said:
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Click to expand...
Click to collapse
Same for me with the processor.
When i reboot my phone i usually have 90 mb of free ram, after starting a few applications, like browser and phonebook, it plummets down to 20 mb.
I do have some extra applications that starts as services, like systray monitor and 3g watchdog.
when i open atk after a fresh reboot i see that some applications that i don't even use is started, like footprints, settings and calendar, even my webrowser is started, whats up with that, can it be disabled?
I think the issue is that we have some applications that autostart withous us using them, and also programs that we download that autostarts as services and maybe having memory leaks...
I came to chime in with my experiences of the CDMA hero and sluggishness.
I watch memory like a hawk (thanks Mogul) and I too have around 80-90mb free ram on start, but it can get down to around 30 rather quickly. Once it gets down here, I notice that screen transitions and random lag occurs in apps. If I go into Advanced Task Killer and kill many of the stragglers, my menus are as smooth as can be.
It is most certainly NOT a placebo effect.
One thing I really like about Advanced Task Killer (pay version) is that it has the "Auto End" feature, where it will kill all apps not chosen to be excluded at the interval that you choose. For example, I have determined the system applications that need to be on all the time, and I've excluded those. Every hour, ATK kills everything else. For the most part, my Hero hovers around 70MB now at all times, although it can get down there to around 30-40MB if I'm right around the 1 hour mark.
That feature alone makes it much better than Taskiller IMO. Totally worth 99 cents
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
MercuryStar said:
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
Click to expand...
Click to collapse
Shahpur.Azizpour said:
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
Click to expand...
Click to collapse
No, you've not understood the explanation.
The iPhone will always* terminate an application that isn't on its list of "approved" multi-tasking apps once it isn't active any more (i.e. you've switched tasks).
Android will try to keep whatever it can in memory, but eventually will start killing processes in order to keep the system running.
So, if you're on an iPhone listening to something on Spotify and you want to browse something on the web, the iPhone will "kill" Spotify when you switch to the web browser. On Android this won't occur except in the most critical of resource low situations, but then again, I'd imagine other apps would get killed before Spotify.
Read this article, specifically the section from "Component Lifecycles" onwards specifically "Activity Lifecycle", "Saving activity state" and "Processes and lifecycles".
Regards,
Dave
* Unless it has been jailbroken!
I am new to Android - just got a Droid 3.
How do I stop the system from auto-killing a certain app? When I play Angry Birds, if the phone goes to sleep on timeout, when I turn it back on, the App has to re-load from scratch (rather than opening to where I left off last time). I'm assuming the system decided to kill it for lack of memory, but how do I STOP it from doing that (like an ignore list)?
Will I need a third party app?
Any help is appreciated!
not really. the Android system does a pretty good job of reclaiming unused memory. ive been dealing with this for a while trying to keep a replacement lock screen in memory
Sounds like Verizon installed a task killer. I know their employees do that saying you need one. But you don't. Make sure you uninstall it. It is most likely set to kill apps off ever x minutes. Usually Android keeps foreground apps in memory for a long time unless the system needs it. But doesn't sound like it would. I wonder what the Droid 3 memory settings are for stock now. I have the Evo 3D and they are set at a higher threshold(as I'm kills unused apps sooner) compared to my older HTC phones(Evo and Hero). How long do you let the phone sit idle before coming back?
Sent from my iPhone with the bigger GeeBees.
notasimpleway said:
Sounds like Verizon installed a task killer. I know their employees do that saying you need one. But you don't. Make sure you uninstall it. It is most likely set to kill apps off ever x minutes. Usually Android keeps foreground apps in memory for a long time unless the system needs it. But doesn't sound like it would. I wonder what the Droid 3 memory settings are for stock now. I have the Evo 3D and they are set at a higher threshold(as I'm kills unused apps sooner) compared to my older HTC phones(Evo and Hero). How long do you let the phone sit idle before coming back?
Sent from my iPhone with the bigger GeeBees.
Click to expand...
Click to collapse
It's not obvious which program that would be - there's nothing called Task Killer. Plus, most of the VZW bloatware can't be uninstalled anyway. Apart from rooting (locked bootloader on Droid 3), what can I do to force it to stay open?
Also, it gets killed immediately on turning off the phone. As in, I start the game, hit sleep, hit wake a second later and the game reloads from scratch. Very irritating.
Any thoughts are appreciated, thanks!
jbroses said:
It's not obvious which program that would be - there's nothing called Task Killer. Plus, most of the VZW bloatware can't be uninstalled anyway. Apart from rooting (locked bootloader on Droid 3), what can I do to force it to stay open?
Also, it gets killed immediately on turning off the phone. As in, I start the game, hit sleep, hit wake a second later and the game reloads from scratch. Very irritating.
Any thoughts are appreciated, thanks!
Click to expand...
Click to collapse
I just tested this with Angry Birds from the time I posted till just now and it was right where I left the game. It may be called Advanced Task Manager. Or something like that. And you should be able to uninstall it. It would have been installed by the person selling the phone and not at the factory.
Sent from my iPhone with the bigger GeeBees.
Go to the Market, download Spare Parts. Open and scroll down to Activity/Process Management. Select normal. It may not have been the problem, but worth a shot. Are you hitting the home button before putting the phone to sleep? What do you see immediately upon turning the screen on and unlocking the phone? Angry Birds? The home screen?
Sent from my iPhone with the bigger GeeBees.
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
By default, every application runs in its own Linux process. Android starts the process when any of the application’s code needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
[...]
If the user leaves a task for a long time, the system clears the task of all activities except the root activity. When the user returns to the task again, it’s as the user left it, except that only the initial activity is present. The idea is that, after a time, users will likely have abandoned what they were doing before and are returning to the task to begin something new
Click to expand...
Click to collapse
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Shinigami20 said:
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Click to expand...
Click to collapse
it actually happens instantly. in other words - open angry birds, begin level. sleep phone, wake phone. angry birds reloads from the beginning. this is all within the span of 5 secs.
i thought it might be my lock screen - widgetlock, but i disabled that and it just happened again, this time with opera mini as i was writing this. I was writing this post, went to a text, came back to opera within 30 secs and it had shut down and reopened (no tab with my partially composed message).
is the droid 3 just shutting things down more aggressively? is there a way to tweak that? maybe too much other crap is running and I should get a task killer? thoughts?
jbroses said:
it actually happens instantly. in other words - open angry birds, begin level. sleep phone, wake phone. angry birds reloads from the beginning. this is all within the span of 5 secs.
i thought it might be my lock screen - widgetlock, but i disabled that and it just happened again, this time with opera mini as i was writing this. I was writing this post, went to a text, came back to opera within 30 secs and it had shut down and reopened (no tab with my partially composed message).
is the droid 3 just shutting things down more aggressively? is there a way to tweak that? maybe too much other crap is running and I should get a task killer? thoughts?
Click to expand...
Click to collapse
do not sleep your device, try entering level then return to home switch to other apps. Then open angry bird again and see what happen
On my desire Z, it kill the app every time i sleep the phone. Keep the phone alive then I have 3 apps running at same time without being killed. But it's not likely that I have RAM shortage. 3 apps is constant no matter what apps
Flipz explains that well. Autokiller is a great little app to adjust those settings. Used it for over two years now. I actually got to watch that app evolve. Great dev. Only works if you are rooted.
Shinigami20 said:
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Click to expand...
Click to collapse
Sent from my iPhone with the bigger GeeBees.
Thanks for all the responses. I've tried to address them all:
Spare Parts - I installed this and set the Activity to Normal (it WAS set on aggressive). Unfortunately, this didn't help.
Press the Home key - Pressing the Home key and then going back to Angry Birds DOES work. It picks up right where you left off. Unfortunately, when the phone goes to sleep, it restarts Angry Birds on waking.
What do I see when I wake the phone - It goes to my WidgetLocker lock screen. Once unlocked, the very first thing that shows up is the Angry Birds "Rovio" loading screen. No home screen in between.
Any other thoughts are much appreciated! Is there any way to simply exempt Angry Birds from being closed by the system automatically? It seems like this should be possible!
Can you try something out for me? I want to give evidence to my theory.
Download another 3d game, load a level, then sleep the device. See if there's a lot of stuttering/reloading when you wake the device back up.
Any news on this? I got the same problem with CM 9.1 on my Doubleshot (aka M4GS). When I have like 10 tabs or so opened in Opera, Android kills the task. But not when I put it into sleep, but right when I'm browsing! That's really annoying since after restarting Opera I have to reopen every single tab manually from the history.
Already tried Spare Parts, but it doesn't offer some kinda whitelist for apps that shouldn't be autokilled.
It's really frustrating, Android's autokilling feature was one of the few things, that I didn't like about that OS when I switched from Windows Mobile to Android a few years ago. And I still hate that feature. Why can't I decide by myself which apps to be closed and which ones not? Give back the power to the user I say!
At least there HAS to be a solution to force Anddroid, not to kill a specified app (e.g. Opera) and kill all the other running apps instead. Any 3rd Party task killer has some kinda ignore list, so how could Android be tweaked to do the same?
Shani Ace said:
Any news on this? I got the same problem with CM 9.1 on my Doubleshot (aka M4GS). When I have like 10 tabs or so opened in Opera, Android kills the task. But not when I put it into sleep, but right when I'm browsing! That's really annoying since after restarting Opera I have to reopen every single tab manually from the history.
Already tried Spare Parts, but it doesn't offer some kinda whitelist for apps that shouldn't be autokilled.
It's really frustrating, Android's autokilling feature was one of the few things, that I didn't like about that OS when I switched from Windows Mobile to Android a few years ago. And I still hate that feature. Why can't I decide by myself which apps to be closed and which ones not? Give back the power to the user I say!
At least there HAS to be a solution to force Anddroid, not to kill a specified app (e.g. Opera) and kill all the other running apps instead. Any 3rd Party task killer has some kinda ignore list, so how could Android be tweaked to do the same?
Click to expand...
Click to collapse
I agree. I was downloading a file in Opera, switched to other apps, then went back to opera and it reopened.. Needless to say the download failed. This really sucks.
Use titanium and freeze the stock task manager (if any).
Android, by default, keeps only 3 (correct me if I'm wrong) applications' sessions in memory, but that's obviously no reason for it to kill angry birds right after the display is closed.
Try installing Minfree (I think it's available on the Play Store) to understand when and why Android is killing the application. It'll give you the parameters on which the Android Auto killer operates, but you will need ROOT to be able to edit them.
And no, there isn't a way to earmark an application such that it isn't killed, at least, not that I know of.
Hope this helps.
Haters gonna hate
potatoes gonna potate.
Check out v6 supercharger and all ur questions will be answered.
http://forum.xda-developers.com/showthread.php?t=991276
sent from my DNA
jbroses said:
I am new to Android - just got a Droid 3.
How do I stop the system from auto-killing a certain app? When I play Angry Birds, if the phone goes to sleep on timeout, when I turn it back on, the App has to re-load from scratch (rather than opening to where I left off last time). I'm assuming the system decided to kill it for lack of memory, but how do I STOP it from doing that (like an ignore list)?
Will I need a third party app?
Any help is appreciated!
Click to expand...
Click to collapse
Hi, excuse me for not reading other posts and replying directly but wanted to share something that works for me and does not kill certain launched apps. Open any app, then come out of the app and tap on recent apps button and you will see the apps that are currently launched. Depending on your OS and model, are you able to lock an app (by slightly dragging the app icon down and then tapping on the lock icon). I did that for one of the games and surprisingly even after several minutes, I was able to continue from exactly where I left off. Hope this helps. Let me know.
Screenshot: http://1.bp.blogspot.com/-9Bs7dxj7t3o/VZHLFAF6fdI/AAAAAAABI0Q/WXFhUv1c2gw/s1600/IMG_0023.JPG
Hi Everyone,
Basically, I got my Samsung Galaxy Player 4.0 in January, and when it comes to the features, I have been loving it. This is my first Android device.
However, I have been having problems lately. First, some basic information: it's an 8gb device, and I have a 32gb class 10 microSD card in it. I have a huge number of apps on it (over 200), however, I keep careful tabs on what is running in the background, reporting an app if it runs in the background even when not needed and that will reopen if killed, and if I don't really need it, deleting it after a week. I've only had to do that with a couple of apps so far. As I use this a lot as a PDA (I don't have a phone, this basically covers those bases), I have a couple of things that always run in the background, which I want there (textplus, Linphone, MailDroid, SwipePad). After getting rid of the services that I don't need, I'm still looking at over 100MB free RAM. I'm still on the stock ROM, and I'm using GO launcher Ex. I reboot daily.
My problem is that it crashes often - sometimes daily. Usually, it will go something like this: An application freezes, the whole system becomes unresponsive, and I either have to reboot it by holding down the power button for 8 (?) seconds, or something snags and it reboots by itself. Usually the first sign is that the haptic feedback for the home button comes about a second later after I press it - except then it is almost always too late. The power button will usually turn the screen on or off, but the lockscreen won't appear, I'll see the screen as it was before, frozen. Sometimes, it eventually reboots, while sometimes it doesn't, making me hold down the power button to reboot it, and sometimes, just as it will start "becoming unfrozen" (it goes to the home screen and it starts loading), it will reboot.
It seems to be that after an approximate time of active use, it will crash. Before that, apps can freeze, FC, and within a few seconds, I'll be back on the home screen or in another app, doing something else. After that, on the other hand, it seems to me that whenever an app freezes or has a problem, it basically takes down the whole system with it.
Something tells me that this isn't just normal (otherwise Android wouldn't have over 50% of smart phone market share ), because I haven't heard of problems like this before, and other people with Android I know don't seem to be having the same problems (if any, at all). I have been reading around, and saw some thread about another phone describing similar problems, and it turns out it was a motherboard problem, so the phone was returned for warranty, except I don't remember where that was, I'm just hoping it's something like that...
OK, now that you've read my long post (sorry, I thought it would be best to give more details than get asked about them), I really hope this isn't something normal, because outside of this problem, I'm really enjoying all the possibilities, capabilities and flexibilities of Android (I'm looking at you, iPod). It's really quite aggravating, today I lost my public transit itinerary on Google Maps (I feature I love), and thankfully, I remembered enough to make it through, but it is quite frustrating. Please tell me this is not Android being Android?
Go Launcher is not Officially supported on these devices and swallows the small amount of ram very quickly, I tried it for a day and got rid of it because of how badly it impacted performance.
edit: looks like since I tried it they added support for our players, still won't run it, its to much of a system hog.
I don't know, but I tried switching to the default launcher, and it already crashed earlier than usual. Any other ideas? I'll try some other launchers over the next few days.
Sounds like you are running out of system resources. You say you have a couple hundred apps installed and I bet some of those are becoming active and hogging precious ram and cpu resources in the background until the system crashes. I have a 2 year old Samsung Captivate and I only have minimal amount of apps because it will often big down and become unresponsive and crash. So before you head out to a repair shop, remove some of your many apps and see if that helps.
So, if I understand, even if an app runs in the background for a short period of time, it still consumes resources, even after it's stopped running?
trainman261 said:
So, if I understand, even if an app runs in the background for a short period of time, it still consumes resources, even after it's stopped running?
Click to expand...
Click to collapse
If you have a titanium backup freeze apps that run in backround and see what happens ..when you open programs they will stay in memory so use some memory kill widget to clean memory from time to time.I have a stock rom witch is not very good with memory menagment so sometimes when memory is full it just stop and only help is restarting ..so i use app "quick system info" which give you memory ajd cpy usage displayed in status bar and when memory is close 2 full i just click on that and it kill all other aps except what a use in that moment.
Sent from my GT-I9000 using XDA
So, basically, the ROM is to blame? As to Titanium backup, I think that needs root, and I'm not quite ready to root yet (I've done enough hacking on my iPod). I do plan on upgrading to android 4.0 eventually (once all the issues get fixed, this is my main device, after all), and I think I'm going to have to root it at that point, but I'll be able to test it on a different ROM then, as well as try freezing apps. For now, I've tried LauncherPro, which seems a lot more lightweight, and it seems to be making it through the day until I reboot, and seems to be very stable... it also loads my widgets lightnight fast, which is great.
Correct me if I'm wrong, but the way I understand it is:
obviously there are memory leaks, every OS has that
Android will not kill services, but only programs
If there are places where memory can be freed, Android will do that when necessary
If no memory can be freed, and there is barely any memory left, than a minor FC or a frozen app is all it will need to push Android off the cliff
Is this the way it works? And, then, when I upgrade to 4.0 (CM9), most of those problems should be gone (because of better memory management)?
I use the tablet mostly for playing. And I am used to move between them without issues. Unless I open a bunch of other apps or browser with multiple tabs and what not. The games remain running without issues or at least they used to. Normally I don't update anything, except for the games because they are live service and I can't play them if I don't. After learning that this update would improved multitasking I updated.
Ever since I can't keep the games open if I leave them for like 20 minutes or maybe less, haven't time it.
Using it as I did, closed them. So I decide to clear all and only play one. After a notification, went to that game for daily tap immediately went back to the prev game and it had close, which cost me a match. After finishing what I was doing on that game. I went to the settings to see if something was amiss. And all the apps I remember disabling that I couldn't uninstall like Youtube are still disabled. I don't have any social media app like FB or anything that would be constantly running. And went back to the game. Lo and behold had to restart again. I checked Dev options and Apps "Background process limit" still standard. Memory is at 4~4.5 with so much free I don't get I it's been so aggressive. Have 66 apps on "deep sleeping" have things like digital well being and other monitoring stuff also off. And the only thing I changed was enabling the "Labs" to allow Multi window for all apps. And just now, went to homescreen while I picked something from the kitchen, I know I didn't take more than 5 min because the screen didn't even timed out. And when I tap on a game, had to relaunch.
God this is ridiculously annoying. And non of the games updated since. I only updated a couple of apps from store.
And worst, I updated believing it would be better at multitasking. Like it would be smarter when using split screen, but it isn't. Maybe it does improve for Samsung apps. But I've seen nothing good from anything I use. And changes to the UI could've been implemented better. Like having dual pane only when you are holding the tablet lanscape. I remember having very old android device that had dual pane but revert to single if you hold them portrait.
I'm considering doing a full reset. But I'm hoping not too. Between the apps and games, which most are 5GB+ up to nearly 10GB it would take me a very long time to set everything again, Easily a full day for some games. (Very bad old, first gen copper line DSL)
Is anyone have any type of similar issues. Cause it would suck if I reset it and that's just how it works now. And it wants me to use the "keep open" feature. Which I don't like, I do like to use the clear all.
One of the main reason I got this particular tablet was for the multitasking. This is the first device I didn't try rooting out of the bat because of a warranty and what not and decided to give it a go as is. Now I'm not sure If I'm just spoiled by years for rooted and heavily modified devices. Or this is just a Samsung thing.
@Omizuke: Not sure if this is related to RAM management, but I'm also on September update. When I update apps via Play Store/Galaxy Store, the device will completely freeze for as long as 30 seconds. It just locks up, I can't do anything. Can't pull down the status bar, nav buttons don't work. Then suddenly it returns to normal. I get the same thing when connecting to WiFi or pairing via Bluetooth. ROM is clean flashed with Odin, i also did a factory reset.
This didn't happen at all on the July update.
I'm not seeing any issues with app killing, as you've described it. All opened apps continue running and I can return to them on demand. I play a lot of games, COD Mobile in particular, and I switch apps a lot between rounds.
I feel you on the not wanting to set up everything again. I save cached copies (APKs/obbs) of my games/apps on my SD card, so I can set everything up without Internet. Just use an app like Total Commander/X-plore to copy the apps.